Your books close without rebuilding a spreadsheet.
Every invoice, client payment, driver payout, wallet top-up and job fee posts itself as a balanced journal entry. Not a CSV export — a real double-entry general ledger, with a trial balance and a balance sheet built off the journal lines. Close a month and the financial fields on every job inside it lock.
The systems we compared stop at the job sheet.
So the operation ends where the money starts, and somebody rebuilds it by hand every month.
Two visible ledgers, one general ledger underneath.
You and your ops staff see two simple ledgers: what you owe Fusion Link, and what you owe your drivers. Your accountant sees a balanced double-entry general ledger underneath both.
Your wallet
Top-ups, job fees, refunds, and booking site template debits. Every line links to the real job or event that caused it.
Driver payouts
Jobs ledger, payables, settlements, payouts. Tracked per-driver across every operator they drive for.
Double-entry GL
A seeded chart of accounts for every operator, with receivables split into supplier, corporate and passenger sub-accounts. Every event writes a balanced journal entry, validated before it posts.
Reversing voids
Voids never delete — they post a reversing entry with a hard link to the original. The audit trail is intact even when the line cancels itself.
Rebuildable ledger
If the ledger ever drifts, it can be rebuilt from the history it was posted from — and rebuilding twice cannot double anything. A ledger you can reconstruct is a ledger you can trust.
Sub-account discipline
AR breaks into passenger / corporate / supplier sub-accounts so an aging report shows who owes you what, not just a single AR blob.
The reports your accountant asked for.
Built straight off the journal lines — not derived from job CSVs or fudged from booking totals. The same data your auditor wants to see.
Statement-grade
- Trial Balance — every account's debit/credit total over a date range
- Balance Sheet — assets / liabilities / equity at a point in time
- Account Ledger — every journal line touching a given account
- Profit and loss across jobs, drivers, clients, and revenue
Operational
- AR aging waterfall: 0-30 / 31-60 / 61-90 / 91-120 / 120+
- AP aging waterfall on driver payables
- Settlement statements by driver, by period
- Activity monitor on every state change
Exports
- Google Sheets export for accountants who live in spreadsheets
- A digest email once a day
- Evidence ZIP per job (photo + GPS + audit trail) for dispute defence
- The ledger can be rebuilt from history, and rebuilding it twice changes nothing
The chasing happens without you.
An overdue invoice chases itself at 3, 7 and 14 days past due. Fusion Link runs that ladder for you, and ages what you are owed as you open the page.
Aged receivables and payables
Client receivables and driver payables on one overview, each aged into 30-day bands. Fusion Link computes them when you open the page, not overnight.
Overdue chasing
An invoice you actually emailed gets chased at 3, 7 and 14 days past due. One email per stage, the highest stage only, and a switch to turn it off.
Sequential invoices
Numbers run in sequence per operator, atomically, so no two invoices ever share one.
Real invoices, not glorified emails.
A PDF the client can file, a number that cannot collide, and a tax rate that stops moving the moment you issue it.
A real PDF, and a send log
Fusion Link renders the invoice as a PDF. Emailing it stamps who you sent it to and when, which is also what makes the invoice eligible for chasing.
Tax-rate snapshot
The invoice stores the rate that applied on the day you issued it. A later change to your country's rate never mutates an invoice you already sent.
Transactional void
Voiding an invoice posts a reversing journal entry. Nothing is mutated in place; the audit trail keeps the original alongside the void.
Lock the past so you can close the month.
Closing a period freezes financial fields on every job in it. Operational fields stay editable — so you can fix a typo on a driver name without re-opening books.
Period lock
Pickup date inside the closed range → financial fields locked: driver pay, client rate, charges, payment status, settlements.
Operational fields stay editable
Driver name, notes, and client contact stay editable after close. You are locked out of book-changing edits, not out of corrections.
Reason-gated reopen
Admin-only reopen requires a written reason. The reopen, the reason, and the eventual re-close all land in the audit log.
Built for global ground transport from day one.
Currency-safe money
JPY, SGD, USD — all round-trip without rounding bugs. No more 'lost cent' tickets at month-end close.
Daily FX refresh
Rates behind your booking site's home-currency preview refresh daily. The charge itself always settles in your own currency, so a moving rate never reaches your books.
Spreadsheet export
Trial balance, balance sheet, and account ledger all exportable to Google Sheets. Direct push if your accountant prefers it.
What the books do not do.
Three limits, stated here rather than found in your second month.
Payouts are recorded, not paid
Driver Pay is tracked as a payable and cleared when you pay it. Fusion Link records the payout and posts the entry; it does not move the money.
Tax defaults cover part of the map
A rate is suggested in 23 markets and follows the country you registered in. Elsewhere an invoice issues with no tax row, and you set the rate yourself.
Earlier history needs one run
Journal entries post live from the day you join. An operator who ran jobs before the ledger existed runs the backfill once, and the earlier history posts too.
Give your accountant the real thing.
Sign up free. Your first job posts its own journal entry, at a flat US$0.40 a job. Run the backfill once and your earlier history posts too.