01 · Contracts
Sonic parses the PDF. You approve the terms.
Customer, line items, prices, ramps, and net terms — typed and tied to the clause. Nothing bills until a person approves.
The cheapest place to be right
Finance’s nightmare is an invoice that is wrong in front of a customer.
Sonic structures the deal. Catalog matches attach stable identifiers; they do not wipe order, PO, or account codes the document already contained. On approve, an unlinked customer can be created the same way products and list prices are — an existing name is linked, not duplicated.
Enterprise software subscription
Northwind Analytics · 1 Apr 2026 – 31 Mar 2029 · INR
2. Commercial summary
Initial term 36 months, auto-renewal unless 90-day notice. Annual escalation 10%.
3. Pricing
Platform ₹ 20,000 / month. Seats 180 × ₹ 400. API overage on the contracted meter. Loyalty discount 2% on renewal.
Net 30. Invoice in advance. Subscription starts on the payment date.
Customer
| Product | Model | Qty | Amount |
|---|---|---|---|
| Platform | flat | 1 | ₹ 20,000 |
| Seats | per unit | 180 | ₹ 72,000 |
| API calls | usage | — | metered |
| Loyalty discount | flat | — | − ₹ 2,000 |
01
Extract
A signed PDF becomes a customer, line items, prices, ramps, phases, and net terms — grounded to the clause and reviewable before anything bills.
02
Catalogs
Matches attach identifiers. They do not invent carriers, products, or rate indexes — they link or leave gaps.
03
Review
Operators see what the model used, field next to source clause, before anything is committed to the record.
04
Freeze on approve
Corrections stay in the record. Nothing bills until a person approves. Carrier deals can start from a file the same way.
05
Addendums
A deal changes after signing too, and is parsed the same way — repricing waits on approval, never applied silently. Up to nine addendums upload with the base contract as one linked packet, phases built from each one’s effective date.
06
Memory
Your parsing rulebook carries forward automatically. Confirmed corrections are remembered per organisation too, and become a shared prior once enough organisations independently agree.
In review
Approve is the freeze.
In review. Extraction is done. A person can see and correct it before anything is committed.
Approved. The contract freezes. Corrections stop applying silently, and an unlinked customer or product is created or linked the same way as elsewhere in the catalog.
Schedule: Active. Billing actually starts running off it — marketing does not skip a step.
In review
2
Awaiting approve
Approved
6
Schedule: Active
This week
1
PDF uploaded
| Agreement | Account | Status | Schedule |
|---|---|---|---|
| Enterprise software subscription | Northwind Analytics | In review | — |
| Platform + seats · 36 mo | Nimbus Cloud | Approved | Active |
| Support retainer | Apex Tools | Approved | Active |
| API overage addendum | Nimbus Cloud | In review | — |
| Annual renewal | Northwind Analytics | Approved | Active |
00
Platform
One chain. The order.
01
Contracts
PDF to a typed agreement
02
Catalogs
Who you bill, what you sell
03
Subscription
The schedule is the core
04
Shipment model
Rate cards, not months
05
Usage & seats
Events and snapshots
06
Shipment uploads
Process, confirm, create, invoice
07
Invoices
Drafts grow. Sent do not.
08
Watchtower
Inbox, cadence, a person
09
Revenue
Billed is not recognised
10
Bank rec
A deposit is a fact
11
Integrations
Pipes in and out
Next
See it on your contracts
A walkthrough on the agreements and files you actually bill from — not a slide deck.