Your Documents Don't
Disagree With Themselves.
They Disagree With Each Other.
Valinexis reads a set of related business documents as one case, checks them against each other, and tells you in money what does not add up — then records what a human decided to do about it. No model decides anything; every finding traces to a rule you can read.
Almost No Business Risk
Lives Inside One Document
It lives between documents — between a policy that was in force and a loss that happened a day after it lapsed, between what an appraiser approved and what a body shop charged, between what was ordered and what was billed.
Single-Document Tools Read Down, Not Sideways
Extraction tells you an invoice says $14,200. It cannot tell you the appraisal approved $12,390 — or name the four lines that account for the difference.
Checking Everything Is Not Affordable
Cross-document review is line-by-line and arithmetic-heavy. Teams sample rather than check, because the economics of manual review force it. What escapes the sample is the leakage.
The Cost Is the Loop, Not the Discovery
A short file is set aside, chased by hand days later, resubmitted, and reviewed again from the top. A second deficiency nobody caught the first time starts the loop again. Turnaround is consumed by round trips, not by review.
"The Model Thought So" Is Not a Finding
In an audit conversation with a supplier, a hospital, a body shop — or a regulator — a probabilistic answer is not admissible. You need a rule you can read, that produces the same answer every time.
Leakage Escapes the Sample.
Time Escapes the Loop.
Cross-document checking is done today by people under time pressure, sampling rather than checking. And when something is missing, the cost is not the discovery — it is the days of chasing that follow it.
Duplicates Across Time and Reference
The same line billed twice on one invoice, or the same invoice resubmitted a quarter later under a slightly different reference.
Arithmetic Nobody Re-Does
Quantity times rate against the line amount, on every row of every document — and rounding applied one way, consistently, across thousands of lines.
Three Round Trips Instead of One
A deficiency found today, another found next week, each one costing a person, an email and days of turnaround that nobody counts as review.
Six Stages. Nothing in the
Decision Path Is a Guess.
Documents arrive however the sender prefers. A ranked list of findings comes back, and a decision is recorded against it.
1 — Arrive: Four Ways In, and the Sender Picks
A watched folder, an email inbox, a direct API call, or a manual upload — plus SFTP for senders who will only move files that way. Documents belonging to one matter do not have to arrive together: a first notice of loss on Monday and a repair invoice three weeks later find each other.
2 — Recognise: Identify the Document, or Say So
Each document is read against its template. Where the sender did not say what a document is, it is recognised from the fields on its own page — and where recognition is not confident, the system says so rather than guessing.
3 — Map: Bind Every Field to a Shared Concept
Every extracted field is bound to a canonical concept from a shared dictionary — 124 concepts today, scoped by line of business. Rules are written against the concept, never against a template's own labels. That is what lets one rule serve every carrier's claim form layout, and keep working when a new one is onboarded.
4 — Assemble: Documents Find Their Own Case
Documents group themselves into a case by a value read off their own faces — a claim number, a purchase order number. A case knows what it still needs, because its case type declares which documents are required, and says so rather than waiting silently.
5 — Validate: Read Sideways Across the Case
Once the case is complete, it runs against its rule pack. Rules address values by document role — the billed invoice total against the approved total, the billed line against the approved line — so a rule reads sideways across the case rather than down one document.
6 — Decide and Respond: Keep the Judgement, Close the Loop
Findings come back ranked worst-first. A reviewer records what happens next, and that decision is kept against the evidence as it stood at the time. Where the file is short, the system composes the request back to the sender listing exactly what is outstanding — in one pass, not three.
An Agent Is a Configured Pipeline
Not a model making judgement calls. An agent is a case type, its document roles, its canonical mappings and its rule pack. Both agents run on the same engine — the difference between them is entirely content.
Insurance Claims Audit
Cross-document claim file validation, before an adjudicator sees the file. Any line — motor, health, property, commercial — asks the same four questions. Six packs ship configured across four lines of business, and every document, check and threshold is yours to change on a screen.
InsuranceAP Match
Purchase-to-pay reconciliation — two-way, three-way and four-way. Deterministic checks across purchase order, goods receipt and supplier invoice, with line arithmetic checked on every row rather than on a sample — and the rule pack is yours to extend.
Accounts PayableWhat Makes It Different
Six things, and they are the same six whether you are validating a collision claim file or reconciling a supplier invoice.
It Reads Sideways
Single-document extraction tells you an invoice says $14,200. This tells you the appraisal approved $12,390 — and names the four lines that account for the difference.
It Doesn't Photograph Data You Already Have
A purchase order is rows in a table; a policy is data in an administration system. Where a value lives in a system of record, it is taken from there exactly, rather than rendered to a page and guessed at again.
It Is Deterministic, and That Is a Feature
A rule you can read, that produces the same answer every time, is admissible in a conversation with a supplier, a hospital or a body shop — and with a regulator. Every finding names the rule that raised it.
It Checks Every Line, Not a Sample
The economics of manual review force sampling. The economics here do not. Line arithmetic runs on every row of every document in the case.
It Closes the Loop, Not Just the Check
Finding that a file is short in two seconds saves nothing if telling the sender still takes a person and a week. The request goes back listing everything outstanding, in one message.
It Records the Judgement, Not Just the Finding
Who accepted what, over which objection, and why — frozen against the evidence as it stood. The first thing an auditor asks, and the last thing most systems can answer.
This Was Built For You If...
Your people settle files where the repair invoice has to be reconciled against an approved schedule — part type, labour hours and labour rate, line by line — and there is never time to do it on every file.
Claims & AdjudicationSomebody on your team confirms, by hand, that an invoice matches a purchase order, that the goods actually arrived, and that this invoice was not already paid last quarter under a slightly different reference.
Procurement & Accounts PayableHalf your turnaround time is round trips — a file arrives short, gets chased days later, comes back missing something else, and nobody can tell you which senders account for it.
Operations & Shared ServicesYou need to explain a decision to an auditor or a regulator two years later — what the file said, what the system flagged, who accepted it anyway, and on what stated grounds.
Audit, Risk & CompliancePricing and Plans
Licensed per tenant and per line of business. A case is one matter — however many documents it contains, and however long they take to arrive.
Pilot
₹
19,999
/month
- 1 tenant, 1 line of business
- Up to 1,000 cases/month
- Shipped rule packs
- Watched folder or manual upload
- HTML, PDF and CSV outputs
- 90-day run retention
CHOICE
Business
₹
74,999
/month
- Up to 5 tenants, 4 lines of business
- Up to 10,000 cases/month
- Your own rules and tolerances
- All four intake routes, SFTP and webhooks
- Decision capture and overrides
- Operations measurement view
Enterprise
Custom
/annual
- Unlimited tenants and lines of business
- Committed annual volume
- Private deployment in your Azure subscription
- Your own content packs
- Retention and residency to your policy
- Integration Guide, support and SLA
Indicative plans shown for illustration. Final pricing is confirmed after a scoping call.
Send Us One Case
One settled claim file, or one purchase order with its receipt and invoice. We will return the findings — ranked worst-first, with the money at stake on every row.
Valinexis, A Product By
Contact Info
- No.102,2nd Floor,17th Cross,6th Sector, HSR Layout , Bengaluru, Karnataka
- info@lemniscale.com
- +91 7702820516
-
+91 7702820516