Approvals that hold the line on authority before anything posts.
DataFlow holds any document above a user’s authority limit for approval by a higher-authority user, rather than posting it. Over-limit documents wait in an approver’s queue, and every approval, rejection, escalation and re-route is logged — so control is built in, not bolted on.
The problem
When sign-off lives outside the system.
If approvals happen over email and a nod in the corridor, the wrong values slip through and nobody can prove who agreed to what.
Over-limit values slip through
Without a hard authority limit, a high-value invoice or credit note can be posted by whoever happens to key it in, past the point of any review.
Approvals lost in email
Sign-off scattered across inboxes and messages means no single queue to work through and no reliable record that an approval ever happened.
Approvers away, work stuck
When the approver is out of office and there is no cover, documents sit and stall — or get released without the review they needed.
The same person keys and approves
With nothing separating who raises a document from who signs it off, one person can enter and authorise the same high-value invoice, and the control exists only on paper.
Overview
Authority limits, enforced by the system.
Set the limit once, and DataFlow holds anything above it.
Authority limits per user, group and document type
Limits held per user, per group and per document type. Applies to any document type you configure.
Per typelimits by document type
User & groupauthority held both ways
Over-limit documents held for approval
Documents above the limit are held, not posted. Escalated to a higher-authority user for approval.
Above limitheld every time
Higher authorityescalation to approve
Approver queue, feedback and out-of-office cover
Approve or reject, with a feedback note on rejection. Out-of-office flag re-routes to a nominated cover user.
One queuedocuments to review
Coverout-of-office re-routing
Transaction Authorisation History and the remote portal
Every approval, rejection, escalation and re-route logged. Remote web Authorisation Portal for laptop or tablet.
Full historyof every decision
Laptop or tabletclear the queue anywhere
Explore more
More capabilities.
Authorisation is one of the controls DataFlow builds in — explore the other capabilities that keep the accounts accurate and defensible.
An authority limit is the maximum monetary value a user or group can post for a given document type without escalation. DataFlow holds these limits per user, per group and per document type.
What happens to a document above the limit?
It is held rather than posted, and escalated to a higher-authority user. It waits in that approver’s queue, where it can be approved to release it or rejected — a rejection carries a feedback note back to whoever raised it.
What happens when an approver is out of office?
An out-of-office flag with a date range re-routes documents to a nominated cover user, so approvals keep moving while the approver is away.
Can approvers work remotely?
Yes. A remote web Authorisation Portal lets finance directors and senior approvers clear their queue from a laptop or tablet, typically for purchase orders, with password confirmation before an approval is recorded.
