Where the TruckMate SQL extract starts
The TruckMate to EXSPEEDITE migration page describes a SQL extract of customers, tariffs, equipment, and settlements. This blueprint does not replace that page and it does not invent TruckMate table names. The controller uses the extract the carrier already has, then checks the accounting fields below before anything is handed to Sage Intacct. Product behavior for the ledger connection is on Sage Intacct TMS integration and TMS Sage Intacct integration.
Field checklist the controller verifies
| Record | Field the controller verifies | Sage Intacct destination |
|---|---|---|
| Customer invoice | Invoice number, invoice date, bill-to customer, linehaul, fuel surcharge, accessorial lines, and invoice total. | Accounts receivable invoice, after the controller maps the general ledger accounts. |
| Settlement bill | Payee, settlement number, pay date, earning lines, and deduction lines. | Accounts payable bill, after the controller maps the accounts. |
| Entity | Operating company the controller selects for that invoice or bill. | Sage Intacct entity the controller confirms. |
| Dimension | Location or terminal, department, customer, equipment, and driver, when the chart uses that tag. Unused tags stay blank. | Sage Intacct dimension the controller maps. |
| POD | Document reference the controller can open from the invoice. | Attachment or link the controller confirms is present. |
Source, EXSPEEDITE, and accounting fields
The controller ticks off this map before a batch. A CPA firm did not co-author it. This note does not state a sync success rate.
| Source field | EXSPEEDITE field | Accounting field | Who verifies it |
|---|---|---|---|
| Invoice number, invoice date, bill-to customer, linehaul, fuel, accessorial lines, and total on the TruckMate SQL extract. | The same values on the customer invoice in EXSPEEDITE. | Sage Intacct accounts receivable invoice, and the general ledger accounts the controller mapped. | Controller |
| Payee, settlement number, pay date, earning lines, and deduction lines on the TruckMate SQL extract. | The same values on the settlement bill in EXSPEEDITE. | Sage Intacct accounts payable bill. | Controller |
| Operating company on the TruckMate SQL extract. | Entity on the order. | Sage Intacct entity. | Controller |
| Terminal, department, customer, equipment, and driver tags on the TruckMate SQL extract. | Dimension tags stored with the order. | Sage Intacct dimension the controller mapped. A tag with no dimension stays blank. | Controller |
| POD reference on the TruckMate SQL extract. | POD document on the order. | Attachment or link on the Sage Intacct invoice. | Controller |
Check one closed invoice and one settlement bill in a sandbox or a parallel batch before a cutover. If a row does not match, stop that row. This note does not state a sync success rate.
If the carrier wants to estimate unbilled detention before that invoice exists, use the carrier-entered formula on the margin leakage benchmark. This blueprint does not publish that dollar amount. The links to that benchmark and to the other blueprints are in the list below, once each.
What should a fleet CFO review before the first Sage Intacct batch?
The field map above: invoice, settlement bill, entity, dimension, and POD. The controller verifies each row. This note does not state a sync success rate. A CPA firm did not co-author it. Consulting does not require a software purchase.