How to prepare an accounts payable ageing report

UK regulation around payment practices is tightening, and your accounts payable (AP) ageing report is where you prove your position. To give you context, the Fair Payment Code (FPC) launched in December 2024 with tiered performance thresholds and the government's late payment consultation confirms its intention to cap maximum payment terms at 60 days, whilst giving the Small Business Commissioner powers to impose fines.

If you're processing hundreds of payables a month, the report can't just reconcile anymore. It has to account for every outstanding supplier invoice, categorise each by age, and match the total to your general ledger (GL) before month-end close.

It also has to hold up as evidence of your payment performance under the FPC and, for qualifying companies, your Payment Practices Reporting (PPR) submissions. Verify regulatory thresholds with your accountant or legal adviser, but the trajectory is clear: an ageing report built only for reconciliation, without compliance alignment, is putting you at risk of falling behind.

What should an AP ageing report include?

Each invoice line requires a small set of core fields for both reconciliation and decision-making.

Beyond these core fields, you'll also need to include credit memos (entered as negative amounts) and debit memos (entered as positive amounts) as separate line items per vendor. It's better not to net these against invoice balances without disclosure, because auditors will want to see each item on its own row.

Your statutory accounts will also need specific creditor breakdowns. Financial Reporting Standard 102 (FRS 102) requires separate disclosure of related party balances. It also requires creditors to be split between amounts falling due within one year and amounts falling due after more than one year. The requirement to disclose taxation and social security creditors separately comes from The Large and Medium-sized Companies and Groups (Accounts and Reports) Regulations 2008 (SI 2008/409), Schedule 1.

Tag these categories in your ageing report from the start. The data then maps cleanly to your statutory accounts and saves your team time at year-end. If you leave the tagging to year-end, you're rebuilding from transaction-level detail under audit pressure.

If you're operating across multiple entities, you'll need to decide whether to prepare a single consolidated ageing report or entity-level reports. This sounds straightforward, but in practice intercompany transactions complicate things quickly. Tagging those balances separately keeps your external supplier obligations accurate and makes consolidation adjustments much simpler at close.

How to set up ageing buckets for UK payment terms

A standard ageing bucket structure looks like this:

Age from the due date, not the invoice date. Payment terms vary across vendors, so ageing from the invoice date gives a misleading picture. A Net 60 invoice aged from its invoice date looks 30 days more overdue than it actually is. Document your chosen method in your AP policy and apply it consistently, so different team members run the report the same way.

Align your buckets to UK regulatory thresholds. The default statutory payment term under the Late Payment of Commercial Debts (Interest) Act 1998 (the Late Payment Act) is 30 days unless otherwise agreed. The Fair Payment Code measures performance at 30-day and 60-day thresholds: Gold status requires at least 95% of invoices paid within 30 days. The government's late payment consultation proposes capping maximum payment terms at 60 days, which would make anything in your 61-to-90-day bucket a potential compliance issue.

If you're an FPC signatory, you'll need to evidence those percentages, typically using payment performance data such as your PPR submissions. Ageing buckets aligned to these thresholds make compliance reporting easier. Tag supplier size in your vendor master, separating small and medium-sized enterprises (SMEs) from large suppliers, so you can segment performance by the FPC's tiered thresholds without a separate exercise at reporting time.

Many accounting systems let you set ageing categories by days or months with custom thresholds. Some also group transactions into a current period and several previous periods, with period lengths that can be adjusted for ad hoc reporting without changing your defaults.

How to prepare the report step by step

How do you know the report is complete before you reconcile it? The sequence below is designed so gaps don't surface on day three of close. If your company has signed the FPC or qualifies for PPR, this reconciliation also underpins your compliance submissions, so it needs to be tight.

Step 1: Post all outstanding entries

Generate the report only after all entries in both your AP sub-ledger and your GL have been posted. Unposted transactions are one of the most common causes of reconciliation failures, and they're also one of the most avoidable. Verify that both your AP sub-ledger and GL are in balance individually before attempting cross-reconciliation.

Step 2: Gather and verify invoice data

Pull your complete list of open invoices and cross-reference each one against two sources: your AP ledger and vendor statements. This comparison catches missing invoices, incorrect amounts, and transactions you haven't yet processed.

For month-end reporting, apply cut-off discipline: record all vendor invoices relating to the accounting period through the cut-off date. Raise accrual journal entries for any invoices received but not yet processed.

If you receive invoices in foreign currencies, record them at the transaction exchange rate on the invoice date. Check whether your accounting system revalues open foreign-currency payables at the period-end rate. This can shift balances between ageing buckets and create reconciliation differences that look like data errors but don't need fixing.

Step 3: Categorise each invoice by vendor and due date

Following the structure from your ageing buckets:

• Enter invoices not yet due in the Current column

• Enter overdue invoices in the column matching the number of days past their due date

• Enter credit memos as negative amounts and debit memos as positive amounts in the Current column for each vendor

• Total each row horizontally for a per-invoice figure

• Total each ageing column vertically for bucket-level subtotals

Where a single vendor has multiple invoices spanning different ageing buckets, each invoice gets its own line. Aggregating invoices of different ages into a single row loses the granularity you need for payment prioritisation.

Step 4: Reconcile the report to your general ledger

Your AP sub-ledger total, the AP trial balance, and the GL control account balance must all agree. If you've ever seen a gap appear that nobody can explain at first glance, it's almost always one of the causes below.

If totals differ, the most common causes are direct journal entries posted to the AP control account that bypass the sub-ledger, unposted entries, transactions dated outside the report period, and misallocated early payment discounts.

Step 5: Correct errors and produce the final report

Correct any recording errors with journal entries. After all corrections have been posted, run a final ageing report dated at month-end. This post-correction report is the version you should use for financial reporting and management review. Circulating intermediate versions risks decisions being made on incomplete data.

Common errors that distort your ageing report

It's day two of close, your ageing report total is £14,000 higher than the trial balance, and you don't know where the gap is. What's likely gone wrong? When your ageing report doesn't match your GL, the cause usually sits in one of these areas. Most are easy to fix once you know where to look, but any distortion that reaches your FPC or PPR submissions compounds the problem.

Duplicate invoices inflating liabilities. When the same invoice is processed twice, your report overstates what you owe, and payment runs may result in double disbursements. It's worth searching for duplicate invoice numbers and vendor name entries as a standard review step.

Credit notes sitting unapplied. Unapplied credit notes cause the report to overstate outstanding liabilities. Reconciling vendor statements against the ageing report monthly catches these before they migrate into older buckets.

Disputed invoices not segregated. Invoices under formal dispute shouldn't be treated the same as undisputed overdue invoices. Under prompt payment guidance, statutory interest applies only to undisputed, valid invoices. Consider maintaining a timestamped record of when each dispute was raised. This protects your position if the matter escalates.

Incorrect payment terms in the vendor master. Payment terms entered incorrectly place invoices in the wrong ageing bucket. Under the Late Payment Act, the default payment term is 30 days unless otherwise agreed, and payment terms longer than 60 days may be challenged if they're grossly unfair to the supplier. An invoice that appears to be within terms may already be accruing statutory interest at Bank of England base rate plus 8%, so periodic validation of your supplier master data is worth the effort.

All four errors share a root cause: data quality at the point of entry. The ageing report can only be as accurate as the information feeding it, which is why automation at the input stage makes such a difference.

How automation can reduce manual ageing report effort

If your team is still keying invoice data by hand, automation removes the errors that manual entry introduces: the typos and missed postings your ageing report would otherwise inherit. When you're processing hundreds of invoices a month under deadline pressure, manual errors scale with volume.

Optical character recognition (OCR), which reads invoice text automatically, reduces manual keying and the transcription errors that follow. Automated three-way matching, where the invoice is matched to the purchase order and goods receipt note, resolves invoices faster and prevents them from sitting unmatched in older ageing buckets.

For European mid-market finance teams, a spend management platform that captures and codes invoice data on upload and exports deduplicated transactions to your accounting system addresses this at source. Spendesk's accounting integrations with Xero, NetSuite, and Sage export pre-coded data in one click, so your accounting system receives transaction-level detail ready for invoice processing and ageing reports. That kind of cleaner input data makes reconciliation easier and frees up time your team would otherwise spend chasing discrepancies.

In practice, multi-entity teams face the same challenge at scale. GWI, a mid-market data agency based in the UK, needed consistent receipt capture across five countries to keep their ageing data clean. After adopting the platform, they reached 95% receipt compliance. Fewer unmatched transactions sitting in older buckets means a faster path to a reconciled report.

How to make the ageing report a recurring control

The preparation steps and the error checks aren't separate exercises. The five steps catch exactly the distortions described in the previous section: duplicates, unapplied credits, disputed invoices in the wrong bucket, and incorrect payment terms. When you embed that process into a monthly cadence, the compliance evidence builds itself.

Ideally, run a working version weekly for cash flow planning and produce a formal reconciled report at every month-end close. Share it with procurement and treasury so payment scheduling works from the same data. Research commissioned by the Department for Business and Trade and the Small Business Commissioner estimates that late payments cost the UK economy almost £11 billion per year. With the FPC's proposed fining system on the horizon, a reconciled ageing report from every close is the evidence you'll need.

If your team is still building this process manually, Spendesk brings invoice approvals, payment tracking, and month-end reporting together in one platform. Book a demo to see how it fits your AP workflow.

Frequently asked questions about AP ageing reports

How does an AP ageing report differ from an AR ageing report?

An AP ageing report tracks what your company owes suppliers, while an accounts receivable (AR) ageing report tracks what customers owe you. Together, they give a complete picture of working capital. Finance teams often review both side by side to forecast net cash positions and identify periods where outgoing obligations may exceed incoming collections.

Can your accounting software generate the report automatically?

Most modern accounting systems, including Xero, NetSuite, QuickBooks, and Sage, have built-in aged payables reports with customisable ageing periods, date ranges, and output formats. The report quality depends entirely on the quality of data going in, so the preparation steps in this guide still apply even when the report itself is automated.

How often should you run an AP ageing report?

It depends on your volume. Finance teams processing a high number of payables typically run a working version weekly to catch errors early and flag overdue invoices before they drift into older buckets. The formal reconciled version should be produced at every month-end close and retained as your compliance record for FPC and PPR purposes.

What should you do when a vendor disputes their ageing balance?

Start by pulling both your AP ledger record and the vendor's latest statement, then work through each open item line by line. The most common causes are invoices your team hasn't yet processed, credit notes that haven't been applied, or partial payments allocated to the wrong invoice. Document the resolution and update your ageing report before finalising it for the period.