TMS Logo

TMS Documentation

RMIS

RMIS supports carrier onboarding, compliance monitoring, and carrier document sync when connected for your organization.

Setup checklist

  1. Confirm your RMIS account details.
  2. Open Settings, then Integrations.
  3. Select RMIS.
  4. Enter the RMIS Client ID and API password.
  5. Turn on Enable RMIS onboarding.
  6. Save settings.
  7. Contact support for initial bulk import from monitored carriers if needed.

Test workflow

  1. Search for one carrier by RMIS ID, DOT, or MC/MX number.
  2. Sync carrier details.
  3. Review authority, insurance, packet details, documents, contacts, payment details, and factoring evidence.
  4. Compare the synced profile with RMIS.
  5. Approve or keep the carrier inactive based on your policy.

Normal usage

Use RMIS during carrier onboarding and ongoing compliance review. Review synced compliance data and documents before changing a carrier’s approval status.

When RMIS onboarding is enabled, ARK TMS can refresh monitored carrier data in the background with RMIS Delta sync. Turning off RMIS onboarding also stops scheduled Delta sync. Use manual sync when a carrier record looks stale or when you need to verify a change before dispatch.

Manual sync is for carriers already onboarded in RMIS and accepts RMIS ID, DOT, or MC/MX. Invitation preview accepts DOT or MC/MX and first attempts to sync an existing carrier; if RMIS cannot return the expanded record, the invitation flow can continue to send an invite.

RMIS certification notes, status, payment, and factoring details may appear in the carrier profile when available from the provider.

Only one carrier onboarding provider can be active at a time. Turning on RMIS onboarding disables Highway and MyCarrierPortal onboarding actions.

Troubleshooting

  • Carrier not found: confirm the identifying details in RMIS.
  • Identifier rejected: use a real DOT, RMIS ID, or MC/MX docket value; all-zero or malformed values cannot be sent to the provider.
  • Sync asks for an invite: the carrier is not onboarded in RMIS yet.
  • Sync or invite action missing: confirm RMIS onboarding is enabled and no other carrier onboarding provider is active.
  • Synced data looks incomplete: compare the carrier profile in RMIS and sync again.
  • Documents missing: confirm the documents are available in RMIS.
  • Packet status differs: use RMIS as the comparison point before approving the carrier.
  • Data looks stale: run manual sync or wait for the next auto-sync, then compare the last-synced time.
  • Duplicate carrier conflict: when multiple local carriers match the same RMIS customer ID, DOT, or MC/MX identity, resolve or archive the duplicate carrier records before retrying sync.
  • Monitored carriers need initial import: contact support.