ObligePay

How it works

From contract to payment decision, in one traceable line

Each stage produces an artifact the next stage consumes, and every artifact is inspectable. Nothing in the chain requires you to trust a black box.

  1. 01

    Contract

    The agreed terms

  2. 02

    Obligation

    What must be true

  3. 03

    Evidence

    Independent sources

  4. 04

    Reality

    Reconstructed events

  5. 05

    Certificate

    Recorded result

  6. 06

    Payment

    Decision

The audit workflow

Nine steps

  1. 1

    Upload the invoice

    PDF, PNG, JPG or JPEG. File type and size are validated on the server and the file is stored under your organization's own prefix.

  2. 2

    Upload the contract

    The governing agreement or rate confirmation containing the accessorial terms.

  3. 3

    Extract information

    AI reads both documents and proposes structured fields — invoice number, carrier, charge lines, clause text. Output is schema-validated before anything is stored, and every extracted value stays editable.

  4. 4

    Identify obligations

    The clause becomes an obligation object: free time in minutes, rate in cents per hour, billing increment, cap, and measurement points. This is the object the rest of the pipeline reasons about.

  5. 5

    Add evidence

    Evidence is pulled from the configured providers for the required types, or attached as documents and manual entries. Provenance and reliability travel with each observation.

  6. 6

    Reconstruct events

    Observations are assembled into a timeline. Multiple sources describing one event are resolved deterministically; material disagreement is flagged as a conflict rather than smoothed over.

  7. 7

    Verify

    Each contract condition is evaluated against the reconstructed facts, producing one of six statuses — including honest ones like insufficient evidence and conflicted.

  8. 8

    Calculate

    Deterministic code computes chargeable time, billable increments, supported amount and potential recovery in integer cents. AI is not involved in any arithmetic.

  9. 9

    Generate the Reality Certificate

    Everything above is written to an immutable versioned record with a SHA-256 content hash, ready to support a payment decision or a dispute.

Worked example

A $2,400 detention charge

Simulated detention audit

Simulated demo
  1. Charge on the invoiceDetention, stop 2 — $2,400.00
  2. Obligation found in clause 7.3(b)120 min free time, $75.00/hr, 15-min increments
  3. Evidence requiredGPS, facility gate, EDI
  4. Reconstructed arrival08:04
  5. Reconstructed departure09:41
  6. Measured dwell97 minutes
  7. Condition: dwell > 120 minNot satisfied
  8. Chargeable minutes: max(0, 97 − 120)0
  9. Supported amount$0.00
  10. Potential recovery$2,400.00

Notice what determined the outcome. The invoice was internally consistent — the rate was right, the charge code was permitted, the arithmetic summed. A document-comparison audit would have passed it.

What changed the answer was measuring the duration instead of accepting it. Three independent sources agreed the vehicle was at the facility for 97 minutes, which is inside the contractual allowance, so the condition that creates the obligation was never triggered.

Had the sources disagreed materially, the result would have been conflicted rather than unsupported — and no recovery would be claimed until a human resolved it.

Run it interactively