PactMeter

Controls

Every control here works today.

They share one commercial state, one evidence model and one kind of finding. Nothing on this page is a placeholder.

Commercial truth

What was promised, read from your documents with the words and the page.

Contract truth
NeedsContracts, amendments, price letters (PDF or text)
ProducesEvery commitment: price, dates, customer, and the exact quotation. Anything not readable exactly is listed as not read, never guessed.
Amendment chain
NeedsThe same documents
ProducesOriginal term, each amendment with its effective date, and the price that applies on any date.
Exception and protection registry
NeedsThe same documents
ProducesEvery price exception and hold: in force, ending soon or ended, and what the price becomes afterwards.
Conflict resolver
NeedsThe same documents
ProducesTwo sources giving one customer different prices for the same dates, side by side. Never resolved silently.
Commercial state versions
NeedsSaved runs
ProducesWhat was added, removed or changed between saved versions of the commercial state, including a price corrected under the same rule id.
Customer commercial passport
NeedsSaved runs
ProducesOne account: price today and what protects it, the position on any date, the timeline, findings, money and invoice history.

Change assurance

Can we safely make this change?

Change Guard
NeedsSources, customers, invoice lines, one stated change
ProducesA historical replay of the change, ending in SAFE, REVIEW or BLOCK from fixed rules. A person records the decision; nothing is released automatically.
Change diff and blast radius
NeedsChange Guard
ProducesFor each account that moves, the unit price before and after; who is protected, outside the tier, held for review or breached, with the money.
Pre-change checklist
NeedsUploaded sources
ProducesBefore anything runs: unread documents, ambiguous rules, conflicts, refused rows, and whether the change lines up with the data.
Counterfactual comparison
NeedsTwo saved change runs
ProducesThe two side by side: the money difference, the accounts only one of them moves, and the protected prices only one of them breaks.
Golden accounts
NeedsAccounts you mark on their passport
ProducesEvery change result opens with what it does to each of them: breaks a protection (with that line’s own money), moves, held, protected, or untouched.
Change Evidence Pack
NeedsA saved change run
ProducesA PDF to forward internally: decision, change, sources with hashes, what was understood, replay money, affected and protected accounts, findings, the engine’s calculation steps, digests and limits.

Revenue integrity

What was billed, or is about to be, against what was promised.

Promise drift and price leakage
NeedsSources and invoice lines
ProducesEach line billed off the supported price, with the variance, the rule and the quotation. A difference is a reason to look, not proof of a breach.
Invoice preflight
NeedsDraft invoice lines, before sending
ProducesEach draft line: ready to send, fix before sending (with the supported price and the amount), or hold when no price can be established.
Discount leakage and missed entitlement
NeedsA discounts file
ProducesDiscounts given beyond, without or after what was authorised, and committed discounts that were never applied.
Usage to bill
NeedsA usage file
ProducesUsage minus entitlement times rate, against what was billed, period by period.
Credit and refund guard
NeedsA saved run’s credit notes
ProducesCredits with no matching invoice, larger than the invoice, dated before it, or more than one against the same invoice.
Configuration drift
NeedsA configured-price export
ProducesWhere another system’s configured price differs from what the documents commit to on that date.

Renewals and watch

What is about to change by itself.

Renewal guard
NeedsA customer, a proposed renewal price and date
ProducesSAFE, REVIEW or BLOCK against whatever still protects that customer on the renewal date.
Expiry radar
NeedsThe documents
ProducesCommitments that end within 90 days, and the price that follows.
Anomaly detection
NeedsA customer’s own invoice lines
ProducesA line far from that customer’s own recent median, unexplained by a nearby rule change. An anomaly is worth a look, not a proven breach.
Root cause
NeedsFindings
ProducesFindings grouped by the rule behind them, with the accounts and the combined money.

Proof and action

One chain from a finding to its source, and a person who decides.

Findings and decisions
NeedsSaved runs
ProducesEvery finding in one list, filtered by type, with the decision a person recorded on each.
Evidence room
NeedsA finding
ProducesFinding, customer, invoice line, rule, source text, calculation and decision, in one chain, with a downloadable evidence pack.
Recovery cases
NeedsA finding a person confirmed
ProducesA case that moves one step at a time. The supported amount is calculated; the recovered amount is only what a person reports.

What is deliberately not here

PactMeter does not price with volume tiers, rebates or bundles, does not forecast, does not reconcile invoices against purchase orders or quotes (not built), does not connect to a billing system, ERP or CRM, does not change a price, send an invoice, issue a refund or contact a customer, and does not use a model to decide any amount or verdict. Details and limits.

There are no marketing or third-party cookies, so there is nothing to switch on for them.