Integrations

Integrations connect ARK TMS to accounting, tracking, carrier onboarding, compliance monitoring, and visibility tools.

Available integration areas

• QuickBooks Online: accounting sync for invoices, payments, and accounting review.
• ARK Tracking: driver tracking requests and load visibility from ARK TMS.
• MacroPoint: shipment tracking through MacroPoint visibility services.
• TruckerTools: driver tracking and reefer-related tracking settings.
• MyCarrierPortal: carrier onboarding, packet collection, monitoring, and documents.
• RMIS: carrier onboarding, compliance monitoring, auto-sync, and documents.
• Highway: carrier onboarding, monitoring, alerts, webhooks, and documents.
• project44: shipment milestone and visibility updates.
• Load-board posting providers: posting, updating, refreshing, and removing available loads when enabled.

Setup checklist

1. Assign an internal owner for the integration.
2. Confirm account access with the provider.
3. Gather credentials, customer mappings, and carrier monitoring requirements before configuration.
4. Open Settings, then Integrations.
5. Configure and save the integration.
6. Run one test workflow before using it broadly.
7. Confirm the team knows which system remains the source of record for each workflow.

Test workflow

Use one normal business case first: one invoice, one tracked load, or one carrier profile. Confirm the record starts correctly, updates as expected, and produces the expected result in ARK TMS and the connected provider.

Avoid using unusual exceptions for the first test. Test access, required fields, and normal status updates before testing edge cases.

Normal usage

Review integration results as part of the existing workflow. Accounting users should review sync status before closing billing work. Dispatch users should review tracking status from the load. Carrier teams should review onboarding, documents, and monitoring results before approving carrier use.

Troubleshooting

• Missing credentials: confirm provider access and reconnect the integration.
• Record did not sync: confirm required fields, status, mapping, and provider account access.
• Duplicate or mismatched record: review customer, carrier, or account mapping before retrying.
• Tracking did not start: confirm the load is dispatched and contact details are complete.
• Load-board posting is blocked: confirm required stop city, state, and appointment details.
• Carrier data looks incomplete: compare the carrier profile in the provider portal and contact support if the provider record is correct.

When to contact support

Contact support for credential issues, provider sync setup, initial bulk carrier import, accounting sync questions, or integration behavior that does not match the expected workflow after the basic troubleshooting checks.