Approvals
One inbox for everything waiting on you, driven by approval rules, delegations, reminders and escalation, and maker-checker separation.
Approvals collects every document waiting for your decision: journal entries, AP bills, payment runs, held bank transfers, submitted budget versions, prepared FX revaluations and, for users who manage vendor banking, pending vendor bank and tax ID changes. Owners define the routing rules, delegations, reminders and escalation here. Open it from the company app launcher under Accounting > Approvals; it appears when your accounting access includes it.
- Who uses it
- Every approver. Accounting owners manage rules; anyone can delegate their own approvals.
- When
- Daily, and before payment runs and close.
- What it holds
- Open approval slots (yours and those you cover as a delegate), documents returned to you, approval rules and delegations.
Key workflow
- Define approval rules. A rule matches AP bills, payment runs or journal entries by amount band, entity, project or vendor risk (a new vendor, a compliance hold, recently changed bank details). Its ordered steps can name a user, a role such as controller, a project team role such as project manager, or any N of M approvers. The lowest-priority matching rule wins; with none, the configured amount bands apply.
- Work the inbox. The inbox lists each slot you can fill, including those you cover as a delegate. Documents without exceptions can be approved together.
- Reject with a reason. Rejecting returns the document to its preparer, spends the earlier approvals and shows the reason under Returned to you.
- Delegate while away. A delegation lets a colleague fill your slots for a date window, for chosen document types, up to a maximum amount and within chosen entities. The approval records both names.
- Remind and escalate. Turn on reminders and escalation, set your business days and holidays, and give each kind of item (AP bills, payment runs, journal entries, held bank transfers, vendor bank changes, submitted budgets and FX revaluations) a policy: a reminder every N business days, and up to three escalation levels every M business days to the next role up, the delegator, controllers, owners or a named user. Reminders go only to people who can approve the item now. For a routed document, escalation adds the target to the waiting step, so they can approve it; other kinds are notify-only. A daily job sends each reminder and escalation at most once, even when re-run.
- Work the overdue list. Overdue approvals lists items past their threshold, longest first, with who each waits on, its escalation level and its history. The same list is a dashboard widget.
Controls
- Maker-checker: under the default strict policy, nobody who prepared or edited a document can approve it, directly or as a delegate. A delegate needs the same approval right and entity scope.
- A document snapshots its route when submitted, so later rule changes do not alter it. Submission is refused when no eligible approver remains.
- An escalation target must hold the approval right, reach every entity on the item, rank at least as high as the step it waits on, and not have prepared, edited, submitted or already voted on it. Everyone left out, and why, is recorded. Escalation never bypasses the approve call’s own checks, and changing escalation settings needs step-up.
- Small-team mode permits configured self-approvals with a written reason. Each one is listed in the Self-approved report for close review.
Current boundaries
For the full procedure, exceptions and examples, read the Security and controls workflow guide.
API operations
15 operations · 8 read · 7 write · base path /rest/v1.0/companies/{company_id}/accounting
- GET
/approval_delegationsList approval delegations - POST
/approval_delegationsCreate an approval delegation - DELETE
/approval_delegations/{id}Revoke an approval delegation - GET
/approval_rulesList approval rules - POST
/approval_rulesCreate an approval rule - DELETE
/approval_rules/{id}Deactivate an approval rule - GET
/approvals/escalation/historyApproval escalation history of an item - GET
/approvals/escalation/policiesList approval escalation policies - POST
/approvals/escalation/policiesSave an approval escalation policy - POST
/approvals/escalation/runRun reminders and escalation now - GET
/approvals/escalation/settingsApproval escalation settings - PUT
/approvals/escalation/settingsSave approval escalation settings - GET
/approvals/inboxApprovals inbox - GET
/approvals/overdueOverdue approvals - GET
/approvals/self_approvedSelf-approved documents
Parameters, request and response fields, errors and a generated example for each operation are in the REST reference for this app. Read scopes, step-up and permissions in the Accounting API guide.
Keep exploring
Related across os.construction
- GlossarySegregation of dutiesSplitting key steps of a transaction, such as entering, approving, paying and reconciling, between different people so no one person can both commit and conceal an error or fraud.
- GlossaryAccounts payableMoney your company owes to subcontractors, suppliers and vendors for work, materials and services already billed.
- DocsJournal EntriesPrepare, approve, post and reverse journals, recurring entries and job cost allocations with maker-checker controls.
- DocsApproval workflowsDesign multi-step approvals for change orders, pay applications, purchasing, AP and more, then approve from My approvals on the web or your phone.
- BlogHow to close the month in construction accounting: a step list from cutoff to lockA construction month-end close gets every cost and every billing into the right month, proves cash and the subledgers against the ledger, updates the WIP schedule from current cost-to-complete, has someone else review it, and then locks the period. Here is the step list, an example close calendar and a worked example of what one late invoice does to WIP.
- BlogConnecting an AI assistant to your construction data: a permissions-first checklistAI assistants can now read and act on project records through connectors such as the Model Context Protocol. Before you connect one to RFIs, commitments or AP, decide whose credential it uses, what it can see, whether it can write, who approves, and how you'll know what it did.
Was this helpful?
Run it on your own project.
Start a 14-day free trial. Want a say in what ships next? Join the founding program.
14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →