Evidence over assertion
A charge is supported when independent records establish the facts the contract depends on — not when a document says so.
About
The evidence layer for commercial obligations
Contracts create obligations. Obligations have conditions. Conditions are satisfied — or not — by things that actually happen in the world. ObligePay is built to connect those three layers before money moves.
Why we exist
A gap that sits between three documents
In most commercial relationships, three things are supposed to line up: what the contract requires, what the invoice claims, and what actually happened. Accounts payable teams have good tools for comparing the first two. Almost nobody systematically checks the third.
The result is a category of charge that is impossible to properly evaluate from documents alone — anything that depends on duration, quantity, condition or timing. The invoice asserts a fact; the contract prices that fact; and the underlying event goes unexamined.
Meanwhile most companies already hold the data that would settle the question. Telematics, gate systems, RFID portals, transportation and warehouse systems, EDI feeds and document archives all describe the same movements the charges refer to. It is rarely connected to the payment decision.
Positioning
ObligePay is not an AI invoice-auditing tool. Invoice auditing is a document-comparison discipline; it caps out at catching internal inconsistency. We are building a verification layer for contractual obligations, which is a different and larger problem.
Freight detention is our first working product because the obligation is narrow and the evidence is available. The architecture is deliberately domain-neutral so procurement, construction, insurance and manufacturing obligations can follow.
Principles
How we make decisions
Determinism where money is concerned
Language models interpret documents. Ordinary code performs arithmetic on integer cents. That boundary is not negotiable.
Honest uncertainty
"Insufficient evidence" and "conflicted" are real outcomes. We would rather return them than manufacture a confident answer.
Records, not verdicts
Every verification produces an inspectable, versioned certificate that shows its inputs. History is appended to, never rewritten.
Where we are
Current stage
ObligePay is an early-stage product. The freight detention verification engine, the evidence architecture, the audit workflow and the Reality Certificate record are implemented and working. Live evidence integrations are not yet connected — the MVP ships clearly labelled mock providers in their place, and every simulated figure in the product is labelled as such.
We make no claims about guaranteed savings, legal or regulatory compliance, patents, or the absence of competitors. We publish no customer names, reviews, certifications, awards or performance statistics, because we have not earned any yet.