Pre-audit

Pre-audit ranks vendor contracts by spend and documentation gaps before a full invoice-to-contract review, focusing audit hours where they matter.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
Pre-audit

A pre-audit is a scoping pass that identifies which vendor contracts, categories, and time periods are worth a full invoice-to-contract review before that review begins. It runs on readily available data: the vendor list, contract file completeness, and total spend by category. The goal is not to find leakage yet. It is to decide where a deeper audit will pay for itself and where it will not.

Its output is a short list, not a finding. It names the vendors and contract categories worth examining first, and states why each was included or excluded. What changes after a pre-audit is sequencing: the team stops treating every vendor equally and starts the deeper work where a contract exists to test against and the spend justifies the hours it takes.

1. What is pre-audit?

A pre-audit is a short scoping exercise that ranks vendor contracts by spend, contract-file completeness, and time since last review, so a company knows where to point a full invoice-to-contract audit. It produces a prioritized list of vendors and categories, not a finding of leakage. It answers one question: given limited audit hours, where should they go first.

It sits before the work described in a freight and 3PL audit or a contract labor and staffing audit, not instead of it. A full diagnostic still has to run the invoice-level checks that a pre-audit only points toward.

2. What data does a pre-audit require?

A pre-audit needs the vendor master with spend by category, the contract repository, and dates of the last rate change or renewal for each vendor. It does not need invoice-level detail yet. The point is to see which vendors have a contract on file at all, which contracts are old enough that terms may have drifted from practice, and which categories carry spend large enough to justify a full review.

Missing contracts show up here first, before any invoice is opened.

  • Vendor master: Total spend per vendor over the review period, by category.
  • Contract repository: Whether a signed contract exists for each vendor with meaningful spend.
  • Rate card currency: Date of the last rate card or amendment, to flag contracts overdue for a look.
  • Renewal and change dates: Recent renewals or ownership changes, which raise the odds terms shifted.

3. How does a pre-audit differ from the full diagnostic?

A pre-audit ranks candidates; the full diagnostic tests them. The pre-audit works at the vendor and category level using spend totals and contract metadata. The diagnostic works at the line-item level, matching individual invoice charges against rate cards, volume tiers, and surcharge schedules to find specific instances such as a rebate gap or a missed credit memo.

One decides where to look, the other looks.

Skipping the pre-audit on a large vendor base means spending diagnostic hours on contracts too small or too undocumented to be worth it. The pre-audit runs in days on spend totals and contract metadata. The full diagnostic runs line by line and delivers a prioritized roadmap in 2 to 4 weeks, across ValueXPA diagnostics.

4. Which vendors does a pre-audit usually flag first?

A pre-audit flags a vendor when spend is material relative to the category, the contract has not been revisited since a rate or volume change, or no contract can be located at all despite active spend. Each of these is a condition that can be checked mechanically against the vendor master and contract file. None of them require opening an invoice, which is what keeps the pre-audit fast.

A vendor with a rate card older than the last renewal cycle is a candidate for review under index escalation misapplied or volume tier misapplication once the full audit starts.

For the wider pattern this sits inside, start with the margin drift guide.

5. Frequently Asked Questions (People Also Ask)

Is a pre-audit the same thing as the Margin Drift Diagnostic?

No. The pre-audit is a scoping step that decides which vendors and categories the diagnostic should examine first. The diagnostic itself is the line-by-line invoice-to-contract review, delivered as a prioritized recovery and prevention roadmap in 2 to 4 weeks, across ValueXPA diagnostics.

How long does a pre-audit take?

It depends on how complete the vendor master and contract repository already are. A company with a maintained contract file can complete it in days. One with contracts scattered across email and shared drives will spend most of that time just locating the documents.

Does a pre-audit require reading every contract in full?

No. It works from contract metadata, whether a contract exists, its category, and its last amendment date, rather than reading full contract terms. Reading terms line by line against invoices is the job of the full diagnostic that follows.

What happens if a vendor has spend but no contract on file?

That vendor is flagged automatically. Spend without a locatable contract means there is nothing yet to test invoices against, which makes it a priority for document recovery before or during the full audit.

Can a pre-audit be done with spreadsheet data alone?

Yes. It only needs a vendor list with spend by category and a way to check contract existence and dates, both of which are commonly available in a spreadsheet export from the ERP and a contract folder listing.

Does a pre-audit find any actual overbilling?

No. It identifies where to look, not what is wrong. Specific issues such as a duplicate payment or an accessorial charge creep are found during the full invoice-to-contract review, not during scoping.

How is a pre-audit different from a contract inventory?

A contract inventory just lists what exists. A pre-audit adds spend and recency to that list and produces a ranked order for review, so it is a contract inventory used for a decision rather than kept as a record.

Who typically runs a pre-audit inside a company?

Usually the AP lead or procurement lead, since they already have access to the vendor master and contract repository. A controller or CFO reviews the resulting priority list before committing hours to the full review.

1. What is pre-audit?

A pre-audit is a short scoping exercise that ranks vendor contracts by spend, contract-file completeness, and time since last review, so a company knows where to point a full invoice-to-contract audit. It produces a prioritized list of vendors and categories, not a finding of leakage. It answers one question: given limited audit hours, where should they go first. It sits before the work described in a [freight and 3PL audit](/glossary/freight-and-3pl-audit) or a [contract labor and staffing audit](/glossary/contract-labor-and-staffing-audit), not instead of it. A full diagnostic still has to run the invoice-level checks that a pre-audit only points toward.

2. What data does a pre-audit require?

A pre-audit needs the vendor master with spend by category, the contract repository, and dates of the last rate change or renewal for each vendor. It does not need invoice-level detail yet. The point is to see which vendors have a contract on file at all, which contracts are old enough that terms may have drifted from practice, and which categories carry spend large enough to justify a full review. Missing contracts show up here first, before any invoice is opened. - Vendor master: Total spend per vendor over the review period, by category. - Contract repository: Whether a signed contract exists for each vendor with meaningful spend. - Rate card currency: Date of the last rate card or amendment, to flag contracts overdue for a look. - Renewal and change dates: Recent renewals or ownership changes, which raise the odds terms shifted.

3. How does a pre-audit differ from the full diagnostic?

A pre-audit ranks candidates; the full diagnostic tests them. The pre-audit works at the vendor and category level using spend totals and contract metadata. The diagnostic works at the line-item level, matching individual invoice charges against rate cards, volume tiers, and surcharge schedules to find specific instances such as a rebate gap or a missed credit memo. One decides where to look, the other looks. Skipping the pre-audit on a large vendor base means spending diagnostic hours on contracts too small or too undocumented to be worth it. The pre-audit runs in days on spend totals and contract metadata. The full diagnostic runs line by line and delivers a prioritized roadmap in 2 to 4 weeks, across ValueXPA diagnostics.

4. Which vendors does a pre-audit usually flag first?

A pre-audit flags a vendor when spend is material relative to the category, the contract has not been revisited since a rate or volume change, or no contract can be located at all despite active spend. Each of these is a condition that can be checked mechanically against the vendor master and contract file. None of them require opening an invoice, which is what keeps the pre-audit fast. A vendor with a rate card older than the last renewal cycle is a candidate for review under [index escalation misapplied](/glossary/index-escalation-misapplied) or [volume tier misapplication](/glossary/volume-tier-misapplication) once the full audit starts. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide.

Questions & Answers

Is a pre-audit the same thing as the Margin Drift Diagnostic?

No. The pre-audit is a scoping step that decides which vendors and categories the diagnostic should examine first. The diagnostic itself is the line-by-line invoice-to-contract review, delivered as a prioritized recovery and prevention roadmap in 2 to 4 weeks, across ValueXPA diagnostics.

How long does a pre-audit take?

It depends on how complete the vendor master and contract repository already are. A company with a maintained contract file can complete it in days. One with contracts scattered across email and shared drives will spend most of that time just locating the documents.

Does a pre-audit require reading every contract in full?

No. It works from contract metadata, whether a contract exists, its category, and its last amendment date, rather than reading full contract terms. Reading terms line by line against invoices is the job of the full diagnostic that follows.

What happens if a vendor has spend but no contract on file?

That vendor is flagged automatically. Spend without a locatable contract means there is nothing yet to test invoices against, which makes it a priority for document recovery before or during the full audit.

Can a pre-audit be done with spreadsheet data alone?

Yes. It only needs a vendor list with spend by category and a way to check contract existence and dates, both of which are commonly available in a spreadsheet export from the ERP and a contract folder listing.

Margin Drift Resources