Sign in

Blog · Procurement and supply chain · Procurement

Source to pay analytics: connect sourcing to actual spend

Compare approved sourcing baselines and contract terms with actual invoice lines. Work through realized price savings, contract variance and spend reconciliation without confusing volume changes with savings.

The short answerSource to pay analytics compares sourcing decisions with the purchasing results that followed. It connects an approved baseline, awarded terms and actual invoice lines to measure negotiated savings, realized price savings and differences from contract. Use actual quantities for all three comparisons, reconcile invoice totals, and separate price effects from changes in volume, scope or timing.

Source to pay analytics tests whether sourcing awards and contract terms show up in actual invoiced spend. Compare the same purchased quantities at the approved baseline price, the awarded price and the net invoiced price. That separates an achieved price improvement from lower spending caused by buying less.

Define the sourcing outcome you are measuring

Start with one awarded category and one closed reporting period. The business question is specific: did the agreed prices and eligible terms reach the purchases made under this award? A claim that sourcing saved money needs a documented counterfactual price and evidence of what was bought.

The baseline should be approved before interpreting results. It might be the prior comparable price or another authorized reference, but the selection must be recorded. Keep its effective date, currency, unit of measure and scope beside the price. A baseline without those details can make an ordinary specification change look like savings.

This article measures realized purchase-price savings, not a guarantee of reduced operating expense. Inventory timing, accruals and consumption can move the income statement separately. For downstream processing time rather than sourcing outcomes, use procure to pay analytics.

Connect the award, contract and invoice records

Use an award file with the category, supplier, item, approved baseline and awarded unit price. Add the applicable contract terms and effective dates. Then bring net invoice lines, including credits, with purchase order references and actual quantities.

File Minimum fields Question it answers
Approved baseline Item, comparable specification, unit, price, approval date What price are we comparing against?
Sourcing award and terms Supplier, item, awarded price, validity, eligible charges What should the purchased quantity cost?
Purchase and receipt records Order line, item, receipt quantity, contract reference Was the purchase within the award's scope?
Invoice and credit detail Invoice line, order reference, quantity, unit, net amount What was actually invoiced?

Preserve line identifiers during matching. One contract can cover many orders, and one order can generate several invoices. Comparing only supplier totals can hide purchases made under different contracts or outside the effective dates.

As a useful documentation reference, the federal proper invoice requirements in FAR 32.905 include contract or order references, quantity, unit of measure, unit price and extended price. Those are practical matching fields for this analysis; the federal rule is not a requirement being imposed here on private-company purchasing.

Work the sourcing result at actual quantities

A fictional US packaging buyer purchased cartons and labels in the reporting period. The example excludes tax and freight, uses comparable specifications and includes all eligible invoice credits. Prices are in USD per each; quantities are actual purchased units.

Item Actual quantity Baseline unit price (USD) Awarded unit price (USD) Actual net unit price (USD)
Cartons 10,000 2.00 1.80 1.86
Labels 20,000 0.50 0.45 0.44

Negotiated savings at actual volume = Actual quantity x (Baseline price - Awarded price)

Realized price savings = Actual quantity x (Baseline price - Actual net price)

Contract price variance = Actual quantity x (Actual net price - Awarded price)

Positive contract variance means actual cost exceeds the award comparison. A negative amount is favorable. Calculate each line before adding the results.

Item Baseline cost (USD) Award cost (USD) Actual cost (USD) Negotiated savings (USD) Contract variance (USD) Realized savings (USD)
Cartons 20,000 18,000 18,600 2,000 600 1,400
Labels 10,000 9,000 8,800 1,000 -200 1,200
Total 30,000 27,000 27,400 3,000 400 2,600

The identity is 3,000 - 400 = 2,600: negotiated savings less the adverse net contract variance equals realized savings. Realization is 2,600 / 3,000 = 86.7%, rounded to one decimal place. All dollar amounts in the example are exact.

Cartons account for the adverse difference; labels partly offset it. That directs a review of the carton invoices and eligible terms. It does not establish an overcharge until purchasing and accounts payable confirm whether the difference reflects an authorized charge, a changed term or an error.

Rebuild the comparison in a spreadsheet

Put the first table in columns A through E, starting with cartons on row 2. Add baseline cost in F, award cost in G, actual cost in H, negotiated savings in I, contract variance in J and realized savings in K:

F2 =B2*C2
G2 =B2*D2
H2 =B2*E2
I2 =F2-G2
J2 =H2-G2
K2 =F2-H2

Enter the expression after each cell label and fill down. Check =I2-J2-K2; it must return zero for each item and for the summed columns. The cost variance guide explains how to extend a comparison beyond purchase prices without mixing the effects.

For a category control, suppose Invoices column C contains the category and H contains net invoice amounts. This formula totals packaging rows:

=SUMIFS(Invoices!$H$2:$H$5000,Invoices!$C$2:$C$5000,"Packaging")

The SUMIFS documentation explains how the function sums rows meeting specified criteria. Keep the selected ranges aligned and verify that they include the full reporting period. Covirage is not affiliated with Microsoft.

Reconcile scope before reporting a savings rate

Suppose the category also contains an unmatched packaging purchase. Keep that invoice in the spending control even though it lacks an approved comparable baseline.

Reconciliation category Net invoiced spend (USD)
Matched award lines above 27,400
Unmatched purchase 1,500
Category invoice control 28,900

Matched coverage is 27,400 / 28,900 = 94.8%, rounded to one decimal place. The realized savings remain $2,600 on matched comparable lines. Do not extend that result to the unmatched purchase or subtract the unmatched invoice as though all of it were leakage.

Finance owns the reconciliation to the ledger and the approved savings treatment. Procurement owns award eligibility and commercial explanations. Accounts payable confirms invoice and credit corrections. Keep those responsibilities explicit so an unresolved match cannot become a reported achievement merely because the reporting deadline arrived.

Where it goes wrong

  • Volume mistaken for savings. Reprice actual quantities throughout. Comparing a smaller actual purchase with a larger original budget confuses demand with sourcing performance.
  • Different units or specifications. Normalize pack sizes and comparable scope before multiplying quantities by prices. Leave unresolved substitutions outside the savings calculation.
  • Credits and charges omitted. Follow the same net-cost policy for each period. Credit notes, tax and foreign exchange in procurement spend covers the related normalization problem.
  • Every mismatch called leakage. Effective dates, tier thresholds and eligible freight can explain a difference. Review the contract evidence before classifying the variance.

Compare your sourcing files in Covirage

Bring the approved baseline, award terms and invoice or credit exports, including the category control total. Covirage maps the columns, its tools compute and check the comparisons, and the external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring a sample of your own purchasing records.

See Covirage for procurement teams for the supporting business reporting approach.

Questions people ask

How is source to pay analytics different from procure to pay analytics?

Source to pay analysis asks whether sourcing awards and contract terms appeared in actual purchasing results. Procure to pay analysis commonly examines the downstream ordering, receipt, invoice and payment process. They can use shared files while answering different management questions.

Are negotiated savings the same as realized savings?

Negotiated savings compare the approved baseline price with the awarded price. Realized price savings compare that same baseline with actual net invoice prices at actual quantities. Freight, credits, substitutions and purchase timing can explain why the amounts differ.

Can lower total spend be reported as sourcing savings?

Only after separating the effects of quantity, scope and price. Buying less can lower spending without improving purchase prices. Reprice the actual quantities at both the approved baseline and the awarded terms before reporting a realized price savings figure.

What if an invoice cannot be matched to a sourcing award?

Keep it in a visible unmatched category and include it in the spend control. Investigate supplier aliases, missing contract references, changed units and purchases outside the award. Do not assume an unmatched invoice has achieved the negotiated savings rate.