Capture and validation
An electronic invoice arrives structured; paper and PDF are documents that must be read. Extracted fields are matched against purchase order and delivery data; a field that does not match is never guessed — it becomes an exception.
- Electronic and manual documents join one queue
- Three-way matching rules are written down
- Low-confidence fields go to exception rather than guesswork
- Duplicate invoice checking sits at the head of the chain
Approval flow and authority
The approval chain follows amount, cost center and contract status. Delegation and absence are built into the flow; a document awaiting approval must never disappear into someone's inbox.
- Delegation is defined inside the flow
- Waiting documents trigger reminders and escalation
- Approval authority is bounded by amount and cost center
- Approval records are usable during audit
Exception management
An exception is a natural part of the process, not a failure of it. What matters is whose queue it lands in, how long it waits, and whether its cause is classified. An unclassified exception cannot be improved.
- Exception causes are classified and counted
- The three most frequent causes are worked each period
- Supplier-caused exceptions become feedback
- Waiting time is tracked per exception type
Accounting and ERP integration
The chain completes when the accounting entry exists. Integration is not a one-way transfer: a status change in the ERP returns to the process side so both systems show the same truth.
- Entry creation and status feedback run both ways
- Account coding is proposed through a rule set
- A failed transfer never disappears silently
- A shared identifier travels for reconciliation