Why the Accounts Payable Aging Report Won't Tie at Month-End | Corpay

It's day three of close, and your accounts payable aging report is $253,485 short of the AP control account in the general ledger. That number is the net of timing and posting differences, and most teams hunt for them vendor by vendor while inputs keep changing. A gap on day three is normal, but one you still can't explain on day five usually means a control problem.

Here's what the aging should tie to, the seven usual reconciling items, and a worked example down to one residual. Cutoff, accruals, payment rails, and a weekly routine that empties close week follow.

If you need the basics first, the step-by-step guide to building and reading an AP aging report covers them.

Key takeaways

• The open-item aging should equal the AP control account at the same as-of date, after documented reconciling items.

• Most variances come from posting-date mismatches, manual control-account entries, unposted batches, unapplied credits, payments in transit, FX and intercompany, and duplicate vendors.

• Received-not-invoiced accruals never show on the aging. That's by design, but it's where the completeness risk sits.

• Reconciling items should age too. One that's the same every month is usually an old manual entry.

• Reconciling weekly and locking the control account to subledger-only postings moves most of the tie-out work out of close week.

Contents

• What should the accounts payable aging report tie to?

• Why does AP reconciliation take so long at month-end?

• Which reconciling items keep the aging and the GL apart?

• What does an AP aging-to-GL reconciliation look like?

• How do cutoff and received-not-invoiced accruals change the tie-out?

• How do payment rails slow the AP tie-out?

• How can you shorten AP reconciliation without cutting corners?

• Payments that post back to your ERP

• Frequently Asked Questions

What should the accounts payable aging report tie to?

Your AP aging's open-item total should equal the GL's AP control account balance at the same date and time, after documented reconciling items. Accrued liabilities belong in a separate account.

The aging is a subledger view of open invoices, credit memos, and debit memos by age bucket. The control account should receive postings only from the AP subledger, so any other entry becomes a reconciling item.

Before you chase dollars, settle what "tie" means in your ERP. An aging run by document date and a GL run by posting date will disagree on every invoice dated one month and posted the next. Some "as of" reports also pick up later postings, so a day-five rerun may not match your day-one copy.

Auditors care because of completeness. According to PCAOB's AS 1105 on audit evidence, completeness means "All transactions and accounts that should be presented in the financial statements are so included." A tie-out proves only that the subledger and the GL agree, which is narrower than proving the liability is complete.

Why does AP reconciliation take so long at month-end?

The variance is the net of many small timing and posting differences. Most inputs aren't final until the last day, and teams usually find each item by comparing vendors one at a time instead of by category.

According to APQC's Open Standards Benchmarking data, the median monthly close, measured from the initial trial balance to completed consolidated statements, takes 6.0 calendar days. APQC's benchmark for the monthly close counts weekends in that figure. AP sits near the front of that sequence, so every day the tie-out runs late pushes back accruals, the adjusted trial balance, and consolidation.

Invoice approval adds its own lag, measured in APQC's invoice-to-approval cycle time. APQC's Open Standards Benchmarking data puts the median at 5.0 days from receipt of an invoice until it's approved and scheduled for payment. An invoice that arrives on the 26th is often still in approval at close, yet the goods behind it were received.

The variance you see is also a net figure. A $90,000 unposted payment and an opposite $90,000 manual entry net to zero, so a small variance can hide two large errors. Teams that stop once the gap looks small tend to find those pairs at audit.

There's no good neutral benchmark for how long the AP tie-out alone should take. Published close figures cover the whole process, so treat any AP-only number with suspicion unless its methodology is public.

Which reconciling items keep the aging and the GL apart?

Seven items explain most gaps between the aging and the control account. Some reverse on their own next month, and others accumulate until someone fixes them.

1. As-of date and posting-period mismatches put an invoice in one month on the aging and in another month in the GL.

2. Manual journal entries posted directly to the AP control account change the GL with no matching subledger record.

3. Unposted or parked invoices and failed payment postings leave the AP or payment system out of step with the GL, usually after an integration error.

4. Unapplied payments, vendor credits, and debit balances reduce what you owe in one ledger before the other catches up.

5. Payments in transit and void-and-reissue timing create items that are settled in one ledger and still open in the other.

6. FX revaluation and intercompany payables in multi-entity books often post in the GL only, outside the vendor subledger.

7. Duplicate vendor records and duplicate invoices inflate the aging and can split one vendor's balance across two records.

Items 1, 3, and 5 are mostly timing and tend to clear next month, though a failed posting clears only once someone reposts it. Items 2, 4, 6, and 7 are errors or judgment calls, and they accumulate. Sort every open line by whether it self-reverses, then work the non-reversing ones first, because they'll still be there at audit.

Multi-entity books make item 6 heavier. Picture a 12-entity NetSuite OneWorld company where intercompany payables revalue every month. Each revaluation hits the GL without touching the subledger, so the line recurs by design and needs a standing explanation.

Duplicates are the cheapest item to prevent upstream, through the duplicate-invoice and three-way-match checks in an AP automation best-practices guide.

What does an AP aging-to-GL reconciliation look like?

Start with the aging total, then add or subtract each documented reconciling item until you reach the GL balance. Whatever is left unexplained is the residual, and that's the part that needs investigating.

Here's how the $253,485 gap breaks down in an illustrative example with hypothetical figures for one entity closing Sept. 30.

Illustrative example with hypothetical figures.

Lines 2 and 4 are the ones to fix at the source. The freight accrual belongs in accrued liabilities, and the failed batch needs a repost plus a logged integration error so it doesn't happen again. Line 5 recurs by design and just needs a standing note.

Line 6 is the one teams live with longest. A residual that never moves is almost always an old manual entry or a conversion balance carried over from an ERP migration. I'd chase it once, with a dated history of the control account back to go-live, instead of re-proving it every close.

Reconciling items need their own aging. A line open for three closes should go to the controller with an owner and a date, because by then it's no longer timing.

How do cutoff and received-not-invoiced accruals change the tie-out?

Cutoff follows when goods or services are received, whatever the invoice date. Anything received by period-end but not yet invoiced is booked as an accrued liability, which is why it never shows on the aging.

Received-not-invoiced balances, often called GRNI, come from three-way-match data. A purchase order and a receipt with no invoice is the accrual candidate, and it surfaces in the matching exception queue. If you've followed how AP workflows have moved from paper to exception-based processing, you'll recognize that queue as the place GRNI gets built.

Services without receipts, such as legal fees and utilities, have to be estimated from contracts or run rates. Book them as reversing accruals dated the first day of the next period. Each entry then unwinds when the invoice posts, so nothing is counted twice.

Auditors test the other side with a search for unrecorded liabilities. They pull invoices received or paid after period-end and look for ones that belong to the prior period. Completeness risk concentrates here, because an aging can tie to the penny and still leave out a liability nobody has invoiced yet.

There's no universal precision threshold for accrual estimates. It's a materiality judgment you make with your auditors, and the answer for a $60 million distributor won't match a $3 billion manufacturer's. Agree on it in writing before year-end.

How do payment rails slow the AP tie-out?

Each payment method records, settles, and fails on a different clock. The more rails and portals you run, the more payments sit in the gap between "paid in AP" and "posted in the GL."

Checks in the US fell to 9.2 billion payments worth $24.45 trillion in 2024, according to the Federal Reserve's 2025 Payments Study. That's down 1.8 billion payments and $1.92 trillion from 2021. Each voided or reissued check reopens a liability, and each check released from a separate portal before the ERP records it becomes a timing item.

According to AFP's 2026 Payments Fraud and Control Survey, 76% of organizations experienced attempted or actual payments fraud in 2025. Checks were the most frequently targeted method, with 58% of organizations reporting check fraud. Each positive pay exception or stop-payment in the last week of the month becomes a void-and-reissue pair to clear.

Electronic rails have their own gaps. ACH payments settle after release and can come back as returns, and virtual card payments carry an authorization date and a later settlement date. Run three payment portals and you have three remittance files to post, each on its own schedule.

Days payable outstanding rebounded to 59 days in 2024 among large US public companies, according to The Hackett Group's 2025 U.S. Working Capital Survey. As terms stretch, more items sit in the 31-60 and 61-90 buckets, which adds lines to review without being a problem in itself.

The fewer places payment status lives, the fewer paid-but-unposted items you chase. Each extra portal must agree with the ERP before the control account can.

How can you shorten AP reconciliation without cutting corners?

Move the tie-out out of month-end week. Reconcile weekly, block non-subledger postings to the control account, and categorize reconciling items so the close only deals with new ones.

1. Run the aging and the GL at the same timestamp, with a documented report setting for posting date or document date.

2. Restrict manual journal entries to the AP control account, with an approval workflow and a monthly report of any that get through.

3. Reconcile weekly, or daily for high-volume entities, so month-end handles only the last few days.

4. Keep a standing reconciling-items schedule with categories and ages, and escalate anything open for more than two closes.

5. Reconcile vendor statements for your top vendors by spend each quarter to catch unrecorded invoices and duplicates.

6. Consolidate payment rails so payment status writes back to the ERP automatically.

Steps 1 and 2 are control fixes, and they cost almost nothing. The third and fourth move investigation out of close week. Statement reviews and fewer rails cut risk, since one catches what the aging never saw and the other removes posting failures at the source.

Most teams automate invoice capture first, and that helps approvals. The tie-out problem sits further downstream, at payment posting and control-account discipline, so weigh capture against payment write-back when you set the next project's priority. An AP automation software buyers' guide helps you check whether an ERP integration writes payment status back.

Corpay AP Automation: Payments that post back to your ERP

Failed postings and scattered payment status are the reconciling items that keep returning, and they're the items Corpay AP Automation is designed to reduce. It works alongside your ERP. Invoice capture, approval routing, and payments automation across virtual card, ACH, and check run in one workflow.

Payment status and confirmations sync back to NetSuite, Sage Intacct, Microsoft Dynamics 365, or Acumatica. Because the payment and its GL posting come from the same workflow, fewer paid-but-unposted items reach your reconciliation. With a two-way NetSuite integration, for example, the payment record flows back to the ERP instead of waiting on a manual upload.

Software handles the speed, and our team handles the messy middle. We manage vendor enrollment, payment delivery, exceptions, follow-up, and reconciliation support. That includes moving vendors off paper checks to virtual cards or ACH, which means fewer voids and reissues to clear at month-end.

Corpay offers 100+ ERP integrations through API, SFTP, or file-based connections. If failed postings or scattered payment status are behind your reconciling items, Talk to an Expert about tying payments back to your GL.

Frequently Asked Questions

Should the AP aging report match the balance sheet?

Yes, the AP aging report's open-item total should match the balance sheet's AP control account at the same as-of date, net of documented reconciling items. It won't match total current liabilities, because accrued liabilities and other payables sit in separate accounts. When your AP aging does not match the balance sheet and nothing documented explains the gap, check report settings and manual journal entries first.

How often should you reconcile the AP subledger to the general ledger?

Monthly is the minimum for any entity that closes its books monthly. Weekly works better for most mid-market and enterprise teams, and high-volume entities often reconcile daily. The shorter the interval, the fewer items you're explaining at once and the easier each one is to trace to a specific day's postings. Whatever the cadence, the month-end reconciliation should still be a full tie-out that a reviewer signs.

Are accrued liabilities included in the AP aging report?

No, the aging lists invoiced liabilities only. Received-not-invoiced goods and services sit in an accrued liabilities account, which is the practical line between accrued liabilities and accounts payable. A perfect tie-out can still leave the balance sheet incomplete if those accruals are missed. Review the accrual schedule next to the aging so both sides of the liability get a look before sign-off.

Why does my AP aging report change when I rerun it for a past date?

Many ERPs rebuild a historical aging from current data, so invoices, credits, or payments posted after the as-of date can change the result. Backdated entries into a closed period have the same effect. Save a copy of the aging at the moment you close, and document whether it runs by posting date or document date.

How do outstanding checks affect AP reconciliation?

An issued check has already relieved AP, so it's off the aging and out of the AP control account. Until it clears, it's a bank reconciliation item. AP gets pulled back in when a check is voided or reissued, since each void reopens the liability in both ledgers.

Who should own the AP-to-GL reconciliation?

The AP team should prepare it, since they know the vendors and the subledger best. Someone outside AP, usually a senior accountant or the assistant controller, should review and sign off. That separation matters most for manual journal entries to the control account, which an AP preparer shouldn't be approving alone.

David Luther

Product Marketing Program Manager

David Luther, MBA is a product marketing program manager with years of experience in commercial banking, finance, and technology sectors, with research and writing appearing in financial publications.

AP Automation

Payments Automation