Skip to content
← All services

Invoice price checks · WORKFLOW PACKAGE

Catch the price change. Keep the source.

Turn repeated invoice comparisons into a focused review list, with the original lines attached to the questions worth checking.

Talk through a bottleneck

Proposed workflow example. Final scope follows the diagnostic.

The job to improve

A familiar item arrives at a new price. A pack size changes. A substitution makes two lines look comparable when they are not. Checking every detail manually takes attention away from the operation.

How we would approach it

  1. Read the agreed invoice lines and compare like items and pack sizes.
  2. Flag price changes, substitutions and uncertain matches instead of silently treating them as equivalent.
  3. Prepare a review list that points back to the original evidence.

What you would receive

A sourced price-change list and a repeatable process for checking each new batch of invoices.

What your team approves

Your team verifies the flagged items. You decide whether to question a charge, contact a vendor or change a purchase. The workflow does not place orders.

How we would judge the work

Manager review time, verified discrepancies and credits actually received. A price change or flagged line is not automatically a saving.

Illustrated example

Compare the unit price.

Use the same unit for both quantities, such as pounds or individual items. Enter the total price for each pack in dollars.

The starting numbers are a generic example: $40 for 10 units and $44 for 11 units. Both equal $4 per unit.

Pack prices and quantities

Earlier pack

Current pack

Enter 0.000001 to 1,000,000, using up to 6 decimal places and 16 characters. Use a decimal point, without commas or currency symbols.

Illustrative comparison for review

Earlier unit price
$4.00 / unit
Current unit price
$4.00 / unit
Unit-price change
0.00%

The unit price is unchanged.

Unit price = pack price ÷ quantity. Change = (current unit price − earlier unit price) ÷ earlier unit price × 100. Unit prices round to 4 decimal places, with at least 2 shown; values below $0.0001 use that threshold. Percentages round to 2 decimal places. Halfway values round away from zero; calculations use unrounded values.

Your entries stay in this browser tab and are not saved, sent, or included with an inquiry. Review item specifications and pack units alongside the invoice before drawing conclusions.

BEFORE WE START

Practical questions.

Can a higher case price mean an unchanged unit price?

Yes. An illustrative $40 pack containing 10 comparable units and a $44 pack containing 11 both cost $4 per unit. Compare the contents and terms before deciding whether the price actually changed.

What about substitutions, quality and delivery charges?

Those can make a simple comparison misleading. Different grades, brands, freight terms or minimum orders should stay visible as review questions. A lower unit price alone is not a purchasing recommendation.

A CLEAR FIRST ENGAGEMENT

Start with the diagnostic$750
Build around your needsCustom quote

The $750 diagnostic is credited toward your agreed implementation if you proceed.

A focused workflow and a connected operating system are different projects. Your quote reflects complexity, data readiness, integrations and support. Builds and advisory work are scoped and priced separately, with scope and price agreed before work begins.

Tell me where the work gets stuck.

Seamus will reply to discuss your operation and whether this is a useful starting point. No files or payment are needed with your inquiry.

Talk through a bottleneckEmail Seamus