Blog · Alternatives and comparisons
Evaluate price analysis software with your own invoice lines and dated price lists. This guide works a pricing check, compares tool approaches, and sets out the evidence a business team should require before choosing.
Price analysis software should compare the prices your company actually invoiced with valid benchmarks and show the rows behind the differences. Evaluate it using a closed-period invoice export, dated price lists and a small set of expected answers. A result that cannot reconcile to revenue is not ready for a pricing decision.
A commercial finance team may want to know whether realized prices changed within a product, where discounts concentrate, or whether invoicing followed customer agreements. Those are different comparisons. Write down the benchmark, eligible transactions and decision owner before evaluating tools.
For realized prices, start with net invoiced revenue after relevant credits and allowances. The SEC's financial statements guide explains how returns and allowances reduce gross revenue to net revenue. A test using gross invoices while excluding their credits will overstate the amount the business earned.
Procurement has a related but separate job. Federal Acquisition Regulation 15.404-1 distinguishes examining an overall proposed price from examining separate cost elements, and calls for historical comparisons to reflect material differences in terms and quantities. That is a useful comparison principle, not a requirement imposed here on every private business. Use purchase price analysis for the buying-side question.
There is no useful universal ranking without the files, frequency and review process. Evaluate approaches rather than assuming a product category guarantees the required checks.
| Approach | Appropriate evaluation question | Evidence to request |
|---|---|---|
| Spreadsheet workbook | Can the finance owner maintain this bounded review? | Visible formulas, dated lookups and a revenue tie-out |
| Business reporting tool | Can reviewers compare consistent segments each reporting cycle? | The underlying rows and reconciliation behind every displayed total |
| Commercial planning tool | Does the team need an approved process for changing assumptions? | Clear separation of actual invoices from proposed prices |
| File-based analysis with Covirage | Can the supplied rows support the business question? | Mapped columns, figures computed and checked by its tools, and explanations traced to rows |
A workbook may be sufficient for a small, infrequent review. A larger recurring process may justify more structured reporting. Treat usability, access arrangements and repeatability as things to test with the people who will perform the review; they are not established by a presentation of attractive totals.
Covirage is an option for examining supplied business files. Its tools compute and check the figures, and the external AI model explains the results.
Include invoice ID, line ID, posting date, customer ID, product ID, quantity, unit, currency and net line revenue. Add list price and its effective dates from the approved price list. Retain agreement references if the question concerns contracted prices.
Match a product to the list effective on its invoice date. Require one valid match per eligible line; missing or overlapping effective dates need resolution. Convert cases and individual units consistently before any price comparison. Keep currencies separate unless finance supplies an explicit translation basis.
Use these assumptions for a US distributor's acceptance file. Every line is in USD, quantities are individual units, list prices are valid on the invoice date, and this small example has no later credits or separate freight charges.
| Invoice line | Product | Quantity | List unit price (USD) | Net unit price (USD) | List value (USD) | Net revenue (USD) | Gap to list (USD) |
|---|---|---|---|---|---|---|---|
| A | Standard | 100 | 20.00 | 18.00 | 2,000 | 1,800 | 200 |
| B | Standard | 300 | 20.00 | 19.00 | 6,000 | 5,700 | 300 |
| C | Premium | 100 | 40.00 | 40.00 | 4,000 | 4,000 | 0 |
| Total | 500 | 12,000 | 11,500 | 500 |
The expected calculations are:
List value = Quantity × applicable list unit price
Net revenue = Quantity × net unit price
Realization = Total net revenue / total list value
The result is 11,500/12,000 = 95.83%, rounded to two decimals. The dollar check is 12,000-500 = 11,500. The three line realization percentages are 90.00%, 95.00% and 100.00%; their simple average is 95.00%, which is not the portfolio result. The portfolio ratio weights by list value.
The $500 gap establishes a difference from list. It does not establish an unauthorized discount, because approval terms are not in this file. The dedicated price realization by customer guide covers the agreement comparison in depth.
Ask each evaluator to reproduce the expected result, then identify line B as the largest dollar gap. Next change only line A's supplied net unit price from $18.00 to $18.50. Its revenue increases by 100×0.50 = $50, so total revenue must become $11,550 and realization 11,550/12,000 = 96.25%.
This simple change tests whether a revised input reaches the stated output. Restore the original file after the check and retain the two sets of expected answers. Do not accept a different total without a documented explanation of exclusions or treatment.
Follow with an exception test: remove the applicable list price from one line. The report should make the missing benchmark visible, rather than treating it as zero or silently dropping the line. Ask who reviews unresolved rows and how the revenue in the matched subset relates to the full export.
For period comparisons, a blended selling price can change when the product mix changes. The price volume mix owner explains that decomposition. For an agreement compliance review, use the separate invoiced versus contracted price workflow rather than treating list price as the contract.
Bring an invoice export and a dated price list with the units and benchmarks needed for your question. Covirage maps the columns; its tools compute and check the supplied figures, 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 data.
See revenue driver analysis for the supporting business context.
Use invoice lines, dated price lists and applicable customer agreements from one closed reporting period. Include quantities, currency, units of measure, credits and stable product identifiers. A carefully bounded file is more useful than a large export whose dates and prices cannot be matched.
An overall average can rise because customers bought more expensive products. Compare prices within equivalent products and terms first. Then separate changes in unit prices from changes in volume and product mix before describing a movement as a price increase.
Descriptive price analysis shows what happened against a stated benchmark. A decision about future prices also needs business judgment about demand, costs, customer commitments and competitive conditions. Do not assume a tool offers optimization or market research simply because it summarizes historical invoices.