An invoice approval workflow you can repeat

What an invoice approval workflow is

An invoice approval workflow is the set of steps a bill must pass before it enters payment. It is more than a manager's signature. The workflow checks whether the bill matches a purchase order, whether the goods or services arrived, whether budget is available, and whether the amount and bank details are correct.

A healthy workflow therefore involves more than one role. Finance matches the documents. The relevant manager confirms the work happened. The budget owner decides whether the bill is paid now, postponed, or rejected. Every step produces a decision that needs to be recorded, not just an attachment in an inbox.

Why the workflow stalls

The problem is rarely the approval itself. It is the lack of a clear place to see where a bill stands. A few patterns repeat:

• The invoice goes to several people at once, and nobody feels responsible for answering.
• Approval arrives in a short message, with no record of the version or amount approved.
• The bill changes after approval, but the approver is never told.
• Proof sits scattered across email, shared folders, and the accounting system.
• Payment deadlines pass because nobody knows who is waiting.

Finance then spends time re-asking what should already be on record. That time adds no control. It only adds delay.

A sequence you can repeat

No single workflow fits every organisation, but the sequence below is a safe starting point. Adjust the number of steps to the size of the bill and the shape of your team.

1. Receive the invoice and record its number, date, vendor, amount, and currency.
2. Match the invoice against the purchase order and proof of delivery.
3. Check the bank details and confirm no vendor change is unverified.
4. Ask the relevant manager to confirm the work was actually done.
5. Ask the budget owner to approve when the amount passes your threshold.
6. Freeze the approval record, then pass the invoice to payment.

If a step finds a discrepancy, the workflow does not need to continue. Send it back to the submitter with a clear reason. That reason is part of the record too, because people later need to know why a bill was held, not only that it was held.

Who approves what

Clear role separation stops one person from holding the whole decision. The table below is a common split for small and mid-sized teams.

On a very small team, one person may hold two roles. What matters is not the headcount but a sensible separation of duties. The person who submits a bill should not be the only person who approves it.

The proof that should remain after payment

After an invoice is paid, the questions usually arrive later. An auditor asks for proof that the amount paid matches the amount approved. A new manager wants to know why a particular bill went through. A vendor asks about payment status. A good record answers all of this without another search through email.

At minimum, keep four things: the approved invoice file and its fingerprint, the sequence of approval steps and who took them, the time of each decision, and the document version in force at each step. If the bill changes, the old version stays and the new version earns its own approval.

In Segel the record is frozen when the route finishes and sealed with a timestamp from a trusted time authority. Anyone holding the sealed file can check it on the verification page without asking for access to your internal systems.

Measuring whether the workflow improved

The workflow is not the goal. Paying bills on time with enough control is. Two simple measures already tell you a lot: the time from invoice receipt to the final decision, and the number of bills returned for issues that should have been caught early.

• Cycle time per stage, not just the total. The longest stage is usually the one to fix.
• Returns for incomplete documents, kept separate from returns for amount mismatches.
• Invoices near their due date with no decision, so they can be prioritised.

What this workflow does not solve

An approval workflow does not judge whether a vendor's price is reasonable, does not replace bookkeeping, and does not guarantee that a bill is legally valid. It only ensures the decision is taken by the right people, on the right version of the document, and that the decision is recorded.

The defensible claim is narrower: the record is tamper-evident, so changes to the file or the history become visible, and it is independently verifiable by anyone holding a copy. That is enough to answer an auditor without claiming more than you can prove.