Reclass

Reclass shifts a charge into a different cost or GL category so the invoice line no longer maps to its contract clause during matching. Read the full guide.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
Reclass

A reclass is the practice of recording or coding a charge under a different cost category or general ledger line than the one its governing contract clause covers. It surfaces on the invoice as an ordinary line item, so nothing about the document itself signals that the review process needs to match it against a different rule than the one it appears to belong to.

Reclass is a coding practice, not a pricing error in itself. Once a charge is coded under the wrong category, invoice-to-contract matching pairs the line against the wrong rule, or against no rule at all, and the amount billed is never tested against the term that actually applies to it. The fix is a category cross-check run before the rate check, confirming the invoice line's coded category matches the category the governing clause expects.

1. What is reclass?

Reclass is when a vendor records a charge under a cost category, GL code, or line description different from the one its governing contract clause covers. A freight surcharge coded as a base transportation charge, or a labor premium coded as regular hours, are both reclasses. The invoice still reads as normal; the mismatch is between the label on the line and the clause that actually prices it.

The word describes a coding event, not a dollar amount. A reclass can be an honest administrative shortcut, a template applied without checking, or a way to route a charge around the clause that would cap or reject it. Intent is not visible from the invoice line alone.

2. Why does reclass cause margin drift?

Invoice-to-contract matching works by pairing a line's category to the clause written for that category: a rate card row, a volume tier, a not-to-exceed cap. When a charge is coded into a category the clause was never written for, the match either fails silently or attaches to the wrong rule, and the true governing term never gets tested against the amount billed.

This is the mechanism behind margin drift generally: contract terms exist in one structure, invoice coding exists in another, and a reclass widens the gap between them.

3. How does reclass differ from a legitimate cost allocation?

A legitimate allocation splits a real, shared cost across departments or projects using a documented method, and the total billed still traces back to the contracted rate. A reclass changes which clause the charge is tested against, not how it is split. The distinguishing question is not how the number was divided but whether the category label still points to the clause that actually governs the charge.

Reviewers can check this without judging intent: pull the line's category code, find the clause written for that code, and confirm the two match before checking the rate itself.

4. How is reclass caught in an audit?

Reclass is caught by tracing each invoice line back to the specific contract clause that governs it, independent of how the vendor labeled or coded the charge, then confirming the category assigned on the invoice matches the category the clause was written for. A mismatch between the two, found before the rate itself is even checked, is the signal.

This is a category-level check, separate from and prior to a rate-level check, which is why it catches drift that a simple rate comparison would miss entirely.

  • Category cross-check: Each invoice line's cost category is compared against the category the contract's clause structure expects, before the rate is checked, so a mismatched label surfaces on its own.
  • Clause tracing: The reviewer traces each charge back to the specific clause it should sit under, rather than accepting the vendor's stated category, closing the gap a reclass depends on.
  • Sample re-coding: A sample of lines is re-coded independently of the vendor's own labels, then compared against the original coding to surface systematic mismatches.

For the wider pattern this sits inside, start with the margin drift guide. See also accessorial charge audit: the surcharges nobody validates and rate card enforcement: why approved timesheets still produce wrong invoices.

5. Frequently Asked Questions (People Also Ask)

Is reclass the same as fraud?

No. Reclass describes a coding outcome, a charge sitting under the wrong category, and that outcome can result from an honest template error, an administrative shortcut, or a deliberate attempt to avoid a clause. The label alone does not tell you which.

Does reclass always change the dollar amount billed?

Not directly. Reclass changes which contract clause the charge is tested against. The dollar impact comes afterward, when the wrong clause, or no clause, ends up governing an amount that should have been capped, tiered, or rejected.

Where does reclass most often show up on an invoice?

It can appear anywhere a vendor assigns its own cost category or GL code to a line item, since that coding step is where the mismatch between label and governing clause originates.

Can three-way matching catch a reclass?

Three-way matching checks the invoice against the purchase order and receipt. It does not test whether the invoice's cost category matches the category the contract clause was written for, so a reclass can clear three-way matching untouched.

How is reclass different from accessorial charge creep?

Accessorial charge creep is a specific pattern of add-on fees drifting upward over time. Reclass is a broader coding mechanism: a charge moved into a different category, which can affect any clause type, not only accessorials.

What contract language reduces reclass risk?

A contract that defines cost categories explicitly, and ties each clause to a specific category code rather than a general description, gives a reviewer a fixed reference to check invoice coding against.

Does reclass apply outside freight and labor?

Yes. Any vendor category that assigns cost codes, including maintenance, IT services, and MRO, can carry a reclass, because the underlying mechanism is a coding choice, not a feature of one service category.

Who typically assigns the category code on an invoice?

The vendor's billing system assigns the code at invoice generation, based on its own internal service or product taxonomy, which is not always mapped one-to-one with the buyer's contract structure.

1. What is reclass?

Reclass is when a vendor records a charge under a cost category, GL code, or line description different from the one its governing contract clause covers. A freight surcharge coded as a base transportation charge, or a labor premium coded as regular hours, are both reclasses. The invoice still reads as normal; the mismatch is between the label on the line and the clause that actually prices it. The word describes a coding event, not a dollar amount. A reclass can be an honest administrative shortcut, a template applied without checking, or a way to route a charge around the clause that would cap or reject it. Intent is not visible from the invoice line alone.

2. Why does reclass cause margin drift?

Invoice-to-contract matching works by pairing a line's category to the clause written for that category: a rate card row, a volume tier, a not-to-exceed cap. When a charge is coded into a category the clause was never written for, the match either fails silently or attaches to the wrong rule, and the true governing term never gets tested against the amount billed. This is the mechanism behind [margin drift](/guides/margin-drift-vs-legitimate-price-increases-how-to-tell-them) generally: contract terms exist in one structure, invoice coding exists in another, and a reclass widens the gap between them.

3. How does reclass differ from a legitimate cost allocation?

A legitimate allocation splits a real, shared cost across departments or projects using a documented method, and the total billed still traces back to the contracted rate. A reclass changes which clause the charge is tested against, not how it is split. The distinguishing question is not how the number was divided but whether the category label still points to the clause that actually governs the charge. Reviewers can check this without judging intent: pull the line's category code, find the clause written for that code, and confirm the two match before checking the rate itself.

4. How is reclass caught in an audit?

Reclass is caught by tracing each invoice line back to the specific contract clause that governs it, independent of how the vendor labeled or coded the charge, then confirming the category assigned on the invoice matches the category the clause was written for. A mismatch between the two, found before the rate itself is even checked, is the signal. This is a category-level check, separate from and prior to a rate-level check, which is why it catches drift that a simple rate comparison would miss entirely. - Category cross-check: Each invoice line's cost category is compared against the category the contract's clause structure expects, before the rate is checked, so a mismatched label surfaces on its own. - Clause tracing: The reviewer traces each charge back to the specific clause it should sit under, rather than accepting the vendor's stated category, closing the gap a reclass depends on. - Sample re-coding: A sample of lines is re-coded independently of the vendor's own labels, then compared against the original coding to surface systematic mismatches. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide. See also [accessorial charge audit: the surcharges nobody validates](/guides/accessorial-charge-audit-the-surcharges-nobody-validates) and [rate card enforcement: why approved timesheets still produce wrong invoices](/guides/rate-card-enforcement-why-approved-timesheets-still-produce).

Questions & Answers

Is reclass the same as fraud?

No. Reclass describes a coding outcome, a charge sitting under the wrong category, and that outcome can result from an honest template error, an administrative shortcut, or a deliberate attempt to avoid a clause. The label alone does not tell you which.

Does reclass always change the dollar amount billed?

Not directly. Reclass changes which contract clause the charge is tested against. The dollar impact comes afterward, when the wrong clause, or no clause, ends up governing an amount that should have been capped, tiered, or rejected.

Where does reclass most often show up on an invoice?

It can appear anywhere a vendor assigns its own cost category or GL code to a line item, since that coding step is where the mismatch between label and governing clause originates.

Can three-way matching catch a reclass?

Three-way matching checks the invoice against the purchase order and receipt. It does not test whether the invoice's cost category matches the category the contract clause was written for, so a reclass can clear three-way matching untouched.

How is reclass different from accessorial charge creep?

Accessorial charge creep is a specific pattern of add-on fees drifting upward over time. Reclass is a broader coding mechanism: a charge moved into a different category, which can affect any clause type, not only accessorials.

Margin Drift Resources