No API? The mapped file still lands in ADP, on schedule.
When API access is not available, Onboarded builds the file ADP's flat-file import expects, translates the values to ADP's codes, and delivers it over SFTP on a schedule.
At a glance
Why connect it through Onboarded
The export nobody wants to own.
Without an API, the handoff to payroll is a person exporting a file, fixing the column order, translating a few values by hand, and uploading it before a deadline. It works until the week they are out, or until the format changes and nobody notices until the import fails.
No manual export step
Onboarded generates the file and delivers it on schedule. Nobody is reformatting a spreadsheet before a payroll cutoff.
Values arrive in ADP's codes
Onboarding values are translated to the codes ADP expects, with a defined fallback for anything unmapped.
Change a mapping without breaking the file
Mappings are versioned, so a field can be updated without breaking the format already running in production.
Reduction in manual data entry. That is what happens when the handoff between onboarding and the systems downstream stops being a person.
Integration features
Configured by admins, not by an engineering ticket
Every output field, its source, and its format are configured inside Onboarded. Changing what goes in the file does not require a build.
No-code field mapping
Every output field, its source, and its format are configured within the platform by an admin.
Value translation
Onboarding values map to the codes ADP expects, with a defined fallback for anything unmapped.
Versioned mappings
A mapping can be updated without breaking the file format already in production.
Inside Onboarded
The file format is a screen, not a script.
Output columns, their sources, their formats, and the value translations all sit in one configuration screen. Versioning means you can prepare the next mapping while the current one keeps running.
Field coverage
Coverage is defined per customer
There is no fixed field list here, and that is the point of the flat-file route.
Whatever the import accepts
What goes in the file is whatever ADP's flat-file import accepts, mapped to your sources during setup.
Because mapping is configuration rather than code, adding a field later is an admin change, not a project. The versioning is what makes that safe: the format already running in production keeps working while the new version is prepared.
Beyond this integration
One connection, not the whole story.
Onboarded is the onboarding and compliance engine for high-volume and complex hiring, and ADP is one of 50+ native integrations. Other tools store the worker record. Onboarded runs the work across the systems you already use.
We do not replace payroll, recruiting, benefits, identity verification, or background checks. We make them work as one, with two-way sync rather than a one-way export.