One approval engine for all 16 modules: purchasing, payments, invoices, payroll, inventory adjustments, journal entries, budget. You define once who authorises what and from what amount — and every signature leaves a record.
What it solves
In most companies, authorisation lives in a WhatsApp message, an email or a corridor conversation. It works until the day someone has to explain who approved a two-hundred-thousand purchase, and then there is no document — only memories that do not match. And meanwhile, nobody can see what is waiting for approval.
What is included
Purchasing, Accounts Payable, Accounts Receivable, Invoicing, Inventory, Payroll, Banks, Cash Register, Petty Cash, Accounting, Fixed Assets, Budget, CRM, ConstructFlow, Prestamello and Support all use the same one. The rule is defined once, not sixteen times.
Up to X the area manager approves it; above that, senior management. The line is written once and stops being argued over on every document.
It is not a warning you can ignore: the engine blocks execution. Anything awaiting approval is not paid, not shipped and not posted.
Each approver sees their own items in a list, with how long each has been waiting. What has been stuck for three days is visible, instead of surfacing when someone complains.
Who requested it, who approved or rejected it, when, and with what note. It is what turns "I think Juan approved it" into a document.
It does not just sit as a status: it returns the document to where it belongs, so whoever requested it can fix it instead of starting over.
How it works
Who approves, from what amount, and how many approvers per band.
By module and document type: not everything needs a signature.
What is pending is visible, you approve or reject it, and the document carries on by itself.
In detail
On approval the document applies itself: the order goes out, the payment joins the run, the entry is posted. Separating the two is what leaves things approved and undone.
That is why every level takes more than one. With a single approver, their holiday stops the company's purchasing — and nobody saw it coming when setting it up.
Rejecting without saying why forces a conversation to find out — and that conversation is exactly what the workflow was meant to avoid.
The engine is shared, but approving an invoice does not mean the same as approving an inventory adjustment. Each module defines its own effect without rewriting the workflow.
If the document no longer applies, the request is withdrawn instead of sitting in someone's inbox forever.
And the requester gets one when it is resolved. A workflow that depends on someone remembering to check the inbox is a workflow that stalls on Fridays.
Who it is for
And today authorisation is requested by message.
And you have to prove who authorised each thing.
Because nobody knows what is waiting for their signature.
Common questions
No. It comes with the platform and runs across every module you have subscribed to. It is not a paid add-on.
Yes, that is the usual way: you define amount bands and each one has its own approvers.
That is why each level takes several approvers. With only one, their absence stops the process — and it is worth planning for that when setting it up.
Yes: the inbox is just another screen of the platform and works in a mobile browser.
Yes: who requested, who resolved, when and with what note, tied to the document that triggered the request.
Approval executes the document, so you correct it the way that document allows — a credit note, a reversing entry — and that correction is recorded too.
And also
We will show you Approvals running on a case much like yours, with no obligation.