Integrations and Connected Accounts

Most of what you see in VoiceERP arrives from somewhere else. Cortex, Amazon's DSP portal, brings in drivers, vehicles, routes, and scorecards; Netradyne brings in safety events; your payroll provider is where hours and bonuses end up. Here's which pages each connection powers, and where each one is managed.

Settings → Integrations holds the two connections you manage yourself: Netradyne Account, where you enter the login we use to pull safety events, and Payroll Integration, where you switch on the payroll file and pick your provider. Once Netradyne is connected, a third section, Netradyne Alert Coaching, appears below them.

Cortex is deliberately not a form. There is no username, password, or Connect button for it anywhere in the app — we set it up for your company, and you steer it with the switches on the pages it feeds.

When it is live, Viki puts a pale blue note atop four pages. Settings → Drivers reads "Hey! I'm connected to Cortex and will periodically pull your driver data automatically"; Fleet Management says the same for fleet data, Rostering for "your driver route info," and Scorecards for "your most recent scorecard." Three of the four add a warning worth taking seriously — changes you make by hand "may be lost or overwritten with data from Cortex" the next time the sync runs.

The same feed sits behind things with no banner at all. Driver statuses move on their own: new hires arrive with the Onboarding status, people who stop working turn Inactive, and anyone on Cortex's Offboarding page is marked Offboarded. Qualifications and roles on a driver's profile are read-only for the same reason, and the Cortex forecast that schedule generation plans against comes from here too.

Two switches are yours. On the Rostering page, the gear opens Daily Ops Settings, whose Rostering tab carries Sync Routes with Cortex — "Automatically sync driver routes and schedules with Cortex." With it off, that page's banner changes to "You can enable connection to Cortex in the rostering settings." On Settings → Drivers, Sync onboarding associates creates accounts for associates on Cortex's Onboarding tab so you can schedule them before their start date, and a second switch decides whether they can sign into the driver app before day one. For a single record you want to hold by hand, Edit Driver has a Disable Cortex auto-sync for this driver checkbox.

The sync runs on its own throughout the day, and a couple of pages narrate it while data is on its way: schedule generation shows "No route demand has synced from Cortex for this week yet" until the week's routes arrive, the end-of-day report lists "Still syncing: Cortex route data" while a day is finishing up, and the Scorecards page tells you plainly whether you're current — "Your scorecards are up to date." or "We're missing your scorecards for the following week(s)." If something looks out of date beyond those, reach out to VoiceERP support.

Each has a manual fallback: a scorecard PDF uploads from its week's row, a day's roster builds from a CSV or a Cortex schedule export, and drivers upload from Settings → Drivers with the CSV Type dropdown set to Netradyne, Payroll, or VoiceERP CSV Template.

Netradyne is your camera system, and the account you enter under Settings → Integrations is what lets us pull safety alerts in and hand them to Viki for coaching; the full setup has its own article. If someone rotates that password in Netradyne, update it here so the alert sync keeps flowing. If alerts ever seem to dry up unexpectedly, re-entering the account here is the first thing to try — and VoiceERP support can confirm the connection from our side.

The Payroll Integration section turns on a payroll file you can import straight into ADP or Paycom, and the Payroll Provider you pick there decides whether week rows on the Scorecards page offer an ADP Timecard or Paycom Timecard upload; payroll has its own article.

Most "the integration isn't working" reports turn out to be a matching problem. Data arrives under a name or ID that does not line up with anyone on your roster and lands on a Match Drivers screen — one exists for Netradyne alerts, timecards, DVIC reports, and the other weekly files. Admin Tasks is the other half: Driver Name Unmatched and Missing Payroll ID wait there on a person, and until someone clears them the work behind them is frozen. Transporter ID is what most matching keys off, so a driver created without one is the usual culprit.

Start on the page itself and read its alerts, then check Admin Tasks for a backlog. Use the manual upload to keep the day moving. If none of that explains it, Settings → Other has a Customer Support section with our email and phone number.