Catalogs
Customers, shippers, carriers, products, meters, list prices. Contracts point at these records. They do not invent them on the invoice.
Function · Ops
Defaults so the next contract is not blank.
Parsing instructions, confirmation days, invoice-from, meters, list prices, templates. Ops is how billing stays typed after the first deal.
The mess
The first contract was heroic. The second started as a blank form.
This is the role: defaults. Billing is the document. Ops is why the next deal is typed — customers or shippers already named, list prices already shaped, parsing instructions already bracketing the rulebook, confirmation days already set.
Org defaults
Invoice-from, tax identifiers, seat confirmation days, AI parsing context. Team access stays company settings — never a hidden URL.
Templates
Usage and seats keep landing after go-live. A warehouse pipe is how events arrive without a monthly hero upload.
What Sonic does
Approve can fill the catalog. Defaults fill the next deal.
An unlinked contract customer can materialise on approve the same way products and list prices do — an existing catalog name is linked, not duplicated. Creating during review stays optional. Parsing instructions bracket the structurer rulebook: operator preamble first, the same block again after.
Sonic AI
CustomersShippersCarriersProducts
| Account | Status | Source | Net terms |
|---|---|---|---|
| Nimbus Cloud | Active | Contract | Net 30 |
| Northwind Analytics | Active | Contract | Net 30 |
| Apex Tools | Active | Manual | Net 15 |
| Delta Pack | Draft | Upload alias | — |
| Westbound Logistics | Active | Contract | Due on invoice |
A catalog match attaches an identifier. It does not invent the account — it links, or it waits.
Sonic AI
Usage
2 templates
Event files
Seats
1 template
Daily snapshots
Last process
3 Apr
Sample only
| Template | Grain | Worksheet | Status |
|---|---|---|---|
| API events | Usage | daily_export | Ready |
| Seat snapshots | Seats | pupm_daily | Ready |
| Warehouse sync | Usage | — | Connected |
| Legacy CSV | Usage | sheet1 | Needs process |
Uploading a sample does not bill. Process computes the preview.
Templates are the pipe after go-live.
Usage and seats keep landing. A warehouse pipe is how events arrive without a monthly hero upload. Meters stay named in the UI. Seat labels are catalog names, never an id.
Usual mess
The second contract is a blank form.
Usage arrives as a monthly hero upload.
In Sonic
Approve can fill the catalog. Defaults fill the next deal.
A warehouse pipe after go-live. Templates stay mapped.
Questions
Open the answer here.
These are the questions this page raises. The full list lives on FAQ.
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.
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.
Do you have case studies?
Not named ones yet. We will not invent a logo wall. The honest path is a walkthrough on the contracts and files you actually bill from — book a demo.
Next
See it on your contracts
A walkthrough on the agreements and files you actually bill from — not a slide deck.