Connects to the tools you already run on

Three integrations today, each one built because a yard asked for it. Here's exactly what connects — and an honest list of what doesn't yet.

Integration 01 — Xero

The invoice run lands in Xero, ready to send

At the end of the week (or whenever you run it), Cartage Core builds draft invoices from captured loads and pushes them into Xero — coded the way your accountant set up, with per-vehicle detail your clients can actually read.

Draft invoices, not surprises — review before anything is sent.
Account codes — set once per client, applied every run.
Per-vehicle tracking — line detail down to the truck, which settles "which truck did that" disputes fast.
Subcontractor statements alongside — what you bill and what you owe, generated in the same run.

Xero — draft invoice Example data

INV-2026-0841 · Hawke's Bay Quarry Ltd

Billing period: week ending 14 Aug 2026

Item	Qty	Rate	Amount
AP40 basecourse — per tonne	412.6 t	$18.50	NZ$7,633
FAF surcharge	412.6 t	$0.42	NZ$173
Wait time — site	3.5 h	$95.00	NZ$333
Per-vehicle detail	HT-201 · HT-204 · HT-207

Status in Xero: DRAFT — nothing sent without your review. Account code: 4110-Cartage.

Integration 02 — EROAD

The live fleet map runs on EROAD telematics

If your trucks already run EROAD, Cartage Core reads truck positions from the same hardware and puts them on the dispatch board. Arrival detection knows when a truck lands at a quarry or site — the board updates itself, and so do the customers you choose to give visibility.

Truck positions, live — on the map and on the job.
Quarry/site arrival detection — the basis for automatic load capture start and arrival alerts.
No second box in the cab — we use the telematics you already pay for.
Compliance records — odometer data helps autofill the daily pre-check.

Need an EROAD account? Set one up first — most cartage fleets already run one for RUC and driver work time.

EROAD data on the board Example data

HT-201 arrived at Pine Hill Rd pit 09:41 · auto-detected from EROAD position

Integration 03 — Weighbridge (optional module)

The pit visit becomes the docket

For yards that weigh their own loads, the weighbridge module pulls the ticket straight off the indicator. No re-typing the weight, no transcription errors, no second copy of the truth.

Ticket → load record — the weight lands on the load, attached to the right truck and job.
Works with most modern indicators — we'll confirm yours before you pay for anything.
Reconciliation-ready — supplier invoices and your own tickets match line by line.

Weighbridge — ticket 20481 Example data

32.4 t gross

Vehicle	HT-204 · NZ-HA-4832
Product	GAP65 drainage
Time	09:41:07 NZST
Status	Linked to load CC-1042

The honest bit

What doesn't connect yet

We'd rather tell you what's real than sell you a roadmap. Here's what's not built — and how to ask for it.

Fuel cards

Not connected yet. Fuel spend lives outside Cartage Core for now — the FAF engine handles the fuel cost side of your rates.

Payroll systems

Not connected yet. Subcontractor pay statements export from Cartage Core; direct payroll feeds are on the wish list.

Your system here?

The roadmap is driven by operators. If your yard needs a connection, ask — integrations get built when yards ask for them.

Ask for an integration