In short

The contract set the price. The invoice never read it.

Contract intelligence in Nexus turns the agreement package into the reference the money is checked against. Rebate thresholds, price protections, volume tiers and payment terms are held as structured terms and tracked against actual spend, so an invoice that ignores them is caught before payment. Superseded provisions are flagged when someone relies on them, and comments, redline review and sign-off are held on the document until it is fully executed.

The pattern

How this goes wrong in practice

Contracts are negotiated carefully and then filed. The invoices that follow are checked against the purchase order, if they are checked at all.

The rebate tier nobody claimed

Spend crossed the volume threshold in the third quarter. The rebate was never invoiced back.

Price protection ignored

The contract caps increases for twelve months. The invoice raised the price in month eight.

Paying the superseded rate

An amendment changed the rate. Invoices are still checked against the original agreement.

Terms that drift

Payment terms on the invoice quietly differ from the contract, and early-payment discounts are lost.

The schedule in a different folder

A pricing schedule was finalised after signature and never reached the people approving invoices.

A package still in review

Work started on a contract that was never fully executed, and nobody can say which version governs.

What you get

The output

The terms you negotiated, held where the invoices are checked.

Commercial terms register

Prices, rebates, tiers, protections and payment terms, held as structured data with the clause each came from.

Spend against terms

Actual spend tracked against thresholds and tiers, so earned rebates and breached protections surface.

Superseded-term alerts

A warning when an invoice or a person relies on a provision a later amendment replaced.

Review and sign-off record

Threaded comments, redline review and sign-off held on the document until the package is fully executed.

Questions

Common questions

How is this different from Lexara?

Lexara is for legal teams reconciling contract packages against themselves. Contract Intelligence in Nexus holds the commercial terms that invoices, carrier charges and spend are checked against. The same reading engine sits underneath both.

How do you know which amendment controls?

By execution date and by what each amendment explicitly supersedes. Where precedence is unclear, that ambiguity is reported as an exception for a person to decide.

Does it replace our contract management system?

No. It reads the agreements wherever they are stored and holds the commercial terms for reconciliation. Your contract repository stays where it is.

Can it read scanned agreements?

Yes. Scanned and photographed documents are read the same way as native files, and low-confidence terms are flagged for review.

Related

Keep reading

Nexus overview

How the reconciliation engine works end to end, from intake to close.

Lexara for legal teams

Contract package reconciliation for law firms and in-house counsel.

AP & Three-Way Match

Purchase order, receipt and invoice reconciled before payment.

Which of your contract terms are invoices actually checked against?

Bring one supplier agreement and a quarter of its invoices. We will show you what the terms say and what was paid.

7-day free trial · Card required before the trial ends · No migration