How it works
From your files to a decision you can defend.
Seven steps, each one inspectable. You see what PactMeter understood before it calculates anything.
- 01
Ingest
Upload contracts, amendments and price letters as PDF or text, plus a customers CSV and a transactions CSV.
Files are stored in your workspace only. PDFs need a text layer. A file that cannot be read is named, not skipped.
- 02
Understand
Documents are read conservatively, sentence by sentence and table by table. Each rule keeps the file, page and exact words.
A statement that is approximate, undated, or has no reference is not turned into a price: the customer’s lines are held for review.
- 03
Build the commercial state
Rules become a shared model: customers, list prices, contract holds, amendments, exceptions, with dates and sources.
Precedence is fixed and written down: exception, then amendment, then contract hold, then list price.
- 04
Check reality
Every invoice line is priced under those rules. Lines billed off the supported price become price findings.
A difference is a reason to look, not proof of a breach; a person confirms.
- 05
Test a change
State the change and how it is applied. PactMeter shows what it understood before running, then replays your history under the change.
There is no default rollout. Changing the list price and repricing every account are different actions with different consequences.
- 06
Show the proof
Money, who is affected, who is protected and why, each finding opening onto the invoice, the rule, the source text and the calculation.
Money is integer arithmetic. The release decision comes from fixed rules. No model takes part in it.
- 07
Decide and follow up
Approve, hold or reject a change. Confirm or dismiss a finding, with a reason. Open a recovery case from a confirmed price finding.
Every decision is recorded with who and when. Nothing changes in your systems and no customer is contacted.