AP recovery audit in food and beverage manufacturing

Executive Summary

Food and beverage manufacturers carry three billing structures that most AP teams are not staffed to verify line by line: catch weight invoicing on perishable and protein inputs, co-packer or co-manufacturer tolling statements, and commodity index pass-through clauses on ingredient contracts. Each one replaces a fixed unit price with a variable calculation, and a variable calculation is where an invoice can drift from its contract without ever looking wrong on its face.

The mechanism is the same across all three: the invoice states a number that looks plausible in isolation, but the number depends on an input (actual shipped weight, a tolling yield percentage, an index value on a stated date) that AP does not independently verify. Three-way matching checks the invoice against the purchase order and receipt. It does not recompute a catch weight extension or check whether a co-packer's tolling statement used the contracted yield rate.

What changes this is treating each variable-price mechanism as its own control point: pulling the source data the invoice depends on (scale tickets, tolling yield reports, published index values) and recomputing the invoice independently, rather than trusting the vendor's arithmetic.

1. How does AP recovery audit differ in food and beverage manufacturing?

It differs because a meaningful share of food and beverage vendor spend is billed on variable, not fixed, terms: catch weight for perishable and protein inputs, tolling yield for co-packed product, and commodity index pass-through for ingredient contracts. Each replaces a static unit price with a calculation AP must reconstruct from source data, not just match against a PO.

A recovery audit built for a fixed unit price catches quantity errors and duplicate payments. It was not designed to catch a catch weight extension computed off the wrong scale ticket, or a tolling statement that applied last quarter's yield percentage instead of the current contracted rate.

That difference is structural, not a matter of degree. Industrial distribution and metal fabrication vendors bill against a rate card or a per-unit price that does not move invoice to invoice. Food and beverage inputs, particularly meat, cheese, and produce, are priced against the actual weight delivered, which changes every shipment.

The audit therefore needs a different source document for each mechanism: the scale ticket for catch weight, the tolling agreement's yield table for co-pack statements, and the published index value for pass-through clauses. Without those three source documents, the invoice cannot be independently recomputed, only compared to itself.

2. What is catch weight pricing and where does it drift?

Catch weight pricing bills the actual delivered weight of a perishable or protein product rather than a fixed case price, so the invoice total depends on a scale ticket generated at the vendor's dock, not on a number your ERP already holds. Drift appears when the invoiced weight does not match the scale ticket, or when a contracted price break by weight tier is not applied.

A catch weight item, a case of chicken breast or a block of cheese, ships at a weight that varies shipment to shipment. The contract sets a price per pound, but the pound figure on the invoice comes from the vendor's own scale reading at time of pack or ship.

AP systems built around fixed unit pricing have no independent record of that weight to check against. The purchase order states an estimated case count and price; the invoice states an actual weight the buyer's dock did not necessarily record with the same precision.

The recovery audit's job here is to pull the vendor's own scale ticket or bill of lading weight and compare it line by line to the invoiced weight, and separately to check whether a weight-tier price break in the contract, common on volume-priced protein contracts, was applied at the correct tier rather than the prior shipment's tier.

3. How does co-packer and tolling billing create audit gaps?

A co-packer bills for converting raw ingredients into finished product using a tolling agreement that sets a yield percentage, the ratio of finished output to raw input the co-packer is contractually allowed to charge against. Drift occurs when the tolling statement bills against a lower yield than the agreement specifies, charging for input that should have converted to billable finished goods.

Tolling arrangements are specific to contract manufacturing relationships, which are common in food and beverage and largely absent in the other verticals this audit covers. The manufacturer supplies or pays for raw ingredients, the co-packer converts them, and the yield percentage in the agreement sets how much raw input is allowed per unit of finished product before the co-packer absorbs the loss.

A co-packer's monthly tolling statement states an actual yield achieved and bills processing fees against it. If the stated yield is below the contracted floor, the manufacturer is being billed for the co-packer's own inefficiency, a cost the tolling agreement was written to exclude.

This is not a duplicate payment or a rate card mismatch in the sense a generic AP audit looks for. It requires reading the tolling agreement's yield clause and recomputing the statement's yield claim against the raw input volumes actually shipped to the co-packer.

4. Which contracts carry commodity index pass-through clauses?

Ingredient supply contracts for dairy, grain, and edible oils commonly tie the invoiced price to a published commodity index on a stated pricing date, adjusted by a contracted formula. Drift appears when the invoice uses a different date's index value, an outdated formula version, or fails to pass through a decrease with the same speed it applies an increase.

A pass-through clause exists so neither party bears full commodity volatility alone: the buyer's invoice price moves with a named index, read on a date the contract specifies, run through a formula also stated in the contract.

The audit point is date and formula fidelity. An index value read three days after the contracted pricing date, during a week the index moved, produces a different invoice price than the contract specifies, and the difference does not announce itself on the invoice.

The asymmetry risk is separate and worth checking on its own: a supplier applying an increase the day the index moves but a decrease only at the next scheduled review is following the letter of a poorly drafted clause, not a contract violation, but it is still a recovery opportunity to renegotiate. This is general information, not legal advice.

5. Can standard three-way matching catch these drift types?

No. Three-way matching checks that an invoice matches its purchase order and a goods receipt. It confirms quantity and a stated unit price were both authorized. It does not recompute a catch weight extension, verify a tolling yield percentage, or check an index value against a contracted pricing date, because none of those calculations live inside the PO or receipt record.

The PO for a catch weight item states an estimated quantity and price; it cannot state an exact weight that does not exist until the shipment is packed. Three-way matching therefore approves the invoice on the PO and receipt it has, and the weight-driven price extension passes through unexamined.

Tolling statements often are not run through PO matching at all: they are periodic invoices against a service agreement, closer to a subscription than a purchase order line. The yield calculation inside them sits entirely outside the AP system's normal control.

Commodity pass-through clauses fail for a different reason: the correct price depends on an external, time-stamped data point the ERP does not hold. Matching software checks internal records against each other. It has no mechanism to fetch a commodity index value and check whether the invoice used the contractually specified date.

6. What source documents does a recovery audit need for this vertical?

Three documents outside the standard PO-invoice-receipt set: the vendor's scale ticket or bill of lading for catch weight items, the tolling agreement's yield table alongside the co-packer's production report, and the published commodity index value for the contracted pricing date on pass-through invoices. Without these, the invoice can only be checked against itself.

Gathering these documents is the difference between a recovery audit that reviews food and beverage spend the same way it reviews any other indirect category, and one that actually tests the mechanisms specific to this vertical.

None of these documents live inside a standard ERP purchase order or receipt record. They are held by the vendor, or by a plant quality or procurement team outside AP's normal workflow, which is precisely why they go unchecked in a standard audit cycle.

• Scale tickets or BOLs: The vendor's own weight record at time of ship or pack, needed to verify a catch weight extension independently of the invoice.
• Tolling yield tables: The contracted yield floor from the co-packer agreement, compared against the co-packer's stated production yield for the billing period.
• Published index values: The commodity index reading for the exact date the pricing contract specifies, not the date the invoice happens to cite.
• Contract formula versions: Pass-through clauses are sometimes amended; an invoice applying a prior formula version understates or overstates the correct price.

For the wider pattern this sits inside, start with the margin drift guide. See also margin drift vs. legitimate price increases: how to tell them apart and accessorial charge audit: the surcharges nobody validates.

7. Frequently Asked Questions (People Also Ask)

Does catch weight pricing apply to all food and beverage vendors?

It applies specifically to inputs sold by variable weight, mainly proteins, cheese, and fresh produce. Packaged, shelf-stable ingredients and most non-food inputs like packaging materials are priced on fixed units and do not carry this drift mechanism.

What is a tolling yield percentage?

It is the ratio of finished product a co-packer is contractually allowed to bill for relative to the raw input supplied. The agreement sets a floor; a co-packer billing against a lower actual yield is charging for input that did not convert to billable output.

How do we verify a commodity index pass-through invoice?

Pull the published index value for the exact date the contract specifies, run it through the contract's stated formula, and compare that result to the invoiced price. A discrepancy usually traces to a wrong pricing date or an outdated formula version.

Can our ERP flag catch weight discrepancies automatically?

Only if it is fed the vendor's scale ticket or bill of lading weight as a separate data point to compare against the invoice. Most ERPs store an estimated PO quantity, not an independently captured actual weight, so this check has to be built as a manual or supplementary step.

Is a co-packer's tolling statement covered by standard three-way matching?

Usually not, because tolling statements are billed against a service agreement rather than a discrete purchase order and receipt. They need to be checked against the agreement's yield table directly.

Do pass-through clauses ever work against the buyer?

They can if the clause is asymmetric, applying price increases immediately while delaying decreases to a scheduled review date. That is not a contract violation, but it is worth flagging for renegotiation. This is general information, not legal advice.

How is this different from the AP recovery audit approach in other verticals?

Other verticals covered by this audit approach bill largely on fixed unit prices or standard rate cards. Food and beverage adds three variable-price mechanisms, catch weight, tolling yield, and commodity pass-through, that require different source documents and a different verification method entirely.

What is margin drift in the context of a tolling agreement?

It is the gap between the yield percentage the tolling agreement specifies and the yield actually billed on the co-packer's statement. The gap is easy to miss because the statement looks like a routine processing invoice rather than a contract compliance question.