Sign-Off Where It Actually Matters
A single approval engine sits inside the posting pipeline of every document that moves money or stock. A small adjustment goes straight through. A big one waits for a person. Nobody queues for nothing.
One Engine, Every Document
Approvals are wired into the posting pipeline of 16+ document types across sales, purchasing, inventory and manufacturing. A document that needs sign-off simply cannot post without it.
Value Thresholds
Set the number that matters. A GH₵ 200 stock adjustment posts immediately; a GH₵ 20,000 one waits for a manager. Control scales with the amount at risk, not with paperwork.
Routing to the Right Person
Routing picks the approver for the document, its branch and its value — so requests land with someone who can actually decide, not in a shared inbox everyone ignores.
Reminders That Chase
Requests sitting too long get chased automatically. The stock does not stay frozen because one person was out of the shop on Thursday.
Document Flow
Roughly 37 document types resolve into one linked graph. From a sale, walk to its delivery, its return, its receipt and its journal entries — drawn as a visual flow inside the app.
Full Audit Trail
Every mutating action and every denied read is recorded with actor, time and context. Sensitive fields are redacted, so the trail is safe to keep and safe to share.
What happens to a GH₵ 20,000 stock adjustment
The clearest way to explain an approval engine is to follow one document. Here is the path a high-value stock write-off takes, from the storekeeper's screen to a posted general-ledger entry.
- 01
Drafted
A storekeeper records damaged goods worth GH₵ 20,000 and saves the adjustment. Nothing has moved yet — stock levels and the ledger are untouched.
- 02
Policy evaluated
On post, the engine reads the policy for stock adjustments. The value clears the threshold, so the post is held instead of completing.
- 03
Routed
The request is routed to the approver configured for that branch and that value band, and shows up in their approvals queue with the full document attached.
- 04
Chased if it stalls
If nobody acts, reminders go out. Meanwhile the bottleneck dashboard shows the document ageing and names who is holding it.
- 05
Approved — and only now posted
The manager approves. The same pipeline that was blocked resumes: stock is written down, cost layers are consumed and the journal entries post to the GL.
- 06
Recorded and linked
The audit trail holds who approved it and when. Document flow links the adjustment to its journal entries, so a year later the story is still readable.
A GH₵ 200 version of the same adjustment skips steps 02 to 05 entirely. It posts on save. That is the whole point: control is spent where money or stock is genuinely at risk, and nowhere else.
See where documents are piling up
Approvals fail quietly. A purchase order nobody signed is a delivery that never arrives, three weeks later. The bottleneck dashboard makes the queue visible — what is waiting, how long it has waited, and who is holding it.
Ageing by document type
Spot the process that always stalls, not just the document.
Named holders
Accountability instead of a shrug about “the system”.
Redacted audit history
Every action and every denied read, with sensitive fields masked.
Documents the engine covers
Approval policies attach to the documents below. Each one posts through the same pipeline, so the rule you set once behaves the same way everywhere.
Approvals touch every part of the business
Put the guardrails where the money is
Set your thresholds, pick your approvers, and let everything under the line keep moving.