Sync fleet cards with Miter + Coast

The integration uses phone number as the unique identifier to match records between the two systems. If a person with that phone number already exists in Coast, the sync updates that existing record with the data coming from Miter instead of creating a duplicate person. If phone numbers do not match, or a team member has no phone number on file in Miter, the sync cannot reliably link the two records, so keeping phone numbers accurate and unique in Miter is important for a clean sync.

The sync moves team members and status by phone number regardless of how many entities you run in Miter, but Coast’s spending policies, card issuance, and default roles are configured within Coast per company setup. If you operate multiple legal entities or regions, plan your department and location naming in Miter carefully, since those values are designed to carry directly into Coast and will shape how you group cards and spend policies on the Coast side.

Yes. The Miter and Coast integration only handles workforce data: team members and active or inactive status. Card issuance, spend limits, merchant restrictions, and whether a card is fuel only or an open Visa card are all configured directly in Coast by an admin. New team members synced from Miter land under a default policy and role automatically, and from there Coast admins have full control to adjust card level settings for each person or vehicle.

No. Coast does not have jobs, timesheets, cost codes, pay rates, or payroll concepts, so none of that data moves between the two systems. The Miter and Coast integration is limited to workforce data: team members and employment status. Expense categorization like GL codes and cost centers is handled inside Coast and can be pushed from Coast to accounting systems such as QuickBooks, NetSuite, or Sage Intacct separately, outside the scope of the Miter to Coast sync.

Connecting the two systems links your Miter account to Coast so team member records begin syncing automatically going forward. Once connected, existing team members in Miter sync into Coast as people, matched or created using phone number as the identifier, and each lands under a default spending policy and role in Coast. From there, a Coast admin issues cards, sets merchant restrictions and spend limits, and assigns cards to individuals or vehicles based on the roster now populated from Miter.