# Plan the connections around your TMS

RunaboutX's public site identifies integration categories relevant to trucking operations: ELD and telematics, load boards, accounting, payments, and documents. These are categories to evaluate. No named third-party connector, production status, or data sync frequency is publicly confirmed.

## Map the data, not just the logo

For each current tool, list the records it owns, the fields RunaboutX would need, the direction of sync, timing, failure handling, and who resolves a mismatch. For example, a telematics connection should answer whether it supplies an event timestamp, last known location, or both. A billing handoff should answer which system owns the final invoice number.

| Connection category | Example question |
| --- | --- |
| ELD / telematics | Which status signal is authoritative when data is delayed? |
| Load boards | Which offer fields can enter a load record, and who confirms them? |
| Accounting | Which system creates the final invoice and payment status? |
| Payments | What is approved in the TMS versus released elsewhere? |
| Documents | How are rate confirmations and PODs matched to a load? |

Use the [TMS integration planning guide](/resources/learn/tms-integration-planning/) to prepare a system inventory. In a [demo](/#contact), ask for the exact connection, availability, setup requirements, and support boundary for your stack.

---

Canonical: https://www.runaboutx.com/integrations/
Last reviewed: 2026-09-26