Leak 19 · Suppliers & Procurement - Supplier terms not being captured

A 2% discount for paying in 10 days is a 36% annualized return. Paying on day 30 anyway, or paying on day 12 and missing it, throws that away.

Diagnostic note. Symptoms, required records, an initial check, and possible fixes. This shorter note does not include a full worked example.

What is it?

Supplier payment terms include discounts, extended terms, dating programs, and freight allowances that are negotiated and then not reflected in how AP actually pays. The leak is the difference between the terms you have and the terms you use.

Family
Suppliers & Procurement
Primary owner
Controller
Secondary owners
Purchasing Manager, CFO
Primary impact
Cash / EBITDA
Typical data source
Supplier agreements, AP payment history
Detection difficulty
30-day measurability

Ask yourself

What share of available early-payment discounts did you take last year, and what share of invoices were paid before they were due without a discount?

Yes, partially, no, or don’t know. “Don’t know” is the most useful answer, because it points at the test below.

What does it look like?

Warning signs. None of these proves the leak exists. They tell you where to look.

  • Early-pay discounts available but taken inconsistently.
  • Invoices paid before due date with no discount.
  • Negotiated extended terms not loaded into the supplier record, so invoices are paid on the default.
  • Freight allowances or prepaid-freight thresholds not applied to POs.

What data do I need?

The minimum viable set. Most of it is already in your ERP.

Field
Supplier terms as negotiated
Supplier terms as loaded in the ERP
AP payment history: invoice date, due date, paid date, discount taken

The initial check

Start with a small sample. Gathering the exports, agreements, or observations is separate from running the check; agree that work with the person who owns the records.

  1. 1Export last quarter’s AP payments with invoice date, due date, paid date, and discount taken.
  2. 2Count discounts available versus taken, and invoices paid more than five days early with no discount.
  3. 3Compare the terms in the ERP for your top ten suppliers to the terms in their agreements.
Missed discount = Σ discount available but not taken; early payment cost = Σ (days paid early × amount × daily cost of capital)

Then ask one question: Are the ERP’s payment terms for each supplier the ones you negotiated?

How much could it be costing us?

A conservative range, not a headline. The goal is a number management can trust enough to investigate.

Annual missed discounts + cost of capital on early payments + unused freight allowances

Common root causes

Fixes fall into three layers. Not every problem needs software, and almost none needs AI first.

Process
AP pays on a schedule that ignores discount dates, and negotiated terms are not communicated to AP.
Data
Supplier master terms are stale or default.
Technology
The payment run does not optimize for discount capture.

What should we do?

Start with the simplest intervention that could solve it. Move down the list only if the one above is not enough.

  1. Level 1

    Data

    Reconcile supplier master terms to agreements for the top 30 suppliers.

  2. Level 2

    Process

    Run payments on discount dates and due dates, not a weekly default.

  3. Level 3

    Workflow

    A payment-run recommendation that ranks invoices by discount value and cash position.

Where AI helps

  • Extracting terms from agreements and invoices to compare against the supplier master.

Where AI probably doesn’t

Loading the right terms and changing the payment schedule is a controller’s task, not a software project.

Before you call it a leak

  • Taking a discount may not be worth it when cash is tight and the line of credit costs more than the discount is worth. Compare rates.

Think this might be happening in your business?

Turn the finding into a next step.

If the numbers say there is something there, send us what you found and we will help you decide whether it is worth a full investigation. No transaction files needed for that conversation.

Let’s start with one thing.

What would better performance look like?

Bring a result you want to improve, a symptom, or a workflow you already understand. You do not need to know the bottleneck yet. We’ll help choose what to investigate first.

No transaction files needed for the first conversation.