Every platform ambition eventually tempts you to swallow a neighbouring category. Sonic has said no to several on purpose. The no is a feature — it tells you what we optimise for and what we will not pretend to own.
This is not negative marketing. It is scope discipline for a contract-to-cash chain that has to stay auditable.
Not a payment processor
Stripe and Razorpay collect on an invoice link. Your bank settles wires. Sonic matches what lands to the invoice it was meant to pay — including partials, batched payouts net of fees, and near-matches on payer name.
Building a processor would mean asking customers to move payment relationships for our convenience. That is not a convenience they asked for.
Honest scope: payment links and paid status via integrations; bank rec matching (prototype maturity on edge cases); no card vault as a core product.
Not a tax engine of record
GST, VAT, and line-item tax rates are configuration you own. Sonic applies them on invoices and journal tax lines; we do not maintain global tax law as a determination engine, and we will not pretend otherwise on a sales call.
Your accountant or dedicated tax software remains authoritative for returns and filing.
Not your general ledger
NetSuite, or whatever ERP holds your chart of accounts, remains the book of record. Sonic produces journal-ready entries with debits-equal-credits and links back to source invoices, credit notes, shipments, and adjustments.
Export CSV or sync through integration. Controllers still own mapping, period close, and sign-off.
Also honest: revenue recognition in Sonic is operational reporting and journal generation from your configured methods — not ASC 606 / Ind AS 115 certification.
Not a CPQ or deal desk
We read what the CPQ or signed PDF produced — the agreed terms — and turn that into a schedule or rated shipment. Quoting logic, discount approval chains, and negotiation workflow live upstream.
Not a replacement for operator judgement
AI assists contract parsing, collections copy, and match suggestions. It does not:
- Approve contracts without human review.
- Send dunning blindly to unvalidated contacts.
- Rewrite sent invoices.
- Invent recognition policy.
What Sonic does own
The span from agreement → billable document → sent invoice → collections on sent unpaid → cash match → journal trail, organisation-scoped:
| Capability | Where it lives |
|---|---|
| Subscription schedules | Phases, gates, seats, usage, commitments |
| Shipment billing | Rating, uploads, shipper bill-to, rate indexes |
| Document integrity | Invoice immutability after send |
| Collections | Watchtower cadence that stops on payment |
| Ingestion | Idempotent high-volume usage and seat pipelines |
A platform that claims all six neighbouring categories has usually built one well and is improvising on the rest.
Watch out for
- Evaluate vendors on the chain you actually run, not the logo wall of integrations.
- If tax filing lives elsewhere, do not expect Sonic to audit your nexus study.
- Bank rec is reconciliation, not treasury management.
- Freight and subscription in one org is a workspace choice — still not a CPQ.
- Draft invoices recomputing is normal; sent invoices changing is not — anywhere on the chain.