Loading
Loading
Money path · cash
LiveRe-keying approved work into a separate invoicing tool is how lines get lost and disputes start. Operational invoices should birth from authorised scope; books of record stay in Xero/MYOB — export is Dry-run today with a gated live push path, not Connected theatre.
Primary persona: Advisor / owner / accountant (ops)
The problem
Jobs finish in one system; invoices live in another; AR is a Friday spreadsheet surprise.
Why it matters
GST-aware totals for AU/NZ-first shops without pretending to be the general ledger.
Payment records update AR so owners see cash risk daily.
Partial pay support matches real customer behaviour.
Text-to-pay / portal pay path expanding — Stripe shop Checkout Stub without keys, live when configured.
Proof from the live demo
Captured from the seeded multi-tenant demo. Open the same surface with demo credentials.


Stage sequence
Each stage lists the action, the business why, and the intended outcome. This is how we implement and test the product — not marketing fiction.
Action
Ensure produce-complete jobs have approved billable lines; fix scope gaps.
Why this stage
Invoicing unapproved work creates chargebacks and trust damage.
Action
Create GST invoice from RO; lock issued document version.
Why this stage
Document integrity matters for disputes and accounting export later.
Action
Record cash/card/payment, or hosted Stripe Checkout when keys are configured (Stub without keys — path expanding).
Why this stage
WIP that is READY but unpaid is still working capital stress.
Action
RO/invoice progress to PAID/CLOSED; dashboard AR widgets update. Xero export remains Dry-run unless gated live.
Why this stage
Owners manage cash from the same OS that ran the job — not a second tool.
Related search intent