Document comparison
Reads the invoice
- Compares the billed amount to a rate table
- Checks the charge code is permitted
- Confirms a document is attached
- Accepts the asserted duration as given
- Produces an exception code
Product
An invoice tells you what was billed. Evidence tells you what happened.
ObligePay doesn't merely read invoices. It identifies contractual obligations, determines what evidence is required, reconstructs relevant events, compares evidence against contract conditions, performs deterministic calculations and records the result.
Not invoice auditing
What the difference looks like in practice
Obligation verification
Establishes what happened
- Extracts the obligation and its measurement points
- Declares the evidence required to test it
- Reconstructs the event sequence from independent sources
- Measures the duration rather than accepting it
- Produces a versioned, hashed certificate
Capabilities
Six things the platform does
Obligation identification
Rather than classifying invoice line items, ObligePay works backwards from the charge to the contractual obligation that would create it — and stores that obligation as structured parameters: free time in minutes, rate in cents per hour, billing increment, cap, and the specific measurement points the clause names.
Evidence requirement mapping
Each obligation declares which evidence types could establish its conditions. A free-time clause measured arrival-to-departure needs perimeter evidence; one measured gate-to-gate needs the facility's own records. The requirement is explicit, so gaps are visible before verification runs.
Event reconstruction
Observations from independent sources are assembled into a timeline. Where multiple sources describe the same event, selection is deterministic and the disagreement is recorded as a spread rather than averaged away.
Condition evaluation
Reconstructed facts are compared against the contract's conditions one at a time, each with its observed value, threshold and operator. The comparison is inspectable, not a score.
Deterministic calculation
Supported amounts are computed in integer cents with explicit rounding to the contractual increment. Every step is recorded as an expression you can re-derive by hand.
Reality Certificate
The result is written to an immutable, versioned record containing the transaction, obligation, contract rule, evidence sources, timeline, amounts, status, calculation and a content hash.
Outcomes
Six possible verification statuses
Forcing every charge into approve-or-deny hides the cases that matter most. ObligePay returns the status the evidence actually supports.
Verified
Evidence supports the full billed amount.
Unsupported
The contract does not support this charge on the observed facts.
Contradicted
Evidence supports a smaller amount than billed.
Conflicted
Independent evidence sources disagree.
Insufficient evidence
Required evidence is missing or incomplete.
Requires human review
Automated verification could not settle the facts.