CLMContract management

Check the invoice against the rate you signed.

Scanned and typed agreements are read into structured fields — parties, dates, values, terms and clauses. Ask a question in plain English and get the clause back, cited, from your own contracts.

Request a pilot What it does not do yet

What it does

Built to produce a verdict, not a to-do list.

The rate card becomes a control, not a filed document.

Scanned and native agreements read into structured fields — parties, dates, values, terms and clauses
Ask a question in plain English and get the clause back, cited, from your own contracts
Contracted rates and payment terms compared against what vendors actually invoice, once the check is switched on for your organisation

app.docinflow.ai

Contracts in DocInflow

What it actually does, step by step.

Each stage below is a real part of the product, not a category. The counts come from the configuration the product ships with.

verdicts an invoice line can take against a rate card

rungs on the ladder that decides which contract governs an invoice

fields whose every change is written to an audit row

Bring the paper in

53 source field names read into 14 typed contract fields
Notice periods parsed from prose — “three months” becomes 90 days
A master agreement parents its SOWs, amendments and rate cards
A duplicate on number and counterparty is refused until you confirm it

Draft, route and sign

Compose from a form, render a typeset PDF, file it as version one
Routing rules match on contract type and value band, first match wins
Up to twenty signers, each on their own single-use link
The signed copy files itself as the next version and the contract goes active

Read what the paper says

Clauses extracted page by page, each reporting the page it starts on
Obligations typed as deliverable, milestone, penalty or escalation
Ask in plain English; answers cite the excerpt they came from
Contract text is escaped and fenced, so a crafted PDF cannot steer the model

Decide which contract governs an invoice

A ladder of evidence, not a similarity score — and the report names the rung it used
An explicit human override outranks every inference and is stored per invoice
Tax registration beats a vendor link; a vendor link beats a fuzzy name
Ruling that no contract governs is a decision that is recorded, not a gap

Hold the invoice to the rate card

Each line matched to a rate-card row by item code, then by description
Six verdicts, from within contract to price above, below, or item not in it
Payment terms compared only where a real window can be read from the text
Where a purchase order exists, both legs are reconciled against the same card

Sweep, renew and prove

A nightly sweep raises renewal tasks 90 days out, and catches expired ones too
Vendor insurance, MSME, GST, PAN and ISO tracked against expiry
Maverick spend lists every order flowing to a vendor no contract covers
Version history is append-only, with a clause-by-clause diff between any two

Bring the paper in

53 source field names read into 14 typed contract fields
Notice periods parsed from prose — “three months” becomes 90 days
A master agreement parents its SOWs, amendments and rate cards
A duplicate on number and counterparty is refused until you confirm it

Draft, route and sign

Compose from a form, render a typeset PDF, file it as version one
Routing rules match on contract type and value band, first match wins
Up to twenty signers, each on their own single-use link
The signed copy files itself as the next version and the contract goes active

Read what the paper says

Clauses extracted page by page, each reporting the page it starts on
Obligations typed as deliverable, milestone, penalty or escalation
Ask in plain English; answers cite the excerpt they came from
Contract text is escaped and fenced, so a crafted PDF cannot steer the model

Decide which contract governs an invoice

A ladder of evidence, not a similarity score — and the report names the rung it used
An explicit human override outranks every inference and is stored per invoice
Tax registration beats a vendor link; a vendor link beats a fuzzy name
Ruling that no contract governs is a decision that is recorded, not a gap

Hold the invoice to the rate card

Each line matched to a rate-card row by item code, then by description
Six verdicts, from within contract to price above, below, or item not in it
Payment terms compared only where a real window can be read from the text
Where a purchase order exists, both legs are reconciled against the same card

Sweep, renew and prove

A nightly sweep raises renewal tasks 90 days out, and catches expired ones too
Vendor insurance, MSME, GST, PAN and ISO tracked against expiry
Maverick spend lists every order flowing to a vendor no contract covers
Version history is append-only, with a clause-by-clause diff between any two

Scroll sideways for the rest of the flow.

A rate you agreed is only a rate if something checks it.

Most contracts are honoured where a buyer happens to remember them. The agreement should be doing that work, not the buyer.

Core capabilities

Strengthen your agreements end to end

It knows which contract this invoice falls under

Which agreement an invoice falls under is decided by a ladder of evidence rather than a similarity score — an explicit human ruling, then a vendor link confirmed by tax registration, then the link alone, then GSTIN equality, then a fuzzy name. Every report names the rung it used.

└─You can see why a contract was chosen, not just that one was
└─A person can overrule the inference, and that ruling is stored per invoice
└─Deciding no contract governs is recorded as a decision, not left as a gap

The rate you negotiated is the rate you pay

Each line is matched to a rate-card row by item code first and description second, then classified against the agreed price band into one of six states — within contract, above, below, item not in the contract, unreadable, or no reference at all.

└─A price above the card is named as such, with the band it broke
└─An item nobody put on the rate card is visible rather than assumed fine
└─Where a purchase order exists, both legs are checked against the same card

Ask your contracts a question, get the clause back

Clauses are extracted page by page, so each reports the page it starts on. Answers cite the excerpt they came from, and contract text is escaped and fenced before it reaches the model, so a crafted PDF cannot steer the answer.

└─“What is our liability cap here” is answered with the clause, cited
└─Obligations become dated tasks typed as deliverable, milestone or penalty
└─A document you did not write cannot rewrite the instructions

See the spend no contract is covering

A nightly sweep raises renewal tasks ninety days out and catches contracts that already expired, tracks vendor insurance, MSME, GST, PAN and ISO against their expiry, and lists every order flowing to a vendor no active contract covers.

└─Renewal windows come to you, ninety days ahead
└─Maverick spend is a list, not an audit finding a year later
└─An expired compliance certificate is visible before the vendor invoices again

How the check works

The documents, and what is compared between them.

What changes

The difference is where the check happens.

Typical practice

Signed contracts sit in a shared drive. The negotiated price is honoured where a buyer remembers it, and nobody compares invoices back to the agreement.

With DocInflow

The contract is the control: invoices are compared to its rate card and payment terms, and each deviation becomes an owned task.

Typical practice

Answering "what is our liability cap with this supplier" means opening files one by one and reading.

With DocInflow

The question is asked in plain English and answered from your own contracts, with the specific clauses cited.

Not built yet — said plainly

Renewal actions and reminder suppression once a task is cleared

We publish what is not built yet because you will find it in the first ten minutes of a trial anyway — and because a vendor who tells you the boundary is the one worth believing about everything inside it.

The rest of the platform

It is one system underneath.

Same document layer, same control model, same audit trail — which is why a price agreed in a contract can be checked on an invoice and land in the ledger without leaving the product.

P2P

Procure-to-Pay

Order, receipt and invoice matched line by line.

Explore

O2C

Order-to-Cash

Prove you delivered exactly what was ordered.

Explore

EXIM

Trade Finance

Letters of credit examined before a bank sees them.

Explore

R2R

Accounting

A real double-entry ledger, not a reporting layer.

Explore

Run it on your own documents.

A pilot runs on your paperwork, not a sample file. Send a real set — a purchase order with its invoice, or a letter of credit with its proforma invoice — and we will run the checks on it.

Request a pilot