Sample Pricing & Cost Check output - From a missed price update to a verified correction.
In this fictional worked example, an approved price of $13.10 was invoiced at $12.40 for 400 units. The $280 difference is reviewed, the price record is corrected, and the next invoice is checked. The historical difference is not counted as recovered cash.
Illustrative completed review / no client results claimed
- 1. Validate the $280
The pricing reviewer confirms the agreement and effective date, checks returns and later credits, and records the decision.
- 2. Correct the record
The authorized owner updates the customer price. Whether to pursue a historical adjustment is a separate commercial decision.
- 3. Verify the next invoice
The next 100-unit invoice uses $13.10. That is $70 more revenue than the old price on those units; gross-profit impact depends on costs and other terms.
| Transaction | Applicable rule | Observation | Supporting evidence | Review status | Financial treatment | Next action |
|---|---|---|---|---|---|---|
| INV-0902 · BRG-018 | $13.10 per EA effective August 31 | 400 EA invoiced at $12.40 on September 2: $280 difference | INV-0902 line 4; CP-008; reviewer checks agreements and credits | Confirmed in this illustrative review | $280 historical discrepancy; $0 recovered cash recorded | Pricing owner corrects the price record; next invoice is checked at $13.10 |
| INV-10482 · BRG-214 | Price update approved for April 1 | Invoice used the earlier price on April 18 | INV-10482 line 3; price record PR-2291; approval memo 03-27 | Pending validation | Potential discrepancy—not recovered cash | Check exceptions and later credits |
| INV-10511 · MOT-440 | 12-month fixed-price agreement | Price remained unchanged after supplier cost increased | INV-10511 line 1; agreement CA-118 (valid through Dec 31) | Dismissed | Authorized transaction—no error | Retain agreement as supporting evidence |
| INV-10537 · VAL-018 | Customer-specific price expired May 31 | June invoice retained the expired price | INV-10537 line 2; price record PR-1874 (end date May 31) | Needs context | Unclassified pending renewal check | Verify renewal or extension approval |
The dismissed row is intentional: a useful review rules out false positives instead of producing a longer exception list.
How evidence becomes a finding - The register preserves what is known—and what is not.
- Observation. State what the transaction data shows without assuming why it happened.
- Applicable rule. Link the customer-approved price, cost, agreement, effective date, or exception used for comparison.
- Validation status. Record whether the customer reviewer confirmed, dismissed, revised, or deferred the item.
- Financial treatment. Separate a discrepancy from an amount that may be recoverable and from a future margin opportunity.
- Supporting evidence. Preserve the transaction and commercial record references needed to reproduce the analysis.
- Next action. Name the check, owner, approval, or correction required to resolve the item.
Scoped data request - Enough data to answer one defined question.
The exact request follows the agreed check. A typical check may use transaction lines, adjustments or credits, supplier-cost records, customer-pricing records, effective dates, and documented exceptions for one supplier or category and one period.
- Read-only exports. The initial method works from agreed files and supporting records; it does not require ERP write access.
- Authorized reviewer. Someone who understands the applicable commercial rules validates apparent discrepancies.
- Defined handling. Transfer, access, processing, retention, and deletion arrangements are agreed before confidential data is provided.
Let’s start with one thing.
What would better performance look like?
Bring a result you want to improve, a symptom, or a workflow you already understand. You do not need to know the bottleneck yet. We’ll help choose what to investigate first.
No transaction files needed for the first conversation.