# Medius Alternatives for Mid-Market Manufacturers

> Comparing source-to-pay suites against a contract-based audit: what each catches, what each misses, for manufacturers above $100M in revenue.

Source: https://valuexpa.com/insights/medius-alternatives-mid-market-manufacturers
Publisher: ValueXPA (https://valuexpa.com)
Updated: 2026-09-05

---

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. Manufacturers evaluating a change from an existing source-to-pay platform usually start by comparing feature lists across vendors, then discover the harder question is not which suite has more features, but whether a suite is the right tool for the specific leakage they are trying to stop.

This guide covers the alternatives a mid-market manufacturer should actually weigh, what each does well, and where a procurement suite of any brand stops regardless of vendor.

## Executive Summary

Source-to-pay suites like Medius automate invoice capture and forward-looking approval routing. They are built to catch coding errors and missing approvals on the next invoice, not to test whether the price on that invoice matches the contract behind it. For a mid-market manufacturer weighing options, the real question is not which suite to buy instead, but which problem needs solving first: process speed or price accuracy.

A manufacturer with $100M and above in revenue runs 12 to 18 months of invoices through contracts nobody has re-checked since signing. A procurement suite processes those invoices faster. It does not know the rate card changed, the rebate tier was never claimed, or the surcharge outlived the fuel spike that justified it. That work requires reading the contract and comparing it line by line against what was actually billed.

The alternatives worth evaluating fall into three groups: other procurement suites with different strengths, a fixed-scope audit that tests historical accuracy, and a combination of both run in sequence. This guide covers what each does well, where each stops, and how to decide which one your business needs first.

## 1. 1. What does a source-to-pay suite actually do well?

**A source-to-pay suite automates invoice capture, routes approvals against workflow rules, and enforces three-way matching between the invoice, purchase order, and receipt. It gives finance teams visibility into spend commitments before the invoice arrives and reduces manual data entry. These are genuine, valuable capabilities for controlling forward-looking process errors at scale.**

Suites in this category are strong at what they were designed for. Invoice capture through OCR or e-invoicing removes manual entry. Workflow routing gets an invoice to the right approver based on amount, category, or cost center. Three-way matching checks the invoice against the purchase order and the goods receipt, and blocks payment when the quantities or the PO reference do not line up.

These controls prevent a real category of error: paying for goods never received, paying twice because two people keyed the same invoice, or paying without the right sign-off. For a manufacturer running many invoices a month across dozens of vendors, that alone is worth the investment.

The capability stops at the PO and receipt. Three-way matching checks the invoice against those two documents; it does not test whether the unit price on the PO still matches the rate card the contract specifies, or whether a surcharge line item was ever authorized to appear at all. The suite enforces whatever rule it was configured with. If the rule was built from a stale price file, the suite enforces the stale price faithfully, invoice after invoice.

## 2. 2. Why doesn't three-way matching catch a rate card violation?

**Three-way matching confirms that quantity billed equals quantity ordered and received. It does not read the underlying contract, so it cannot detect a rate that drifted from the negotiated schedule, a volume tier that should have triggered a lower price, or a surcharge that outlived the condition that justified it. Those checks require comparing the invoice to the contract text, not to the PO.**

A purchase order carries the price the requester typed in or the price the ERP pulled from a price file. If that price file was last updated when the contract was signed, and the contract had a step-down at a volume tier, the PO carries the old price and the invoice matches the PO perfectly. The match passes. The overcharge ships through unflagged.

The same gap applies to surcharges. A fuel surcharge added during a rate spike is a separate line item, not a change to the base unit price, so a three-way match sees it as a normal charge on an approved PO. Nothing in the workflow tests whether the index that justified the surcharge has since fallen.

Rebate clauses sit outside the invoice entirely. A rebate is paid or credited later, based on cumulative volume across a period, and no invoice-matching workflow tracks a threshold across dozens of invoices to confirm the vendor actually issued the credit when the threshold was crossed.

None of this is a defect in the suite. It is a description of what invoice-to-PO matching checks, versus what a contract clause requires. Closing that gap needs the contract terms loaded as rules, or a one-time review that reads the contract directly.

## 3. 3. What is the fixed-scope diagnostic alternative and how is it different?

**A fixed-scope Margin Drift Diagnostic reviews 12 to 18 months of historical invoices against the actual contract terms, not against the PO. It is priced as a project, not a percentage of recoveries, and the client keeps 100% of what it finds. It runs in parallel with any existing suite rather than replacing invoice processing.**

The diagnostic starts from the contract: the rate card, the volume tiers, the rebate clauses, the surcharge schedule, the not-to-exceed caps. Each invoice is matched against those terms directly, which is a different check than matching an invoice to a PO that may already carry a stale price.

Because it looks backward across 12 to 18 months of historical spend, it finds drift that has already accumulated: a rate that quietly rose after a contract renewal, a rebate tier crossed and never invoiced, a surcharge condition that expired months ago. A suite configured going forward cannot see into that history unless someone builds the same rule set and runs it retroactively, which is effectively the same project.

The commercial structure differs from most recovery audit firms too. It is [fixed-scope, not contingency](/guides/fixed-scope-vs-contingency-fee-recovery-audits-the-real-cost), so the client is not paying away 25% to 50% of recoveries to a third party. And it is not a replacement for invoice processing: a manufacturer keeps its existing suite running invoices day to day while the diagnostic runs separately against history and produces a prioritized recovery and prevention roadmap in 2 to 4 weeks.

## 4. 4. Should a manufacturer replace its suite or add a diagnostic?

**These are not competing purchases. A source-to-pay suite runs the day-to-day invoice-to-PO workflow. A diagnostic tests whether the contract terms behind that workflow are still accurate. Replacing a suite does not recover money already lost to stale rates; it only changes how future invoices are processed. A manufacturer weighing both should plan for sequencing, not exclusivity.**

The decision to switch suites is driven by process pain: slow approvals, poor visibility, integration gaps with the ERP. Those are legitimate reasons to evaluate a new platform, and a manufacturer should not expect a new suite, however good, to surface money already overpaid under the old one.

A diagnostic answers a different question: is the money already gone recoverable, and are the contract terms currently enforced actually the terms in the contract. Running one before a suite migration has a practical benefit beyond the recovery itself. It produces a clean, current rule set: correct rate cards, correct tier triggers, correct surcharge conditions, which is exactly what needs to be loaded into whichever suite is chosen next.

Running the diagnostic after a migration works too, and has its own logic: it tests whether the new suite's configuration actually reflects the contracts, rather than inheriting whatever rules were carried over from the old system unchanged.

## 5. 5. What should a manufacturer look for when comparing suites?

**Evaluate a source-to-pay suite on ERP integration depth, approval workflow flexibility, exception handling, and reporting, because those are the capabilities it is actually built to deliver. Do not evaluate it on whether it detects historical contract drift, because invoice-to-PO matching was never designed to read a contract clause. Those two evaluations answer different questions and neither substitutes for the other.**

A manufacturer that evaluates every option purely against a checklist of leakage-detection features will end up disappointed with all of them, because none of the major source-to-pay platforms were built primarily to re-derive contract terms from PDFs. That is not a gap unique to one vendor. It is a category boundary.

The integration and reporting questions below are where suite choices genuinely differ from each other, so that is where the comparison work belongs.

### A. Integration and workflow fit

The strongest procurement suites integrate directly with the ERPs manufacturers already run, including systems used across metal fabrication, packaging, and building products supply chains. Check how the suite handles exception routing: what happens when a PO does not exist, when a receipt is partial, or when a vendor bills before goods arrive. A suite that handles exceptions gracefully saves AP real time every week.

### B. Reporting and spend visibility

Good suites give finance a live view of committed spend against budget, by category and cost center, before the invoice even lands. That visibility is genuinely useful for forecasting and for catching maverick spend outside approved vendors. It is a different kind of visibility than a contract compliance review, which looks at whether the approved vendor is billing at the approved rate.

## 6. 6. How does this play out for a $200M manufacturer choosing between options?

**Worked example, using the 1% to 3% band. A manufacturer takes its annual service vendor spend and applies that range to get an order-of-magnitude estimate of what a full diagnostic might recover, separate from whatever a procurement suite is doing to speed up future invoice processing. Neither figure tells the manufacturer which contracts are leaking, only whether the exercise is worth running.**

Take your annual service vendor spend, the categories a suite already processes: freight, contract labor, maintenance, professional services. Multiply that figure by the 1% to 3% band that a full Margin Drift Diagnostic finds across service vendor spend, across ValueXPA diagnostics. The result is an order-of-magnitude estimate of what a diagnostic might surface, independent of anything the suite is doing.

That estimate does not tell you which specific contracts are leaking. It tells you whether the exercise is worth the 2 to 4 weeks a diagnostic takes. A manufacturer with meaningful service vendor spend across freight, staffing, and maintenance contracts can run this arithmetic before committing budget to a suite migration, an audit, or both.

The suite decision and the diagnostic decision can run on separate timelines. Nothing about starting a diagnostic requires pausing a supplier evaluation for a new platform, and nothing about signing with a new suite requires waiting for the diagnostic to finish first.

## 7. 7. What does a manufacturer actually give up by choosing only one path?

**Choosing only a procurement suite leaves 12 to 18 months of historical overbilling unexamined, because forward controls do not look backward. Choosing only a diagnostic leaves future invoices to whatever manual process exists today, because a one-time review does not run approval workflows. A forward control that persists what the diagnostic finds closes both gaps together.**

A suite-only path is efficient for volume and weak for verifying the underlying contract is correctly modeled. It runs indefinitely once configured, but the configuration is only as accurate as the price file behind it, and price files go stale as contracts renew.

A diagnostic-only path is strong at finding what already leaked and weak at stopping the next occurrence, unless its findings get built into an ongoing control, whether that is the existing suite reconfigured with corrected rules or a dedicated continuous enforcement layer.

The two are complementary rather than competing, and a manufacturer choosing between them is really choosing sequencing, not exclusivity. Start with whichever problem is costing more right now: slow, error-prone invoice processing, or invoices paid against terms nobody has re-verified in years.

For the wider pattern this sits inside, start with the margin drift guide. See also [margin drift vs. legitimate price increases](/guides/margin-drift-vs-legitimate-price-increases-how-to-tell-them) and the [accessorial charge audit](/guides/accessorial-charge-audit-the-surcharges-nobody-validates).

For the wider pattern this sits inside, start with the [margin drift](/insights/best-invoice-validation-software-smb) guide.

## 8. Frequently Asked Questions (People Also Ask)

### Does a source-to-pay suite replace the need for a contract compliance audit?

No. A suite enforces whatever rate and rule set it was configured with. It does not independently verify that configuration against the underlying contract, so a stale rate card or an expired surcharge condition passes through invoice after invoice unless something else checks the contract directly.

### Can a suite be configured to catch rate card drift?

A suite can be configured with correct rules if someone first re-derives them from the current contracts. That re-derivation is contract review work, not a suite feature. A diagnostic is one way to produce that clean rule set before loading it into the suite.

### Is switching source-to-pay platforms worth doing before a diagnostic?

The two solve different problems. Switching platforms addresses process speed and integration. A diagnostic addresses whether money was already overpaid under contracts nobody re-checked. Neither substitutes for the other, and both can proceed on separate timelines.

### What does the diagnostic cost compared to a contingency recovery firm?

The diagnostic is fixed-scope, priced as a project rather than a percentage of recoveries, and the client keeps 100% of what it finds. Traditional contingency recovery audit firms charge 25% to 50% of recoveries instead.

### How long does the diagnostic take?

A Margin Drift Diagnostic produces a prioritized recovery and prevention roadmap in 2 to 4 weeks, reviewing 12 to 18 months of historical invoices against contract terms.

### Will a new suite find money already lost to expired surcharges?

Not on its own. A new suite processes invoices going forward against whatever rules it is configured with. It does not look backward across already-paid invoices unless someone builds and runs that historical rule set separately, which is the diagnostic's job.

### Should a manufacturer run the diagnostic before or after choosing a new suite?

Either order works. Running it first produces a clean rule set to load into the new suite. Running it after tests whether the new suite's configuration actually reflects the contracts rather than carrying over old rules unchanged.

### What contract terms does three-way matching never check?

Volume tier triggers, rebate clause thresholds, surcharge expiration conditions, and not-to-exceed caps. Three-way matching checks quantity against the PO and receipt; none of those terms live in the PO.

### Is contract complexity quietly draining your operating margin?

A small systematic drift between your negotiated contracts and your actual vendor billing compounds quietly across a year of invoices. Stop guessing at your exposure and run a targeted audit.

**[Take the Free Screener → https://valuexpa.com/margin-drift-screener](https://valuexpa.com/margin-drift-screener)**

## Executive Summary

Source-to-pay suites like Medius automate invoice capture and forward-looking approval routing. They are built to catch coding errors and missing approvals on the next invoice, not to test whether the price on that invoice matches the contract behind it. For a mid-market manufacturer weighing options, the real question is not which suite to buy instead, but which problem needs solving first: process speed or price accuracy. A manufacturer with $100M and above in revenue runs 12 to 18 months of invoices through contracts nobody has re-checked since signing. A procurement suite processes those invoices faster. It does not know the rate card changed, the rebate tier was never claimed, or the surcharge outlived the fuel spike that justified it. That work requires reading the contract and comparing it line by line against what was actually billed. The alternatives worth evaluating fall into three groups: other procurement suites with different strengths, a fixed-scope audit that tests historical accuracy, and a combination of both run in sequence. This guide covers what each does well, where each stops, and how to decide which one your business needs first.

## 1. 1. What does a source-to-pay suite actually do well?

A source-to-pay suite automates invoice capture, routes approvals against workflow rules, and enforces three-way matching between the invoice, purchase order, and receipt. It gives finance teams visibility into spend commitments before the invoice arrives and reduces manual data entry. These are genuine, valuable capabilities for controlling forward-looking process errors at scale. Suites in this category are strong at what they were designed for. Invoice capture through OCR or e-invoicing removes manual entry. Workflow routing gets an invoice to the right approver based on amount, category, or cost center. Three-way matching checks the invoice against the purchase order and the goods receipt, and blocks payment when the quantities or the PO reference do not line up. These controls prevent a real category of error: paying for goods never received, paying twice because two people keyed the same invoice, or paying without the right sign-off. For a manufacturer running many invoices a month across dozens of vendors, that alone is worth the investment. The capability stops at the PO and receipt. Three-way matching checks the invoice against those two documents; it does not test whether the unit price on the PO still matches the rate card the contract specifies, or whether a surcharge line item was ever authorized to appear at all. The suite enforces whatever rule it was configured with. If the rule was built from a stale price file, the suite enforces the stale price faithfully, invoice after invoice.

## 2. 2. Why doesn't three-way matching catch a rate card violation?

Three-way matching confirms that quantity billed equals quantity ordered and received. It does not read the underlying contract, so it cannot detect a rate that drifted from the negotiated schedule, a volume tier that should have triggered a lower price, or a surcharge that outlived the condition that justified it. Those checks require comparing the invoice to the contract text, not to the PO. A purchase order carries the price the requester typed in or the price the ERP pulled from a price file. If that price file was last updated when the contract was signed, and the contract had a step-down at a volume tier, the PO carries the old price and the invoice matches the PO perfectly. The match passes. The overcharge ships through unflagged. The same gap applies to surcharges. A fuel surcharge added during a rate spike is a separate line item, not a change to the base unit price, so a three-way match sees it as a normal charge on an approved PO. Nothing in the workflow tests whether the index that justified the surcharge has since fallen. Rebate clauses sit outside the invoice entirely. A rebate is paid or credited later, based on cumulative volume across a period, and no invoice-matching workflow tracks a threshold across dozens of invoices to confirm the vendor actually issued the credit when the threshold was crossed. None of this is a defect in the suite. It is a description of what invoice-to-PO matching checks, versus what a contract clause requires. Closing that gap needs the contract terms loaded as rules, or a one-time review that reads the contract directly.

## 3. 3. What is the fixed-scope diagnostic alternative and how is it different?

A fixed-scope Margin Drift Diagnostic reviews 12 to 18 months of historical invoices against the actual contract terms, not against the PO. It is priced as a project, not a percentage of recoveries, and the client keeps 100% of what it finds. It runs in parallel with any existing suite rather than replacing invoice processing. The diagnostic starts from the contract: the rate card, the volume tiers, the rebate clauses, the surcharge schedule, the not-to-exceed caps. Each invoice is matched against those terms directly, which is a different check than matching an invoice to a PO that may already carry a stale price. Because it looks backward across 12 to 18 months of historical spend, it finds drift that has already accumulated: a rate that quietly rose after a contract renewal, a rebate tier crossed and never invoiced, a surcharge condition that expired months ago. A suite configured going forward cannot see into that history unless someone builds the same rule set and runs it retroactively, which is effectively the same project. The commercial structure differs from most recovery audit firms too. It is [fixed-scope, not contingency](/guides/fixed-scope-vs-contingency-fee-recovery-audits-the-real-cost), so the client is not paying away 25% to 50% of recoveries to a third party. And it is not a replacement for invoice processing: a manufacturer keeps its existing suite running invoices day to day while the diagnostic runs separately against history and produces a prioritized recovery and prevention roadmap in 2 to 4 weeks.

## 4. 4. Should a manufacturer replace its suite or add a diagnostic?

These are not competing purchases. A source-to-pay suite runs the day-to-day invoice-to-PO workflow. A diagnostic tests whether the contract terms behind that workflow are still accurate. Replacing a suite does not recover money already lost to stale rates; it only changes how future invoices are processed. A manufacturer weighing both should plan for sequencing, not exclusivity. The decision to switch suites is driven by process pain: slow approvals, poor visibility, integration gaps with the ERP. Those are legitimate reasons to evaluate a new platform, and a manufacturer should not expect a new suite, however good, to surface money already overpaid under the old one. A diagnostic answers a different question: is the money already gone recoverable, and are the contract terms currently enforced actually the terms in the contract. Running one before a suite migration has a practical benefit beyond the recovery itself. It produces a clean, current rule set: correct rate cards, correct tier triggers, correct surcharge conditions, which is exactly what needs to be loaded into whichever suite is chosen next. Running the diagnostic after a migration works too, and has its own logic: it tests whether the new suite's configuration actually reflects the contracts, rather than inheriting whatever rules were carried over from the old system unchanged.

## 5. 5. What should a manufacturer look for when comparing suites?

Evaluate a source-to-pay suite on ERP integration depth, approval workflow flexibility, exception handling, and reporting, because those are the capabilities it is actually built to deliver. Do not evaluate it on whether it detects historical contract drift, because invoice-to-PO matching was never designed to read a contract clause. Those two evaluations answer different questions and neither substitutes for the other. A manufacturer that evaluates every option purely against a checklist of leakage-detection features will end up disappointed with all of them, because none of the major source-to-pay platforms were built primarily to re-derive contract terms from PDFs. That is not a gap unique to one vendor. It is a category boundary. The integration and reporting questions below are where suite choices genuinely differ from each other, so that is where the comparison work belongs. ### A. Integration and workflow fit The strongest procurement suites integrate directly with the ERPs manufacturers already run, including systems used across metal fabrication, packaging, and building products supply chains. Check how the suite handles exception routing: what happens when a PO does not exist, when a receipt is partial, or when a vendor bills before goods arrive. A suite that handles exceptions gracefully saves AP real time every week. ### B. Reporting and spend visibility Good suites give finance a live view of committed spend against budget, by category and cost center, before the invoice even lands. That visibility is genuinely useful for forecasting and for catching maverick spend outside approved vendors. It is a different kind of visibility than a contract compliance review, which looks at whether the approved vendor is billing at the approved rate.

## 6. 6. How does this play out for a $200M manufacturer choosing between options?

Worked example, using the 1% to 3% band. A manufacturer takes its annual service vendor spend and applies that range to get an order-of-magnitude estimate of what a full diagnostic might recover, separate from whatever a procurement suite is doing to speed up future invoice processing. Neither figure tells the manufacturer which contracts are leaking, only whether the exercise is worth running. Take your annual service vendor spend, the categories a suite already processes: freight, contract labor, maintenance, professional services. Multiply that figure by the 1% to 3% band that a full Margin Drift Diagnostic finds across service vendor spend, across ValueXPA diagnostics. The result is an order-of-magnitude estimate of what a diagnostic might surface, independent of anything the suite is doing. That estimate does not tell you which specific contracts are leaking. It tells you whether the exercise is worth the 2 to 4 weeks a diagnostic takes. A manufacturer with meaningful service vendor spend across freight, staffing, and maintenance contracts can run this arithmetic before committing budget to a suite migration, an audit, or both. The suite decision and the diagnostic decision can run on separate timelines. Nothing about starting a diagnostic requires pausing a supplier evaluation for a new platform, and nothing about signing with a new suite requires waiting for the diagnostic to finish first.

## 7. 7. What does a manufacturer actually give up by choosing only one path?

Choosing only a procurement suite leaves 12 to 18 months of historical overbilling unexamined, because forward controls do not look backward. Choosing only a diagnostic leaves future invoices to whatever manual process exists today, because a one-time review does not run approval workflows. A forward control that persists what the diagnostic finds closes both gaps together. A suite-only path is efficient for volume and weak for verifying the underlying contract is correctly modeled. It runs indefinitely once configured, but the configuration is only as accurate as the price file behind it, and price files go stale as contracts renew. A diagnostic-only path is strong at finding what already leaked and weak at stopping the next occurrence, unless its findings get built into an ongoing control, whether that is the existing suite reconfigured with corrected rules or a dedicated continuous enforcement layer. The two are complementary rather than competing, and a manufacturer choosing between them is really choosing sequencing, not exclusivity. Start with whichever problem is costing more right now: slow, error-prone invoice processing, or invoices paid against terms nobody has re-verified in years. For the wider pattern this sits inside, start with the margin drift guide. See also [margin drift vs. legitimate price increases](/guides/margin-drift-vs-legitimate-price-increases-how-to-tell-them) and the [accessorial charge audit](/guides/accessorial-charge-audit-the-surcharges-nobody-validates). For the wider pattern this sits inside, start with the [margin drift](/insights/best-invoice-validation-software-smb) guide.

## Common questions

### Does a source-to-pay suite replace the need for a contract compliance audit?

No. A suite enforces whatever rate and rule set it was configured with. It does not independently verify that configuration against the underlying contract, so a stale rate card or an expired surcharge condition passes through invoice after invoice unless something else checks the contract directly.

### Can a suite be configured to catch rate card drift?

A suite can be configured with correct rules if someone first re-derives them from the current contracts. That re-derivation is contract review work, not a suite feature. A diagnostic is one way to produce that clean rule set before loading it into the suite.

### Is switching source-to-pay platforms worth doing before a diagnostic?

The two solve different problems. Switching platforms addresses process speed and integration. A diagnostic addresses whether money was already overpaid under contracts nobody re-checked. Neither substitutes for the other, and both can proceed on separate timelines.

### What does the diagnostic cost compared to a contingency recovery firm?

The diagnostic is fixed-scope, priced as a project rather than a percentage of recoveries, and the client keeps 100% of what it finds. Traditional contingency recovery audit firms charge 25% to 50% of recoveries instead.

### How long does the diagnostic take?

A Margin Drift Diagnostic produces a prioritized recovery and prevention roadmap in 2 to 4 weeks, reviewing 12 to 18 months of historical invoices against contract terms.

---

ValueXPA runs a fixed-scope Margin Drift Diagnostic that validates every service vendor invoice against contract terms, for $100M+ US industrial manufacturers and distributors. Two to four weeks. The client retains 100% of recoveries. https://valuexpa.com/contact-us