A signed contract usually lives in two places: a folder and somebody's head. DocAI lifts it into a central portfolio, fills in its data automatically, watches deadlines and notice windows — and compares expected billing with actual billing. That way missing revenue or cost does not surface at closing, but while there is still room to act.
After upload a contract does not become an empty register row: the system reads its data from the document itself.
The expiring contracts panel shows, in a colour-coded traffic-light list ordered by urgency, the contracts that expire, become terminable or need an anniversary review within 30, 60 or 90 days. The list is not produced by a monthly report but updated continuously: the notice deadline does not slip by unnoticed, and renewal can be decided in time.
The most common silent loss is not a bad contract — it is the invoice that never got issued.
From the recurring items of a contract the system generates a payment schedule in advance: when an invoice should exist and for how much. It continuously compares this with the invoices actually received and matched to the contract, showing the difference in both currency and percentage.
If no invoice has arrived for a due item past its expected date, it appears highlighted on a separate panel. Incoming invoices and completion certificates are linked to the right contract automatically — by item matching, a date window and contract number references. Completion certificates are read on their own processing path (date, description, acceptance) to support the pre-payment check.
The contract base produces compact KPIs with a currency breakdown: active contract value, monthly recurring revenue (MRR), an ARR-style 12-month forecast of committed revenue and cost, the number of expiring contracts, the expected-versus-actual variance and the missing invoices. Together with the project breakdown, this is the picture someone would otherwise assemble by hand in a spreadsheet every quarter.
The same data can be queried from document chat — with a natural-language question, without building a report.
Contracts are kept in a central portfolio in four categories (revenue, liability, employment, other), filled in by automatic extraction: contract number, title, type, signature and expiry dates, notice period, currency, total value and indexation clause. Each extracted field shows its confidence level as a colour code, with a page reference into the source PDF. Amendments appear as a chronological chain linked to the original contract.
A dedicated panel lists, in a colour-coded traffic-light view ordered by urgency, the contracts expiring, terminable or due for anniversary review within 30, 60 and 90 days. That way a notice window does not slip by unnoticed, and renewal decisions can be made in time.
From the recurring items of a contract, the system generates a payment schedule in advance: when an invoice should exist and for how much. It continuously compares this with the invoices actually received and matched to the contract, showing the difference in both currency and percentage. If no invoice has arrived for a due item past its expected date, it is highlighted on a separate panel — so missing revenue or cost does not surface only at closing.
Yes. Incoming invoices and completion certificates are linked to the right contract automatically, based on item matching, a date window and contract number references. Completion certificates are read on their own processing path (date, description, acceptance) and support the pre-payment check.
Yes, every contract change is recorded in a structured audit trail: who changed what, and when. It can be reviewed inside the contract portfolio and is part of the system-wide logging — every open, change and download is traceable, with role-based access control.
In a 30-minute demo we walk through your own workflow — with your documents, on your terms. No obligation.
Request a demoThe same processing engine serves every area — introducing one gives you the whole engine.
Incoming invoices read, checked against four registries and matched with NAV data.
Read more →Field-level KIE from invoices, contracts, payslips and bank statements — with confidence signals.
Read more →Ask your own archive in natural language and get source-referenced answers.
Read more →Fill out the form below and our team will reach out shortly to schedule a demo.
We only use your data to respond to your inquiry. We do not share it with third parties. Legal basis: your consent and pre-contractual steps (GDPR Art. 6(1)(a) and (b)). For details, see our privacy policy.