Evaluate the work
Schedules, rates, and dunning rules are explicit. AI output is reviewable. Sent invoices are frozen. Journals that do not balance do not publish.
00 · Platform
Customer or shipper, product, list price, contract, schedule or rated shipment, invoice, cash, journal. The order matters. Models do not know how your company bills — that knowledge is captured by doing the work, with a human in the loop where money moves.
Schedules, rates, and dunning rules are explicit. AI output is reviewable. Sent invoices are frozen. Journals that do not balance do not publish.
The contract, the phase, the meter, the shipper match, the deposit — one organisation’s record. Downstream modules do not re-interpret the deal.
Morning ritual: did it go out, did it land, did they pay, is anything stuck. Interfaces fit finance work, not a prompt window.
Agents
01
Read the agreement
Turns a signed PDF into a typed customer, products, prices, ramps, and net terms — grounded to the clause, reviewable before anything bills.
The schedule is only as good as the contract behind it.
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 |
02
Run the schedule
The live artefact. Phases, proration, activation gates, amendments. Invoices draft themselves from the schedule — never rewritten once sent.
Everything upstream exists to produce this. Everything downstream is derived from it.
Customer
Nimbus Cloud
Start
On payment
Duration
36 months
Cadence
Monthly
Gate
Payment date
TCV
₹ 3.81 Cr
| Product | Model | Qty | Rate | Amount |
|---|---|---|---|---|
| Platform | flat | 1 | ₹ 20,000 | ₹ 20,000 |
| Seats | per unit | 200 | ₹ 400 | ₹ 80,000 |
| Subtotal | ₹ 1,00,000 | |||
| Product | Model | Qty | Rate | Amount |
|---|---|---|---|---|
| Platform + 10% | flat | 1 | ₹ 22,000 | ₹ 22,000 |
| Seats + 10% | per unit | 200 | ₹ 440 | ₹ 88,000 |
| Subtotal | ₹ 1,10,000 | |||
2 phases shown · platform ramps 10% each contract anniversary.
03
Price the haul
Carrier contracts, rate indexes with branches, mapped uploads. Each movement is rated from the card — no monthly schedule required.
A truck moves. The file arrives. The invoice is already the rate the contract promised.
Uploads
1
Shipments
13
Priced
₹ 1,53,200
Invoiced
₹ 0
Exceptions
1
| Shipment | Shipper | Lane | Mode | Status | Rated |
|---|---|---|---|---|---|
| SHP-441 | Westbound | BLR → HYD | Road | DRAFT | ₹ 18,400 |
| SHP-442 | Westbound | HYD → MAA | Road | DRAFT | ₹ 21,150 |
| SHP-443 | Delta Pack | PNQ → BOM | Road | DRAFT | ₹ 9,780 |
| SHP-444 | Apex Tools | DEL → JAI | Rail | DRAFT | ₹ 14,220 |
| SHP-445 | Westbound | MAA → COK | Road | DRAFT | ₹ 16,900 |
| SHP-446 | Delta Pack | BOM → PNQ | Road | REVIEW | ₹ 7,340 |
5 shipments selected · ₹ 80,450
04
Chase the late ones
Overdue sent invoices, dunning cadences, suggested next steps. Automatic when you want it, a person when you don't. Sequences stop the moment payment lands.
Sending an invoice is not getting paid.
Nimbus Cloud
INV-1042 · ₹ 1,00,000 · due 11 Apr
ar@withsonic.ai · 1 Apr
Invoice INV-1042 — April platform + seats. Due 11 Apr. Net 30.
Suggested · D+7
Nimbus Cloud, INV-1042 is 12 days past due. Cadence is on sent unpaid only — this is the next step, not a new invoice.
Review & sendSequences stop the moment the deposit matches.
Send reminder?
Nimbus Cloud · INV-1042 is 12 days past due. This sends the D+7 cadence email now.
05
Match the cash
An invoice marked paid is a claim. A deposit is a fact. Sonic matches them on amount, reference, and the billed party — customer or shipper.
Stop chasing people who already paid.
Matched
₹ 2,14,400
4 lines
Unmatched
₹ 1,00,000
1 line
Open invoices
3
sent unpaid
Needs review
1
operator queue
Suggested match
₹ 1,00,000
06
Post the books
Waterfall and journal from the same invoices. Subscriptions defer and recognise over the term. Freight recognises on the shipment date. Debits equal credits.
When an auditor asks why an amount is in a period, the link is the answer.
Billed
₹ 1,00,000
Deferred
₹ 91,667
Recognised
₹ 8,333
Tax collected
₹ 18,000
In balance
Yes
| Product | Type | Account | Debit | Credit |
|---|---|---|---|---|
| Platform | INVOICE DAY | Accounts receivable | ₹ 20,000 | — |
| Platform | INVOICE DAY | Deferred revenue | — | ₹ 20,000 |
| Platform | POINT-IN-TIME | Deferred revenue | ₹ 1,667 | — |
| Platform | POINT-IN-TIME | Revenue | — | ₹ 1,667 |
| Seats | INVOICE DAY | Accounts receivable | ₹ 80,000 | — |
| Seats | INVOICE DAY | Deferred revenue | — | ₹ 80,000 |
| Seats | POINT-IN-TIME | Deferred revenue | ₹ 6,667 | — |
| Seats | POINT-IN-TIME | Revenue | — | ₹ 6,667 |
| Total · 1–30 Apr | ₹ 1,08,333 | ₹ 1,08,333 | ||
Debits equal credits. The invoice is the link.
The chain
Subscription organisations run a billing schedule. Shipment organisations rate each haul from a carrier contract. Both share invoices, Watchtower, bank rec, and the journal.
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
Subscription path
01
Who you bill, what you sell, how each thing is priced — including meters for usage and seats.
02
What this account agreed to. Approve materialises missing catalog records instead of blocking you.
03
Phases, ramps, proration, activation gates, amendments. Invoices draft from here.
04
Usage events and seat snapshots land through templates or a warehouse connection.
05
Review, send, collect. Sent documents are not rewritten.
06
Watchtower on overdue sent invoices. Bank rec against deposits. Waterfall and journal from the same source.
Shipment path
01
Separate catalogs. The shipper is always the bill-to. Invoice-from can be your organisation or the carrier.
02
One carrier deal: term, frequency, rated charges, mapping. Fuel tables live on rate indexes, with optional carrier branches.
03
A carrier file is processed, shippers confirmed, shipments created, then invoiced — per haul or grouped by the deal’s window.
04
One ledger per shipment, net of rate lines. The haul date owns recognition.

A signed PDF is cheaper to get right than an invoice a customer has already seen.

Freight bills a shipment, not a month. The rate card is already the contract.

Watchtower, the deposit, and the journal are the same chain — not three exports.

Isolation
Operators see their workspace. Shipment mode hides subscription-only catalogs; subscription mode hides freight-only ones. Settings belong to the company, not the page.
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
A walkthrough on the agreements and files you actually bill from — not a slide deck.