Contracts that understand what happens next.
Duncet turns financial agreements into executable workflows, connecting obligations, deliverables, invoices, approvals and payments from signature to settlement.
Master Services Agreement
- Client
- Northstar Industries
- Provider
- Example Services Ltd.
- Contract Value
- $240,000
- Effective
- Jan 12
Awaiting extraction…
A signed contract is only the beginning.
Companies sign thousands of agreements containing financial commitments. But after signature, those commitments become fragmented across contracts, email, ERP, procurement, invoices, spreadsheets, payment systems and project management tools.
The agreement says one thing. The financial systems often know something else.
Duncet connects the two.
No single source of financial truth
Turn language into financial logic.
“Customer shall pay 25% upon completion of Phase I and the remaining 75% within 30 days of final acceptance.”
Source — MSA §3.1
25%
Trigger — Phase I complete
75%
Trigger — Final acceptance
Due — 30 days
Every contract contains a chain of obligations.
Duncet models each agreement as a graph of connected states — from the moment it's signed to the moment it's settled.
- 01Contract
- 02Deliverable
- 03Acceptance
- 04Invoice
- 05Approval
- 06Payment
- 07Settlement
Deliverable accepted?
Create payment obligation
Hold
Each transition in the graph is governed by conditions drawn from the contract itself — so the workflow only advances when reality matches the agreement.
Understand the agreement, not just the document.
Duncet helps interpret financial language and structure it into fields your systems can use. Extraction quality varies by document — Duncet surfaces its confidence and keeps a human in the loop.
Identifies
Parties
Extracts
Amounts
Extracts
Currencies
Maps
Payment Terms
Surfaces
Milestones
Identifies
Deadlines
Surfaces
Penalties
Identifies
Renewals
Maps
Conditions
Surfaces
Approval Requirements
Extracts
Deliverables
Every commitment becomes something you can act on.
Vendor
Example Supplier
Amount
$84,000
Trigger
Delivery accepted
Payment Terms
Net 30
Lifecycle
Make invoices answer to the contract.
A conceptual illustration of how Duncet compares an incoming invoice against the obligation the contract created.
Total
$240,000
Milestone
Phase II
Expected
$60,000
Amount Billed
$60,000
Milestone Referenced
Phase II
- AmountMatch
- MilestoneMatch
- Payment TermMatch
Connect agreement to payment.
Duncet doesn't replace your ERP, procurement or payment systems — it connects the agreement to what those systems do next.
Contracts change when reality changes.
Duncet treats each agreement as a living financial object — a record that updates as milestones are met, deliverables are accepted and invoices arrive.
- JAN 12Contract signed
- FEB 03Milestone submitted
- FEB 08Deliverable accepted
- FEB 09Invoice received
- FEB 10Obligation activated
- MAR 11Payment due
When reality doesn't match the agreement, Duncet surfaces it.
The invoice amount differs from the contractual obligation. Duncet doesn't assign blame — it flags the discrepancy for human review.
Phase II Payment
$60,000
Invoice
$78,000
Difference
$18,000
Never hide the reasoning behind the workflow.
Every AI-derived financial workflow stays traceable back to the underlying agreement — the language, the section, the clause.
“Payment is not yet eligible because the contract requires formal acceptance of the Phase II deliverable. The acceptance event has not been recorded.”
Source — Contract §4.2
$60,000
- Source
- Master Services Agreement §4.2
- Trigger
- Phase II acceptance
- Term
- Net 30
When the contract changes, the workflow should know.
Duncet updates the fields that depend on the agreement. Changes to connected financial systems still require authorization.
$60,000
Phase II payment
$72,000
Phase II payment
Duncet updates
A calendar built from obligations, not reminders.
Each entry is generated from a contractual obligation Duncet has identified — not entered by hand. Figures below are illustrative.
Ask the contracts what they require.
A natural-language interface over the contracts you've connected or uploaded — Duncet doesn't access agreements it hasn't been given.
Query
Which supplier contracts have payments due in the next 30 days?
7 contractual obligations are currently scheduled within the next 30 days.
Also ask
“Which agreements require customer acceptance before payment?”
A single, restrained view of contractual exposure.
Illustrative interface values shown for demonstration.
248
Active Contracts
1,842
Financial Obligations
67
Upcoming Payments
23
Pending Conditions
8
Exceptions
Built for the teams that sit closest to the obligation.
Procurement
Connect supplier contracts to invoices, milestones and payments.
Finance
Track contractual obligations before they become surprises.
Accounts Payable
Validate invoices against contractual terms.
Legal
Make financial clauses operational after signature.
Revenue Operations
Track customer obligations and payment triggers.
Enterprise Operations
Create visibility across contractual commitments.
Sit above the systems you already use.
Duncet doesn't need to replace existing financial infrastructure. It connects the agreement to what happens afterward.
Make financial obligations programmable.
Request
POST /v1/obligations
{
"contract": "contract_481",
"trigger": "delivery.accepted",
"amount": 60000,
"currency": "USD",
"terms": "net_30"
}Response
{
"status": "pending",
"trigger": "delivery.accepted",
"payment_due": null
}AI interprets. People remain in control.
Duncet does not independently move money. It surfaces what the contract requires and hands authorized action to the systems you already trust.
Extract
AI identifies the obligation.
Verify
A human reviews the interpretation where needed.
Activate
The authorized workflow is enabled.
Execute
Existing financial systems carry out the action.
Every obligation has a history.
Most contracts are written for humans.
Financial systems speak in events.
Duncet connects the two.
Make every agreement executable.
Duncet turns financial contracts into living workflows that connect obligations, conditions, invoices, approvals and payments from signature to settlement.