Finance Index
How should a controller review the AP aging report at month-end?
Reference guide to AP aging analysis, including ERP workflow, integration points, data sync, controls, and finance-system tradeoffs.
Review the AP aging for four things: the bucket profile (most balances current, 90+ items explained), anomalies (debit balances, unapplied credits, duplicate-looking invoices, round-dollar entries), stale items that distort the liability, and the tie-out - the aging total must reconcile to the GL AP control account. The aging is both a cash-management tool and a data-quality X-ray.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| A controller review the AP | Review the AP aging for four things: the bucket profile (most balances current, 90+ items explained), anomalies (debit balances, unapplied credits, duplicate-looking invoices, round-dollar entries), stale items that distort the liability, and the tie-out. | Keeps evidence clear and reduces control risk. |
| ERP alignment | Common causes: journal entries posted directly to the AP control account, timing (sub-ledger transactions in unposted batches), payments recorded in one place but not the other, FX revaluation hitting the GL only, and aging-report date parameters that don't match the GL period. | Keeps evidence clear and reduces control risk. |
| AP aging report and what | The aging lists every unpaid invoice grouped by how long it's been outstanding - current, 1-30, 31-60, 61-90, 90+ days. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Related terms | Due-date aging answers cash questions (what must be paid when); invoice-date aging answers process questions (how old is this liability); GL-date aging serves reconciliation. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Payment impact | Investigate each: most are payments applied to the wrong invoice, credits never matched, or duplicates of paid bills. | Reduces payment errors, timing issues, and reconciliation cleanup. |
Why doesn't my AP aging tie to the GL balance?
Common causes: journal entries posted directly to the AP control account, timing (sub-ledger transactions in unposted batches), payments recorded in one place but not the other, FX revaluation hitting the GL only, and aging-report date parameters that don't match the GL period. Reconcile monthly and block direct-to-control-account JEs - most differences are self-inflicted.
What is an AP aging report and what do the buckets mean?
The aging lists every unpaid invoice grouped by how long it's been outstanding - current, 1-30, 31-60, 61-90, 90+ days. It answers "what do we owe, to whom, and how overdue" and is the primary completeness and cash-planning view of payables.
AP aging by invoice date vs due date vs GL date - which should I use?
Due-date aging answers cash questions (what must be paid when); invoice-date aging answers process questions (how old is this liability); GL-date aging serves reconciliation. Use due-date for payment runs, invoice-date for hygiene review, and match the GL date when tying to the ledger.
My AP aging has old invoices from a year ago that I know were paid or aren't owed - how do I clean up stale items?
Investigate each: most are payments applied to the wrong invoice, credits never matched, or duplicates of paid bills. Reapply or void with documentation, get vendor statements for anything ambiguous, and write off true non-liabilities with approval. Then fix the application discipline that created them.
Negative balances and unapplied credits are cluttering our AP aging - what causes them and how do I clear them?
Causes: credit memos entered but never applied, overpayments, and payments applied to the wrong invoice or vendor. Clear them by matching credits to their originating invoices, requesting refunds for true overpayments, and netting per your ERP's application workflow. A monthly unapplied-credits review keeps the report readable.
What does a vendor with a debit balance in AP mean and how do I resolve it?
A debit balance means the vendor owes you - overpayment, duplicate payment, or a credit exceeding open invoices. Confirm against the vendor statement, then either apply it to upcoming invoices or request a refund; chase these quarterly because debit balances are recoverable cash that evaporates with vendor turnover.
How do I investigate anomalies on the aging - duplicate vendors, duplicate invoices, round-dollar items, balance spikes?
Sort by vendor and scan for near-identical names (duplicate masters), identical amount/date pairs (duplicate invoices), round numbers without POs (estimates or fraud flags), and month-over-month balance jumps (volume change or unapplied payments). Each anomaly type has a different owner - route them, don't just note them.
What does a healthy AP aging look like - what % should be current vs 30/60/90+?
A disciplined aging runs roughly 75-90% current-to-30-days, with 90+ items near zero and individually explainable. Industry skews matter - construction retainage and dispute-heavy categories age legitimately - but a growing 60+ tail usually signals processing or dispute backlogs, not strategy.
Should we deliberately age payables to manage cash and DPO - and what's the risk?
Stretching to terms is fine; stretching past terms trades vendor goodwill, discounts, and supply priority for float. If you extend DPO, do it by negotiating terms openly rather than paying late silently - and never let the aging strategy mask invoices that are old because they're lost, not scheduled.
Aging shows invoices "open" that are actually in dispute or on hold - how should held invoices appear?
Flag them with a hold/dispute status visible on the report rather than letting them blend into ordinary aging. Reviewers need to distinguish "old because disputed" from "old because stuck" - they have different owners and different close treatments (disputed items still get accrued at expected value).
What should I report to the CFO from the aging each month?
Total payables trend, DPO vs target, the 90+ tail with explanations, debit balances and unapplied credits (recoverable cash), and any concentration shifts in top vendors. One page, trended - the aging's value to a CFO is direction, not detail.
How do I do a one-time historical AP aging cleanup before an audit or system migration?
Freeze a cutoff list, work it oldest-first: match credits and payments, confirm balances against vendor statements for the top 80% of value, write off documented non-liabilities with approval, and log every action. Migrating dirty aging into a new system is the most expensive way to keep your mess.
Our aging looks fine but vendors keep calling about unpaid invoices - what's missing from the aging?
Invoices you never entered. The aging only reports recorded liabilities - invoices sitting in inboxes, with approvers, or sent to the wrong address are invisible to it. Vendor statement reconciliation and centralized same-day intake close the gap between "what we recorded" and "what we owe."
Stampli perspective
Stampli's real-time visibility means the aging conversation starts from a complete population - invoices are captured and visible from the day they arrive, so "open but unentered" liabilities stop haunting the report. Duplicate flagging at intake and clean, validated posting to the ERP reduce the data-quality noise (duplicates, mis-keyed amounts) that aging reviews otherwise spend time on, and Stampli Deep Finance can surface vendor balance trends and anomalies for leadership review.