Customers & shippers
Subscription bill-to, or freight bill-to. Aliases from carrier files are confirmed on upload, not invented on preview.
02 · Catalogs
Named customers, shippers, carriers, products, prices, and indexes. Contracts and schedules point at these records — they do not invent them on the invoice.

Source of truth
A bill-to, a product with a price, a carrier, an index. Organisation defaults fill the next deal so you are not starting from a blank sheet.
The records
Customers for subscriptions. Shippers and carriers for freight. Products, list prices, and meters stay named — never left as an internal id. The next contract starts from these blocks, not from a blank sheet.
| 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.
Subscription bill-to, or freight bill-to. Aliases from carrier files are confirmed on upload, not invented on preview.
The model and the amount. Variants for a carrier when freight needs them. Meters stay named in the UI.
Who hauled, selected on the contract. Published series with Default and optional branches.
Profile, tax identifiers, invoice-from defaults, seat confirmation days, and parsing instructions. Team invites, two-factor, and feature flags stay company settings — never a hidden URL.
Priced the same way, everywhere
Subscription uses nine models: one fixed fee, six usage shapes, two seat shapes. Shipment uses two: a flat amount, or a formula. Tax category and revenue recognition method live on that same catalog entry — not guessed when the invoice goes out.
Subscription · nine models
The schedule bills from these. Mixed models can share an invoice when the deal says so.
A recurring or one-off fee. The amount on the price is the amount that bills.
One rate — or a percentage — on metered usage, with an optional floor and cap.
One marginal tier applies to all usage in the period. Classic volume pricing.
Usage rounds up to whole packages. One price per package.
Each band stacks. You pay every band you crossed, not only the last one.
Usage becomes a package count first, then graduated bands apply to that count.
A prepaid commitment by slab. Usage above the slab bills at an additional unit price.
One rate per seat. Removals are not refunded; mid-period adds can prorate.
Seats in each band at that band’s rate, summed. No flat fee per tier.
Shipment · two models
Rate cards use Shipment Rated. The kind is flat or formula — not a monthly schedule dressed up as freight.
A signed amount per shipment — per kilometre, per load, per stop. The rate card holds the number.
An expression over shipment values, other charges on the same card, and a published index on the haul date.
On every price
Two facts travel with the catalog entry. Neither is a global default, and neither is decided at send time.
Every product and every price variant carries its own tax category. Invoice tax is looked up from the catalog — not inferred when the document is issued.
The recognition method sits on the same price: how this line becomes revenue. A schedule cannot recognise what a price never described.
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.