AP Month-End Close Checklist: 2026 Timeline & CSV

Your AP month-end close does not get slow on the last day of the month. It gets slow two weeks earlier, when invoices sit unprocessed, receiving data is not matched to POs, vendor statements are ignored, and accruals live in someone's inbox.

The fix is not a longer close meeting. It is a checklist that starts before cutoff and turns close week into review work. Use this AP month-end close checklist to lock the period, record every vendor obligation, reconcile the AP subledger, and hand the controller a clean close package.

For spreadsheet teams, download the checklist CSV and assign an owner to every row before the next cutoff.

AP Close Timeline: From Pre-Close to Package

The fastest teams move AP work left. By day one after cutoff, the job should be exception clearing and evidence review, not invoice hunting.

D-5

Pre-close sweep

Pull every invoice source and send cutoff reminders.

D-2

Exception clearing

Resolve PO matches, request statements, and prepare accrual inputs.

D0

Cutoff

Lock receipt time, tag late invoices, and prevent silent backdating.

D+1

Completeness

Post approved invoices, run duplicate checks, and tie AP to GL.

D+3

Close package

Deliver aging, accruals, reconciliations, and exception log.

Why AP Month-End Close Gets Stuck

Recent close benchmarks tell the same story from different angles. Ledge's 2025 month-end close benchmark found that 50% of finance teams take 6 or more business days to close, and the most time-consuming work is reconciliation, accruals, data cleanup, variance analysis, and department follow-up. Ventana Research, now part of ISG found that only 53% of companies complete the monthly close within six business days.

AP owns several of the blockers behind those numbers:

• Invoices are missing from the system when accounting starts reconciliations.
• Purchase orders, receipts, and invoices do not match cleanly.
• Accrual estimates depend on department replies instead of receiving data.
• Vendor statements expose credits, short pays, and unapplied payments too late.
• AP aging reports are rebuilt after corrections instead of reviewed from live data.

That is why the best AP month-end close checklist starts before the accounting period ends. If AP waits until day one after close to find invoices, every downstream accounting task starts late.

Q2 2026 AP Close Calendar

For Q2 2026, the final calendar day is Tuesday, June 30, 2026. US teams that observe Independence Day on Friday, July 3, should not plan controller review for that day unless the team explicitly works the holiday. Move final AP sign-off to Monday, July 6 if needed.

Date	Close milestone	AP owner action
Friday, June 26	D-2 business days	Send cutoff reminder, clear open invoice exceptions, request statements from top vendors.
Monday, June 29	D-1 business day	Run final pre-close invoice sweep across email, Slack, AP inbox, and supplier portals.
Tuesday, June 30	Cutoff	Lock AP receipt cutoff time, timestamp late invoices, freeze manual backdating.
Wednesday, July 1	Close day 1	Finish invoice entry, PO matching, duplicate checks, and preliminary AP aging review.
Thursday, July 2	Close day 2	Book accruals, reconcile vendor statements, resolve AP subledger differences.
Friday, July 3	Holiday risk	If observed as a holiday, only urgent exception clearing should remain.
Monday, July 6	Close day 3 or 4	Deliver AP close package to controller with open exception log.

If your team closes in India, the same Q2 close lands on Tuesday, June 30, but without the US July 3 holiday conflict. Keep the three-day sequence: cutoff Tuesday, AP processing Wednesday, accruals and reconciliations Thursday, final AP package Friday.

The AP Month-End Close Checklist

Use this as the working checklist. The CSV version includes owners, evidence requirements, and automation shortcuts.

When	Task	Evidence to attach	Pass condition
D-5 to D-3	Send invoice and accrual cutoff reminders to department heads.	Reminder message and deadline list.	Every department knows the AP cutoff time.
D-3	Pull invoices from AP inbox, Slack, portals, mail, and shared drives.	Inbox export or intake queue.	No invoice source is unchecked.
D-2	Resolve high-value matching exceptions.	PO, receipt, and invoice match log.	All material PO-backed invoices are matched or listed as exceptions.
D-2	Request statements from top 20 vendors by spend or invoice count.	Vendor statement folder.	Statements received or follow-up owner assigned.
D-1	Review open POs and receipts not yet invoiced.	Open receipt and GRNI report.	Accrual candidates are complete.
Cutoff	Lock invoice receipt cutoff and prevent backdated AP entries.	Cutoff timestamp and period policy.	Late invoices are tagged to the correct period.
Day 1	Enter, code, and approve all in-period invoices.	Approved invoice queue.	No material invoice is waiting for data entry.
Day 1	Run duplicate invoice checks before final posting.	Duplicate review report.	Suspected duplicates are blocked or cleared.
Day 1	Reconcile AP subledger to the general ledger control account.	AP subledger tie-out.	Difference is zero or fully explained.
Day 2	Book AP accruals for received-not-invoiced goods and services.	Accrual schedule and support.	Every material accrual has owner, amount, and reversal date.
Day 2	Reconcile vendor statements and unresolved credits.	Statement reconciliation log.	Material vendor differences are resolved or documented.
Day 2	Review AP aging for old balances and negative vendor balances.	AP aging report.	Stale items and credits have an action owner.
Day 3	Prepare AP close package for controller review.	Close package folder.	Controller can review without asking AP for missing support.
Day 3	Archive support and update next-month issue log.	Workpapers and lessons log.	Recurring blockers are assigned before next pre-close.

Five Workstreams That Actually Cut Close Time

1. Invoice Processing Backlog

The close risk: Invoices pile up all month. By the time accounting starts close, AP is still entering bills, coding line items, chasing approvals, and matching POs. Every downstream task is blocked until invoices are in the system.

Checklist actions:

• Process invoices daily during the final week, not in one batch after cutoff.
• Confirm every received invoice has vendor, invoice number, date, amount, due date, GL code, department, and approval status.
• Complete three-way matching for PO-backed invoices before day one.
• Route exceptions by materiality, not by arrival order.
• Review invoice processing time metrics to spot the vendors or departments that create late-cycle drag.

Automation shortcut: Automated invoice scanning should capture invoices on arrival, check for duplicates, read line items, and route approvals before close week. AP still reviews exceptions, but the routine data entry work is already finished.

2. Expense Accruals

The close risk: Goods and services were received, but the invoice has not arrived. AP and accounting then estimate accruals from open POs, receiving reports, emails, and department replies. If those inputs are late, the close slips.

Checklist actions:

• Pull open POs with receipts but no invoice.
• Review recurring vendors that usually bill after month-end.
• Ask department owners for material services received but not yet invoiced.
• Record accrual amount, vendor, department, GL account, support, and reversal date.
• Compare this month with prior-month accrual reversals to catch misses.

Automation shortcut: Use PO, receipt, and contract data to maintain a running accrual view during the month. When AP can see what was ordered, what was received, and what was invoiced, the accrual is the gap. That is much faster than asking every department to remember what happened.

3. Vendor Reconciliation

The close risk: Vendor statements expose the messy items: credits not recorded, short-paid invoices, duplicate invoices, payment application errors, and invoices the vendor says are open but AP cannot find.

Checklist actions:

• Reconcile the top 20 vendors by spend, invoice volume, or recurring close issues.
• Match statement balances to the AP subledger.
• Investigate open items above your materiality threshold.
• Confirm credit memos, refunds, and vendor prepayments are recorded.
• Log unresolved items with owner, amount, vendor contact, and expected resolution date.

Automation shortcut: Treat reconciliation as continuous work. If payments, invoices, and credits are matched during the month, the close-week task becomes exception review. For the mechanics, see payment reconciliation and AP aging report automation.

4. Period Cutoff

The close risk: Invoices dated the 30th arrive on the 3rd. Payments initiated in one period clear in the next. Someone backdates an entry to "clean it up." Cutoff mistakes create reclasses, audit questions, and controller review loops.

Checklist actions:

• Define the AP cutoff date and exact time before the final business day.
• Timestamp every invoice when received, not when entered.
• Tag late invoices as late-arriving and route them through the accrual process.
• Block manual backdating unless controller-approved.
• Keep a cutoff exception log with reason and approval.

Automation shortcut: System-enforced cutoff rules make the policy real. The system should assign period based on receipt timestamp, invoice date, PO receipt, and approval status, then flag exceptions instead of letting users silently backdate.

5. AP Reporting and Review

The close risk: The controller needs an AP package, but the underlying data is still moving. AP aging changes after reconciliations. Accrual support is in separate folders. Vendor exceptions live in email. The review becomes a scavenger hunt.

Checklist actions:

• Generate the AP aging report after invoice posting and again after accrual review.
• Tie the AP subledger to the GL control account.
• Summarize open exceptions by amount, vendor, owner, and target resolution date.
• Include AP KPIs such as invoice cycle time, backlog count, duplicate holds, aging over 60 days, and accrual adjustments.
• Store workpapers in one close package folder with a stable naming convention.

Automation shortcut: When invoices, approvals, payments, and reconciliations update continuously, reporting is not a build step. It is a review step. That is how AP moves from "we need two days to assemble support" to "the support is already there."

Three-Day AP Close Routine

The practical target is not a magical zero-day close. It is a close where AP is not the blocker.

Day 0: cutoff discipline

Lock the cutoff, label late invoices, and stop silent backdating. Any invoice received after cutoff either belongs to the next period or goes through accrual review. Do not let AP clerks solve timing issues one invoice at a time.

Day 1: invoice completeness

Finish invoice entry, approvals, coding, PO matching, and duplicate checks. If a material invoice cannot be approved, it should appear on the exception log with owner and next action. The controller should not discover it during review.

Day 2: accruals and reconciliations

Book received-not-invoiced accruals, reconcile top vendor statements, and tie the AP subledger to the GL. This is where AP proves the period is complete.

Day 3: close package

Deliver the AP aging, subledger tie-out, accrual schedule, vendor exception log, duplicate hold report, and open issue list. The package should answer the controller's next question before they ask it.

Ramp's month-end close guide frames close work in pre-close, execution, and post-close phases. AP should use that same structure, but with a stronger cutoff rule: anything not ready by day one must be either accrued, listed as an exception, or moved to the next period with evidence.

What to Measure After This Close

Do not judge the AP month-end close by whether the team survived it. Track the blockers that predict next month's delay:

Metric	Good target	Why it matters
Open invoices at cutoff	Down month over month	Shows whether invoice intake is under control.
PO match exceptions older than 5 days	Under 10% of PO invoices	Measures whether receiving and AP are aligned.
Accrual adjustments after controller review	Down 50% in 90 days	Shows whether AP accrual support is improving.
Vendor statement exceptions over threshold	Owner assigned within 1 business day	Prevents old vendor issues from reappearing each close.
AP close package ready time	Day 3 by noon	Gives accounting time to review without weekend work.
AP-caused reclass entries	Down month over month	Proves the close is cleaner, not just faster.

Tie these to your broader accounts payable KPIs. A faster close that creates more reclasses is not a win. The goal is speed with fewer corrections.

Where Ken Fits

Ken helps AP teams remove the first bottleneck: invoice intake. Drop an invoice in Slack and Ken extracts vendor details, line items, due dates, taxes, and totals; checks for duplicates; routes approval; and preserves the thread context AP needs for close support.

That means fewer invoices hiding in inboxes, fewer manual entry delays, and a cleaner audit trail when accounting asks why a bill was approved, held, or accrued. It does not replace controller judgment. It gives AP the evidence package earlier.

FAQ

What should AP complete before month-end close starts?

AP should complete invoice intake, PO matching for material invoices, duplicate checks, cutoff reminders, and the first review of open POs before close starts. The goal is to make day one after month-end about clearing known exceptions, not discovering missing invoices. If AP starts close with unprocessed invoices from multiple inboxes, accruals and reconciliation will start late.

How long should the AP month-end close take?

AP should aim to finish its close package within 3 business days after cutoff. The full finance close may take longer because accounting, FP&A, payroll, AR, and tax have their own workstreams. AP is on track when invoice completeness, accrual support, vendor reconciliation, AP aging, and the subledger tie-out are ready by day three.

What is included in an AP close package?

An AP close package should include the AP aging report, AP subledger to GL tie-out, accrual schedule, vendor statement reconciliation log, duplicate invoice hold report, cutoff exception list, and unresolved issue tracker. Each item should have an owner, support file, materiality threshold, and review status so the controller can approve without chasing AP for evidence.

What causes AP close delays most often?

The most common AP close delays are late invoices, unresolved PO match exceptions, missing accrual support, vendor statement discrepancies, cutoff confusion, and manual reporting. These are usually process problems from earlier in the month. If AP only works on them after cutoff, the close becomes a catch-up exercise.

Can a small AP team use this checklist without close software?

Yes. A small team can use the downloadable CSV with owners, dates, and evidence links. The discipline matters first: daily invoice intake, clear cutoff rules, weekly vendor follow-up, and a running accrual log. Software helps when invoice volume grows, but a two-person AP team with a clean checklist will close faster than a larger team that batches everything at month-end.

Related Posts

• Invoice Processing Time Metrics: Benchmarks That Expose AP Bottlenecks
• AP Aging Report Automation: Stop Rebuilding the Same Spreadsheet
• Payment Run Scheduling Without Burning Vendor Trust
• Invoice GL Coding Automation: Workflow & Controls