What integrates with MapTrack today
MapTrack integrates with accounting platforms (Xero, MYOB, QuickBooks), OEM and fleet telematics feeds, and fuel cards, and it ships a documented public API plus CSV/XLSX import and export for everything else. ERP platforms like SAP, Oracle and Dynamics 365 are supported as scoped integration projects, not one-click connectors. Knowing which of those buckets your system falls into is the difference between a two-minute setup and a two-month project.
The integration directory lists 150+ telematics, OEM, fuel-card and management-system data sources. More than 120 have at least one live data feed today; others are available on request, so coverage is not uniform. The data types you get (location, odometer, engine hours, fuel, fault codes) vary by source, which is why we tell everyone the same thing: confirm your specific provider and fields in a pilot before you build a process around them.
A useful mental model is three buckets. First, connections you switch on and configure: accounting and telematics feeds. Second, things you build yourself against the public API or with imports and exports. Third, scoped projects where MapTrack works with your IT team: ERP exchange. The rest of this article walks through each bucket, what data actually moves, and where the sharp edges are.
Accounting: Xero, MYOB and QuickBooks
The most common integration question we get from Australian operators is about Xero. The integration connects through Xero OAuth 2.0: you authorise access from your MapTrack account, map your asset categories to Xero fixed asset types, link cost centres to Xero tracking categories, and choose which data points sync. MYOB and QuickBooks follow the same pattern for their platforms.
What moves is financial asset data. Purchase costs and supplier details when new assets are added. Depreciation schedules, using straight-line or diminishing value methods, so book values stay consistent between the two systems. Maintenance costs from completed work orders, posted as categorised expenses so finance can see spend by asset or project. And disposals: when an asset is sold or written off in MapTrack, the corresponding fixed asset record is updated so the balance sheet stays honest.
The reason this matters is boring and expensive: in most businesses the physical asset register and the fixed asset ledger are two spreadsheets maintained by two people who have never met. Every audit becomes an archaeology project. If you want to see what a clean starting point looks like before connecting anything, our free fixed asset register template shows the fields finance needs and the asset register template shows the operational side. Getting those two views to agree is the real job; the integration just keeps them agreeing.
Telematics: OEM and fleet GPS feeds
If your machines already report telemetry, MapTrack can use it. There are two families. OEM feeds come from the manufacturer's own system: Caterpillar, Komatsu, John Deere, Hitachi, Volvo CE, Liebherr, JCB, Bobcat, Kubota and Case all publish machine data through their portals. Fleet telematics platforms like Geotab, Teletrac Navman, Verizon Connect and Samsara aggregate whatever hardware you have fitted. Fuel cards (BP, Ampol) round out the picture with fuel transaction data.
Inside MapTrack, the feed gives your asset records live context: current linked-tracker positions on the asset map, and odometer or engine-hour readings that can drive service schedules instead of someone walking the yard with a notepad. For dedicated live tracking, geofences and trip history, MapTrack also offers GPS hardware and the MapTrack Telematics platform as its own product, which is worth a separate conversation if minute-by-minute location is the goal.
Setup is configured per provider, and this is where honesty beats brochures: not every source publishes every field. One provider gives you location, engine hours and fault codes; another gives location only. Run a pilot on three or four machines, confirm the fields arrive, then scale. A telematics feed that quietly stops updating engine hours will silently stall a service schedule that depends on it, so check the feed as part of your preventive maintenance routine, not just at go-live.
ERP: what is real and what is a project
Here is the part most vendors fudge, so we will not. MapTrack does not ship prebuilt one-click connectors for SAP, Oracle, Pronto Xi, IBM Maximo or Dynamics 365. Anyone who tells you their field tool plugs into a live ERP in an afternoon is describing a demo, not a production system. What MapTrack provides is a scoped integration pattern: the ERP remains the system of record, MapTrack runs the field layer (assets, QR scans, forms, photos, signatures), and the exchange between them is designed and verified with your IT team or integration partner.
The building blocks that exist today: a documented public API covering master data (assets, categories, custom fields, locations, people and account users) with API key access, manual CSV/XLSX import and export, and outbound automation webhooks. Work orders, form submissions, attachments, meter readings and inventory movements are not public API resources today; moving those requires custom middleware, which is exactly why the scope conversation has to happen before the contract, not after. Our ERP field operations guide covers the reference architecture in detail.
Who owns the project matters as much as the technology. Operations defines the field workflow, maintenance defines the asset and work order rules, and IT controls ERP credentials, middleware, security and release. The projects that go badly are the ones where nobody decided which system owns each object before someone started syncing. Decide ownership first, pilot the field workflow second, build the exchange third.
What data flows where
The table below is the one-glance version: each integration family, what actually moves, and how it is delivered.
| Integration | What moves | How it is delivered |
|---|---|---|
| Accounting (Xero, MYOB, QuickBooks) | Purchase costs, depreciation, maintenance expenses, disposals | OAuth connection, then category and cost-centre mapping |
| OEM and fleet telematics | Location, odometer, engine hours, fuel, fault codes (varies by source) | Configured data feed per provider; confirm fields in a pilot |
| Fuel cards | Fuel transaction data by vehicle | Configured feed per card provider |
| Public API and files | Master data: assets, categories, custom fields, locations, people, users | API key access, CSV/XLSX import and export, outbound webhooks |
| ERP (SAP, Oracle, Pronto Xi, Maximo, Dynamics) | Agreed subset of master data, evidence and status changes | Scoped project with your IT team; no prebuilt connector |
Integration-readiness checklist
Most integration pain has nothing to do with the software on either end. It comes from dirty data and undecided ownership. Work through this list before you connect anything, whichever platform you are connecting:
- Name the system of record for each object. Assets, locations, people, costs, work orders: one owner each, in writing. Every sync conflict traces back to skipping this.
- Clean the asset register first.Duplicates, ghosts and "misc excavator" rows sync just as fast as clean data. Start from the asset register template if yours needs a rebuild.
- Give every asset one unique ID. The rego, the fleet number and the finance asset code can all exist, but one of them has to be the join key between systems.
- Agree the category and cost-centre mapping. For accounting sync this IS the integration: which MapTrack categories map to which fixed asset types and tracking categories.
- Confirm who owns credentials. API keys, OAuth grants and provider logins need a named owner, not a shared inbox and a prayer.
- Pick a pilot cohort. Three to five machines or one cost centre. Prove the fields arrive and the mapping holds before you scale.
- Decide what happens on failure. Duplicates, retries, rejected updates: boring until the first month-end reconciliation, then critical.
- Check your maintenance history is captured. Expense sync is only as good as the work orders behind it. A paper-based workshop should start with the equipment maintenance log and digitise from there.
Honest limits
Three limits worth knowing before you commit. First, coverage across the 150+ data sources is not uniform: the fields available differ by provider, and some sources are available on request rather than live today. Second, there is no prebuilt ERP connector, and any production ERP exchange is engineering work with your IT team; treat vendor claims to the contrary (from anyone) with suspicion. Third, the offline boundary: MapTrack forms, selected asset records, QR tags and files support offline capture and sync when you are back in coverage, but the integration exchanges themselves run when connected.
None of those limits are unusual, and all of them are manageable if you know them going in. That is the point of this article. If you want to talk through your specific stack, the fastest path is a conversation with the team: book a demo and bring your provider list, or start with the integrations overview and the directory to check your systems first.
