Damage payments
Including on-site payment, with its own cap and its own rules.
orbit indemnity
/
Claims · Indemnity payments
/
In PoC
The claim file reviews itself. A person decides the payment.
At the service office, an indemnity claim is still put together by hand: someone eyeballs owner, account holder, CFDI tax ID and amount, then types it all again into the core system. orbit indemnity reads the file, runs the cross-checks and returns a verdict with its evidence, plus a pre-filled entry sheet for the analyst to confirm.
orbit indemnity
indemnity · documents
01 · Context
The review nobody owns.
The customer walks into the office with the vehicle registration, an ID, a bank statement, the CFDI invoice and the settlement letter. Staff scan them, check by eye that owner, account holder, CLABE, tax ID and amount all match, and then type the same data again into every section of the claim. Nothing validates it beforehand. A wrong account or payee shows up after the money has gone out, and a missing document gets requested on the second or third resend.
02 · What it is
orbit indemnity in one sentence
A document review engine for auto indemnity claims that takes the file through the screen or by email, classifies and reads every document, cross-checks the data between documents with configurable rules, and returns a verdict, a payment opinion and the claim entry sheet, with every value tied to the document and page it came from.
03 · How it works
Four steps. No magic.
From a loose claim file to a confirmed entry sheet, without retyping.
01
Intake
The file comes in by dragging it onto the screen or by email, and both doors feed the same queue. It unzips, turns photos into PDF, splits pages, spots duplicates and replies with what arrived and what is missing.
02
Reading
It classifies every document and extracts its fields with a confidence score and a source. The CFDI is read straight from the XML with no model involved, and VIN, CLABE, RFC and CURP are checked against their own structure.
03
Validation
The rules match owner against payee, account holder and CLABE, the CFDI tax ID, the VIN against OCRA and REPUVE, the amount and the age of the bank statement. A rule with no data stays amber, never green.
04
Entry and payment
Out come the verdict, the risk level, the payment opinion with the tax breakdown checked against the CFDI, and a pre-filled payment order. The entry sheet stays a draft until the analyst confirms it.
How it works · orbit indemnity live
What it does not promise
It is not yet connected to the insurer's core system or document repository: in the pilot, claim data is entered with the file or inferred from the documents, and the entry sheet is copied into the core by hand. It does not query external registries such as OCRA or REPUVE on its own; it uses the lookup that comes in the file. Nor does it decide the payment: verdict and risk come from the rules, the AI only reads, compares names and explains, and authorization is recorded by a person with the right profile.
04 · What it does
Where it goes to work.
Six places where the same engine goes to work.
Total loss
Asks for the original invoice and plate cancellation, explaining why, and checks the tax breakdown against the CFDI to the cent.
Total theft
The theft-report rule flips: here the report must exist, along with the police complaint and the theft record.
Uploader view
A signed link shows the customer which document is missing, why it is needed and what it must contain.
Pattern alerts
The same CLABE, payee or address showing up on files from a different claim raises the risk level.
Several countries
A new country is set up by cloning the document catalog, rules and field map from a template, with no code changes.
05 · Benefits
What changes when you have it.
What changes at the office when document cross-checks stop being done by eye.
Request demo1
No value without a source
Every field links to the document and page it came from, highlighted in the viewer.
2
Missing data is not green
A rule that found no data stays pending: the engine never approves by default.
3
Analysts look where it matters
Each field's confidence is corroborated by structure, and the file says what to check first.
4
Measured time, not estimates
Three separate clocks: engine, analyst and calendar. Customer wait time is shown on its own and never added in.
5
Rules the business can tune
New rules written in plain language, tested against past files before going live, with history and rollback.
06 · Before and after
What changes, side by side.
Same office, same claim file, a different path.
Before / Without orbit indemnity
Today's day-to-day
- ✕ Documents are compared by eye, one against another.
- ✕ The same data gets typed in twice.
- ✕ A missing document is found out late.
- ✕ Nobody measures how long each claim takes.
- ✕ Changing a review criterion means retraining everyone.
After / With orbit indemnity
With orbit indemnity
- ✓ Rules cross-check every value and show them side by side.
- ✓ The entry sheet comes pre-filled and the analyst confirms it.
- ✓ The acknowledgment says what is missing as soon as the file arrives.
- ✓ Three clocks track engine, analyst and calendar time.
- ✓ Rules are edited, tested and published with a stated reason.
07 · Industries
Where it applies today.
Built around the auto insurance indemnity claim.
01 / Auto insurers
Service offices and claim payments
The main target: the analyst who reviews the file, the authorizer who releases payment and the team that sets the rules.
02 / Multi-country operations
One engine, catalogs per country
Insurers with offices outside Mexico that need global rules and local exceptions on the same engine.
08 · Contact
Let's see it with your operation.
In 30 minutes we'll tell you whether orbit indemnity fits your process, what it integrates with and what it doesn't, and what a pilot looks like. If it doesn't fit, we'll tell you that too.
Run the discovery with rocky