What is an AP ageing report? How to read it and act on what it shows

On a Tuesday morning, the CFO takes a call from your biggest packaging supplier. Their statement shows Rp 64,800,000 outstanding, most of it more than 60 days old, and they will hold the next delivery until it’s paid. The CFO opens last month’s AP ageing report. It shows the same supplier at Rp 34,000,000, none of it overdue.

Both can’t be right, and the supplier is. Two invoices worth Rp 30,800,000 are sitting in a project manager’s inbox and were never entered. The ones that were entered had their due dates counted from the day someone keyed them in, not from the invoice date, so invoices that were weeks old look as if they’re not due yet.

An AP ageing report can only show what it knows, and this one knew less than the supplier did. This guide explains what goes into the report, which date to age from, how to read and reconcile it, where it goes wrong and how to make it reliable.

What is an AP ageing report?

An accounts payable (AP) ageing report lists the supplier invoices you haven’t paid yet, grouped by how long they’ve been outstanding or overdue, as at a given date. Each row is usually a vendor, and each column an age band, often called a bucket: not yet due, 1–30 days, 31–60, 61–90 and over 90.

It answers three questions at once: how much you owe suppliers, how much of that is late and who it’s owed to. Its mirror image is the receivables (AR) ageing, which does the same for what customers owe you.

The ageing is the detail behind one number in the general ledger: the balance of the accounts payable control account. On the same date, the two must agree. If they don’t, at least one of them is wrong.

What goes into the report

• The as-at date. The report is a snapshot. Run for 31 October, it shows what was open at the end of that day.
• Open invoices. Every posted supplier invoice that isn’t fully paid, with its invoice date, due date and the amount still open.
• Partial payments and credit notes. Applied to the invoices they settle, so only the remaining balance is aged.
• Debit balances. Down payments to vendors, overpayments and unused credit notes, where the supplier owes you. They should show as their own lines, not be netted away quietly.
• The age bands and grouping. Usually 30-day buckets, by vendor, and in a group of companies by entity as well.

Ageing by invoice date or by due date

The same invoice can land in different buckets depending on what the report counts from.

• By invoice date, the age is the number of days since the invoice was issued. It shows how old your debts are, whatever the terms.
• By due date, the age is the number of days past the due date, and anything not yet due sits in its own column. It shows what is late.

Take an invoice dated 15 September on 60-day terms, so due on 14 November. On a report for 31 October, ageing by invoice date puts it in the 31–60 day band, at 46 days old. Ageing by due date puts it in “not yet due”, with 14 days to go.

For paying suppliers, age by due date: a vendor on 60-day terms isn’t late at day 46. Keep the invoice date and the date received as columns, because the gap between them shows invoices that reached AP late. And count due dates from the date your terms say, usually the invoice date, never the date someone got round to entering it.

A worked example: reading the report and reconciling it

Here’s the summary of a mid-sized company’s AP ageing for 31 October, aged by due date:

Days past due	Invoices	Amount
Not yet due	42	Rp 612,400,000
1–30	17	Rp 184,750,000
31–60	6	Rp 96,300,000
61–90	2	Rp 41,500,000
Over 90	3	Rp 23,050,000
Total	70	Rp 958,000,000

About 64% is not yet due, and Rp 345,600,000 is overdue. The Rp 184,750,000 in the first overdue band is usually timing: invoices waiting for the next payment run. The three invoices over 90 days are a different kind of problem. Old balances are rarely bills someone forgot; they are usually stuck on something:

Over 90 days	Why it’s still open	Amount
Logistics vendor	Price differs from the PO, credit note requested	Rp 12,400,000
IT services vendor	Duplicate of an invoice paid in July	Rp 8,250,000
Cleaning contractor	On hold, faktur pajak missing	Rp 2,400,000
Total		Rp 23,050,000

Each needs a different person. The first needs procurement to get the credit note from the vendor. The second isn’t owed at all: it’s the July invoice entered a second time, and until it’s cancelled it can be paid twice. The third is waiting for the vendor to issue a faktur pajak, which your policy requires before payment.

Then check the total against the ledger:

Reconciliation, 31 October	Amount
AP control account, general ledger	Rp 971,200,000
AP ageing total	Rp 958,000,000
Difference	Rp 13,200,000

The difference traces to a manual journal: an accrual for goods received but not yet invoiced, posted straight to the AP control account instead of to accruals. The ageing doesn’t include it, because there is no invoice behind it. The fix is to reverse the journal, post it to accruals and stop manual journals reaching the control account at all. Until the two numbers agree, neither belongs in the month-end pack.

What to look for when you read it

• Overdue by vendor, not just in total. Rp 40 million overdue across thirty vendors is a process problem. The same amount with one key supplier is a delivery risk.
• Debit balances. A vendor with a debit balance owes you money: a down payment not yet settled, a credit note never used or an invoice paid twice.
• The trend. Compare with last month. Overdue growing while total payables stay flat means payment runs aren’t keeping up.
• What falls due next. The not-yet-due column, split by week, is the start of next month’s cash forecast.

Why AP ageing reports are so often wrong

• Invoices that never reached AP. The report only covers posted invoices. Bills in inboxes, desk drawers and WhatsApp chats are invisible until the supplier calls.
• Due dates counted from the wrong date. Terms counted from the entry date make late invoices look current.
• Payments not applied. A payment recorded against the vendor but not matched to its invoice leaves the invoice open in an old band, with an unapplied payment beside it, so the vendor looks more overdue than it is.
• Manual journals to the control account. The ledger and the ageing drift apart, and nobody can say which is right.
• Rebuilt by hand every month. Exported, cleaned up in a spreadsheet and sent days later, it describes a position that has already moved.

AP ageing in Indonesia

• Post the withholding against the invoice. When PPh 23 is withheld from a payment, the amount transferred is less than the invoice total. If the withholding isn’t posted against the invoice, the remainder stays in the ageing indefinitely, looking like an unpaid balance.
• Settle down payments against the final invoice. Advances paid before delivery (uang muka pembelian) show as debit balances. Apply each one to the invoice it belongs to, so neither stays open on its own.
• Track invoices waiting for a faktur pajak. Invoices held for a missing or incorrect faktur pajak keep ageing while they wait. Give them their own hold reason, so someone chases the vendor instead of the invoice quietly getting older.
• Show foreign-currency payables in both currencies. Invoices in US dollars or other currencies are translated at the month-end rate, so their rupiah value moves even when nothing has been paid. Age them in the invoice currency, with the rupiah value alongside.
• One ageing per PT, and one for the group. In a group with several companies, run the ageing for each entity so it reconciles to that entity’s ledger, and keep intercompany payables in their own section.

Signs your AP ageing needs work

You probably need to look at your AP ageing if any of these sound familiar:

• Supplier statements regularly include invoices you’ve never seen.
• The ageing total doesn’t match the AP control account, or nobody checks.
• The over-90 bucket holds the same items it held three months ago.
• Vendors have debit balances nobody can explain.
• Invoices paid net of PPh 23 still show a small open balance.
• The report is rebuilt in a spreadsheet every month-end.
• Finance finds out an invoice is overdue when the vendor calls.

The most overdue invoice is usually the one that isn’t on the report.

How to make your AP ageing reliable

1. Age by due date. Count due dates from the date your terms specify, and show the invoice date and the date received alongside.
2. Log every invoice on the day it arrives. Use one inbox or portal for all supplier invoices, and record each one before anyone approves it.
3. Apply everything. Match each payment, credit note, down payment and withholding to the invoice it settles, when it’s posted.
4. Reconcile to the ledger every month-end. Agree the ageing total to the AP control account, explain every difference and keep manual journals off the control account.
5. Give every overdue item a reason. Disputed, awaiting a credit note, awaiting a faktur pajak, awaiting a receipt or on hold. An item without a reason gets paid or escalated.
6. Review the oldest items with procurement every month. Disputes are usually theirs to resolve with the vendor.
7. Compare supplier statements. Each quarter, check your key suppliers’ statements against the ageing to find invoices that never reached you.
8. Stop building it by hand. Produce the report on a schedule from live data, so month-end is spent reviewing it, not assembling it.

---

How Procapy helps

Proca to Pay keeps the ageing complete at the source. Invoices are received by email, upload or vendor submission on the day they arrive, and ProcAI reads the vendor, amount, invoice date, due date, payment terms and any early-payment discount. The clock starts on the day of receipt, visibly, so an invoice can’t sit unnoticed in an inbox. Approved invoices go into payment runs that Procapy proposes from what is due, discountable and overdue, and payment status posts back to your ERP against each invoice, so the AP ageing reflects what has actually left the bank. Unmatched or returned payments are flagged for follow-up, and vendors can see the status of their own invoices, from received to paid.

Proca Agents take the monthly assembly off your team. An agent assembles recurring reports such as the AP ageing on the schedule you set, for example the last business day of the month, and the team reviews the numbers instead of building the spreadsheet. Agents can also draft replies to vendors and chase unanswered vendor questions on the cadence you choose, with every action logged with its reasoning.

Most teams are live in under two weeks. Book a walkthrough and bring your AP ageing and next month’s expected invoices, and we’ll build the payment calendar and the outflow forecast live. The cash flow and payments page has more on payment runs and forecasting.