Accounts Payable Month-End Close: Process & Checklist

The accounts payable month-end close is the structured sequence of tasks AP teams complete at period end to ensure every vendor obligation is accurately recorded before the books close. The process covers aging review, outstanding invoice resolution, cutoff enforcement, three-way matching, AP subledger-to-GL reconciliation, accrual booking for uninvoiced liabilities, variance analysis, and final close entries. Most AP teams complete this sequence in four to six business days, though automation can compress that timeline significantly.

Getting this right matters because AP close accuracy directly affects financial statement reliability. A missed invoice, an incorrect accrual, or an unresolved exception at this stage does not stay contained within AP. These errors cascade into general ledger misstatements, trigger audit findings, and delay the delivery of financial reporting that the rest of the organization depends on. For companies with APQC-benchmarked close timelines, even a one-day delay in AP creates downstream pressure on consolidation, reporting, and analysis.

The gap between current practice and what is achievable remains wide. According to a survey of nearly 1,200 accounting professionals on month-end close times, 30% reported that their month-end close still takes one to three weeks, and 58% plan to increase their automation investment to accelerate the process. Those numbers point to a shared reality: most AP teams know their close workflow has room for improvement, but translating that awareness into a repeatable, faster process requires a clear framework.

This guide provides that framework. Each section walks through a specific phase of the AP close process with embedded checklists you can adapt to your own workflow, covering pre-close preparation, cutoff enforcement, matching and reconciliation, accrual booking, and how invoice data extraction automation changes each step. This is not a general month-end close guide. Every section addresses AP-specific tasks, sequenced in the order your team should execute them.

Why AP Should Close First in the Monthly Sequence

Accounts payable sits at the top of the subledger dependency chain. The balances AP produces flow directly into cost of goods sold, accrued liabilities, and cash flow projections. If those numbers aren't final, every downstream ledger is building on incomplete data.

Consider what AP feeds into:

Cost of goods sold and inventory valuations. Goods received but not yet invoiced (GRNI) accruals originate in AP. Until AP confirms which vendor invoices have been recorded and which need accrual, the inventory subledger can't produce an accurate valuation.
Accrued liabilities on the balance sheet. Unrecorded AP invoices directly misstate current liabilities. The GL can't close accrued expense accounts until AP has identified every obligation that belongs in the period.
Cash flow projections. Treasury and FP&A teams pull AP aging data to forecast near-term cash requirements. Incomplete AP data means those forecasts are wrong before they're even published.

AR close, inventory close, and fixed asset close all depend on accurate AP numbers to varying degrees. AR needs correct intercompany AP balances for elimination entries. Fixed assets can't capitalize vendor invoices that AP hasn't yet recorded. The dependency runs in one direction: AP feeds the others, not the reverse.

What happens when AP doesn't close first. The symptoms are predictable and disruptive. Late-arriving AP entries force journal entries into GL periods the controller thought were closed. AP aging reports don't tie to the GL, triggering reconciliation loops. The full close timeline slips because the controller is waiting on AP to finish before signing off on the financial statements. In the worst cases, the CFO or audit committee receives reporting packages with "pending AP" caveats, which erodes confidence in the numbers.

Last-minute AP adjustments are particularly damaging because they cascade. A single batch of invoices posted after the GL soft close can change COGS, shift inventory valuations, alter accrued liabilities, and move the cash flow forecast, all at once.

A recommended close sequence for AP-heavy operations:

Accounts Payable — finalize all invoice entries, accruals, and reconciliations
Accounts Receivable — complete billing, revenue recognition, and intercompany eliminations
Inventory — adjust valuations using final AP and GRNI data
Fixed Assets — capitalize additions, record depreciation using confirmed AP entries
General Ledger — consolidate subledger balances, post final adjusting entries, close the period

This sequence isn't universal. Organizations with minimal AP volume or those where revenue recognition is the primary bottleneck may order things differently. But for any operation where vendor invoices represent a significant portion of monthly activity, closing AP first eliminates the most downstream rework.

Without that AP anchor, the rest of the close calendar is provisional. Every team is waiting, and no one can plan their work with certainty.

Pre-Close Preparation: Aging Review and Outstanding Items

The AP aging report is the foundation of every pre-close cycle. Before you reconcile a single account or book an accrual, you need a clear picture of what your open vendor obligations actually look like. Running and analyzing your AP aging report at the start of the pre-close phase surfaces the items that will stall your close if left unaddressed: invoices stuck on hold, unapplied vendor credits, duplicate entries, and balances old enough to raise questions about whether they represent real liabilities.

Pull the report segmented by vendor and by age bucket (current, 30, 60, 90+ days). This dual view lets you spot patterns that a single view misses. A vendor with a large current balance and an offsetting credit memo from three months ago needs attention now, not during reconciliation.

Pre-Close Checklist

Work through these items systematically before moving into the close itself:

Pull the full AP aging report by vendor and by age bucket. Confirm the report date aligns with your close calendar.
Identify invoices on hold or in dispute. Escalate unresolved disputes to purchasing or the vendor relationship owner. Any invoice still on hold at close will either delay your numbers or force an accrual you could have avoided.
Investigate balances aged over 90 days. For each one, determine whether it represents a legitimate pending liability, a stale entry that should be written off, or a misclassified item that belongs elsewhere. Guidance on cleaning up aged AP balances before close can help you build a repeatable triage process for these.
Clear vendor credit memos and debit balances by applying them against outstanding invoices. Unapplied credits distort your aging buckets and inflate your reported liabilities.
Verify that invoices pending approval have been routed and actioned. Chase down any approvals sitting in someone's inbox. An invoice that arrived three weeks ago but never cleared the approval workflow is functionally invisible to your aging report until it posts.

Where AP Teams Lose the Most Time

Pre-close cleanup is the single largest time sink in the monthly AP close. The work itself is not conceptually difficult. What consumes hours is the manual chase: tracking down invoices that were received but never entered, following up on approval bottlenecks, and investigating aged line items one by one to determine if they are valid. Every month, AP staff repeat this cycle with the same friction.

Pay attention to the interaction between aged balances and payment timing. Some items sitting in the 60- or 90-day bucket may be tied to extended payment terms or early payment discount windows. Clearing these prematurely can forfeit negotiated terms, while ignoring them can misstate your obligations. Flag these during triage so they are handled intentionally rather than swept into a blanket write-off.

Reducing the Backlog Before Close Begins

The pre-close aging review gets dramatically faster when the backlog of received-but-unentered invoices is already minimal. This is where batch invoice processing changes the equation. With a tool like Invoice Data Extraction, AP teams can run the entire backlog of received invoices through automated extraction in minutes, not days. The platform handles mixed formats and automatically filters out cover sheets, remittance advices, and summary pages that get mixed into vendor email batches.

The practical result: when you pull your aging report at the start of pre-close, it already reflects the vast majority of invoices your organization has received. You are reviewing a clean list of genuine open items rather than spending the first days of close entering a backlog. The goal of this entire phase is to reduce your open items to only valid, substantiated liabilities.

Enforcing the AP Cutoff Date

The AP cutoff is the specific point in time after which no new invoices are recorded in the current period. Any invoice received after the cutoff gets recorded in the next period instead. This boundary exists for one reason: to ensure expenses are recognized in the correct period, which is fundamental to accrual-based financial reporting. Get the cutoff wrong, and your financial statements misstate liabilities and expenses for both the current and subsequent periods.

Auditors specifically test cutoff by pulling invoices recorded in the days immediately before and after period end, looking for items booked in the wrong period. Weak cutoff controls are among the most common AP audit findings, and they can trigger broader questions about the reliability of your entire close process.

Setting and Communicating the Cutoff

Announce the cutoff date and time to every department and key vendor well before month-end. This is not a suggestion; it is a prerequisite. Departments that submit invoices late and vendors that send them to the wrong contact are the two biggest sources of cutoff violations. A standing reminder sent five business days before the cutoff, followed by a final notice on the cutoff date itself, reduces late submissions significantly.

For detailed guidance on managing invoices that arrive after the deadline, see AP cutoff procedures and late-invoice handling.

Handling the Gray Area

Every organization needs a clear, documented rule for borderline cases. The most defensible approach: if an invoice was received by the cutoff date, it belongs in the current period regardless of when the goods or services were delivered. Adjust this baseline to align with your organization's specific accounting policy, but make sure the rule is written down and applied consistently.

When invoices arrive after the cutoff but clearly relate to current-period expenses, book them as accruals rather than reopening the AP subledger. Reopening the ledger after cutoff undermines the entire purpose of the exercise and creates reconciliation problems downstream.

Documenting Cutoff Decisions

The cutoff is only as strong as the evidence behind it. Auditors want to see proof of when invoices were received, not just when they were entered into the system. Timestamps on received invoices, email receipt dates, and mailroom logs all serve as supporting documentation. Without this evidence trail, your cutoff policy is an assertion rather than a control.

This is where automated invoice processing creates a material advantage. When invoice intake runs through Invoice Data Extraction, every document receives a processing timestamp the moment it enters the system. With extraction completed in 1 to 8 seconds per page and every output row referencing the source file and page number, you get an audit-ready record of exactly when each invoice was received and processed. No manual logging, no reliance on email timestamps that can be disputed. The system-generated trail documents your cutoff decisions automatically.

Cutoff and Early Payment Discounts

One frequently overlooked interaction: invoices approaching discount deadlines may need priority processing before the cutoff to capture the discount and record the correct net expense amount. If your team is focused on capturing early payment discounts before the cutoff deadline, build discount-eligible invoices into your pre-cutoff processing queue. Missing a 2/10 net 30 discount because an invoice sat unprocessed until after the cutoff is both a cash management failure and a potential misstatement of the recorded expense.

Three-Way Matching and AP-to-GL Reconciliation

Before you can close AP for the period, every open invoice needs to tie back to its purchase order and its goods receipt or service confirmation. Three-way matching at month-end is not a routine compliance exercise; it is the mechanism that surfaces discrepancies before they distort your financial statements. An unmatched invoice means an unresolved variance, and unresolved variances either misstate your AP balance or force last-minute adjustments that delay the close.

The volume problem is real. A mid-market AP team processing thousands of invoices per month will inevitably carry a queue of matching exceptions into the close period. Price variances between the invoice and the PO, quantity discrepancies where the receipt does not align with what the vendor billed, and missing receipts where the warehouse never confirmed delivery all create friction. Each exception requires investigation, and investigation takes time you do not have during close week.

The Goods Received Not Invoiced Problem

Three-way matching also exposes a category of liability that is otherwise invisible: goods received not invoiced (GRNI). These are items your organization received into the warehouse or recorded in your system, but for which no vendor invoice has arrived by the cutoff date. GRNI balances represent real obligations that must be identified during the matching review. The accounting treatment falls under accruals (covered in the next section), but the matching process is where you surface them. If your open PO report shows receipts with no corresponding invoice, those line items need to be flagged and quantified.

Matching and Reconciliation Checklist

Use this sequence to work through matching exceptions and complete the AP-to-GL tie-out:

Run the open PO report and match against received invoices. Start with the full population of open purchase orders and systematically confirm which have both a goods receipt and an invoice recorded.
Identify and investigate three-way match exceptions. Pull every invoice that fails the match due to price variances, quantity discrepancies, or missing receipt confirmations. Prioritize by dollar amount.
Escalate unresolvable exceptions. For discrepancies that AP cannot resolve independently, escalate to purchasing or contact the vendor directly. Document the status of each exception and the expected resolution date so nothing falls through the cracks.
Determine accrual treatment for open exceptions. If a match exception will not resolve before the close deadline, assess whether you need to accrue the estimated liability. Do not leave material unmatched items unaddressed.
Reconcile the AP subledger total to the AP control account in the general ledger. Once all matching activity is complete and adjustments are posted, pull the subledger balance and compare it to the GL.
Investigate and resolve any subledger-to-GL difference. Common causes include timing differences from invoices entered but not yet posted, manual journal entries made directly to the AP GL account that bypassed the subledger, and unprocessed invoice batches sitting in a queue.

Why the AP-to-GL Tie-Out Is Non-Negotiable

The AP subledger-to-GL reconciliation is the single most important control in the AP close. The subledger holds the detail; the general ledger holds the summary. They must agree. Any unexplained variance between the two is an audit finding, and auditors will test this tie-out every period. Beyond audit risk, a variance you cannot explain means you do not fully understand your AP balance, which undermines every downstream financial report that depends on it.

Build the reconciliation into your close calendar as a required sign-off, not an optional check. The controller or AP manager should review and approve the tie-out before AP is declared closed.

How Automated Extraction Accelerates Matching

The manual bottleneck in three-way matching is not the comparison logic; it is getting invoice data into a format that can be compared against PO and receipt records in the first place. When AP clerks are manually keying invoice line items, including product codes, quantities, and unit prices, every invoice adds minutes of data entry before matching can even begin.

Automated invoice data extraction eliminates this step. A tool like Invoice Data Extraction converts incoming invoices into structured records with line items already parsed — product codes, quantities, unit prices, and tax amounts — ready for programmatic matching against PO and receipt data.

The impact scales with volume. Your entire month-end invoice queue can be converted to match-ready output in minutes. Instead of your team spending the opening days of close week entering and verifying invoice data, they start the matching process immediately with clean, structured records already in hand.

Booking AP Accruals for Uninvoiced Liabilities

AP accruals at month end serve a single, non-negotiable purpose: recording liabilities for goods or services your organization received during the period but has not yet been invoiced for. Skip this step, and your financial statements understate both expenses and liabilities. The matching principle requires that expenses hit the same period as the revenue or activity they support. AP accruals are how you enforce that principle when vendors haven't sent their invoices yet.

What to Accrue

Three categories account for the bulk of AP accruals at month end:

Goods received not invoiced (GRNI). Your warehouse or receiving system confirms that inventory or materials arrived during the period, but no vendor invoice exists in the AP subledger. This is the most straightforward accrual to identify because the receiving record already exists. The accrual amount is based on the purchase order price multiplied by the quantity received.

Service accruals. Utilities, consulting engagements, facility maintenance, rent, and similar recurring services are often invoiced in arrears. You consumed the service during the period, but the invoice won't arrive until the next month or later. Estimate these accruals using contract terms where rates are fixed, or calculate a three-month rolling average of prior-period actuals for variable services.

Accrued receipt accruals. These cover a narrower scenario: vendor invoices that are known to be in transit or sitting in an intake queue, not yet entered into the AP system. The distinction from GRNI matters. Here, both the goods or services and the invoice may already exist. The gap is purely operational, caused by processing lag between invoice receipt and AP entry.

Estimating Accruals With Defensible Basis

Every AP accrual is an estimate, and every estimate needs documentation that can withstand audit scrutiny.

For GRNI accruals, the PO price and received quantity provide a reliable, auditable basis. Pull open purchase orders with confirmed receipts but no matched invoice. The accrual journal entry debits the expense or inventory account and credits an accrued liabilities account for the PO line amount.

For recurring service accruals, start with the contract. If the contract specifies a monthly rate, use it. If the amount varies, a three-month average of prior actuals produces a reasonable estimate that smooths out fluctuations. Where neither a contract rate nor sufficient history exists, obtain a verbal or written estimate from the vendor.

Document the basis for every accrual. Auditors will sample your accruals and test whether the estimate was reasonable given the information available at period end. A spreadsheet listing each accrual with its source (PO number, contract reference, prior-period average) and the preparer's name is the minimum standard. Vague entries like "estimated utilities" without a calculation will draw audit inquiries.

Reversals and Variance Handling

Standard practice is to reverse all period-end AP accruals on the first day of the following period. This prevents double-counting when the actual invoice arrives and is recorded through the normal AP process. Most ERP systems support auto-reversal of accrual journal entries, and you should use that functionality rather than relying on manual reversal.

When the actual invoice posts, compare it to the original accrual estimate. Immaterial differences require no action beyond the normal reversal and invoice booking. Material variances between the accrual and the actual invoice warrant investigation. A consistent pattern of large variances in one direction signals that your estimation methodology needs adjustment, whether that means updating contract rates, revising average calculations, or obtaining better information from vendors before close.

Accrual Volume as a Process Health Metric

The size and frequency of your AP accruals at month end tells you something important about your invoice processing operation. A team that consistently books large GRNI and accrued receipt accruals likely has a backlog problem. Invoices are arriving but not being processed fast enough to clear before close.

High accrual volume introduces estimation risk. Every estimate is an opportunity for misstatement, and a large accrual portfolio increases the audit burden on your team. Reducing the need for accruals by processing invoices faster during the period is more reliable than perfecting your estimation methodology after the fact. Track total accrual dollars as a percentage of AP activity each month. A declining trend confirms that your upstream processing is improving.

AP Variance Analysis Before Signoff

Before the controller signs off on the close, run a period-over-period comparison of your AP balance, top vendor spend, and accrual estimates versus actuals. Material swings in any of these areas warrant investigation: a sudden increase in AP balances may reflect timing issues in invoice processing, while a spike in vendor spend could indicate unplanned procurement or duplicate payments. This variance review takes minutes when the underlying data is already clean, and it provides the controller with the evidence needed to confirm that the AP close is complete and accurate.

Accelerating the AP Close with Invoice Data Extraction

Every phase of the AP month-end close described above shares a common dependency: getting accurate invoice data into your system fast enough to act on it. The aging review, cutoff enforcement, three-way matching, and accrual booking all stall when invoices sit unprocessed. Automation doesn't replace the close process itself — controllers still review reconciliations, approve accrual estimates, and sign off on entries. What it eliminates is the data preparation layer that consumes the majority of AP close time.

Each phase above showed where manual effort concentrates: keying in backlogged invoices before the aging review, logging receipt timestamps for cutoff evidence, entering line-item data for three-way matching, and estimating accruals for invoices stuck in processing queues. Invoice data extraction tools built for AP teams address all four bottlenecks through a single capability: converting incoming documents into structured, match-ready data fast enough that invoices don't accumulate between periods. Every extracted row references the source document and page, so when a discrepancy surfaces, your team traces it to the original file without searching through folders.

What Accelerated Close Looks Like in Practice

APQC benchmarking data consistently shows that most AP teams complete month-end close in 4 to 6 business days. Teams running largely manual processes often push beyond a full week. The specific time savings from automation depend on your invoice volume and process complexity, but the impact concentrates where manual effort is highest: pre-close data entry and the matching phase.

A realistic accelerated workflow looks like this: on the first day of close, you batch-upload the period's invoices and run a single extraction job with a saved prompt that specifies exactly what your close requires — invoice numbers, dates, vendor details, amounts, tax breakdowns, and document classification. That prompt runs identically each period, keeping your extraction logic consistent across months. You can run multiple extraction tasks in parallel — one for the main invoice batch, another for credit notes or late arrivals — and have structured output ready for import within minutes. The data preparation that used to consume the first two or three days of close compresses into the first few hours.

What remains is the work that actually requires your team's judgment: reviewing reconciliation exceptions, validating accrual estimates against actuals, confirming cutoff decisions, and producing the final close package. That's where AP expertise matters. The extraction layer handles everything upstream.