Revenew International logo

Every contract compliance program runs on one of two models, or, eventually, both. A retrospective audit looks backward across a defined historical period to find and recover leakage that has already happened. A real-time review works forward, evaluating invoices during the approval cycle so discrepancies are caught before payment goes out. They are not competing approaches. They solve different problems, at different points in a contract's life.

What a retrospective audit does

A retrospective contract compliance audit reconciles a historical population of invoices, typically 12 to 36 months, against the underlying contract's pricing, escalation, and scope terms. It is the right starting point for almost every organization, because it establishes a documented baseline: how well has this contract actually been administered against what was negotiated?

Retrospective review is especially valuable when:

  • A contract or supplier relationship has never been independently reviewed.
  • The organization has been through a merger, ERP change, or shift in how contracts are administered.
  • Leadership wants a quantified, objective view of historical leakage before deciding where to invest in prevention.

What a real-time review does

Revenew's Real-Time Reviews evaluate invoices during the approval cycle rather than after payment, catching pricing and scope discrepancies before the money leaves the business. Rather than recovering a credit after the fact, a real-time review prevents the overpayment from occurring at all, which is why it is often described as cost avoidance rather than cost recovery.

Real-time review earns its cost fastest in high-velocity, high-spend environments: active capital projects, plant turnarounds, disaster response, and any engagement where invoice volume and dollar value are both large enough that catching an error before payment is worth meaningfully more than catching it months later.

How the two models compare

Retrospective Audit

  • Timing: After payment, looking back 12–36 months
  • Best for: Establishing a baseline, first-time reviews, long-dormant contracts
  • Outcome: Recovered credits and refunds
  • Typical next step: Root-cause fixes, then consider real-time on highest-risk contracts

Real-Time Review

  • Timing: During the invoice approval cycle, before payment
  • Best for: Active capital projects, turnarounds, disaster response, high-velocity spend
  • Outcome: Prevented overpayments (cost avoidance)
  • Typical next step: Ongoing oversight for the life of the active engagement

Why the sequence usually runs one way

Most organizations start with a retrospective audit, not because it's simpler, but because it answers the question that has to be answered first: where is the leakage, and how much is it worth? A global energy client's program illustrates the pattern clearly. What began in 2003 as a periodic retrospective audit, recovering single-digit millions per cycle, evolved after a string of major internal changes (an ERP upgrade, two outsourced AP transitions) into a continuous, near-real-time review model. Cumulative recoveries over the life of the relationship reached $38.6 million, with the shift to continuous monitoring driving faster identification and a return to industry-standard error rates.

That sequence, retrospective first to establish the baseline and quantify the opportunity, then real-time on the highest-risk, highest-volume relationships, is the pattern Revenew sees most often work. A power producer took a similar path on a capital project, recovering $3 million while strengthening supplier performance through real-time contract compliance oversight layered on top of its existing review program.

Which model does your organization need?

A few questions narrow the decision quickly:

  • Has this contract or supplier relationship ever been independently reviewed? If not, start retrospective.
  • Is there an active capital project, turnaround, or high-velocity spend event underway right now? Real-time review protects the budget while the money is still moving.
  • Did a recent retrospective audit find meaningful, recurring leakage on a specific contract? That contract is a strong candidate for moving to real-time oversight.
  • Is the relationship large enough that a small error rate translates into material dollars? Both models pay for themselves faster at scale.

Getting started

Revenew runs both models, often on the same client relationship at different stages. Contract Compliance Reviews establish the baseline; Real-Time Reviews protect the highest-risk spend going forward.

Request a No-Risk Review to determine which model fits where you are today.

Frequently Asked Questions

What is the difference between a retrospective audit and a real-time review? A retrospective audit looks backward across a historical period, typically 12 to 36 months, to find and recover leakage that has already occurred. A real-time review evaluates invoices during the approval cycle, catching discrepancies before payment is made.
Which model should we start with? Most organizations start with a retrospective audit to establish a documented baseline of historical leakage. Real-time review is typically layered in afterward, on the specific contracts or spend categories where the retrospective audit found the most recurring risk.
Is real-time review only for capital projects? No, though it delivers outsized value there. Real-time review is well suited to any high-velocity, high-spend environment, including turnarounds, disaster response, and ongoing high-volume supplier relationships where cost avoidance is worth more than delayed recovery.
Can an organization run both models at once? Yes, and many do. A common structure is periodic retrospective audits across the broader supplier base, with real-time oversight concentrated on the highest-value or highest-risk contracts identified by those audits.