Skip to content
Two operators reviewing a laptop in an office

Industry · SaaS

The simple tool is lying. The contract is not simple.

Ramps, mixed seats and usage, a setup fee that gates the term. The billing product you bought for “monthly SaaS” is inventing a second set of numbers.

The mess

Monthly SaaS was the brochure. The contract is ramps, seats, and a gate.

A setup fee that starts the term when it is paid. Seats that are how many they had that day, not a delta from the row above. Usage that has to land before send. The tool that only knows “plan plus quantity” will still produce an invoice — it will just be the wrong one.

Ramps

Phases and uplifts as the contract wrote them. The schedule is the plan that bills — not a spreadsheet of intended dates.

Seats

Snapshots versus the balance on record. An add can wait N confirmation days. Removals do not.

The gate

Under on-payment or manual-after-payment, subscription dates stay empty until cash the contract named actually arrives.

What Sonic does

Read the PDF. Approve the schedule. Let it generate.

The commercial term never moves with a gate. Implementation and setup still invoice on their own dates. When payment lands, phase durations become real subscription dates. Daily billing runs on a calendar — a forgotten tab is not what generates the month.

S
PDF · 8 pages0/6 clauses reviewed

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

AccountNorthwind Analytics
Term36 months
Effective1 Apr 2026
TCV₹ 1.18 Cr
Year 1 · products₹ 90,000 / mo net
ProductModelQtyAmount
Platformflat1₹ 20,000
Seatsper unit180₹ 72,000
API callsusagemetered
Loyalty discountflat− ₹ 2,000

Usual mess

Plan plus quantity. The contract had ramps, a gate, and a seat file.

A later usage line edited onto last month’s sent invoice.

In Sonic

The schedule is the plan that bills. Seats are snapshots. The gate waits on the cash the deal named.

A new invoice alongside. Sent documents freeze.

Questions

Open the answer here.

These are the questions this page raises. The full list lives on FAQ.

All FAQs →
Are seats events or snapshots?

Snapshots. Each row is how many they had that day. Sonic compares it to the balance on record and writes an event only when the count changes. Vendor increase/delta columns are not imported — they break at customer boundaries.

What are confirmation days?

An optional hold on seat adds. If you set N days, an increase on date D bills only if the new count still holds through D+N. Removals bill immediately. Incomplete files show as awaiting, not as a guessed invoice line.

Can we start from a signed PDF?

Yes. Upload the agreement, review the structured result, approve. Sonic can materialise the customer and products on approve rather than forcing a blank catalog first. Time-to-schedule is measured in minutes on straightforward contracts.

Next

See it on your contracts

A walkthrough on the agreements and files you actually bill from — not a slide deck.