Construction Supplier Statement Reconciliation at Month-End

Construction supplier statement reconciliation is the month-end control that ties a supplier's monthly statement, from a lumber yard, building-materials chain, ready-mix plant, or specialty distributor, to the underlying invoices, credit memos, and POs in the AP system before the period closes. The bookkeeper's job is to explain every dollar of difference between what the supplier says is open and what the AP aging says is open, post the adjustments that close the gap, and sign off the supplier balance.

Almost every variance fits a small, finite set of patterns. Timing and received-not-invoiced. Missing or misapplied credit memos. Restocking fees on returned material. Duplicate invoices. Misapplied payments. PO-to-line mismatches. Sales-tax bucket errors. The work is to walk those patterns in order, resolve the differential to zero, and route the supporting evidence to sign-off.

Construction makes the walk harder than generic AP for three reasons that show up every month. Credit memos from lumber yards and building-materials suppliers carry restocking-fee lines that change the net cost; capturing only the gross credit and ignoring the restock charge is the most common posting mistake on the pattern. Supplier billing lags the delivery ticket on long jobs, so an invoice that should be in AP for the period genuinely is not yet, and the cutoff has to handle that without misstating the job cost. And the supplier balance has to allocate cleanly across jobs and cost codes, so a credit memo posted to a generic returns account, or an accrual washed through a month-end clearing, hides the cost from the project manager and drifts the job-profitability report. Generic AP-automation explainers treat all of this as "common discrepancies" without ever naming the catalog.

The accounting profession has a canonical scaffolding for the topic. ACCA Global's technical guidance on supplier statement reconciliations identifies six recurring causes of difference between a supplier's statement and the purchase ledger: timing differences, allocation errors, unprocessed credit notes, unprocessed debit notes, discount miscalculations, and data-entry transposition errors. Reconciliation is framed as the control that surfaces them so they can be investigated and discussed with the supplier before the period closes. The construction-AP catalog below extends that scaffolding into the reality the bookkeeper actually sees: credit notes carry restocking-fee lines, allocation errors split across jobs and tax buckets, and timing differences resolve through RNI accruals built off the PO and the delivery ticket.

The workload is real. Kojo Technologies' industry data puts trade-contractor reconciliation effort at 20 hours a week, with 27 percent of supplier invoices carrying errors that surface here. The practitioners doing it, the construction-specialty bookkeeper closing several contractor clients each month, the AP clerk inside a mid-market GC, the controller signing off the residual, deserve a workflow that treats the variance patterns as named, finite, and resolvable.

---

The Variance-Pattern Catalog

Every supplier-statement variance in US construction fits a small set of named patterns. The catalog below extends ACCA's six causes of difference into the construction-AP reality, where credit memos carry restock lines, allocation errors split across jobs as well as tax buckets, and timing differences resolve through delivery-ticket evidence. Each row is a pattern, a one-line description, and the diagnostic handle, the thing to look at first to confirm you are looking at that pattern rather than another.

Pattern	One-line description	Diagnostic handle
Timing / received-not-invoiced	Supplier billed in the period; we have not received and posted the invoice, or have but cutoff put it in the next period.	Compare statement-side invoices missing from AP against open POs and signed delivery tickets.
Credit memo not yet posted	Supplier issued a credit memo (return, price adjustment, short delivery) we have not posted, or we have posted one the supplier has not yet applied.	Walk credit-memo lines on both sides; check return-authorization numbers and material-pickup tickets.
Restocking-fee variance	Supplier credit memo includes a negative restock-fee line; if the original credit or the restock portion is not posted, or the wrong sign is used, the net will not match.	Net the credit-memo lines on the AP side and compare to the statement's net entry for the credit.
Duplicate invoice	Supplier double-statemented; we double-posted; or one side has a duplicate the other does not.	Invoice-number match on the statement-to-AP join; same-vendor / same-date / same-amount fuzzy match for un-numbered duplicates.
Misapplied payment	Our payment hit the supplier's general AR rather than being applied to a specific invoice; the open-item statement still shows the invoice as outstanding.	Trace the payment on both sides; the supplier conversation usually clears it once the remittance is matched to the invoice.
PO-vs-line mismatch	Invoice line items do not cleanly match PO lines because of split lines, merged lines, substitute items, or UOM conversions.	Compare invoice line totals to PO line totals before chasing the rolled-up variance; line-level work is its own deep dive in investigating line-level invoice and PO mismatches.
Sales-tax bucket drift	Supplier applied tax we expected to be exempt (resale or project-exemption certificate on file) or vice versa.	Check the tax bucket on each variance line against certificate-on-file status before assuming the supplier is wrong.
Currency / FX	Rare in pure-US construction; relevant when materials are imported or the supplier bills in non-USD.	Confirm the bill currency and the conversion rate the supplier used.
Manual adjustment not posted	Supplier issued a manual adjustment (a goodwill credit, a rebill correction, a freight reclass) we have not seen yet.	Often surfaces only through the variance; ask the supplier to send the adjustment detail with the next statement.

The catalog is closed. A variance that does not fit one of these is rare, and when one appears, it almost always turns out to be a combination of two patterns rather than a new one, a duplicate of a credit memo, a misapplied payment against a timing-deferred invoice, a restocking-fee posting that also crossed the wrong tax bucket. The first instinct when something looks unfamiliar should be to test whether two patterns are stacked, not to assume the supplier has invented a new failure mode.

The same patterns transfer beyond construction with industry-specific surface details, and the same reconciliation workflow applied to restaurant supplier statements walks them in that vertical.

---

The Investigation Order That Resolves the Variance Fastest

The catalog tells you what you might be looking at. The investigation order tells you what to look at first. The principle behind the order is this: walk the easy-to-confirm patterns first, because they account for the largest share of variances and resolve without a supplier conversation, and defer everything that requires a phone call until you have the evidence packet ready. Calling the supplier's AR clerk before you have checked your own duplicates wastes both sides' time and damages the relationship.

The vendor statement variance investigation runs in this sequence:

1. Compare totals. Take the statement-side outstanding total and the AP-side aged balance for the supplier and note the differential. This is the number every subsequent step has to resolve to zero. Do not start ticking off matched invoices yet, the differential is what gives every later finding its meaning.
2. List statement-side invoices not in AP. Pull the statement detail and look for invoice numbers that do not appear in the AP listing for the period. These are timing variances, where the supplier billed and we have not yet posted, or invoices the supplier billed that never reached the contractor's AP inbox at all. For anything you cannot find, request a copy from the supplier and tag the line in your working file.
3. List AP-side invoices not on the statement. Reverse the join. Anything in the aged AP that does not appear on the statement is either a timing variance the other direction (we posted faster than the supplier billed, common for invoices uploaded close to month-end) or a duplicate. Same-vendor / same-date / same-amount matches against statement-side lines are the duplicate flag; treat them as duplicates until you can prove otherwise.
4. Walk credit memos on both sides. Match each credit memo to its original invoice and verify the restocking-fee handling. Both lines, the original credit and the restock charge, must post, and the net must agree with the statement entry for the credit. The credit-memo and restocking-fee mechanics get a section of their own below.
5. Check tax buckets. When a variance line shows the gross matching but the total off, the cause is almost always a sales-tax bucket mismatch. Reconcile the tax line against the resale or project exemption certificate on file before assuming the supplier is wrong. A surprising share of "the supplier overcharged us" findings turn out to be a missing certificate on the supplier's side.
6. Resolve, post adjustments, document the residual. What is left after the first five steps is either an RNI accrual decision, covered next, or a question for the supplier's AR clerk, covered after that. Post the adjustments, document the residual variance, and route the package to sign-off.

The same procedure runs in Sage 100 Contractor, QuickBooks Online, Foundation, Buildertrend, JobTread, or Knowify; the platform-specific clicks change but the AP clerk supplier statement reconcile workflow does not. Most variances clear in steps 2 through 4; tax-bucket and supplier-conversation residuals clear in steps 5 and 6.

---

Credit Memos and Restocking Fees Done Properly

Credit memos are the variance pattern most likely to break a construction reconciliation, because the supplier's credit memo is rarely a simple negative invoice. It carries adjustment lines, restocking fees on returns, re-shelving charges on yard-pickup, pickup fees when a truck is sent to the jobsite, that change the net cost the bookkeeper has to capture. The reconciliation walk surfaces the variance; this section walks the posting mechanics that prevent it recurring.

The lumber-yard restocking-fee structure is the most common construction-specific shape. Yards typically charge a percentage on customer-returned, good-condition material. The percentage is lower when the contractor brings the material back to the yard in the original packaging within a defined window (often somewhere in the 10 to 15 percent range), higher when the yard sends a truck to pick the material up from the jobsite (often 15 to 25 percent or more, reflecting the freight and handling cost), and stricter still on special-order, custom-cut, or non-stock items that the yard cannot easily resell. LBM Journal has documented these conventions across the trade. The exact percentage depends on the yard's policy and the contractor's account; what matters operationally is that the credit memo reflects both lines, the gross credit and the negative restock charge, and the bookkeeper has to post both.

The two-line posting pattern is the mechanic. The credit memo prints the original return as a positive credit and the restocking-fee line as a negative offset; both lines have to post on the AP side, and the net agrees with the statement entry. The most common mistake is capturing only the gross credit and ignoring the restock line, which produces a recurring variance, the AP shows the credit at gross, the statement shows it at net, and the difference is the restock charge that nobody booked.

The per-job impact is easy to lose. The restock charge is a real cost on the job that originally received the material. Code it to the same job and cost code as the original receipt, not to a generic returns or shrinkage account. Miss the per-job allocation and the project manager sees the gross credit on the cost-report and assumes the return cleaned up the cost when it did not; the variance compounds across multiple returns over the life of the job.

The timing variant: the supplier may have issued the credit memo in the prior period but not applied it to the statement until this period, or the reverse. The resolution is not to re-post the credit memo but to confirm with the supplier which statement period the credit is intended to land in and adjust the reconciliation accordingly, accepting the timing residual into the working file rather than chasing a posting that is already correct on both sides.

The missing-credit-memo case is its own pattern. The supplier may have issued a credit memo the contractor never received, because it went to the project manager who handled the return at the jobsite, or to the field office that authorized the pickup, and never made it to AP. Ask the supplier for the RA number and the date the credit memo was issued, then ask the field for the matching pickup ticket. Once the credit memo is in hand, post it with the same per-job coding the original invoice carried, including the restock charge to the same job. The lesson the working file captures: returns happening in the field need a documented hand-off back to AP, not a verbal note from the project manager.

---

Cutoff, RNI, and the Accrual That Closes the Period Cleanly

When the variance investigation surfaces a statement-side invoice that should be in AP but is not, the cause is almost always one of three. The invoice is in transit, scanned by the supplier and on its way to the contractor's AP inbox but not yet posted. The supplier billed late and the invoice will arrive in the next few days. Or the goods were received against an open PO and no supplier invoice has yet followed. The first two resolve themselves when the invoice arrives, often within a day or two, and the bookkeeper can leave the variance line open and re-test next morning. The third needs a received-not-invoiced accrual, because the cost has been incurred and the period is about to close on it.

Received-not-invoiced in the construction context means something specific: the materials were delivered, a signed delivery ticket is on file, the cost is therefore real and belongs to the job, but no supplier invoice has yet posted to the AP system. Closing the period without the accrual understates the supplier balance, understates AP, and misstates the job cost on the project manager's report. The received not invoiced construction month-end accrual is the entry that fixes all three at once.

The accrual entry is mechanical once the evidence is on file. The PO line gives the unit cost (or the delivery ticket gives the unit cost where the PO is open and partially-billed and the line price has been confirmed). The delivery ticket gives the quantity received in the period. The accrual journal debits the job cost, to the same job and the same cost code the eventual invoice will hit, and credits an RNI liability account that sits on the balance sheet until the actual invoice posts. When the supplier's invoice finally arrives, post the invoice normally to AP and reverse the accrual against the same job and cost code. The job cost ends up correct, the supplier balance ends up correct, and the RNI liability clears.

Per-job discipline is the load-bearing part. Coding the accrual to the same job and cost code the eventual invoice will hit keeps job profitability accurate even when supplier billing lags by weeks, which it routinely does on long jobs and monthly billing cycles. Generic "AP accrued" entries that wash through a single month-end clearing account hide the cost from the project manager, defeat the cost-report, and create a second variance next month when nothing reverses cleanly. The mechanic is the same as estimating month-end accruals for bills that arrive late for utility billing: accrue at the job-and-code level, reverse on the same level when the bill arrives. A sloppy accrual, the wrong amount, the wrong job, or the wrong account, creates the kind of next-month variance that makes a bookkeeper believe a supplier statement is "always wrong" when the wrongness is on the contractor's side.

The cutoff policy decision belongs to the controller. Which delivery tickets without invoices get accrued? Common construction conventions are to accrue everything material to the job above a per-line dollar threshold, or everything older than a defined ageing window (commonly seven or fourteen days) with a delivery ticket on file. The threshold and the ageing window depend on the volume of small POs the contractor runs and the controller's tolerance for clearing-account carryover.

The inverse case: an invoice arrived and posted before the materials were received, an invoice-in-transit on the receiving side, common when the supplier ships and bills the same day and the truck takes a few days to reach the jobsite. The reconciliation is the same shape but inverted: the invoice sits in AP, the cost has not yet hit the job, and the GRNI or invoice-receipt balance carries the timing until the delivery ticket comes in. The PO and delivery receipt evidence that anchors a clean RNI accrual is the same scaffolding that supports a three-way match against the eventual invoice; the workflow walked in matching HVAC supplier invoices to POs and delivery receipts is the line-level version of the cutoff discipline this section frames at the period-close level.

---

Working with the Supplier's AR Clerk When the Variance Will Not Resolve

The variances that survive steps 1 through 5 are the ones that need a phone call. Before making it, hold a structural point in mind: the supplier's AR clerk on the other end is running the same reconciliation in reverse, against the same statement, with the same line-by-line evidence. Treating the call as a collaboration rather than an accusation gets the variance cleared faster on both sides, and the AR clerk who fields a precise, evidenced question this month remembers it next month when there is a tougher one.

What to ask first depends on the pattern, and the question is short:

• "Can you re-send invoice X" for invoices on the statement that cannot be found in AP after the timing check has resolved as much as it can.
• "Can you confirm credit memo Y was applied to the statement, and to which invoice" for credit memos posted on the contractor's side that the statement does not reflect.
• "Can you confirm payment Z was applied to invoice A" for misapplied-payment cases where an invoice still shows open on the open-item statement after the bookkeeper's payment record shows it cleared.
• "Can you re-send the RA and the credit memo for return R" when the field returned material but no credit memo ever reached AP.

What to send when the AR clerk asks for evidence is just enough to resolve the specific question. The AP listing for that supplier filtered to the period under reconciliation. The posted invoice or credit memo PDF for the line in dispute. The delivery ticket where the dispute is on a receipt rather than a posting. The cancelled check or remittance advice when the dispute is on payment application. Send only what is needed; flooding the AR clerk with the entire month's packet slows the response and signals that the contractor has not done the diagnostic work first.

The sales-tax bucket dispute is the special case. When the variance is a tax mismatch, send the resale or project exemption certificate on file along with the question. A surprising share of tax variances clear with the certificate alone, the supplier had no certificate for that project on file, the contractor had assumed the supplier did, and the supplier's billing system defaulted to taxable. Once the certificate is exchanged and the supplier's customer record is updated, the variance clears for that line and prospectively going forward.

The escalation pattern in supplier organizations is consistent enough to plan around. The AR clerk handles routine reconciliation and is the right starting point for almost every question. The credit manager handles disputed amounts and credit-hold decisions, and is the right escalation when the AR clerk has researched and pushed back, or when the disputed amount is material enough to warrant a more senior decision. The regional sales manager owns the relationship at a policy level and is the right party when the dispute is about a policy concession (a restocking-fee waiver for a long-standing customer, a special credit on damaged material, a one-off freight allowance). Escalate up the chain only after the AR clerk has had a reasonable window to respond and only with the residual variance documented in writing; jumping past the AR clerk costs goodwill the contractor will need on the next variance.

Most variances clear in one or two exchanges. A few drag across two or three statement cycles because both sides are waiting on field documentation, a delivery ticket the driver has not yet returned to dispatch, an RA the warehouse has not yet processed. Document the open variance in the reconciliation packet for the period, accept the residual where it is below the contractor's investigation threshold, and carry the rest into next month's reconciliation as a known item. A working file of carryover items is a normal feature of monthly reconciliation; one that never resolves is a signal that something structural is broken on one side.

---

The Reconciliation Packet, Audit Defensibility, and Why Extracted Data Speeds the Walk

Sign-off needs evidence, and the evidence is the reconciliation packet. For one supplier and one period, the packet contains the supplier's monthly statement; the supporting invoices and credit memos posted in the period, matched to the statement lines; the accrual journal for any RNI on open POs and delivery tickets, with the reversal scheduled for next period; the per-job coding for every variance posted; and a sign-off note from whoever ran the reconciliation, naming the residual variance accepted and the rationale. This is what a CFMA-style internal review and a CPA at year-end expect to see, the packet itself, not just a summary line that says the supplier reconciled.

The packet is the artifact that connects the workflow to the per-job coding discipline that runs through everything above. Every adjustment posted in step 6, every credit memo and restock line walked in section 4, every RNI accrual booked in section 5, carries the same job and cost code as the original receipt or invoice. Reconciliation packets that show clean per-job allocation make job-cost reports defensible during a draw review with the bank, a prequalification review with a bonding company, or a CFMA-flavored internal audit. The connection runs both ways: coding construction supplier invoices by job, phase, and cost code at the source means the reconciliation packet practically writes itself, and reconciliation discipline at the period level catches the coding errors that would otherwise compound into the cost report unnoticed.

For general contractors, the AP packet usually pairs the supplier reconciliation with the subcontractor compliance trail. The auditor or CPA at year-end wants to see both as part of the same close evidence, the supplier statements reconciled with their packets, and the subcontractor side covered by tracking subcontractor lien waivers as part of the AP packet. A clean AP close shows the entire payable side defensible: vendor balances reconciled to source, subcontractor payments evidenced by current waivers.

The variance walk is fast or slow depending on what data the bookkeeper has to work with. When supplier invoices and credit memos are already in a structured spreadsheet, with one row per invoice or one row per line item, columns for date, supplier, invoice number, net, tax, total, and a reference back to the source PDF, the walk is a few minutes per supplier. Pivot by supplier and date range, compare the totals to the statement, drill on the variance line, click through to the source PDF for the disputed line. When the same supplier invoices live as PDFs in an email inbox or a shared drive, the same walk takes hours. The catalog and the investigation order are operationally workable on extracted data; on un-extracted PDFs they are aspirational, which is why the work compresses to a single hectic week at month-end for so many AP teams. Automated invoice and credit memo data extraction is the precondition this workflow assumes; the article walks what happens after the extraction is done.

---

A Reconciliation Policy That Scales With the Contractor

At 5 to 10 active suppliers every supplier gets reconciled monthly without anyone thinking about it. Past 30 the bookkeeper cannot reconcile every supplier every month, and the choice becomes which suppliers to prioritize and on what cadence. The construction controller statement reconciliation policy is the document that names the choice, defends it to the CPA at year-end, and gives the bookkeeper the standing instruction.

The prioritization matrix below is a defensible starting point. Adjust the thresholds for the contractor's spend profile, but keep the structure, tier by spend, cadence by tier, threshold by tier, with trigger overrides for known-risk patterns.

Supplier tier	Reconciliation cadence	Variance threshold for investigation
Tier 1: Highest balance / volume (the Pareto-style top 5 to 10 suppliers by spend)	Monthly, against the full statement	Tight, investigate everything above a small fixed amount or 0.5% of monthly spend, whichever is lower
Tier 2: Mid-range (regular suppliers, smaller balances)	Quarterly full reconciliation, with a monthly statement-total check	Higher, investigate material variances only, often 1% of quarterly spend
Tier 3: Occasional / specialty (small balance, infrequent purchases)	Annually, or on-event (balance dispute, credit hold, CPA query at year-end)	Whatever the residual is when the trigger fires
Trigger overrides	Any supplier showing a credit memo, a restocking-fee variance, a payment dispute, or a credit-hold notification moves up a tier for the period regardless of cadence	Tier-1 threshold for that period

The variance threshold itself is a function of the contractor's tolerance for job-cost imprecision and the bookkeeper's investigation cost per line; too low burns hours on rounding, too high lets material errors accumulate to year-end. A common starting point is half a percent of the supplier's average monthly spend, tightened on suppliers with a history of errors and loosened on those with six months of clean reconciliations. The threshold is documented in the policy, not held in the bookkeeper's head; that is what makes it defensible.

Sign-off responsibility separates the work from the accountability. The bookkeeper or AP clerk runs the reconciliation, prepares the packet, and proposes the residual variance for acceptance. The controller signs off the residual, taking responsibility for accepting any below-threshold differences and for any open variances carried into next month's reconciliation. The sign-off note records the rationale for accepting any residual, the open variances, the supplier conversations in flight, and any policy exceptions made for the period. The packet from the previous section is the evidence behind the sign-off, the controller signs that the packet is complete, not that the supplier balance is exactly right to the dollar.

Multi-entity and multi-location contractors run the same prioritization policy with one additional layer. Supplier balances may need to be consolidated across entities for the largest accounts, where a single lumber-yard relationship serves several jobs across two or three legal entities the contractor operates. The reconciliation runs by entity (the supplier's statement comes per legal customer) and rolls up at the parent level for the prioritization tier. The operational discipline of centralizing AP across multi-location and multi-entity contractors is what makes consolidated reconciliation tractable; without it, the same supplier shows up three times in three separate reconciliations and the cross-entity timing differences create variances that look real but are not.

The make-or-buy decision eventually arrives. At 30 to 50 active suppliers, the workflow runs comfortably with one bookkeeper or AP clerk and the discipline above. At 100 to 200, the workflow benefits from extraction tooling that turns supplier invoices and credit memos into structured data the bookkeeper can pivot against the statement, and the in-house build is a defensible choice. At 200 plus suppliers across multiple entities and a meaningful AP team, the controller starts evaluating dedicated AP-automation platforms sized to construction. Comparing AP automation software for construction companies is the next research step for that cohort, framed not as a recommendation but as the matrix of options the controller has to walk before making the buy decision. The reconciliation workflow itself stays the same across all three operating models, what changes is who does which step and how the structured data gets into the bookkeeper's hands.