What is Spreadsheets and manual billing?
Excel (and the shared inbox) is the real incumbent: ageing in a sheet, reminders in a mailbox, revenue in a file named final_v7, seat counts in a vendor export someone pivots manually.
Solutions · vs Spreadsheets and manual billing
Spreadsheets and manual billing vs Sonic AI
The actual incumbent: a workbook, a shared inbox, and someone who remembers. Keep the sheet for analysis — not as the system that decides what customers owe.
What is Sonic AI?
Sonic AI replaces the sheet as the system of record for what customers owe — with frozen issued invoices, sent-only overdue, bank match, and a journal that links back to the source bill. Keep Excel for analysis; stop letting it decide AR.
What changes in practice
- 01
Freeze
Sent invoice is a document — not a row you can still edit.
- 02
One chain
Schedule or haul → invoice → chase → match → post.
- 03
Templates
Map the vendor file once; Process explicitly when ready.
- 04
Export still OK
Analyse in Excel — do not decide AR there.
Same neighbourhood. Different job.
Where the overlap ends.
Overlap
Everyone understands the sheet. It is locally reasonable.
Different job
The sheet cannot freeze a sent invoice, cannot tell Watchtower that a deposit already landed, and cannot rate a haul from last Tuesday’s diesel branch. Sonic exists because that pile starts inventing a second set of numbers.
Where Spreadsheets and manual billing strains
Common pain points teams describe — not a scorecard.
- Billing runs on memory: a ramp step, an uplift clause, or a milestone date is missed because nobody's calendar fired.
- Rows stay editable after send — no immutable issued document.
- Overdue is whatever someone coloured red — not sent unpaid only.
- Bank balance and AR live in different places — false chases are routine.
- Seat vendor delta columns break at customer boundaries — snapshots need discipline the sheet does not enforce.
- Freight rating from rate cards and branch indexes does not live in a pivot table reliably.
- Audit questions get answered from a tab that drifted from the PDF.
- Manual proration is done by day ratio in a cell — and disagrees with the quoted monthly price every quarter.
When Sonic fits
Choose Sonic AI when…
01
Invoices go out when someone remembers, and a missed one is found by the customer.
02
Two people maintain billing and the sheet breaks every close.
03
Issued invoices must not change — corrections need credit notes and traceability.
04
Seat files and usage exports arrive weekly — manual pivoting is the bottleneck.
05
You bill hauls and subscription on different tabs that never agree.
06
Morning standup is five exports — sent, paid, stuck, journal, bank.
On the points that matter
Same questions. Different answers.
Each section is a job finance teams actually run — not a feature checklist copied from a datasheet.
Issued invoices that do not drift
The usual gap
Spreadsheets invite silent edits. Finance discovers the customer PDF does not match the row after someone ‘fixed’ a number.
In Sonic AI
Drafts and in_progress accept new lines. Sent/final/paid freeze. Corrections are credit notes or new invoices — with sequence floors on manual numbers.
- Bulk finalize respects sequence priority — not row order in a sheet.
- Adjustment invoice vs credit note rules by send state.
- Public invoice number for customer-facing surfaces.
Overdue means sent and unpaid
In Sonic AI
Watchtower evaluates sent unpaid only. Drafts are not overdue. Freight drafts get due dates backfilled before classification.
- Dunning cadence with per-customer overrides.
- Email audit: sent, delivered, opened, bounced.
- AI-assisted next sentence — operator approves.
The usual gap
Colouring draft rows red inflates AR and starts chases before an invoice went out.
Bank truth vs AR truth
The usual gap
Bank login in one tab, ageing in another. Reminders go out after the wire landed.
In Sonic AI
Bank rec queue imports CSV or connections; matches amount, reference, invoice numbers, payer vs bill-to contacts.
- Split payment across invoices.
- Partial pay reduces balance; cadence continues on remainder.
- Unmatch when someone picked wrong.
Seat and usage files stop being pivot projects
In Sonic AI
Templates with Process gate, ClickHouse preview, seat snapshot keys, webhook path for partners.
- Never import vendor increase columns.
- Confirmation days: pending adds, LIFO cancel.
- 2 GB usage upload in 10–15 minutes.
The usual gap
Vendor exports need idempotency, customer fuzzy match, confirmation windows, and daily seat expansion — fragile in Excel.
Freight leaves the macro workbook
The usual gap
Diesel branch, shipper match, and invoice-all windows are manual — wrong table, wrong shipper, wrong period.
In Sonic AI
Carrier contract → rate card → upload workspace → shipper frozen at Process → invoice preview.
- Rate index branches — no cross-table fallback.
- Shipper not selected blocks Create — not silent failure.
- Rev rec on haul date; journal explains invoice.
At a glance
Side by side on the decisions that stick.
Issued invoice
Sonic AI
A frozen document
Spreadsheets and manual billing
A row you can still edit
Overdue
Sonic AI
Sent unpaid only
Spreadsheets and manual billing
Whatever someone coloured red
Cash
Sonic AI
Matched, or still a chase
Spreadsheets and manual billing
A separate bank login
Seat snapshots
Sonic AI
Templates + confirmation
Spreadsheets and manual billing
Pivot and pray
Freight
Sonic AI
Rate card + upload path
Spreadsheets and manual billing
Macro workbook
Audit question
Sonic AI
Link to the source bill
Spreadsheets and manual billing
A tab that drifted
The wider landscape
Spreadsheets and manual billing sits in one lane. Most stacks run three.
Billing tools, ERPs, and payment processors each own a slice of contract-to-cash. Sonic is the chain that connects them — not a fourth thing competing for the same lane as Spreadsheets and manual billing.
| Lane | Sonic AI | Billing tools | ERP | Payment processor |
|---|---|---|---|---|
| The job | Bill correctly, collect, match cash, post the trail | Subscriptions, plans, often dunning | Books of record, inventory, GL | Take the payment |
| Grain | Schedule and shipment | Subscription | Neither is the point | A charge |
| Contract PDF | Read, review, approve | Usually typed in, or a CPQ next door | Not this | Not this |
| Issued invoice | Frozen. Credit note or a new document. | Varies | Not the bill you send | A receipt |
| Collections | Sent unpaid only. Cadence with an off switch. | Often card retries / dunning | Ageing reports | Failed-charge retries |
| Bank rec | Operator queue. A deposit is a fact. | Rarely the product | A module, different record | Payouts, not invoice matching |
| Freight bill-to | Shipper | Customer | Customer / vendor | Whoever paid |
| Payments / GL | Not a processor. Not the ledger of record. | Often bundled | The ledger of record | The processor |
See it in the product
Platform pages for this comparison
These are the product surfaces behind the claims above — not a separate architecture tour.
Questions
Open the answer here.
These are the questions this page raises. The full list lives on FAQ.
How do you compare to Chargebee, Stripe, or NetSuite?
Chargebee is subscription billing. Stripe is a processor — Sonic does not take the payment. NetSuite is the GL of record — Sonic is not. The full map, including Zuora, Maxio, Ordway, Zenskar, m3ter, and the spreadsheet, is on Why Sonic AI. The honest test is still a demo on your files.
Will you rewrite an invoice after it has been sent?
No. Sent, paid, void, and final invoices are not rewritten. Corrections are credit notes or a new invoice alongside the original. Drafts and in-progress invoices can still accept lines. Freight has no credit notes — correct the file, or void.
How do bank rec and collections stay out of each other's way?
Watchtower chases what is still unpaid. Bank rec matches deposits to billed parties. An unmatched deposit is cash that already landed — if you don't match it, the cadence will chase a customer who already wired you. Rec is the off switch collections cannot see on its own.
Next
See it on your contracts
A walkthrough on the agreements and files you actually bill from — not a slide deck.