Estimate AP accruals by matching the method to the vendor's billing pattern: use contract rate for fixed fees, most-recent-invoice for stable recurring variable costs, rolling average for seasonal or volatile spend, and prior-period actual only when history is thin or current activity is clearly comparable. Then attach enough support for a reviewer to reproduce the number.
Estimating accruals for uninvoiced services is harder than it sounds. Vendors deliver on their own cadence and bill on another, so the expense is real before any document lands in AP. Contracts behave differently by expense type: some are fixed monthly retainers, some are usage-metered, and some are project-based with milestone billing. Prior invoices are a useful anchor but can mislead when usage shifts, rates change mid-period, or the vendor's billing cycle straddles your close. Materiality thresholds also shape the work - a $300 courier accrual does not deserve the same rigor as a $40,000 legal estimate.
The method depends on the expense type and the audit evidence you can produce, not on a universal default. Accrual estimation is one step inside the full AP month-end close process, and the quality of the estimate shows up in how quickly the rest of the close moves.
The Four AP Accrual Estimation Methods
Four estimation techniques cover the vast majority of month-end accruals for services delivered but not yet invoiced. Each has a specific information requirement and a natural fit. Pick one per accrual line based on what the vendor's billing pattern makes available, then document the choice on your worksheet so reviewers can follow the logic.
Prior-period actual
Definition: Use the vendor-and-GL-account's posted expense from the immediately prior closed period as the current period's estimate.
Inputs: The prior period's GL posting for that vendor and account. Nothing else is strictly required, though known volume or activity signals for the current period should flag whether the prior amount remains a reasonable proxy.
Fit: Stable expenses where month-to-month variance is typically small, or situations where no executed contract exists and vendor invoice history is too thin to support a rolling calculation. This is also the fallback when a new vendor delivered service in the current period but has only one prior billing cycle on file.
Example: If last month's freight charge from the same carrier was $4,820 and shipment volume this month was comparable, book $4,820 subject to adjustment if a known volume signal (a large outbound shipment, a paused lane) suggests otherwise.
Contract rate
Definition: Apply the contracted fixed rate to the proportion of the period during which the service was delivered.
Inputs: An executed contract or purchase order, the contracted rate or monthly fee, and the elapsed service period, typically the full month for a monthly retainer, or a pro-rata fraction when service started or ended mid-period.
Fit: Fixed-fee arrangements without consumption variability. This is the method for SaaS subscriptions billed at a flat monthly rate, retainer professional services (legal, tax, advisory), and contracted recurring services such as janitorial, security, pest control, or managed IT.
Example: If the signed cleaning contract is $1,200 per month and the cleaner delivered service for every scheduled day in the month, book $1,200. If service began on the fifteenth of a thirty-day month, book $600.
Most-recent-invoice
Definition: Use the dollar value of the vendor's most recently received invoice for the same recurring service as the current period's estimate.
Inputs: The previous invoice from that vendor for the same service line. A quick check that the service scope has not changed since the prior bill, same meter, same lanes, same headcount, protects the estimate from becoming stale.
Fit: Recurring variable services where the last bill is a reasonable proxy for this period and no contract rate governs the amount. Useful when vendor history is too short for a rolling calculation or when the last bill already reflects the current cost structure.
Example: If last month's utility bill for the same meter was $3,640 and consumption patterns are comparable, book $3,640.
Rolling average
Definition: Calculate the average of the vendor's last three to twelve invoices for the same service and use the average as the estimate.
Inputs: A clean history of the vendor's prior invoices for the same expense, plus a documented policy on the averaging window. A three-month window suits short history or a fast-changing cost structure; a twelve-month window smooths seasonal variation.
Fit: Variable recurring services where a single-period outlier could distort a most-recent-invoice estimate. Telecom bills with usage spikes, utilities with seasonal swings, and freight with volume fluctuation are typical candidates.
Example: If the last six monthly telecom bills averaged $2,115, book $2,115 and note the window and invoice set on the worksheet.
The accuracy each method can credibly achieve tracks the information the vendor's billing pattern exposes. Contract rate is tightest when the variable is fixed in writing. Rolling average and most-recent-invoice work when recent billing history predicts the current period. Prior-period actual is the fallback when history is thin and no contract anchors the number. Once you have selected a method and calculated a number, the journal-entry mechanics of recording and reversing an accrual covers the recording and reversal side of the entry.
Match the Method to the Expense Type
The same billing patterns repeat across expense categories. Use the matrix as the decision point, then document any exception directly on the accrual schedule.
| Expense type | Start with | Use instead when | Watch for |
|---|---|---|---|
| Utilities | Most-recent-invoice | Rolling average for seasonality; prior-period actual when history is thin | Seasonal HVAC load, rate changes, meter anomalies |
| SaaS and subscriptions | Contract rate | Most-recent-invoice for tiered usage that stayed flat | Mid-period upgrades, overages, seat-count changes, proration |
| Professional services | Contract rate for retainers; prior-period actual for time-and-materials | Rolling average when hours are stable | Scope changes, milestone billing, uneven cadence |
| Telecom and connectivity | Rolling average | Most-recent-invoice for stable flat plans | Overage, roaming, equipment charges, late carrier reconciliations |
| Freight and logistics | Prior-period actual when shipment volume is comparable; rolling average when it is not | Volume-weighted rate-card calculation when shipment counts and rates are available | Fuel surcharges, peak pricing, accessorials |
| Contracted recurring services | Contract rate | Prior-period actual for variable pass-through components | One-off extras, annual escalators, service-level adjustments |
Utilities need special handling when the bill straddles the close date; daily-rate proration for utility bill accruals covers the day-count mechanics. Professional-services accruals need extra skepticism because a law firm or consultant may bill twice in one month and skip the next; outside counsel work-in-progress accruals covers that pattern in detail. Freight often sits beside received-but-not-invoiced inventory, so pair the freight accrual with the GRNI accrual pattern for goods received but not invoiced when both the product invoice and freight bill are missing.
One check sits upstream of every method: cutoff. Getting the AP cutoff procedure for late and post-cutoff invoices right determines which invoices you post as actual expense and which ones you estimate. A cutoff error can double-count or omit an item no matter how defensible the accrual method is.
Audit Evidence for Each Estimation Method
Accrual estimates draw disproportionate scrutiny because the assumptions behind them are often informal, carried in a staff accountant's head rather than filed alongside the journal entry. According to IFIAR's 2025 Survey of Inspection Findings, 35% of inspected listed public-interest-entity audits had at least one inspection finding, and accounting estimates and fair value measurement remained among the highest-frequency finding areas. For your close package, the lesson is practical: estimates need a contemporaneous record of the method, inputs, and assumptions. Audit defensibility for AP accruals is a documentation problem first and a methodology problem second.
The most-recent-invoice and rolling-average methods depend on clean vendor history that can be filtered by vendor, period, service line, and expense type. When that history lives in PDF folders or a GL export that strips away invoice detail, the estimate becomes harder to reproduce. An accountant using an AI tool that converts invoices into structured spreadsheets can preserve vendor-level detail in Excel, CSV, or JSON so the close team can show exactly which invoices were included in the calculation.
What follows is a method-by-method evidence map, in the same order as the four methods introduced earlier. For each, you get the primary evidence an auditor will expect to see attached to the accrual schedule, the secondary evidence that strengthens the position, and the single question most likely to land in the review meeting.
Prior-period actual. Primary evidence is the prior period's GL extract showing the vendor and account's posted expense, accompanied by a short note explaining why current-period activity is comparable. That note is the load-bearing element: without it, you have copied a number rather than estimated one. Secondary evidence consists of operational signals confirming that volumes or rates did not materially change during the period, such as shipment counts, headcount reports, or system usage logs tied to the expense driver. The likely auditor question: "What would have prompted you to pick a different number?" If you cannot answer that cleanly, the method was applied on autopilot.
Contract rate. Primary evidence is the executed contract or purchase order showing the rate and term, paired with a calculation tying the booked accrual to the contracted rate for the elapsed portion of the period. The calculation should be reproducible by a reviewer working only from the contract and the days-elapsed figure. Secondary evidence is proof the service was actually delivered, which depending on the vendor might be a sign-off email, a service ticket, a utilization report, or a delivery confirmation. Without delivery evidence, you have accrued for a promise rather than a performed service. The likely auditor question: "Was there any variable component in the contract that the rate alone does not capture?" Usage-based overages, tiered pricing, and true-up clauses are the common traps.
Most-recent-invoice. Primary evidence is the prior vendor invoice itself, with a visible tie from its amount to the current-period accrual. "Visible tie" means the invoice is attached or referenced by document number, not recalled from memory. Secondary evidence is a one-sentence note explaining why last month's bill is representative of this month, usually citing stable usage, the same seat count, the same headcount of licensed users, or the absence of a rate change. The likely auditor question: "What in this period is different from the period that invoice covered?" This method collapses quickly when pricing changed mid-period or a contract renewed with a step-up.
Rolling average. Primary evidence is the actual invoice set used in the average, the calculation worksheet that produced the average, and a written policy on the averaging window (three, six, or twelve months) and why that window fits the expense pattern. The policy matters as much as the math, because an averaging window selected per-accrual rather than by rule looks like hindsight. Secondary evidence is a variance check comparing the rolling average to the most recent month, so a recent outlier surfaces rather than being buried inside an average. The likely auditor question: "Why this window? What would change the window?" Have a defensible answer ready: seasonality, contract cadence, or volume stability, not "it felt right."
The principle underneath all four: audit defensibility is not about using the most sophisticated method, it is about using the method best supported by the information you actually have, and keeping that support filed with the accrual schedule. A contract-rate accrual with no contract attached fails review faster than a well-documented rolling-average estimate, because the reviewer can reproduce the second and cannot reproduce the first.
Materiality and Method Choice
Materiality in this context is the dollar level below which an accrual error would not change a reasonable reader's view of the financial statements. That threshold is set by the facts of the entity, often through the external auditor's planning materiality, an internal finance policy, or a stated percentage of a base such as pretax income or total expense, so no single cutoff applies to every close.
The practical point is simple: the rigor of the method should scale with the size of the accrual.
Small and individually immaterial. Prior-period actual or most-recent-invoice is usually enough. A full rolling-average build for a minor monthly service charge is disproportionate effort, but the support still needs to exist: attach the prior invoice or prior-period detail and leave a short note on why the amount is still representative.
Moderate and near the threshold. Most-recent-invoice or rolling average is the safer choice because the number is large enough to attract review but not always large enough to justify contract-level rebuilds. This is where the method choice should be explicit on the accrual schedule: note why last invoice is representative, or name the averaging window and file the invoice set behind it.
Large and individually material. Contract rate is the cleanest method where a fixed fee exists. If no fixed rate exists, use rolling average with a named window, a variance check against the most recent month, and primary support attached, such as the contract, invoice sample, or calculation worksheet. At this tier, assume someone will ask how the number was derived and whether a different method would have produced a meaningfully different result.
There is also an aggregation problem. Ten individually immaterial accruals estimated with quick methods can still add up to a material balance when they hit the same account family or reporting area. Before applying a light-touch method across the board, compare the aggregate accrual population against the materiality threshold rather than judging each line in isolation.
When the tier is uncertain, default to the more rigorous method. The extra work to build a rolling average or tie the number back to a contract is usually modest compared with the time lost defending an avoidable variance after review.
True-Up Discipline — Closing the Loop Between Estimate and Actual
Every true-up has three moving parts: reverse the prior period's accrual, record the actual invoice at its real amount, and calculate the variance between estimate and actual for each vendor. The mechanics belong to the journal-entry process already covered earlier; the discipline here is what you do with the variance once the posting is complete.
Set a simple review rule and use it consistently. Many teams start by flagging any vendor whose estimate-to-actual variance exceeds 5% or 10% for method review. Variances below that threshold usually confirm the current method is fit for purpose. Variances above it mean the method, the inputs, or the vendor billing pattern deserves another look before next month.
Persistent positive variance. If actual invoices keep landing above the estimate, the method is systematically under-accruing. Shorten the rolling-average window so recent price movement carries more weight, add a modest buffer where policy allows, or check whether an annual price escalator or usage change was missed in the contract review.
Persistent negative variance. If actuals keep arriving below the accrual, the team is over-accruing and parking expense in the wrong period. That often means the rolling average still reflects an older, higher run rate. In that situation, a most-recent-invoice method may be more faithful if the trend is clearly downward, or the service level may have been reduced without the accrual worksheet catching up.
Erratic variance with no pattern. Some vendors simply bill irregularly enough that no tight estimate is available. Professional-services invoices tied to milestones and freight invoices exposed to surcharges are common examples. If a vendor bills erratically, use a wider rolling-average window and fix the upstream inputs: reporting cadence, PO discipline, and contract terms.
True-up discipline is what turns accrual estimation from judgment into a managed process. A worksheet that keeps each month's estimate, actual, and variance by vendor creates evidence for the next close and shows whether the method is tightening over time. That history is often as valuable to a reviewer as the current month's calculation because it proves the team is learning from its misses rather than repeating them.
Invoice Data Extraction
Extract data from invoices and financial documents to structured spreadsheets. 50 free pages every month — no credit card required.
Related Articles
Explore adjacent guides and reference articles on this topic.
Utility Bill Accruals: How to Estimate, Allocate, and Reverse
Learn how to estimate utility bill accruals at month-end using daily-rate proration, allocate costs by department, and reverse when actual bills arrive.
Invoice Accrual and Reversal Process: A Complete AP Guide
Learn when to accrue uninvoiced liabilities, how to record journal entries, and how reversing entries prevent double-counting — with worked AP examples.
Accounts Payable Cutoff Procedure: Step-by-Step Guide
Step-by-step accounts payable cutoff procedure for handling late invoices, recording accruals, and building evidence packs without slowing month-end close.