Accounts Payable Cutoff Procedure: Step-by-Step Guide

An accounts payable cutoff procedure sets the rule for whether a supplier invoice belongs in the current period, should be accrued, or should be posted in the next period. A workable policy looks beyond the invoice date. It tests when the goods were received or the service was performed, when the invoice reached AP, whether approval is still pending, whether the amount is material, and what evidence supports the liability.

That is why an accounts payable cutoff procedure is really a control over liability completeness at month-end close. The decision is not "did AP finish processing this invoice?" It is "when did the obligation arise, and what is the right way to reflect it in the ledger without keeping the books open longer than policy allows?"

In practice, every period-end invoice falls into one of three paths:

• Current-period posting: The obligation belongs to the closing period and the books are still open, so AP can post it directly.
• Accrual: The obligation belongs to the closing period, but the invoice cannot be fully posted before close, so finance records a supported estimate until the actual invoice is posted.
• Next-period posting: The goods or services belong to the next period, or the item is below policy thresholds, so it is recorded in the following month.

This framework matters because the wrong cutoff decision distorts both the income statement and the balance sheet. Missed liabilities understate expenses and payables. Overly aggressive reopenings slow the close and create rework for AP, accounting, and reviewers.

Teams usually struggle not because the principle is unclear, but because the invoice flow is messy. Documents arrive through different inboxes, approvals lag, goods are received before the supplier sends the bill, and posting happens after the ledger deadline. A useful month-end invoice cutoff procedure has to deal with those operational realities, not just restate accrual accounting rules.

---

Use the Right Dates Instead of the Invoice Date Alone

Invoice date is often the most visible date on the document, but it is rarely the only date that matters. A reliable AP period-end cutoff uses a hierarchy of evidence so the team can decide when the liability actually belongs in the ledger.

Start with the service period or goods receipt date. For recurring services, the key question is when the work was performed or the benefit was consumed. For product purchases, the key question is when the goods were received and accepted. Those dates usually tell you when the obligation belongs in the accounts.

Next look at the invoice receipt date. This shows when AP became aware of the item and helps explain whether a late posting was caused by supplier timing, internal intake delays, or approval backlog. It is important operationally, but it does not override evidence that the cost belongs to an earlier period.

Treat approval date carefully. Approval is a control over authorization, not the economic event itself. If the goods were received on March 30 and the manager approves the invoice on April 2, the timing of the approval may explain why AP did not post it by month-end, but it does not move the liability into April.

The posting date answers a different question: when did the ERP or accounting system record the entry? That matters for workflow tracking and reconciliations, but it should not be confused with when the liability arose. The same warning applies to the supplier's invoice date. It is relevant context, yet it can be earlier or later than the service period, receipt date, or AP receipt date.

When dates conflict, rely on evidence, not habit. A goods received note, other receiving records, service confirmations, and three-way matching tell you whether the liability existed before close. That is the practical difference between an accounts payable cut-off procedure that is defensible and one that defaults to whatever date happens to be easiest to read from the PDF.

---

Surface Received but Unposted Invoices Before Close Day

A strong cutoff procedure starts before the ledger deadline, not when someone notices a missing invoice on close night. According to APQC's monthly close benchmark, finance shared services centers report a median cycle time of 8.0 days to complete the monthly financial close. If your team waits until the last day to ask which invoices are still missing, you have already compressed the review window.

The practical answer is to maintain a received-but-unposted queue several days before close. Every document that has reached AP should appear on a visible worklist with receipt date, vendor, invoice number, amount, current status, and owner. That lets finance separate four different problems that are often mixed together:

1. The invoice was received and can still be posted.
2. The invoice was received but is blocked by coding, matching, or approval.
3. The goods or services were received, but the supplier invoice has not arrived.
4. The invoice is not relevant to the closing period at all.

This is where operating discipline matters more than theory. Centralize intake, review shared inboxes, and clear out side channels like personal email chains. Standardize the review steps so AP can tell the difference between documents that need immediate posting and items that belong on an accrual list. If your team needs a better handoff into close, these pre-accounting steps before posting invoices help define what has to be validated before an item can move into the ledger.

Approval delays create a second source of cutoff risk. A pending approver should not hide a liability that already belongs to the period. Teams should review stuck items separately, escalate aged approvals, and analyze recurring invoice approval workflow bottlenecks so the same blockers do not recur every month.

Some teams support this review with invoice data extraction for month-end close. Platforms like Invoice Data Extraction can pull invoice number, invoice date, vendor, net amount, tax, total, PO number, and document type from mixed supplier batches into Excel, CSV, or JSON. They can also retain source file and page references for each row, which helps controllers review support quickly. Saved prompts are useful when the month-end team wants the same accrual-ready export every period instead of manually rebuilding a spreadsheet from incoming PDFs.

---

Decide Whether to Accrue, Reopen, or Post Next Period

When an invoice is received after month end, start with the economic event, not the email timestamp. The question is whether the liability belongs to the period that just closed. Once you answer that, the accounting treatment becomes much clearer.

Use this decision sequence for a late invoice after month end:

1. Did the goods arrive or the service period end before close? If no, the item belongs in the next period. If yes, keep going.
2. Are the books still open for current-period posting? If yes, post the invoice directly with the right period date and support. If no, keep going.
3. Is the amount above your materiality threshold, and do you have enough evidence to support recognition? If yes, record the accrual. If not, follow policy for next-period posting and document why.

This is why accounts payable accruals should be treated as a policy outcome, not as a sign that AP failed. Sometimes the supplier invoice arrives too late, approvals are still moving, or the document needs matching work that cannot be completed before the ledger closes. If the cost belongs to the closing period, finance may need to accrue invoices at month end even though the final posting will happen later.

Reopening the period should be the exception, not the default. It makes sense when the books are not yet finalized, the amount is significant, and the team can post the actual invoice cleanly without destabilizing the close. Once reporting is effectively locked, an accrual is usually the cleaner control because it captures the liability while preserving a stable close process.

Approval timing does not change period ownership. If the service was delivered in March and the approver signs off in April, the approval date explains the workflow delay but not the accounting period. Record that fact on the accrual worksheet or decision log along with the amount, basis, evidence reviewed, and who approved the treatment. That documentation is what keeps the same invoice from being debated twice.

---

Run a Search for Unrecorded Liabilities and Build the Evidence Pack

An effective cutoff policy does not rely only on invoices that happen to arrive on time. It includes a monthly search for unrecorded liabilities so finance can identify obligations that belong to the period even when the supplier document is delayed or incomplete.

That review should cover several evidence sources:

• Unmatched receiving activity: Look for receipts that have no invoice attached yet, especially for material purchases close to period end. Manufacturers often treat this as a GRNI reconciliation workflow at month-end, because receipts without invoices can sit in clearing accounts long before AP receives the bill.
• Recurring services and utilities: Identify costs that are incurred every month even if the supplier has not billed yet.
• Vendor statements and open-item listings: These often show obligations that AP has not fully captured in the current queue.
• Subsequent disbursement review: Inspect invoices paid shortly after close. If the payment relates to goods or services received before period end, it may indicate a missed liability.

The support file for each decision should be just as disciplined. A defensible evidence pack usually includes the invoice if available, receipt or service confirmation, the relevant approver trail when it affects workflow status, the accrual worksheet entry, and any subsequent-payment support used to confirm the item. If your team needs a tighter standard for receipt evidence, this guide to goods received notes and receiving evidence is a useful complement to the cutoff procedure.

Three-way matching remains valuable here because it ties the PO, receipt, and invoice together when all three exist. When they do not, the goal is still the same: retain enough support to show why the liability belonged in the period and why the amount was reasonable. That discipline matters every month, not only during year-end audit work.

---

Assign Roles, Thresholds, and a Monthly Cutoff Checklist

The procedure becomes reliable only when ownership is explicit. AP should own intake completeness and the received-but-unposted queue. Buyers, receivers, or department leads should confirm whether goods or services were actually received. The controller or delegated reviewer should approve material accruals, set the materiality threshold, and decide when reopening a period is permitted.

Document those rules in the close calendar. Define the last day for normal posting, the cutoff for submitting accruals, the approval path for reopening entries, and the minimum support required for each decision. That is what turns an AP cutoff procedure into a repeatable control rather than a month-end debate.

A practical monthly checklist can stay short:

• Review received-but-unposted invoices before the ledger deadline.
• Escalate blocked approvals and unresolved matching exceptions.
• Identify goods or services received without an invoice.
• Decide whether each item should be posted, accrued, or pushed to the next period under policy.
• Capture the support on the accrual worksheet or decision log.
• Review early next-period payments for missed liabilities and correct the process if patterns repeat.

If the same exceptions appear every month, the fix is usually not a longer close meeting. It is better intake visibility, clearer ownership, and a documented accounts payable cut-off procedure that keeps the AP period-end cutoff decision consistent under pressure.