Detective Control

A detective control finds errors that already occurred, like a contract compliance audit that catches invoice charges a preventive check let through.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
Detective Control

A detective control is a check that finds an error after it has already happened, rather than stopping it before it posts. Margin drift is the gap between what a vendor contract says and what the invoice actually charges, and detective controls are how that gap gets found once a preventive control has already let a charge through. AP teams rely on both kinds of control, but they catch different things at different points.

1. What Counts As A Detective Control?

A detective control is any review that examines transactions after they have posted and flags the ones that violate a rule. Invoice-to-contract matching against a rate card, a periodic audit of paid invoices, and a variance report comparing billed amounts to a contract are all detective controls. They do not stop the payment. They surface it for correction, credit, or recovery.

Detective controls sit downstream of the transaction. A three-way match at receipt is preventive; a quarterly review of already-paid invoices against contract terms is detective.

2. How Is A Detective Control Different From A Preventive Control?

A preventive control stops an error before it posts, such as a purchase order block that rejects an invoice above a price ceiling. A detective control finds the error after posting, such as a review that compares paid invoices to a rate card. Preventive controls need the rule configured correctly in advance. Detective controls catch what the preventive rule missed or never covered.

Neither type is complete alone. A contract renegotiated last quarter may not yet be reflected in a preventive rule; a detective review closes that gap.

3. Where Do Detective Controls Fit In An AP Recovery Audit?

An AP recovery audit is itself a detective control, applied retrospectively to a period of paid invoices. It compares what was billed against contract terms and flags variances such as a rate card mismatch, a missed credit memo, or a duplicate payment. The finding is a candidate for recovery, not a stopped payment, because the invoice has already been paid.

This is why the audit runs against history rather than the next invoice. It is diagnostic, not preventive, by design.

4. What Are Common Examples Of Detective Controls In AP?

Common detective controls include a periodic reconciliation of paid invoices against a vendor's rate card, a review for duplicate payments across vendors, a check for unapplied rebates, and a comparison of billed scope to contracted scope. Each one runs after payment and produces a finding that requires a correction or a recovery, not a blocked transaction.

Detective controls vary by category. Freight and 3PL, contract labor, and MRO spend each carry their own recurring variance types worth checking.

  • Rate card reconciliation: Compares billed unit prices against the contracted rate card for the period.
  • Duplicate payment review: Checks paid invoices across vendors and periods for repeated payment of the same charge.
  • Credit memo tracking: Confirms that credits owed under the contract were actually issued and applied.
  • Scope-to-contract comparison: Checks billed line items against what the contract actually authorizes.

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.

5. Frequently Asked Questions (People Also Ask)

Is an audit a detective control?

Yes. An audit examines transactions that have already occurred and flags the ones that violate a rule, which is the defining feature of a detective control, as opposed to a preventive control that blocks the transaction beforehand.

Does a detective control stop a bad payment?

No. By the time a detective control runs, the invoice has typically already been paid. The control produces a finding, such as an overcharge or a missed credit, that then becomes a candidate for recovery rather than a blocked transaction.

Why not just rely on preventive controls?

A preventive control only catches what its rule was configured to catch. Contract terms change, exceptions get made, and new vendors get onboarded without every rule updated. A detective control checks the actual paid history against the actual contract, closing gaps a preventive rule missed.

What is the difference between detective and corrective controls?

A detective control finds the error. A corrective control is the action taken afterward, such as issuing a credit memo request or updating a rate table. Detective controls identify the problem; corrective controls resolve it.

Can a detective control become a preventive one?

A finding from a detective control, such as a recurring rate card mismatch, can be used to configure a preventive rule going forward. The detective review identifies the pattern; the preventive control then blocks it before it recurs.

What triggers the need for a detective control?

A detective control is needed anywhere a preventive rule may be missing, outdated, or never configured, such as after a contract renegotiation, a new vendor onboarding, or a category where terms live in a PDF outside the ERP rather than in a system rule.

Does contract labor billing need a detective control?

Yes. Shift premiums, overtime multipliers, and not-to-exceed caps in staffing contracts are frequently billed incorrectly without a preventive rule catching it, which is why a periodic detective review of paid labor invoices against contract terms matters.

1. What Counts As A Detective Control?

A detective control is any review that examines transactions after they have posted and flags the ones that violate a rule. Invoice-to-contract matching against a rate card, a periodic audit of paid invoices, and a variance report comparing billed amounts to a contract are all detective controls. They do not stop the payment. They surface it for correction, credit, or recovery. Detective controls sit downstream of the transaction. A three-way match at receipt is preventive; a quarterly review of already-paid invoices against contract terms is detective.

2. How Is A Detective Control Different From A Preventive Control?

A preventive control stops an error before it posts, such as a purchase order block that rejects an invoice above a price ceiling. A detective control finds the error after posting, such as a review that compares paid invoices to a rate card. Preventive controls need the rule configured correctly in advance. Detective controls catch what the preventive rule missed or never covered. Neither type is complete alone. A contract renegotiated last quarter may not yet be reflected in a preventive rule; a detective review closes that gap.

3. Where Do Detective Controls Fit In An AP Recovery Audit?

An AP recovery audit is itself a detective control, applied retrospectively to a period of paid invoices. It compares what was billed against contract terms and flags variances such as a rate card mismatch, a missed credit memo, or a duplicate payment. The finding is a candidate for recovery, not a stopped payment, because the invoice has already been paid. This is why the audit runs against history rather than the next invoice. It is diagnostic, not preventive, by design.

4. What Are Common Examples Of Detective Controls In AP?

Common detective controls include a periodic reconciliation of paid invoices against a vendor's rate card, a review for duplicate payments across vendors, a check for unapplied rebates, and a comparison of billed scope to contracted scope. Each one runs after payment and produces a finding that requires a correction or a recovery, not a blocked transaction. Detective controls vary by category. Freight and 3PL, [contract labor](/glossary/contract-labor-and-staffing-audit), and MRO spend each carry their own recurring variance types worth checking. - Rate card reconciliation: Compares billed unit prices against the contracted rate card for the period. - Duplicate payment review: Checks paid invoices across vendors and periods for repeated payment of the same charge. - Credit memo tracking: Confirms that credits owed under the contract were actually issued and applied. - Scope-to-contract comparison: Checks billed line items against what the contract actually authorizes. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide. See also [margin drift vs. legitimate price increases: how to tell them apart](/guides/margin-drift-vs-legitimate-price-increases-how-to-tell-them) and [accessorial charge audit: the surcharges nobody validates](/guides/accessorial-charge-audit-the-surcharges-nobody-validates).

Questions & Answers

Is an audit a detective control?

Yes. An audit examines transactions that have already occurred and flags the ones that violate a rule, which is the defining feature of a detective control, as opposed to a preventive control that blocks the transaction beforehand.

Does a detective control stop a bad payment?

No. By the time a detective control runs, the invoice has typically already been paid. The control produces a finding, such as an overcharge or a missed credit, that then becomes a candidate for recovery rather than a blocked transaction.

Why not just rely on preventive controls?

A preventive control only catches what its rule was configured to catch. Contract terms change, exceptions get made, and new vendors get onboarded without every rule updated. A detective control checks the actual paid history against the actual contract, closing gaps a preventive rule missed.

What is the difference between detective and corrective controls?

A detective control finds the error. A corrective control is the action taken afterward, such as issuing a credit memo request or updating a rate table. Detective controls identify the problem; corrective controls resolve it.

Can a detective control become a preventive one?

A finding from a detective control, such as a recurring rate card mismatch, can be used to configure a preventive rule going forward. The detective review identifies the pattern; the preventive control then blocks it before it recurs.

Margin Drift Resources