Open-payables control

Accounts payable aging review checklist

An accounts payable aging report is a useful queue, not a final statement of what must be paid today. Old balances can represent valid invoices, missing receipts, disputed quantities, unapplied credits, blocked bank changes, duplicate documents, partial payments or stale master data. Each needs a different owner and next action.

Discuss AP aging View buyer resources

By MINJI Wholesale DeskUpdated August 9, 2026

Direct answer

The short version

Review accounts payable aging by defining the reporting entity, supplier population, ledger, account, currency, as-of date, time zone and aging basis before reading any bucket. Reconcile the report total to the accounts payable control balance and retain excluded, unposted, parked, held, debit and credit populations. At document level, validate supplier, invoice or credit identity, posting and document date, contractual due-date basis, currency, original amount, open amount, purchase order, receipt or service evidence, approval, dispute, hold, payment and statement references. Recalculate due date from the supported payment terms rather than assuming invoice date plus a default number of days. Keep not-yet-due, due, disputed, blocked, awaiting receipt, scheduled, paid-unapplied, credit, duplicate-suspect and stale-research states separate. Apply approved payments, credit notes, refunds and offsets once, then investigate negative and zero-net supplier positions that hide old gross items. Prioritize by actual due status, operational risk, supplier relationship, amount, discount or penalty terms from the agreement, fraud or bank-change controls and dependency—not age alone. Assign every material aged item an owner, evidence-based reason, next action and date. Resolve root documents and supplier-account differences before writing off, netting or changing dates. Close an aging exception only when the source document, ledger, payment or credit and supplier statement support the same remaining balance.

Use this before requesting a quotation

Review the full payable population without hiding disputes or moving dates

Define population, date and aging logic

State legal entity, business unit, supplier accounts, ledger, posting status, currency, as-of date, extraction time and time zone. Define whether age is measured from invoice date, posting date, due date or another field and label bucket boundaries exactly. Aging and due status are not the same. Include approved and unapproved invoices, parked documents, debit balances, credit notes, payment proposals, disputed and blocked items in controlled populations even if the main report presents them separately. Record exclusions with count and value. Freeze or version the extract so later review does not mix live changes with the original total. For multi-currency accounts, retain document currency and ledger currency separately. Do not combine supplier aliases until the vendor-master relationship is validated. A dashboard count is incomplete if interfaces, manual journals or recently received documents sit outside the extract.

Prove completeness and ledger reconciliation

Reconcile the aging total to the accounts payable control account or approved ledger source for the same entity, date and currency basis. Bridge unposted invoices, manual entries, payments in transit, foreign-exchange revaluation, supplier debits, account credits and timing differences. Compare the supplier-document population with intake channels, purchase orders, receipts, invoice workflow and payment records to find missing or duplicated items. Sample the report to source documents and sample source documents back to the report. Keep a reconciling-item register with amount, cause, owner and target date instead of forcing totals through an unexplained journal. Validate that canceled, reversed and paid invoices do not remain open and that a payment file not yet settled is not marked as bank-cleared. Review unusual negative supplier balances and zero-net accounts because old invoices and credits may offset while remaining unapplied.

Validate document identity and due-date basis

For each material or old item, confirm supplier legal entity and account, document type, unique number, invoice and posting dates, currency, original and open amount, purchase order, receipt or service, approval and payment terms. UNECE INVOIC structures document identity, references, dates, currency, amounts, payment and line information; use the actual supplier document and agreement as evidence. Reperform the due date from accepted terms, delivery or acceptance milestone when applicable, and approved calendar convention. Do not edit the invoice date or due date merely to move an item out of a bucket. Record disputed due-date basis with both positions. Detect duplicate invoice number variations, a credit posted as an invoice, installment schedules collapsed into one date and an invoice assigned to the wrong supplier account. Keep system-calculated and reviewed due date visible when they differ.

Classify the real open-item state

Assign a reason that leads to action: valid not due, valid due, awaiting approval, missing PO, missing receipt or service evidence, quantity or price dispute, quality claim, credit expected, credit unapplied, payment scheduled, payment rejected, paid but unapplied, duplicate suspect, bank-change hold, supplier statement mismatch, legal hold or stale unknown. Record exact affected amount rather than placing an entire invoice on hold when only one line is disputed, unless policy requires it. Keep operational acceptance, accounting approval and payment release as separate gates. A blocked payment can be valid and overdue, while an old invoice can be invalid or already settled. Link the underlying case and its owner. Avoid vague codes such as query or pending without the missing evidence, responsible party and next review date. Require authority for overrides and preserve the original classification history. Add a cause hierarchy rather than one flat label: process stage, defect family and actionable detail. For example, match failure can divide into missing receipt, wrong unit, over tolerance or duplicate receipt application; payment failure can divide into rejected file, account restriction, beneficiary mismatch or returned transfer. Store who owns the next action and who merely supplied information. Identify dependencies and blocked-by links so several teams do not chase the supplier for the same document. Mark parked items that have never entered approval separately from deliberately blocked approved items. Retain the date a dispute began, last substantive evidence, promised answer and escalation path. This vocabulary turns a bucket total into a repair queue and supports trend analysis without exposing confidential free text.

Apply credits, payments and supplier statements

Match credit notes, debit notes, refunds, advances, deposits, withholding, partial payments and authorized offsets to the specific open documents they affect. UN/CEFACT remittance guidance supports reconciling payment detail with outstanding invoices, credits and debits and then comparing the advised amount with bank receipt. UNECE STATAC supports seller-to-buyer account-status communication for reconciliation. Compare supplier statement and buyer subledger by document number, date, currency, original amount, application and balance. Identify an invoice missing from either side, cash applied to the wrong document, credit used twice, payment in transit, refund not posted and an old supplier credit masking a current payable. Do not net different legal entities or currencies without qualified authorization. Leave unapplied cash and credit visible until allocation is supported.

Prioritize and resolve aged items

Prioritize from supported due status, contractual consequence, supply dependency, value, age, repeated dispute, fraud or bank-detail risk and effort to resolve. Do not automatically pay the oldest item when identity, receipt, beneficiary or duplicate checks are incomplete. For each material item, record the decision, evidence request, owner, supplier contact through validated channels and next date. Resolve missing documents at the source, approve valid receipts, issue or reconcile claims, obtain credit, correct allocation, retry or reverse failed payments and escalate genuine disputes under authority. Any write-off, waiver, settlement or date change requires finance and legal policy, not housekeeping pressure. Group similar root causes for efficient correction while retaining document-level decisions. Review approaching-due invoices early so aging is not merely a report of failures that have already matured. Use a work queue that separates cash scheduling from defect remediation. Suggested operational lanes include clean-and-due, clean-and-future, receipt chase, approval chase, price variance, quantity variance, supplier master review, duplicate investigation, blocked beneficiary, unapplied payment, unapplied credit and dormant balance research. Rank within a lane using documented rules, then display why the item moved. Track touches, handoffs, reopenings and days without activity; a recently discussed ninety-day item may need a different intervention from one nobody owns. Map clusters to intake source, approver group, buying team, receiving site, interface and supplier-account hierarchy. Examine month-end spikes, future-dated documents, back-posting, weekend due dates and invoices just below approval thresholds as data-quality or control signals, not proof of wrongdoing. Keep cash forecast date, accounting due date, supplier-requested date and internal action date in separate columns. When payment is intentionally scheduled later under supported terms, retain the valid due-date calculation instead of moving it to make the queue look current.

Close the review and improve controls

Complete the review when report and ledger reconcile, each material aged item has an evidence-based status and owner, completed payments or credits are applied once, and stale exceptions have a disposition under authority. Record opening and closing population, movements, resolved value, new overdue value and residual by reason. Track due-date accuracy, approval age, missing receipt, dispute age, credit application, rejected payment, duplicate alert, statement mismatch and owner follow-through. Compare trends by process and supplier only after controlling for volume and terms. Sample closed items back to bank and source evidence and sample later supplier statements for reappearing balances. Use recurring patterns to repair purchase-order terms, receipt timing, invoice intake, vendor master, credit application or payment release. Never improve the metric by changing dates, hiding held documents or excluding credits; explain the population honestly. Publish a roll-forward from opening open items through new invoices, corrections, payments, credits, reversals, reclassifications and closing open items, with document counts and values. Add a cohort view by original entry month so resolution can be distinguished from new volume replacing old volume. Track migration between current, early-warning and overdue bands without treating a disputed item as healthy merely because it moved accounts. Measure first-pass match, unassigned owner, inactive days, reopened cases and supplier-statement recurrence. Test concentration across the largest balances and the long tail of small documents; each creates different workload and exposure. Review debit balances independently because a conventional payable dashboard may suppress them. Preserve snapshots and logic version so trend changes caused by new bucket definitions are labeled rather than presented as operational improvement.

Reusable buyer brief

Accounts payable aging review record

Entity, ledger/accounts, supplier population, as-of time and currencies:
Aging basis, bucket boundaries, included/excluded statuses and extract version:
Report total, AP control balance and reconciling items:
Supplier, invoice/credit ID, type, dates, currency and open amount:
PO, receipt/service, approval, dispute and supporting evidence:
Contractual terms, system due date, reviewed due date and difference:
Not-due/due/hold/dispute/payment/credit/duplicate state and reason:
Supplier statement, remittance, bank and account-application result:
Priority basis, owner, requested evidence, action and next date:
Partial payment, credit, refund, offset and residual amount:
Decision/override/write-off authority and retained history:
Opening/closing balance, root cause, control action and closure:

Fill only the details relevant to your request

Before you send the request

Questions buyers often ask

Should AP aging use invoice date or due date

State the report basis explicitly. For payment decisions, validate the due date from the actual terms and supported triggering event rather than relying on age alone.

Why can an old payable remain unpaid

It may lack approval or receipt, be disputed, blocked for beneficiary or duplicate review, have an unapplied credit or payment, or be an invalid stale item.

How are supplier credits handled in aging

Keep them visible, validate and apply them once to supported documents, and review negative or zero-net accounts that hide old gross balances.

What makes an AP aging review complete

The report reconciles to the ledger and every material aged item has a supported status, owner, next action or authorized final disposition.

Keep the request specific

Aging is a management view, not a universal payment decision

Payment due dates, discounts, penalties, setoff, tax, write-off, sanctions, currency and accounting treatment depend on actual agreements, policies and jurisdictions. Use qualified finance, tax and legal review. Do not bypass beneficiary verification, duplicate checks, separation of duties or receipt controls to improve an aging metric. Protect invoice and bank information, and contact suppliers through validated channels. Keep report exclusions and date logic visible: changing an age field or hiding a held invoice does not resolve the obligation or the underlying operational defect.

Send this checklist on WhatsApp

Editorial method

How this guide was prepared

MINJI starts with population and ledger completeness, then validates document identity, due-date basis, operational evidence and real open-item state. UNECE INVOIC structures the payable document; UN/CEFACT remittance guidance supports payment and credit allocation; UNECE STATAC supports supplier-account reconciliation. The review samples both report-to-source and source-to-report and refuses to improve aging by hiding held items or changing unsupported dates.

UNECE UN/EDIFACT — Invoice MessagePrimary invoice structure covering document identity, parties, references, dates, lines, amounts, currency, tax and payment information.
UN/CEFACT — Cross Industry Remittance AdvicePrimary process model for applying payments across outstanding invoices, credit notes and debit notes and reconciling the bank amount.
UNECE UN/EDIFACT — Statement of Account MessagePrimary seller-to-buyer account-status structure used as an aid to reconciling open commercial documents, amounts, dates and currency.

Ready with the key details

Discuss a wholesale request

Send the product reference, estimated quantity and destination so the conversation starts with useful context.

Continue on WhatsApp