⚙️

Fully autonomous project. The Procurement Codex is built, verified, and published end-to-end without manual authoring. Its core logic — the spine, the layer model, and the platform comparison rubric — is rebuilt and improved on every iteration for continuous method validation. Content is generated programmatically and refined each cycle: treat it as a directional learning aid, verify against primary sources, and send corrections — accuracy and fairness compound with each pass.

Episode 12 · Where the process finally costs or earns money

Payment & Working Capital

Eleven steps of governance end in one irreversible act. Payment is where terms negotiated in Ep05 either materialise or evaporate, where a fraudulent bank change becomes an unrecoverable loss, and where the speed of everything upstream turns into the price of money.

Below: the plain concept → how every major platform handles it → best practice → process mining, AI, orchestration and ownership, stacked until standalone is never enough.

L0 · The Concept

What it is

Payment is the execution of the approved liability: selecting invoices due, applying terms, running the payment proposal, releasing funds through a bank or payment provider, and reconciling what settled. Working capital management is the deliberate use of that timing — terms, early payment discounts and third-party funding — to trade cash against cost for both sides of the relationship.

Why it exists

Because the payment run is the last control point before money leaves and the only one that cannot be reversed by a correcting journal. It is also the largest single lever most organisations hold over working capital: days payable outstanding, discount capture and supplier financial health are all decided here rather than in treasury spreadsheets.

What good looks like

Payment runs are scheduled, exception-free and reconciled automatically. Bank detail changes require out-of-band verification and cannot be made by the same person who releases the run. Terms are honoured, so on-time payment is high. Early payment is offered where it is genuinely cheaper than the alternative, and suppliers can see when they will be paid without calling anyone.

L1 · Platform-Native — A vs B vs C

Same rubric for every vendor, 1–5. We state explicitly what each is best and worst at. Toggle platforms to compare.

Platform	Best at	Watch-out

Scores are directional teaching aids based on typical deployments, not vendor benchmarks. Your mileage varies by configuration, module licensing, scope, and integration maturity.

L2 · Best Practice

Design principles

Pay on the terms you agreed — unilaterally stretching payment is a transfer of financing cost onto the supplier, and it is repriced into the next negotiation in Ep05 with interest.
Separate the duties that matter — the person who changes a bank detail, the person who approves the run and the person who releases it should never be the same person, in any organisation of any size.
Verify bank changes out of band — a bank detail change requested by email must be confirmed on a previously known phone number. This one control prevents the most common and most expensive fraud in the cycle.
Make early payment an economic choice — a discount is only worth taking if the implied return beats the alternative use of that cash. Sliding-scale dynamic discounting makes that calculable per invoice rather than a blanket policy.
Give suppliers visibility instead of a phone call — a supplier who can see the scheduled payment date does not chase, and chasing is a cost to both sides that produces nothing.
Design funding to be genuinely optional — supply chain finance should widen supplier choice. If it is introduced alongside an imposed extension of terms, it is a cost transfer wearing a liquidity costume, and it will be seen that way.

KPIs & failure modes

KPIs — on-time payment rate, days payable outstanding against agreed terms, early payment discount capture rate, payment exception and rejection rate, duplicate payment recovery, supplier enquiries about payment status.
Payment fraud — a changed bank detail on a real supplier record, approved because it arrived on plausible letterhead during a busy period. The loss is usually unrecoverable.
Silent terms stretching — a policy of paying late that never appears in any contract, degrades supplier goodwill and reappears as price in the next negotiation.
Discounts left on the table — early payment terms negotiated in Ep05 that nobody ever captures because the invoice was still an exception on the discount date.
Duplicate payments — the same liability paid twice through two channels, typically found months later by a recovery audit that charges a share of what it finds.
Reconciliation drift — payment runs that do not reconcile cleanly to the bank, leaving a suspense account that hides both errors and losses.
Suppliers financing you unknowingly — extended terms plus late payment on top, which pushes the cost of your working capital onto the smallest firms in your base.

The Layer Peeler — watch standalone become a system

Stack layers onto a manual bank transfer and watch the architecture — and the outcome metrics — change. This is the whole thesis of the Codex in one control.

Outcome at this stack level

On-time payment

Discount capture

Payment exceptions

Fraud attempts caught

L7 · The Synergy Composite

A real best-of-breed payment architecture is never one product. Here is the composite, and where the value actually lives — in the seams.

flowchart LR
INV[Ep11 matched and posted invoice] --> DUE[L1 Payment proposal
terms, due date and currency]
SUPP[Ep07 golden supplier record
verified bank details] -.remit-to.-> DUE
DUE --> CTRL{L2 and L6 Controls
segregation, dual release, out-of-band bank check}
FRAUD[L4 Fraud and anomaly detection
new bank, new payee, odd amount] -.risk score.-> CTRL
CTRL --> RUN[L1 Payment run
S4HANA / Oracle / D365 / Coupa Pay]
RUN --> BANK[L5 Bank and payment rails
ACH, SEPA, wire, virtual card]
DISC[L4 Dynamic discounting
sliding-scale early payment] -.cheaper than the alternative.-> DUE
SCF[L5 Supply chain finance
third-party funded, supplier opt-in] -.supplier liquidity.-> BANK
PM[L3 Process mining
Celonis / Signavio] -.late payment root cause.-> CTRL
BANK --> REC[L1 Reconciliation and cash forecast]
REC --> SPM[Ep13 · Supplier Performance and Relationship]

Standalone, a payment module moves money. Wired to Ep07 for verified bank details, Ep11 for a clean approved liability, fraud analytics for the anomalies a human would never spot in a run of nine thousand lines, funding programmes for the suppliers who want cash sooner, and mining for why payments are actually late, it becomes a working capital instrument rather than an administrative task. No single vendor leads on ERP payment controls, funding reach and supplier experience at once — and here the seams are measured in basis points.

The Stack Builder — compose your own

Pick one from each column. The Codex assembles the composite and calls out where the seams need engineering. Shown here for payment and working capital; the same engine powers every episode.

Cheat Sheet — Payment & Working Capital

The 5-second definition

Pay the right supplier, the right amount, on the agreed date, through a controlled and reconciled run — and decide deliberately when paying earlier is worth more than holding the cash.

KPIs that matter

On-time payment rate · DPO versus agreed terms · discount capture · payment exceptions · duplicate payments · supplier payment enquiries.

Scorecard in one line

If a bank detail can be changed and paid in the same week by the same team, no amount of upstream governance matters.

Platforms in one line

ERPs win on payment controls, tax and reconciliation; networks and payment layers win on supplier experience and funding reach; analytics wins on fraud and discount decisions.

The layers

L0 manual transfer → L1 payment run → L2 controls and terms discipline → L3 mining → L4 fraud and discount intelligence → L5 funding and rails orchestration → L6 segregation of duties → L7 composite.

The thesis

Standalone is never enough. Payment becomes working capital only when supplier data, matched liability, controls, funding and analytics are wired together.