# Accounts Payable Aging

> The report that sorts what a contractor owes its suppliers and subcontractors by how long it has been outstanding, balancing cash preservation against paying vendors on time and preserving lien releases.

- Source: https://briq.ai/acu/object/ap-aging
- Department: Reporting, Forecasting & Analytics (https://briq.ai/acu/department/reporting)
- Catalog code: RPT 208 · Level: Practitioner · Track: Finance · 10 min read
- Also known as: AP Aging, Payables Aging, Aged Payables, Creditor Aging

## Definition

An accounts payable aging report lists every unpaid vendor and subcontractor invoice sorted by how long it has been outstanding, so a contractor can manage what it owes, when it is due, and how paying it affects cash. It is the mirror of the receivables aging: where AR is money owed to the company, AP is money the company owes, and the two together define its short-term cash position. In construction it is complicated by pay-when-paid terms, lien waivers exchanged for payment, retainage withheld from subcontractors, and the need to match invoices to purchase orders and receipts before paying. It is not merely a list of bills; a rigorous AP aging is a cash-timing and risk-management instrument that also protects the contractor from paying for work it never received or paying twice.

## Why it matters

Accounts payable is the other half of a contractor's cash timing, and managing it deliberately is one of the cheapest sources of working capital there is. Paying vendors exactly when due - not early, not late - keeps cash in the business longer without harming relationships, and the aging is the instrument that makes that timing intentional rather than accidental. A contractor that pays everything the day it arrives is financing its suppliers with its own scarce cash; one that pays late damages the relationships it depends on. The aging is where that balance is struck.

AP in construction is bound up with lien rights, and paying without collecting the corresponding lien waiver leaves the contractor exposed. A subcontractor or supplier that is paid but does not release its lien rights, or that fails to pay its own lower tiers, can leave a lien on the owner's property that the contractor is obligated to clear. The aging is where payment and waiver are tied together, so cash never goes out without the release that protects the project coming back.

The aging protects against paying for what was never received or paying twice, through the discipline of the three-way match. In a business with thousands of invoices against hundreds of purchase orders and subcontracts, invoices arrive for the wrong quantities, for work not yet done, or as duplicates, and a payables process that does not match invoice to purchase order to receipt before paying will leak money steadily. The aging, coupled with the match, is the control that catches these before the check is cut.

AP timing is a lever on covenant and vendor-health signals that others read. Stretching payables too far shows up as rising days payable outstanding and can strain the supplier relationships and even the trade credit a contractor relies on, while a sudden slowdown in a contractor's payments is one of the earliest external signs of financial distress. Managing the aging keeps the contractor's own signals healthy and its trade credit intact, which matters far beyond the individual invoices.

## Lifecycle

1. **Invoice receipt and capture** — A vendor or subcontractor invoice arrives and is entered against its purchase order or subcontract. Capture accuracy sets everything downstream: an invoice coded to the wrong job or commitment distorts both the aging and the job cost it feeds.
2. **Matching and approval** — The invoice is three-way matched to the purchase order and the receiving or the approved progress, then routed for approval. This is the control step: an invoice that does not match should not be scheduled for payment, and skipping the match is how contractors pay for phantom quantities.
3. **Aging classification** — The approved payable is placed in an aging bucket by its due date under the vendor's terms, with retainage payable and pay-when-paid holds tracked separately. Aging off the due date is what makes the report a cash-timing tool rather than a pile of bills.
4. **Payment scheduling** — Payables are scheduled to be paid when due, prioritized against available cash and any early-payment discounts worth taking. This is where the cash lever is pulled - deliberately timing payment to preserve cash without going past due.
5. **Lien waiver exchange** — For subcontractors and material suppliers, payment is exchanged for the appropriate conditional or unconditional lien waiver. Releasing payment without the waiver forfeits the protection the payment was supposed to buy.
6. **Retainage tracking** — Retainage withheld from subcontractors is tracked toward its release, mirroring the retainage the contractor is itself owed. Retainage payable that is released before the contractor collects its own can create a cash squeeze.
7. **Payment execution** — The payment is issued, sometimes as a joint check to a sub and its supplier to ensure lower tiers are paid. The payment is applied against the invoice and the aging updates.
8. **Reconciliation** — The AP subledger is reconciled to vendor statements and the general ledger. Unreconciled payables - a missing invoice, a duplicate, a misapplied payment - corrupt the aging and the cash forecast that depends on it.

## Anatomy

- **Vendor / subcontractor** — Who is owed. The dimension that drives relationship management, concentration, and lien exposure.
- **Project / job and cost code** — The job and code the payable belongs to. Ties AP to job cost, so a miscode distorts both the aging and the cost report.
- **Invoice and PO / subcontract reference** — The invoice and the commitment it draws against. The basis for the three-way match that prevents overpayment.
- **Invoice date and due date** — When received and when payable under the terms. Aging and scheduling both run off the due date.
- **Original and open amount** — The invoiced amount and what remains unpaid. The open amount is what is scheduled and what hits cash.
- **Aging bucket** — Current, 1-30, 31-60, 61-90, over 90 days. Shows where the contractor is behind and where it is deliberately holding cash.
- **Payment terms and discount** — Net-30, net-45, pay-when-paid, or terms with an early-payment discount. Defines when payment is due and whether paying early pays off.
- **Retainage payable** — Amounts withheld from subcontractors pending their completion. Tracked separately toward release, mirroring retainage receivable.
- **Lien waiver status** — Whether the required conditional or unconditional waiver has been collected for the payment. The protection that must travel with the cash.
- **Match status** — Whether the invoice passed the three-way match. An unmatched invoice should not be paid, so this gates scheduling.
- **Pay-when-paid hold** — Whether payment to a sub is contingent on the contractor being paid by the owner. Shifts the timing of the outflow materially.
- **Payment status** — Scheduled, held, or paid. Turns the aging into a managed payment plan rather than a static list.

## Failure modes

- **Paying without the lien waiver** — Cash goes out to a subcontractor or supplier but the corresponding lien waiver is never collected, so the payment buys none of the protection it was meant to. If that party or its lower tiers later lien the project, the contractor pays for the same work twice - once to the sub and again to clear the lien.
- **Skipping the three-way match** — Invoices are paid on receipt without matching to the purchase order and the receiving, so overbilled quantities, work not yet performed, and outright duplicates all get paid. In a high-volume payables operation this leaks money continuously and quietly, and the leak is nearly invisible without the match.
- **Aging off invoice date, not due date** — The aging runs off invoice date, so payables on longer terms look overdue when they are not and genuinely late ones are lost in the noise. Payment scheduling based on a wrong aging either pays too early and burns cash or too late and burns relationships.
- **Stretching payables into distress signals** — Cash pressure leads to paying everything as late as possible, so days payable outstanding balloons and vendors notice. Trade credit tightens, suppliers demand deposits or COD, and the very slowdown meant to conserve cash starts costing the contractor its supplier relationships and its reputation.
- **Duplicate payments** — The same invoice is entered twice, or a statement and an invoice are both paid, and the vendor is overpaid. Recovering a duplicate payment depends entirely on the vendor's honesty, and much of it is never recovered, so the control has to prevent it rather than catch it after.
- **Retainage released out of sequence** — Retainage owed to subcontractors is released before the contractor has collected the corresponding retainage from the owner, creating a cash gap the aging never flagged. The contractor funds the retainage float itself, sometimes for months.

## Metrics

- **Days payable outstanding (DPO)** — Average days the contractor takes to pay. The headline AP-timing metric, read against DSO to see the cash-cycle balance.
- **Percent paid on time** — Share of payables paid on or just before their due date, neither early nor late. Measures deliberate payment timing.
- **Aging bucket distribution** — How payables spread across buckets. Rising later buckets can mean deliberate cash conservation or genuine distress.
- **Match exception rate** — Share of invoices failing the three-way match. Measures the health of the control that prevents overpayment.
- **Lien waiver coverage** — Share of payments made with the required waiver collected. The protection metric that keeps liens off the project.
- **Early-payment discounts captured** — Value of discounts taken against those available. Money left on the table when cash allows capturing them.
- **Duplicate payment rate** — Duplicate payments as a share of total. A direct read on control failures and leaked cash.

## The AI shift

- **Conversational** — The aging stops being a bill pile you scan and becomes something you interrogate. You ask which payables are due this week versus merely outstanding, which payments are being held for a missing lien waiver or a failed match, which subcontractor retainage is being released ahead of the owner's, and where an early-payment discount is worth taking given cash - with the invoices and commitments cited.
- **Generative** — The documents and communications AP requires are drafted from the record: the lien waiver requests that must accompany each payment, joint-check arrangements where lower tiers need protecting, vendor communications explaining a payment schedule, and match-exception queries back to vendors - grounded in the specific invoice and commitment, for review rather than composition from scratch.
- **Orchestrated** — The aging stops living apart from the controls and cash. Invoices are three-way matched to purchase orders and receipts before scheduling, payments are gated on collecting the required lien waiver, retainage payable is sequenced against the retainage the contractor is owed, and the payment schedule feeds the cash forecast so outflow timing is modeled from real due dates rather than assumed.
- **Autonomous** — The routine motion runs continuously: invoices captured and three-way matched with exceptions held rather than paid, payables aged by due date and scheduled to pay exactly when due within cash limits, lien waivers requested and payment held until they are collected, duplicate invoices detected before payment, and discounts flagged when worth taking - while humans approve every payment run, decide when to hold a vendor, and own retainage-release timing.

## Prompts

### Conversational — Preparing the weekly payment run with cash tight.

```text
Analyze our AP aging to build this week's payment run with cash tight. Show me what is genuinely due this week by due date, separated from what is merely outstanding on longer terms, and separate retainage payable and pay-when-paid holds from ordinary invoices. Flag any payment I should not release yet because the three-way match failed or the required lien waiver has not been collected. Identify any early-payment discounts worth capturing if cash allows, and any subcontractor retainage scheduled to release before we have collected the corresponding retainage from the owner. Prioritize the run to protect our critical vendor relationships and preserve cash.
```

**Expected output:** A prioritized payment run separating due from outstanding, holds flagged for match and waiver, discounts and retainage-sequence issues surfaced - not a list of every open bill.

**Follow-ups:**

- Which of these vendors are on our critical path and must be paid on time no matter what?
- If I defer everything not strictly due, how much cash does that preserve this week?
- Which held invoices need a match exception resolved before next week's run?

### Generative — You need the lien waivers and vendor communications to accompany a payment run.

```text
For this week's approved payment run, draft the documents that must travel with the payments. For each subcontractor and material supplier payment, draft the appropriate conditional lien waiver to accompany the check, referencing the invoice, project, and amount. For the two subs whose lower-tier suppliers are at risk, draft a joint-check arrangement. For the three vendors we are paying on a slightly extended schedule, draft a brief, relationship-preserving note explaining when they will be paid. Keep everything professional and specific to each invoice and commitment, and do not draft a waiver for any payment still failing the three-way match.
```

**Expected output:** A set of waivers, joint-check arrangements, and vendor notes matched to each payment, with unmatched invoices excluded from waiver drafting.

**Follow-ups:**

- Redraft the joint-check arrangement to also protect us if the sub's supplier disputes the amount.
- Draft the unconditional waivers to collect once these payments clear.
- Write the match-exception query to the vendor whose invoice quantity exceeds the PO.

### Orchestrated — You want AP wired to the match, lien waivers, retainage sequencing, and the cash forecast.

```text
Wire our AP process end to end. Three-way match every open invoice to its purchase order or subcontract and its receiving or approved progress, and flag every exception with the specific discrepancy. Gate each scheduled payment on collecting the required lien waiver, and do not let a payment be scheduled without it. Sequence subcontractor retainage payable against the retainage we are owed from the corresponding owner so we never release ours before collecting theirs. Feed the resulting payment schedule, by real due date, into the cash forecast's disbursement timing. Detect any potential duplicate invoices before they schedule. Cite the records for each match and linkage and flag anything uncertain.
```

**Expected output:** An AP process where every invoice is matched, every payment is waiver-gated, retainage is sequenced against collections, and outflows feed the cash forecast, with exceptions and duplicates flagged and records cited.

**Follow-ups:**

- Show me every match exception and its dollar discrepancy.
- Which retainage releases would create a cash gap ahead of our collections, and by how much?
- Update the cash forecast's outflows from this payment schedule and show the effect on our low point.

### Autonomous — Standing policy for running the payables process continuously.

```text
Run our AP process continuously under these rules. Capture and three-way match every invoice to its purchase order or subcontract and its receiving, and hold any exception rather than scheduling it for payment. Age payables by due date, tracking retainage payable and pay-when-paid holds separately, and prepare a payment schedule that pays each invoice exactly when due within available cash, flagging early-payment discounts worth taking. Request the required lien waiver for every subcontractor and supplier payment and hold the payment until the waiver is collected. Detect and hold potential duplicate invoices. Never release a payment, never override a match exception, never release subcontractor retainage, and never stretch a vendor beyond terms without my approval, and route every exception and waiver gap to me.
```

**Expected output:** A continuously matched, waiver-gated payables process with a scheduled run and a short exception queue, where every payment release, override, and retainage release stays with a person.

**Follow-ups:**

- Show me every match exception, every waiver still outstanding, and every duplicate you held this week.
- Which discounts are worth capturing this week if we free up cash, and how much?
- Draft the payment schedule for my approval, with the held items and reasons listed.

## Maturity ladder

- **Level 0 — Level 0 - Pay on receipt** — Invoices are paid whenever they arrive, with no match, no due-date discipline, and waivers collected haphazardly. Cash leaks through duplicates and phantom quantities, and liens slip through.
- **Level 1 — Level 1 - Bucketed** — An AP aging exists but often runs off invoice date, lumps retainage in, and is disconnected from the match and waivers. It lists bills more than it manages them.
- **Level 2 — Level 2 - Matched and gated** — Invoices are three-way matched before scheduling, aged by due date, payments are gated on lien waivers, retainage is tracked separately, and payment timing is deliberate.
- **Level 3 — Level 3 - Assisted** — Matching runs with exceptions flagged, waivers and joint checks are drafted, duplicates are detected, retainage is sequenced against collections, and the schedule feeds the cash forecast for review.
- **Level 4 — Level 4 - Operated** — The payables process runs continuously inside guardrails - capture, matching, aging, scheduling, waiver gating, and duplicate detection - while humans own every payment release, hold, override, and retainage release.

## FAQ

### Why gate payments on collecting a lien waiver?

Because a payment to a subcontractor or supplier is supposed to buy the contractor and the owner protection from a lien, and without the corresponding waiver it buys nothing. If a party is paid but never releases its lien rights, or if it fails to pay its own lower tiers who then lien the project, the contractor can be forced to pay for the same work a second time to clear the lien. Tying each payment to its conditional or unconditional waiver ensures the release that protects the project always travels with the cash, which is why disciplined AP processes will not schedule a payment until the waiver is in hand.

### What is the three-way match and why does it matter in AP?

The three-way match verifies that a vendor invoice agrees with the purchase order that authorized the purchase and the receiving record that confirms the goods or work were actually received, before the invoice is paid. It matters because in a high-volume payables operation invoices routinely arrive for wrong quantities, for work not yet performed, at prices that do not match the PO, or as outright duplicates, and paying them unmatched leaks money continuously and invisibly. The match is the primary control that catches these discrepancies before the check is cut, which is far cheaper than trying to recover an overpayment afterward.

### How far should a contractor stretch its payables?

To the due date, deliberately, but not past it into distress. Paying exactly when due - not early, which needlessly gives up cash, and not late, which harms relationships - is a legitimate and cheap source of working capital, and days payable outstanding is the metric that tracks it. Stretching beyond terms is a different thing: it strains supplier relationships, can tighten or revoke trade credit, and a visible slowdown in a contractor's payments is one of the earliest signals of financial distress that vendors and even sureties watch for. The aging's job is to make payment timing intentional and near the due date, capturing discounts where cash allows, rather than either paying everything immediately or drifting into chronic lateness.

## Related objects

- [Accounts Payable Invoice](https://briq.ai/acu/object/ap-invoice)
- [Three-Way Match](https://briq.ai/acu/object/three-way-match)
- [Lien Waiver](https://briq.ai/acu/object/lien-waiver)
- [Subcontractor Invoice](https://briq.ai/acu/object/subcontractor-invoice)
- [DSO & DPO](https://briq.ai/acu/object/dso-dpo)
- [Cash Flow Forecast](https://briq.ai/acu/object/cash-flow-forecast)