Invoicing and payments: from signed POD to money in the bank
Raise invoices from completed jobs, watch them move from draft to paid, and let automated reminders and late fees do the chasing you never have time for.
How does the invoice lifecycle work?
Every invoice carries a visible state, so you always know where the money is stuck. It starts as a draft raised from a completed job — typically one that just closed with a signed POD — then moves through sending, viewing and payment.
| State | Meaning | What you learn |
|---|---|---|
| Draft | Raised but not issued | Billable work waiting on you |
| Sent | Issued to the customer | The clock on payment terms has started |
| Viewed | The customer has opened it | "We never received it" is off the table |
| Paid | Settled in full (or building via partials) | Done — reconciled and exportable |
The viewed state deserves emphasis: knowing an invoice was opened four days ago changes the tone of a follow-up call entirely.
What does AR automation actually automate?
The chasing. Small fleet owners are usually the credit control department, and chasing happens at 10pm or not at all. Strix lets you set reminder schedules that follow up unpaid invoices automatically, apply late fees under rules you define, and accept partial payments so an invoice can be settled in instalments without falling out of tracking. The system is politely persistent on your behalf — the customer relationship stays yours, the persistence becomes software.
How do Xero and QuickBooks fit in?
Through OAuth invoice export — you connect your Xero or QuickBooks account and invoices flow across without retyping. We are precise about scope: this is invoice export, not a full two-way accounting sync. Strix is where operational billing happens, tied to jobs and PODs; your accounts package remains the ledger of record for your accountant. That division keeps both tools doing what they are good at.
What are marketplace earnings statements?
If you take work from the Smart Taurus job marketplace — consumer jobs you quoted on to fill empty legs — those earnings are accounted for in statements, separate from the invoices you raise to your own customers. Marketplace revenue and direct revenue stay distinguishable, which your bookkeeper will thank you for at year end.
How do Stripe driver payouts work?
Strix supports paying drivers out via Stripe, which matters most for fleets running owner-drivers or subcontractors rather than salaried staff. Payouts happen through Stripe's infrastructure against the work recorded in the platform, so what a driver is owed and what they were paid are connected to the same job records — and the shift history is there when the numbers get queried.
Why tie invoicing to dispatch instead of using a standalone tool?
Because the gap between operations and billing is where revenue leaks. Standalone invoicing means someone re-keys completed jobs into another system — and the jobs nobody re-keyed are the ones that never get billed. In Strix the quote becomes the job, the job ends with a POD, and the POD is the invoice's evidence; nothing falls between systems because there is nothing between them. For a courier fleet, the question "did we invoice everything we delivered this week?" gets answered by the platform, not by an audit. See the pricing page for plans — invoicing is part of the core platform, free to get started, cancel anytime.