# AP Recovery Audit in Building Products

> How AP recovery audit works in building products: price protection, index-linked rate cards, MDF deductions, and job-site freight duplication.

Source: https://valuexpa.com/insights/ap-recovery-audit-in-building-products
Publisher: ValueXPA (https://valuexpa.com)
Updated: 2026-09-05

---

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. In building products, that gap opens in places most AP teams never look: a price-protection clause tied to a commodity index, a co-op ad fund deducted before anyone confirms the ad ran, a rebate tier keyed to SKU categories that get miscoded at the warehouse.

An AP recovery audit built for this vertical has to start from the paper that is unique to it: mill price sheets, ship-and-debit agreements, and job-site delivery tickets, not just a generic [three-way match](/guides/ap-recovery-audit-in-industrial-distribution).

## Executive Summary

Building products manufacturers and distributors run AP recovery audits against contracts that ordinary invoice review cannot parse: price protection clauses linked to lumber and OSB futures, marketing development fund (MDF) deductions taken by the vendor before proof of performance, and job-site freight billed twice across a distributor's yard and a direct carrier. None of these show up in a standard three-way match, because the PO and receipt both look correct. The dispute lives in a side letter or a rebate schedule the ERP never sees.

The mechanism is consistent across all three: someone outside AP, a pricing desk, a marketing coordinator, a regional sales manager, agreed to a term that never made it into a rule the payables system enforces. The invoice pays clean against the PO. The leakage sits in the gap between the side agreement and what actually got billed.

What changes it is treating the commodity index, the MDF schedule, and the delivery ticket as contract documents in their own right, matched against the invoice with the same rigor as a rate card, rather than filed separately from the payment process.

## 1. How does AP recovery audit differ in building products?

**It differs because the controlling document is often not the purchase order. Price protection tied to a commodity index, co-op marketing deductions, and job-site freight tickets sit outside the ERP entirely, in mill price sheets and side letters, so a standard invoice-to-PO match finds nothing wrong even when the price or the deduction is stale or unearned.**

A three-way match confirms the invoice agrees with the purchase order and the receipt. In building products that confirmation is frequently true and still wrong, because the PO was cut against a price sheet that has since moved.

Lumber, OSB, insulation board, and steel roofing components are commonly priced off a published index or a mill sheet that resets weekly or monthly. A price-protection clause typically guarantees the buyer the lower of the order-date price or the ship-date price. If nobody checks the ship-date price against the invoice, the vendor bills the higher of the two by default rather than the lower.

The same pattern repeats with marketing development funds. A vendor deducts an MDF allowance from payment based on a percentage of purchases, then the buyer is supposed to submit proof the co-op advertizing ran. When the deduction posts before the proof is verified, or when no one reconciles the deduction against actual ad spend, the fund becomes an unearned discount the vendor keeps by default.

- **Index-linked price protection:** Order-date versus ship-date pricing on lumber, OSB, and steel components, guaranteed by contract but rarely checked at invoice time.

- **MDF and co-op deductions:** Marketing fund allowances deducted from payment before proof of the advertizing is confirmed.

- **Job-site freight duplication:** A single delivery billed once by the distributor's yard fee and again by a direct carrier invoice.

- **SKU-category rebate tiers:** Volume rebates split by product line (roofing, siding, windows) that get miscoded at receiving and understate the tier earned.

## 2. What is a price protection clause and why does it get missed?

**A price protection clause guarantees a buyer the lower of the price on order date or ship date, common in lumber, OSB, and steel-component contracts where the mill repricing cycle is shorter than the order-to-delivery cycle. It gets missed because the invoice references only the ship-date price, and nobody holds the order-date price sheet against it.**

The clause exists because building products commodities can move meaningfully between the day a distributor places an order and the day a mill ships it. The contract protects the buyer from a price increase in that window, but only if someone compares two numbers that live in different systems.

The order-date price sits on a quote or a price sheet, often a PDF or an email from the sales rep. The ship-date price is what the invoice shows. AP has no reason to pull the older price sheet unless the process specifically asks for it, so the higher of the two prices becomes the invoice default rather than the exception.

This is a mechanism, not a frequency claim: the control that would catch it, matching the invoice against the price sheet in effect on order date, simply is not part of a standard AP workflow. Whether it happens on a given order depends on whether that comparison was built into the process at all.

### A. Where the price sheet lives

Price sheets in building products are typically distributed by the vendor's pricing desk directly to purchasing or sales, not routed through AP or the ERP. An audit has to source them separately, by vendor and by effective date, before a price-protection comparison is possible at all.

## 3. How do MDF and co-op advertizing deductions create leakage?

**MDF and co-op programs let a vendor deduct a marketing allowance from payment, calculated as a percentage of purchases, in exchange for advertizing the buyer is supposed to run and document. When the deduction posts automatically and the proof-of-performance step is skipped, the vendor keeps the allowance whether or not the advertizing happened.**

The program is structured as a discount conditioned on performance: the buyer earns the deduction by running qualifying advertizing and submitting evidence, a tear sheet, an invoice from the ad vendor, a screenshot of a campaign. The condition is what makes it different from a simple [volume rebate](/guides/contract-compliance-in-industrial-distribution).

In practice the deduction often appears on the remittance advice as a line item before the proof-of-performance step has happened at all, because the vendor's system calculates it automatically off purchase volume. AP records the payment net of the deduction and moves on.

The recovery question is not whether the deduction was calculated correctly against the percentage in the contract. It usually is. The question is whether the underlying condition, the advertizing itself, was ever verified. An AP recovery audit checks the MDF schedule against the proof-of-performance file, not just against the purchase volume the deduction was based on.

Two different fund types that get confused with each other in building products contracts.

| Fund type
| Trigger
| What to verify

| Co-op advertizing (MDF)
| Buyer runs qualifying ads
| Proof of performance: tear sheet, invoice, or campaign record

| Volume rebate
| Purchase volume crosses a tier
| SKU coding matches the category the tier is measured against

| Ship-and-debit allowance
| Distributor resells below list
| Resale price and date match the debit memo submitted

## 4. Why does freight get billed twice on job-site deliveries?

**Job-site deliveries in building products often route through a distributor's yard and then a final-mile carrier for oversized or bulky material, and each leg can carry its own freight line. When the distributor's invoice already includes a delivered price and a separate carrier invoice bills the same leg, the buyer pays for one movement twice.**

Roofing bundles, siding, insulation board, and window units are bulky relative to their value, which is why building products freight contracts frequently price delivered-to-job-site rather than delivered-to-dock. The delivered price is meant to already include the last leg.

When a project requires drop-shipping directly to a job site instead of the distributor's yard, a separate carrier is sometimes engaged for that leg, and its invoice can arrive through a different AP workflow than the distributor's invoice. Nothing in either invoice flags the overlap, because each one is individually accurate.

Catching this requires matching the delivery address and date on the carrier invoice against the distributor's own delivered-price invoice for the same order, a comparison that sits across two vendor files most AP systems do not link.

## 5. How do SKU-category rebate tiers get miscalculated?

**Building products rebate programs frequently split volume tiers by product category, roofing, siding, windows, decking, rather than one blended purchase total. If receiving codes a shipment to the wrong category, the purchase volume feeding that tier understates what was actually bought, and the buyer is paid a lower rebate than the contract allows.**

A distributor buying across several building product lines from one vendor rarely earns one flat rebate. The contract typically sets separate volume thresholds by category, because margins and rebate economics differ between, say, roofing shingles and vinyl siding.

The category a shipment gets coded to at receiving determines which tier it counts toward. A miscode, a roofing accessory logged under general hardware, a specialty fastener logged outside its qualifying category, quietly moves volume out of the tier it should count against.

The rebate calculation itself, run by the vendor at year-end or quarter-end, is usually arithmetically correct against the purchase data it receives. The defect is upstream, in how the purchases were categorized before that data ever reached the rebate calculation.

- **Category definitions:** Confirm the contract's category list matches the SKU-to-category mapping used at receiving, not just the mapping used for financial reporting.

- **Threshold proximity:** Categories sitting just below a tier threshold are worth checking first for miscoded volume that would cross it.

- **Cross-year coding drift:** A category mapping that changes between fiscal years without a corresponding update to the rebate schedule can silently shift volume out of a tier that was previously being credited correctly.

## 6. Can a building products distributor run this audit without third-party help?

**A distributor can run parts of it internally if someone owns pulling price sheets, MDF proof-of-performance files, and SKU-category mappings into one comparison against invoices. What is harder to replicate internally is the independence to flag a vendor's own rebate calculation as understated, since the relationship usually sits with sales or purchasing, not AP.**

The mechanical work, matching an invoice against a price sheet, a delivery ticket, or a rebate tier, does not require outside expertise. It requires time, access to documents that live outside the ERP, and a process that treats those documents as audit inputs rather than filed correspondence.

What is harder to do internally is raise a dispute against a vendor that a purchasing or sales relationship depends on. An AP team that finds a shortfall in a rebate calculation still has to escalate it to whoever owns that vendor relationship, and that escalation is easier from outside the account.

Either way, the audit only works if the source documents, price sheets, MDF schedules, delivery tickets, are gathered specifically for this vertical's contract structures rather than assumed to be covered by a standard invoice review. For the wider pattern this sits inside, start with the margin drift guide.

For the wider pattern this sits inside, start with the [margin drift](/guides/cfo-agenda-mid-market-manufacturing) guide.

## 7. Frequently Asked Questions (People Also Ask)

### What documents does a building products AP recovery audit need that a normal audit doesn't?

Mill price sheets by effective date, MDF or co-op advertizing agreements with proof-of-performance requirements, ship-and-debit agreements, and job-site delivery tickets from both the distributor and any direct carrier. None of these live in the ERP, so they have to be collected separately from the vendor or the purchasing desk.

### Who inside the company usually holds the price protection agreement?

It typically sits with the purchasing or pricing desk, not AP, because it was negotiated as part of the commercial relationship rather than the payment process. An audit has to request it directly from whoever manages that vendor rather than expect to find it in the payables system.

### Does a co-op advertizing deduction ever get reversed after payment?

It can, if the buyer disputes the deduction and shows the advertizing condition was not met or was not properly documented. The dispute has to be raised against the specific remittance line and supported with the MDF schedule and whatever proof-of-performance record exists.

### Is a ship-and-debit allowance the same as a rebate?

No. A ship-and-debit allowance compensates a distributor for reselling below list price on a specific transaction, verified against a debit memo. A rebate is calculated against cumulative purchase volume over a period. They use different triggers and need different verification steps.

### Can SKU miscoding at receiving be fixed going forward without an audit?

Fixing the mapping going forward stops new miscoding, but it does not recover volume already misallocated in past periods. An audit is what identifies how much prior volume was miscoded and whether a rebate tier was underpaid as a result.

### Why doesn't three-way matching catch price protection violations?

Three-way matching checks the invoice against the purchase order and the receipt. It does not compare the invoice price against an external price sheet from an earlier date, because that price sheet is not a document the ERP holds or references.

### What is the difference between a duplicate freight charge and a legitimate accessorial fee?

A duplicate charge bills the same movement twice, once inside a delivered price and again on a separate carrier invoice. An accessorial fee bills a distinct service, such as liftgate or inside delivery, that was not part of the base rate. Distinguishing them requires reading both invoices against the same delivery record.

### How often should price sheets be reconciled against invoices?

This depends on how frequently the vendor reprices and how the price protection clause is written. The reconciliation point is the ship date on each order, not a fixed calendar schedule, so the comparison has to happen order by order rather than periodically.

### Is contract complexity quietly draining your operating margin?

A small systematic drift between your negotiated contracts and your actual vendor billing compounds quietly across a year of invoices. Stop guessing at your exposure and run a targeted audit.

**[Take the Free Screener → https://valuexpa.com/margin-drift-screener](https://valuexpa.com/margin-drift-screener)**

## Executive Summary

Building products manufacturers and distributors run AP recovery audits against contracts that ordinary invoice review cannot parse: price protection clauses linked to lumber and OSB futures, marketing development fund (MDF) deductions taken by the vendor before proof of performance, and job-site freight billed twice across a distributor's yard and a direct carrier. None of these show up in a standard three-way match, because the PO and receipt both look correct. The dispute lives in a side letter or a rebate schedule the ERP never sees. The mechanism is consistent across all three: someone outside AP, a pricing desk, a marketing coordinator, a regional sales manager, agreed to a term that never made it into a rule the payables system enforces. The invoice pays clean against the PO. The leakage sits in the gap between the side agreement and what actually got billed. What changes it is treating the commodity index, the MDF schedule, and the delivery ticket as contract documents in their own right, matched against the invoice with the same rigor as a rate card, rather than filed separately from the payment process.

## 1. How does AP recovery audit differ in building products?

It differs because the controlling document is often not the purchase order. Price protection tied to a commodity index, co-op marketing deductions, and job-site freight tickets sit outside the ERP entirely, in mill price sheets and side letters, so a standard invoice-to-PO match finds nothing wrong even when the price or the deduction is stale or unearned. A three-way match confirms the invoice agrees with the purchase order and the receipt. In building products that confirmation is frequently true and still wrong, because the PO was cut against a price sheet that has since moved. Lumber, OSB, insulation board, and steel roofing components are commonly priced off a published index or a mill sheet that resets weekly or monthly. A price-protection clause typically guarantees the buyer the lower of the order-date price or the ship-date price. If nobody checks the ship-date price against the invoice, the vendor bills the higher of the two by default rather than the lower. The same pattern repeats with marketing development funds. A vendor deducts an MDF allowance from payment based on a percentage of purchases, then the buyer is supposed to submit proof the co-op advertizing ran. When the deduction posts before the proof is verified, or when no one reconciles the deduction against actual ad spend, the fund becomes an unearned discount the vendor keeps by default. - Index-linked price protection: Order-date versus ship-date pricing on lumber, OSB, and steel components, guaranteed by contract but rarely checked at invoice time. - MDF and co-op deductions: Marketing fund allowances deducted from payment before proof of the advertizing is confirmed. - Job-site freight duplication: A single delivery billed once by the distributor's yard fee and again by a direct carrier invoice. - SKU-category rebate tiers: Volume rebates split by product line (roofing, siding, windows) that get miscoded at receiving and understate the tier earned.

## 2. What is a price protection clause and why does it get missed?

A price protection clause guarantees a buyer the lower of the price on order date or ship date, common in lumber, OSB, and steel-component contracts where the mill repricing cycle is shorter than the order-to-delivery cycle. It gets missed because the invoice references only the ship-date price, and nobody holds the order-date price sheet against it. The clause exists because building products commodities can move meaningfully between the day a distributor places an order and the day a mill ships it. The contract protects the buyer from a price increase in that window, but only if someone compares two numbers that live in different systems. The order-date price sits on a quote or a price sheet, often a PDF or an email from the sales rep. The ship-date price is what the invoice shows. AP has no reason to pull the older price sheet unless the process specifically asks for it, so the higher of the two prices becomes the invoice default rather than the exception. This is a mechanism, not a frequency claim: the control that would catch it, matching the invoice against the price sheet in effect on order date, simply is not part of a standard AP workflow. Whether it happens on a given order depends on whether that comparison was built into the process at all. ### A. Where the price sheet lives Price sheets in building products are typically distributed by the vendor's pricing desk directly to purchasing or sales, not routed through AP or the ERP. An audit has to source them separately, by vendor and by effective date, before a price-protection comparison is possible at all.

## 3. How do MDF and co-op advertizing deductions create leakage?

MDF and co-op programs let a vendor deduct a marketing allowance from payment, calculated as a percentage of purchases, in exchange for advertizing the buyer is supposed to run and document. When the deduction posts automatically and the proof-of-performance step is skipped, the vendor keeps the allowance whether or not the advertizing happened. The program is structured as a discount conditioned on performance: the buyer earns the deduction by running qualifying advertizing and submitting evidence, a tear sheet, an invoice from the ad vendor, a screenshot of a campaign. The condition is what makes it different from a simple [volume rebate](/guides/contract-compliance-in-industrial-distribution). In practice the deduction often appears on the remittance advice as a line item before the proof-of-performance step has happened at all, because the vendor's system calculates it automatically off purchase volume. AP records the payment net of the deduction and moves on. The recovery question is not whether the deduction was calculated correctly against the percentage in the contract. It usually is. The question is whether the underlying condition, the advertizing itself, was ever verified. An AP recovery audit checks the MDF schedule against the proof-of-performance file, not just against the purchase volume the deduction was based on. Two different fund types that get confused with each other in building products contracts. | Fund type | Trigger | What to verify | | --- | --- | --- | | Co-op advertizing (MDF) | Buyer runs qualifying ads | Proof of performance: tear sheet, invoice, or campaign record | | Volume rebate | Purchase volume crosses a tier | SKU coding matches the category the tier is measured against | | Ship-and-debit allowance | Distributor resells below list | Resale price and date match the debit memo submitted |

## 4. Why does freight get billed twice on job-site deliveries?

Job-site deliveries in building products often route through a distributor's yard and then a final-mile carrier for oversized or bulky material, and each leg can carry its own freight line. When the distributor's invoice already includes a delivered price and a separate carrier invoice bills the same leg, the buyer pays for one movement twice. Roofing bundles, siding, insulation board, and window units are bulky relative to their value, which is why building products freight contracts frequently price delivered-to-job-site rather than delivered-to-dock. The delivered price is meant to already include the last leg. When a project requires drop-shipping directly to a job site instead of the distributor's yard, a separate carrier is sometimes engaged for that leg, and its invoice can arrive through a different AP workflow than the distributor's invoice. Nothing in either invoice flags the overlap, because each one is individually accurate. Catching this requires matching the delivery address and date on the carrier invoice against the distributor's own delivered-price invoice for the same order, a comparison that sits across two vendor files most AP systems do not link.

## 5. How do SKU-category rebate tiers get miscalculated?

Building products rebate programs frequently split volume tiers by product category, roofing, siding, windows, decking, rather than one blended purchase total. If receiving codes a shipment to the wrong category, the purchase volume feeding that tier understates what was actually bought, and the buyer is paid a lower rebate than the contract allows. A distributor buying across several building product lines from one vendor rarely earns one flat rebate. The contract typically sets separate volume thresholds by category, because margins and rebate economics differ between, say, roofing shingles and vinyl siding. The category a shipment gets coded to at receiving determines which tier it counts toward. A miscode, a roofing accessory logged under general hardware, a specialty fastener logged outside its qualifying category, quietly moves volume out of the tier it should count against. The rebate calculation itself, run by the vendor at year-end or quarter-end, is usually arithmetically correct against the purchase data it receives. The defect is upstream, in how the purchases were categorized before that data ever reached the rebate calculation. - Category definitions: Confirm the contract's category list matches the SKU-to-category mapping used at receiving, not just the mapping used for financial reporting. - Threshold proximity: Categories sitting just below a tier threshold are worth checking first for miscoded volume that would cross it. - Cross-year coding drift: A category mapping that changes between fiscal years without a corresponding update to the rebate schedule can silently shift volume out of a tier that was previously being credited correctly.

## 6. Can a building products distributor run this audit without third-party help?

A distributor can run parts of it internally if someone owns pulling price sheets, MDF proof-of-performance files, and SKU-category mappings into one comparison against invoices. What is harder to replicate internally is the independence to flag a vendor's own rebate calculation as understated, since the relationship usually sits with sales or purchasing, not AP. The mechanical work, matching an invoice against a price sheet, a delivery ticket, or a rebate tier, does not require outside expertise. It requires time, access to documents that live outside the ERP, and a process that treats those documents as audit inputs rather than filed correspondence. What is harder to do internally is raise a dispute against a vendor that a purchasing or sales relationship depends on. An AP team that finds a shortfall in a rebate calculation still has to escalate it to whoever owns that vendor relationship, and that escalation is easier from outside the account. Either way, the audit only works if the source documents, price sheets, MDF schedules, delivery tickets, are gathered specifically for this vertical's contract structures rather than assumed to be covered by a standard invoice review. For the wider pattern this sits inside, start with the margin drift guide. For the wider pattern this sits inside, start with the [margin drift](/guides/cfo-agenda-mid-market-manufacturing) guide.

## Common questions

### What documents does a building products AP recovery audit need that a normal audit doesn't?

Mill price sheets by effective date, MDF or co-op advertizing agreements with proof-of-performance requirements, ship-and-debit agreements, and job-site delivery tickets from both the distributor and any direct carrier. None of these live in the ERP, so they have to be collected separately from the vendor or the purchasing desk.

### Who inside the company usually holds the price protection agreement?

It typically sits with the purchasing or pricing desk, not AP, because it was negotiated as part of the commercial relationship rather than the payment process. An audit has to request it directly from whoever manages that vendor rather than expect to find it in the payables system.

### Does a co-op advertizing deduction ever get reversed after payment?

It can, if the buyer disputes the deduction and shows the advertizing condition was not met or was not properly documented. The dispute has to be raised against the specific remittance line and supported with the MDF schedule and whatever proof-of-performance record exists.

### Is a ship-and-debit allowance the same as a rebate?

No. A ship-and-debit allowance compensates a distributor for reselling below list price on a specific transaction, verified against a debit memo. A rebate is calculated against cumulative purchase volume over a period. They use different triggers and need different verification steps.

### Can SKU miscoding at receiving be fixed going forward without an audit?

Fixing the mapping going forward stops new miscoding, but it does not recover volume already misallocated in past periods. An audit is what identifies how much prior volume was miscoded and whether a rebate tier was underpaid as a result.

---

ValueXPA runs a fixed-scope Margin Drift Diagnostic that validates every service vendor invoice against contract terms, for $100M+ US industrial manufacturers and distributors. Two to four weeks. The client retains 100% of recoveries. https://valuexpa.com/contact-us
