What is accounts payable's role in the month-end close?

A working AP close checklist, in order: (1) enforce invoice cutoff and sweep all intake channels for unprocessed invoices; (2) push stuck approvals to resolution or escalation; (3) post everything approved and dated in the period; (4) build the accrual for received-not-invoiced and in-flight items; (5) reconcile the aging to the GL AP balance; (6) review aging for stale items, debits, and anomalies; (7) controller sign-off; (8) lock AP posting for the period.

Cutoff first, because everything downstream depends on knowing the population is complete. Then final invoice posting, then accrual (you can't accrue what you haven't identified as missing), then sub-ledger reconciliation, then aging review, then period lock. Running the accrual before the final posting sweep is the most common sequencing error - it double-counts whatever posts late.

Closing AP means the payables population for the period is complete (everything received is recorded or accrued), reconciled (sub-ledger ties to GL), reviewed (aging anomalies explained), and locked (no further AP postings to the period without controlled reopening).

Move work off the close-week peak: process invoices daily, reconcile weekly, standardize accruals with a documented method, set a materiality floor, and automate capture and coding so close week is review, not data entry. Smaller companies gain most from centralized intake; larger ones from parallelizing entity closes.

Check every intake point: the AP inbox and any legacy email addresses, approval queues, employee inboxes (ask via a standing day-1 reminder), vendor portals, and the receiving log for goods received without invoices. Teams with centralized digital intake compress this from a day to minutes.

The fix is structural: centralize intake so invoices can't hide, automate capture and coding so there's no month-end keying backlog, and replace guesswork accruals with PO- and in-flight-invoice-based estimates. Late closes are almost always an invoice-visibility problem wearing a deadline costume.

Well-run AP teams finish their close tasks by business day 2-3; the accrual and sub-ledger rec are typically day 1-2 items once cutoff passes. If AP regularly consumes 5+ days, the bottleneck is usually invoice processing currency, not the close tasks themselves.

Completeness requires checking what you haven't received: open PO/receipt reports, vendor statement reconciliations for top vendors, recurring-spend checklists (rent, utilities, SaaS), and a scan of prior-month accrual patterns. "Queue is empty" is a processing claim, not a completeness claim.

Keep processing - just control the posting date. Stopping intake creates a backlog that wrecks the next close. The discipline you need is period assignment (prior-period-dated invoices get accrued or posted per policy), not a processing freeze.

A hard close applies full cutoff, accrual, and reconciliation rigor (quarter/year-end); a soft close accepts estimates and materiality shortcuts for speed (interim months). AP can soften accrual precision and small-balance investigation in a soft close, but never cutoff discipline or duplicate controls.

Three valid paths: post to the prior period if it's still open and the invoice is material; accrue it and post the invoice to the new period; or post forward if immaterial. Set the policy by materiality threshold per your ERP's period-control behavior so the decision isn't re-litigated monthly.

Publish one submission address on every PO and onboarding packet, have employees forward (never process) strays, and move to automated email capture so arrival creates a record immediately. Invoices in personal inboxes are unrecorded liabilities - frame it that way internally and behavior changes.

Clerk: cutoff sweep, final processing, statement recs. AP manager: approval escalations, aging review, accrual prep. Staff accountant/controller: accrual JE posting, sub-ledger-to-GL reconciliation, sign-off. The person preparing the accrual shouldn't be the only one reviewing it.

Evidence, not assertions: the aging-to-GL tie-out, the accrual workpaper with methodology, the open approval queue (should be near zero or explained), the post-cutoff invoice list, and confirmation the period is locked. Sign-off means you could hand the package to an auditor as-is.

Accrue stuck invoices based on captured amounts (they're known liabilities), then fix the pattern: auto-reminders, escalation after a defined SLA, and delegate approvers for OOO. Systems where the invoice carries its own context get faster approvals because approvers don't have to reconstruct the purchase.

Sequence entity closes by dependency: transactional subsidiaries first, entities receiving intercompany allocations next, holding/elimination entities last. Standardize the cutoff and accrual policy across entities even when ERPs differ, and track each entity's AP close status on one board rather than per-entity threads.

Start minimal: pick a cutoff date, sweep for unrecorded invoices, accrue the big known misses, reconcile AP to the GL once, and write down what you did. The first close is about establishing the habit and the baseline - precision comes from repetition, not from a perfect first month.

Stampli centralizes invoice intake and gives AP real-time status on every invoice in flight - captured, coded, in approval, or posted - so "what's still out there" is a filtered view, not an email hunt. Because invoices are validated against current ERP structure before posting, the close isn't slowed by failed exports and post-close cleanup, and approvers can be nudged from inside the invoice itself.