Finance Index
What is an invoice cutoff policy, and how do I set one for month-end?
Reference guide to invoice cutoff policy, including ERP workflow, integration points, data sync, controls, and finance-system tradeoffs.
An invoice cutoff policy defines which accounting period a transaction belongs to and the deadline by which invoices must reach AP to be recorded in the closing month. Cutoff exists to satisfy the accounting principle that expenses belong to the period the goods or services were received - not the period the paperwork showed up.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| An invoice cutoff policy | An invoice cutoff policy defines which accounting period a transaction belongs to and the deadline by which invoices must reach AP to be recorded in the closing month. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Cutoff be based on invoice | Service/receipt period governs the accounting; the invoice is just evidence. | Keeps evidence clear and reduces control risk. |
| Enforce cutoff without being | Publish the calendar, automate the reminders, and route exceptions through one approver (the controller) so AP isn't negotiating case-by-case. | Keeps evidence clear and reduces control risk. |
| What do most companies use | Common practice is last business day of the month for invoice receipt, with accrual submissions due day 1-2. | Keeps spend tied to policy, ownership, and review. |
| Best practice | Publish a rolling 12-month close calendar; remind budget owners 5 and 1 business days before cutoff; tell top vendors your invoicing deadline; and state the consequence plainly - after cutoff, it's next period unless material. | Keeps vendor records and payment decisions reliable. |
Should cutoff be based on invoice date, received date, or service period?
Service/receipt period governs the accounting; the invoice is just evidence. Auditors test whether expenses landed in the period the obligation arose - goods received June 28 belong in June even if invoiced July 5 (that's what the accrual is for). Your operational cutoff (the processing deadline) is a workflow rule; your accounting cutoff (which period) is GAAP.
How do I enforce cutoff without being the bad guy?
Publish the calendar, automate the reminders, and route exceptions through one approver (the controller) so AP isn't negotiating case-by-case. Pair enforcement with a service promise: invoices submitted on time post and pay on time. Departments stop fighting cutoff when late submissions cost them visible budget timing, not AP goodwill.
What do most companies use as the invoice cutoff date?
Common practice is last business day of the month for invoice receipt, with accrual submissions due day 1-2. Companies with automated intake can hold cutoff at day 2-3 of the new month and still close on time, because processing is instant.
What are best practices for communicating a cutoff policy?
Publish a rolling 12-month close calendar; remind budget owners 5 and 1 business days before cutoff; tell top vendors your invoicing deadline; and state the consequence plainly - after cutoff, it's next period unless material. Communication beats enforcement.
How should we handle invoices received after cutoff but dated in the prior period?
If the period is still open and the amount is material, post it back. If locked, accrue (if you caught it during close) or post to the current period (if immaterial). Define the materiality threshold in policy so the choice is mechanical.
Expense cutoff vs invoice cutoff vs receiving cutoff - what's the difference?
Receiving cutoff fixes when goods/services count as received (drives the liability), invoice cutoff fixes the processing deadline for the document, and expense cutoff is the umbrella accounting concept both serve. AP's operational deadline is the invoice cutoff; the auditor's concern is the expense cutoff.
How should goods received near month-end be treated when the invoice hasn't arrived?
Accrue them at PO or receipt value - that's the received-not-invoiced accrual. The receipt creates the obligation; the invoice just prices and documents it. This is why timely receiving entry matters more to cutoff quality than invoice speed.
Auditor flagged cutoff errors in our AP testing - what causes cutoff misstatements and how do we prevent them?
Usual causes: posting by invoice date instead of receipt period, invoices hiding outside AP at period end, receiving entered late, and no accrual for in-flight items. Prevention: centralized same-day intake, receipt-date-driven period assignment, and a standing accrual method for everything in process.
How do automated invoice capture tools change cutoff timing?
When capture and coding happen on arrival, the lag between receipt and recording drops to near zero, so you can move cutoff later, shrink the accrual, and reduce estimate error simultaneously. The cutoff date stops being a buffer for processing time.
What are year-end cutoff procedures and how is 12/31 different from a normal month?
Year-end cutoff gets audit testing (subsequent disbursements review), a longer subsequent-events window, harder enforcement (no "post it back" grace), and tax consequences. Hold the cutoff line firmly, document every exception, and expect January invoices to be sampled against December liabilities.
What is the proper period for an invoice spanning two months of service?
Split it: expense the portion for service already delivered, treat the rest as prepaid (or accrue the delivered-but-unbilled portion if invoicing lags). For immaterial amounts, a consistent single-period convention is defensible - write it down and apply it uniformly.
Stampli perspective
Because Stampli captures invoices on arrival through centralized intake and Stampli AI codes them immediately, the gap between "invoice exists" and "invoice is recorded" collapses - which lets companies run later, more generous cutoffs without sacrificing completeness. Real-time visibility into everything in flight means the cutoff decision is made from a complete population, not a hopeful one.