Skip to content

Playbook

Procure to pay

Requisition to payment. The process is well understood and the controls are standard; what costs finance teams their month-end is the exception volume nobody designed for.

  • Odoo Purchase
  • SAP MM
  • SAP Business One

The process

What the standard flow looks like.

  1. 01

    Request

    A requisition captures what is needed and who is accountable for the spend, before a commitment exists. Everything after this is harder to stop.

  2. 02

    Approve

    A release strategy decides who approves based on value, category and cost centre. Approval in email is not a release strategy.

  3. 03

    Order

    The purchase order is the commitment. It carries the agreed price and terms, which is what makes the later match possible.

  4. 04

    Receive

    Goods receipt records what actually arrived, when. This is the control that stops payment for things that were never delivered.

  5. 05

    Match

    Three-way match across order, receipt and invoice, within tolerance. Within tolerance it posts; outside it, a person decides.

  6. 06

    Pay

    Payment runs by due date and terms, with discounts taken where they are worth taking.

Failure modes

Where we expect to find it broken.

Invoices arrive without a purchase order
Someone ordered by phone. The invoice has nothing to match against, so it goes to a person to chase, and it is still unresolved at month-end.
The GR/IR account is nobody's job
Goods received not invoiced accumulates for years. By the time anyone reconciles it, the people who know what each line was have left.
Tolerances are set so tight that everything is an exception
A freight rounding difference blocks an invoice. The team's working day becomes clearing blocks that the system was supposed to prevent.
Duplicate invoices are caught by memory
The same invoice arrives by email and by post with a slightly different reference. Detection depends on someone recognising it.

Scope

What is standard, and what is the actual work.

The distinction matters commercially. Paying to build what the platform already does is the most common way an ERP budget is wasted.

Out of the box

  • Requisition, order, receipt and invoice document flow
  • Release strategies driven by value, category and cost centre
  • Three-way match with configurable tolerances
  • GR/IR clearing and open-commitment reporting
  • Payment proposals by due date, terms and discount
  • Vendor master with payment terms and bank detail controls

Configured or built

  • The release strategy itself — who approves what, and what happens when they are away
  • Tolerance limits per category, which decide how much lands in the exception queue
  • Account determination, so each category posts where finance expects
  • Vendor onboarding and the controls on changing bank details
  • Contract and scheduling agreements for recurring spend
  • Landed cost treatment where freight and duty belong on the item

The agent layer

Where an agent earns its place.

At the edges, where documents arrive unstructured and matching needs judgement. The transaction flow itself stays deterministic.

Invoice triage
Extracts header and line detail from whatever the supplier sent, finds the order and receipt, and either posts within tolerance or routes the exception with the discrepancy already identified.
Duplicate detection
Compares against posted and in-flight invoices on amount, date, vendor and reference, including near-matches a reference check would miss.
Price variance
Checks invoiced price against the contract and flags drift, which is a category of leakage that a tolerance check is specifically designed not to catch.

Outcomes

What changes.

  • Before

    Invoices are keyed by hand and matched by eye.

    After

    Invoices within tolerance post themselves; a person sees only the ones that genuinely need a decision.

  • Before

    GR/IR is reconciled once a year, under duress.

    After

    Ageing GR/IR items are surfaced continuously, while the context still exists.

  • Before

    A duplicate payment is found by the supplier telling you.

    After

    Near-duplicates are flagged before the payment run, not after it.

Questions

What people ask.

Is this OCR?
OCR is one step of it. Reading the document is the easy part; deciding which order it belongs to, whether the difference matters and who should look at it is the part that saves time.
Will it post invoices without a human?
Within tolerances you set, yes — that is the same decision the system already makes on a matched invoice. Outside tolerance it routes to a person. We would not recommend it the other way round.
What about PO-less invoices?
They can be classified and routed to the likely cost centre and approver, which helps. The real fix is upstream: making requisitioning easier than phoning a supplier.

Recognise any of this in your own process?

Book a call