Matching Imported Data to Your Drivers

Almost everything useful in VoiceERP arrives from somewhere else: scorecards and DVIC reports from Amazon, safety alerts from Netradyne, timecards from ADP or Paycom, roster files, payroll exports. Each identifies drivers in its own way. Matching is where those outside names get pinned to the right driver record, so the alert, the hours and the score all land on the same person.

Each source has its own identifier, and the app uses it when it can: Amazon data keys off the transporter ID, payroll files off the payroll ID, Netradyne off its own driver ID. Cortex and scorecards only ever match on the transporter ID, which is why a missing or mistyped one is the first thing to check when Amazon data won't land. Everything else falls back to names, and names vary. "Robert A. Smith Jr." on a timecard, "Bob Smith" in Netradyne and "Roberto Smith" on the roster are one driver. The matching screens settle that once, and remember it.

Whatever the source, the screen is the same shape: the name from the file on the left, a driver picker in the middle, a status chip on the right. The app fills in what it can before you arrive — first by ID, then by exact name (ignoring case, spacing and accents), then by aliases already saved on your drivers. If every row matches on its own, most uploads skip the screen entirely.

The chips tell you how much to trust each row. Exact match means the name is identical to a driver in the system. Partial match means it lined up after dropping a middle name or a suffix like Jr. Suggested match is a fuzzy guess — check it before submitting. Alias match means it matched a name you saved earlier. Override warns that your pick already has a value from that source, which this will replace. A row left blank shows Employee excluded.

Two guardrails matter. Each driver can be used once — matching two file rows to the same person raises "One or more drivers is matched multiple times" and blocks submission. And if the person isn't in VoiceERP yet, the Register Driver panel on the right adds them without losing your place. Cancel Matching discards the work; Submit matches and continue saves it.

When Netradyne sends an alert for a name nobody recognizes, the Netradyne page shows a red banner — a driver exists in Netradyne but not in our system, and won't be notified of their alerts until you match them — with a Match Drivers button. The same alerts queue as Driver Name Unmatched tasks under Viki → Admin Tasks, where Match Driver opens the Match Netradyne Names page: every outstanding Netradyne name beside a driver picker, with a count of names remaining. Pick the right people and press Submit Matches. The Netradyne name is saved as an alias, the waiting alerts attach to the driver, and the tasks close. From then on Netradyne's own ID is stored on that driver, so later alerts match on the ID rather than the spelling.

Match Payroll ID, also reached from Admin Tasks, works the other way around. It lists your active drivers who have no payroll ID beside the unmatched people from your payroll provider, each shown as "Name (ID)". Pair them up and press Submit Matches: the driver's payroll ID is set and the related admin task closes. Rows move from "Not matched" to "Ready to save" to "Matched" as you go.

Timecard uploads match by name instead. If a name in an ADP or Paycom timecard doesn't line up, you get the matching screen — worth finishing, because as it warns, an unmatched employee's timecard is not stored at all.

CDF DPMO, DVIC reports, negative customer feedback and roster files all use the same flow: names in the file that aren't in your past scorecards need pairing. If a driver started this week, upload your scorecard before the other file, or register them from the panel on the matching screen.

Settings → Drivers has two more under Upload Drivers from CSV File: a Netradyne name list and a payroll export. The payroll file needs first name, last name, payroll ID and hourly rate columns, and writes payroll ID, hourly rate and phone number onto whoever you match it to.

Every manual match you submit is saved as an alias on that driver — and for the two Settings uploads, partial and suggested matches are saved too. That's the whole point: next time the file arrives, the name matches itself.

You can also manage aliases directly. In Settings → Drivers the grid carries a Matching Aliases column, and the pencil icon on a row opens Edit Driver, where Add Matching Alias adds another spelling and each entry can be edited or removed. Aliases must be unique across your drivers, so the form tells you if a name is already claimed. That's where to go when a bad match keeps repeating.

The rest is prevention. Upload your scorecard first — it creates records for transporter IDs it doesn't recognize, which is why those drivers open a Verify Driver Details dialog until someone checks them. Keep transporter IDs correct on new hires, and clear the Admin Tasks queue regularly.