Accounts payable aging report: 7 Checks Before the Payment Run

An accounts payable aging report groups unpaid supplier balances by age or overdue status at a chosen date. It helps a business see what it owes, when payments fall due, and which items need investigation. The report is a starting point for payment planning, not automatic permission to pay every listed invoice.

For a contractor or service company, the balance may include partial payments, disputed work, credit notes, and invoices waiting for approval. This article explains seven checks, a worked example, and a practical review process. It also shows why invoice-date aging, due-date aging, and the cash forecast need distinct labels.

What an accounts payable aging schedule shows

The report normally lists suppliers and outstanding invoices, with balances placed into buckets such as current, 1–30 days, 31–60 days, and older. The bucket meaning depends on the aging basis. Thirty days since invoice is different from thirty days overdue.

FreshBooks’ explanation of an accounts payable aging report illustrates one product view. Sage Intacct’s vendor aging documentation provides another example. Confirm the settings in the actual system rather than assuming that every report uses identical rules.

Keep the reporting date visible. An aging report run today may differ from a month-end version because of later payments, postings, or corrections. A reviewer needs to know whether the report reconstructs a historical position or simply displays current open items.

A worked supplier-balance example

Consider a hypothetical supplier with three unpaid invoices at the reporting date. Invoice A has an outstanding amount of 1,000 and is ten days overdue. Invoice B has 600 outstanding and is not yet due. Invoice C has 400 outstanding and is 45 days overdue.

Under a due-date aging basis, 600 sits in current, 1,000 in the 1–30 overdue bucket, and 400 in 31–60. The total payable is 2,000 before any separate unapplied credits or other adjustments.

Now suppose the supplier has issued a valid credit of 200 that has not yet been allocated. The net supplier position may be 1,800, but the report should preserve the credit and invoice detail. Netting it invisibly against the oldest item can hide what still needs reconciliation.

If the report instead ages by invoice date, the bucket placement may change even though the liability does not. This is why the settings belong in the review, not only in a software administrator’s notes.

7 checks before relying on the report

1. Confirm the date and aging basis

State the as-of date and whether buckets use invoice date, due date, or another configured rule. Also check the time and cutoff convention where it affects the result. A report labeled “overdue” should not quietly use days since invoice.

Review how the system handles later payments against a historical report. Some reports reconstruct the earlier position, while others show current open balances with historical dates. Test a known invoice to understand the behavior.

Use consistent settings across periods. If finance changes the aging basis, explain the effect instead of presenting bucket movement as a change in payment performance.

2. Reconcile the total with the ledger

The aging total should reconcile with the relevant accounts payable control balance under the chosen scope and date. Investigate differences such as unposted batches, manual journals, currency treatment, or excluded suppliers.

Do not force the totals to match through an unexplained adjustment. Identify the transaction or configuration issue and follow the accounting correction process. A reconciliation that cannot explain its balancing item provides limited control.

Keep the entity and currency scope clear. A multi-company report may need separate reconciliations before consolidation. Mixing local-currency balances with a reporting-currency total can create apparent differences that the team must understand.

3. Check invoices, credits, and allocations

Review partial payments, credit notes, refunds, and unapplied amounts. A supplier’s net balance may look modest while individual invoices remain unresolved. The detailed allocation tells staff what the supplier may still regard as unpaid.

Inspect duplicate invoices and repeated imports. Similar references or amounts can indicate a duplicate, but they do not prove one. Confirm the supporting document and transaction history before reversing or withholding payment.

Also check negative balances. They may represent genuine supplier credits, advance payments, or a posting error. Keep the reason visible rather than treating every negative amount as a simple reduction of payment need.

4. Separate approval and dispute status

An invoice can be recorded as payable while still needing an operating approval or dispute resolution. The aging report should connect with that workflow without pretending that every unpaid amount has the same cause.

Use short, specific reasons: missing receipt evidence, price query, incomplete work, duplicate review, or pending authorization. Assign an owner and next action. A vague “on hold” status can leave an item aging indefinitely.

Do not let a dispute label become a substitute for follow-up. The business still needs to resolve the issue and communicate appropriately with the supplier. Review old holds separately from ordinary payment scheduling.

5. Verify payment terms and supplier details

Wrong due dates can make a report look better or worse without changing the underlying agreement. Check unusual terms, manual overrides, and supplier-master changes. Keep the agreed evidence available where appropriate.

Before releasing payment, follow the business’s supplier-verification controls. A correct aging amount does not validate a new bank account or payment instruction. Separate financial analysis from authorization and sensitive master-data changes.

Also review critical service relationships. An overdue small invoice can matter operationally if it affects an essential supplier. Prioritization needs context, while still respecting actual obligations and the approved payment process.

6. Connect the report with a dated cash plan

Aging shows outstanding balances at a date. A cash forecast shows expected receipts and payments over time. The business needs both to understand whether its intended payment run fits the cash calendar.

Include known upcoming obligations that may not yet appear as posted invoices through an appropriate planning process. Otherwise, a payment plan can look affordable while ignoring work already committed or received.

Do not interpret a low overdue total as proof of complete visibility. Missing invoices and delayed posting can understate payables. Review cutoff and operational evidence alongside the report.

7. Turn exceptions into owned actions

For each material exception, record the reason, owner, next step, and review date. Examples include obtaining a missing invoice, allocating a credit, resolving a price query, or confirming payment status.

Keep the action separate from the accounting record where necessary, but link the two. The reviewer should see whether the issue progressed since the prior payment run. An aging report without follow-through becomes a recurring list rather than a control.

Preserve the resolution history. If the business later questions why a payment was delayed or changed, the supporting record should explain the decision without relying on staff memory.

Design a practical payment-run review

Begin with a reconciled report and a proposed payment list. Review due dates, approvals, credits, disputes, and cash timing. Then confirm the authorization route and any exceptions requiring a separate decision.

Use a manageable threshold for detailed discussion while retaining controls for all payments. A large-value focus should not allow duplicate or misdirected smaller payments to pass unchecked. The exact process should fit the business’s risk and resources.

After payment, confirm posting and allocation. An amount leaving the bank does not automatically mean the supplier ledger reflects it correctly. Review failed payments, returns, and remittance questions through a clear follow-up process.

What an aging trend can and cannot explain

A rising older bucket can indicate delayed payment, unresolved disputes, wrong terms, missing credits, or poor allocation. The trend is a signal for investigation. It does not establish the cause by itself.

Compare consistent dates and definitions. A report taken just before a regular payment run can differ sharply from one taken just after it. That timing can explain movement without indicating a lasting process change.

Use the report alongside the accounts payable turnover ratio where useful. Turnover summarizes purchases relative to average balances, while aging shows the open items behind a date-specific position.

Improve data quality before automating decisions

Use stable supplier and invoice identifiers, reliable due dates, and a consistent status model. A duplicate supplier record can split balances and hide an overall exposure. Review merges carefully so that different legal suppliers do not become one record.

Anomoz’s guide to data literacy for reporting decisions explains the value of visible definitions and supporting evidence. Keep a route from each summary amount to the relevant documents and transactions.

Automation can prepare an exception list or proposed payment run, but the business still needs appropriate authorization. A rule that pays the oldest item first may ignore credits, disputes, or a payment already in transit.

Test the report with known edge cases

Create a small authorized test set containing a current invoice, overdue invoice, partial payment, credit, and later-dated settlement. Confirm the bucket placement and historical behavior. Keep the expected results as a check after system changes.

Also test missing due dates and invalid dates. The report should make the problem visible rather than silently assigning a favorable category. A clear exception is better than a misleading current balance.

Finally, inspect access and exports. A broad management dashboard may not need bank instructions or detailed supplier contacts. Share the information needed for the decision without exposing unnecessary sensitive fields.

Common mistakes

• Confusing invoice age with days overdue.
• Using a historical date without checking later-payment treatment.
• Ignoring unallocated credits and partial payments.
• Assuming every recorded invoice is approved for payment.
• Treating the aging report as a complete cash forecast.
• Leaving disputed items without an owner or review date.

Also avoid hiding old balances through unexplained write-offs or re-dating. Corrections need evidence and appropriate approval. The aim is an accurate position and a resolved issue, not a cleaner-looking bucket chart.

Give old items a resolution route

An invoice that remains in an older bucket for several payment runs needs a clear explanation and a next decision. Ask whether the barrier concerns evidence, approval, dispute, allocation, or an unavailable contact. Different causes need different owners.

Keep supplier communication linked with the item where practical. A promise to send a credit note or clarify a charge should have a follow-up date. Otherwise, the same explanation can repeat without progress while both parties hold different views of the balance.

Escalate unresolved items through the approved process when the current owner lacks authority. The objective is an accurate liability and a settled decision, not simply movement into a younger bucket.

At the next review, confirm what changed. A resolution record helps finance explain the payment history and can reveal recurring process problems, such as missing purchase references or slow confirmation of completed work.

Make the report support a clear payment decision

An accounts payable aging report becomes useful when its date, basis, and total are reliable. Reconcile it, investigate exceptions, and connect payment choices with approvals and cash timing. Then close the loop so the same unresolved item does not return without progress.