USE CASE

Approval workflows

Approvals that follow your rules, reach the right person and leave a record of who decided what.

The problem

Approvals over chat are fast until something goes wrong. Then nobody can find who approved the purchase, whether the discount was signed off, or why a payment went out. Rigid approval tools fix that and create a new problem: everything waits for one person who is traveling.

How it runs in Sundial

1. Pick the document that needs approval: purchase orders, quotations with large discounts, supplier payments, journal entries or any other document type.

2. Define the workflow states, such as Draft, Pending approval, Approved and Rejected, and the transitions between them.

3. Assign each transition to a role, not a person, so approval moves with the job when people change. Add conditions, for example purchase orders above $25,000 route to the controller; below that, to the purchasing manager.

4. Sundial notifies the approver and shows the pending item in their workspace on desktop or phone. They approve or reject with a comment.

5. Only approved documents can be submitted. Every state change is recorded with who made it and when.

What the team sees

Approvers see one list of what is waiting for them. Requesters see where their document is and who has it. Finance and auditors see the history of every decision on the document itself.

Sample for Kestrel Workspace: 7 purchase orders pending approval, oldest 2 days, average approval time this month 5 hours.

With AI (coming to Sundial)

Sundial is designed so an agent can prepare the document, such as a purchase order drafted from a reorder alert, and stop at the approval step. The agent never approves its own work. This is roadmap framing; workflows today are run by people.

THE NEXT AGE OF ERP

Run the whole business
in one calm system.

Try the demoTalk to us