Finance Index
What AP close metrics should we track, and what are the benchmarks?
Reference guide to close metrics benchmarks, including ERP workflow, integration points, data sync, controls, and finance-system tradeoffs.
Track five: days to complete AP's close tasks (benchmark: by day 2-3), percentage of received invoices fully processed at cutoff (95%+), accrual estimate-vs-actual variance (inside 5-10%), post-close AP adjustments per month (trending to near zero), and invoice cycle time received-to-posted (days, not weeks). Together they measure whether AP enters close current, estimates well, and stays closed.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| What AP close metrics should | Track five: days to complete AP's close tasks (benchmark: by day 2-3), percentage of received invoices fully processed at cutoff (95%+), accrual estimate-vs-actual variance (inside 5-10%), post-close AP adjustments per month (trending to near zero), and invoice cycle time received-to-posted (days, not. | Keeps close, reporting, and system records aligned. |
| How many days to close | Survey medians cluster around 6-8 business days overall; SMBs range widely (3-10+ depending on automation), mid-market typically 5-8, enterprise 5-10 with consolidation complexity. | Keeps accounting records aligned with the ERP. |
| What % of the close | AP-driven tasks (cutoff, accruals, sub-ledger rec) typically occupy the first 2-3 days and feed everything downstream, so AP delay propagates - but in time studies the true long pole is often inventory, revenue, or consolidation. | Keeps close, reporting, and system records aligned. |
| Build a close dashboard | Task completion vs plan (red/yellow/green by owner), invoices remaining unprocessed/unapproved/unposted, reconciliation status by account, accrual booked vs pending, and blockers by name. | Keeps close, reporting, and system records aligned. |
| Workflow | Manual shops run roughly 500-1,000 invoices per FTE monthly; automated teams reach several thousand. | Reduces payment errors, timing issues, and reconciliation cleanup. |
How many days to close is normal by company size?
Survey medians cluster around 6-8 business days overall; SMBs range widely (3-10+ depending on automation), mid-market typically 5-8, enterprise 5-10 with consolidation complexity. Top-quartile performers close in 3-5 days at every size - the differentiator is processing currency and accrual standardization, not headcount.
What % of the close timeline does AP typically consume - is AP usually the long pole?
AP-driven tasks (cutoff, accruals, sub-ledger rec) typically occupy the first 2-3 days and feed everything downstream, so AP delay propagates - but in time studies the true long pole is often inventory, revenue, or consolidation. Measure before assigning blame; AP is the most visible queue, not always the slowest.
How do I build a close dashboard - what should I track daily during close week?
Task completion vs plan (red/yellow/green by owner), invoices remaining unprocessed/unapproved/unposted, reconciliation status by account, accrual booked vs pending, and blockers by name. Update from systems where possible; a dashboard fed by asking people is a status meeting wearing a costume.
What's the benchmark for invoices processed per AP FTE per month, and how does it correlate to close speed?
Manual shops run roughly 500-1,000 invoices per FTE monthly; automated teams reach several thousand. The close correlation is indirect but real: higher per-FTE throughput almost always reflects automation, and automation is what delivers the day-1 processing currency that makes AP's close fast.
What post-close adjustment rate is acceptable - how many late entries after close?
Best practice trends toward zero material post-close AP entries, with a tolerance for a handful of immaterial true-ups monthly. Track count and dollar value; a stable count with shrinking value means estimates improving, while growing counts mean the close is reporting before the books are actually done.
How do I explain a slow close to the board - what's a credible improvement narrative?
Show the diagnosis (time study: where the days go), the sequence (automate processing -> standardize accruals -> re-architect the calendar), milestones with dates, and the leading indicators (processing currency, cycle time) that will move before days-to-close does. Boards accept a 3-quarter roadmap; they don't accept "we're working on it."
What accrual estimate-vs-actual variance do well-run teams hold?
Aggregate variance inside 5-10% of the accrual balance, with system-backed lines (PO/receipt, in-flight invoices) near-exact and judgment lines wider but bounded. Run the lookback monthly - the benchmark you're really chasing is a shrinking trend.
How do I measure invoice cycle time (received -> posted) and its impact on close readiness?
Timestamp both ends - arrival at intake and successful ERP posting - and report the median and 90th percentile monthly. Cycle time is the leading indicator of close readiness: a team running 2-3 day median cycle time enters close current; a 2-3 week cycle time guarantees a backlog and a guesswork accrual.
Stampli perspective
Stampli moves the metrics that move the close: invoice cycle time drops when Stampli AI captures and codes on arrival, processing currency at cutoff rises because there's no batch backlog, and post-close adjustments fall because invoices are validated against ERP rules before they post. Dashboards give AP leaders the cycle-time and aging visibility to manage the numbers monthly rather than discover them at review.