ERP Commission Bridge
ERP Commission BridgePayroll-Ready Commission File Formats for ADP and Workday

Payroll-Ready Commission File Formats for ADP and Workday

Map commission data to ADP and Workday's exact field requirements before payroll runs.

· 9 min read

Payroll-ready commission files for ADP and Workday require more than a valid export. They need correct calculations, exact field mappings, and an integration that the environment supports to deliver them. The controlling principle is to build commission output around the receiving platform’s requirements before the payroll run.

Why commission data creates a distinct payroll file problem

Commission calculations live upstream of payroll, where deal events and plan rules determine what each employee earns. Payroll systems process recorded artifacts in scheduled batches. Commission data must therefore take the form of a structured external input before payroll can use it. A standard wage or time export does not resolve that difference because it does not establish how commission calculations become payable earnings.

The underlying records also span several systems, including HRIS, payroll, CRM, and accounting. To move data across those systems, each entry must refer to the same employee, earning, amount, and period in all of them. The export is therefore a compensation transfer. If its structure does not match what ADP or Workday expects at ingestion, the payroll run can fail or process errors silently.

How ADP Workforce Now receives commission data as a payroll input

ADP Workforce Now requires commission earnings to be mapped to employee identifiers and specific earnings codes before upload. The employee identifier must match ADP’s internal record exactly, including the ADP File Number used by the integration. A mismatch between that number and the commission platform’s employee ID is a common rejection cause. Correct amounts cannot compensate for a record that does not identify the intended employee.

Earnings codes tell payroll how to handle each part of the commission. Base commission, an accelerator, a SPIF, and a clawback need distinct mappings. Incorrect mappings can cause rejected or miscalculated commission payroll runs. The company code must also identify the correct legal entity, while the pay period dates must place the earnings in the intended run. Together, these fields define what is being paid, to whom, and when.

Department codes show where an employee sits in the organization so that the correct wage or commission rate applies. Where rates or plan tiers depend on role or organizational unit, an incorrect department code can attribute earnings to the wrong context. When hours and wages travel with commission amounts in mixed exports, split-by-role must be explicitly enabled. Without it, the integration cannot identify which wage to apply, and no wages will export.

How Workday receives commission data, and why PECI is the current standard for outbound payroll feeds

Workday needs a clear distinction between commission data coming in and payroll feeds going out. Its integration architecture supports SOAP and REST APIs, Reports-as-a-Service (RaaS) bulk extracts, and file-based SFTP delivery. RaaS can provide extracts in CSV, JSON, XML, GData, or RSS, but extraction and ingestion serve different roles in the workflow. However commission data arrives, it must match the fields that receive it. Workday’s official SOAP API uses Earnings_Data, so a normalized structure from another integration layer is not itself the Workday specification.

Workday’s semi-annual R1 and R2 releases can introduce schema changes and deprecate fields, breaking integrations that depend on them. Standard reports create more exposure to this disruption than custom RaaS reports. Workday recommends custom RaaS reports to reduce that risk.

Outbound payroll integration has a different choice of framework. PICOF (Payroll Integration Common Output File) is considered end-of-life, while PECI (Payroll Effective Change Interface) is the recommended approach for new outbound payroll integrations. PECI sends every relevant change with its effective date, so there is less work to reconcile changes between pay periods. For commissions, that allows retroactive adjustments and clawbacks to retain their effective dates. PECI belongs on the outbound side of the design, and the inbound commission schema requires its own definition.

Workday 2026R1 adds governance changes to the inbound templates Import External Payslips, Import External Payroll Documents, and Import External Payroll Results. Standardized payroll vendor identification improves reporting consistency and audit traceability across those integrations. Workday 2026R1 also further enhances the Data Changes on Demand REST API for on-demand requests for payroll interface pay groups, removing the need for scheduled runs or file-based outputs in that workflow. ADP’s Workday compliance integration illustrates the importance of getting the earlier steps right. ADP’s SmartConnect polls Workday after payroll settlement, so commission data must already be correctly positioned in the Workday record before that downstream handoff.

What hybrid integration reality looks like across ADP and Workday environments

Payroll providers may lack fully open APIs, leaving an integration to combine API-based extraction with SFTP file drops. Workday environments can use different combinations of APIs, RaaS extracts, and SFTP depending on tenant configuration and licensed modules. An available API therefore does not establish that a particular commission workflow can use it. Finance must audit the actual tenant configuration rather than design around the cleanest theoretical route.

That audit determines what the commission platform must produce and how it must deliver it. Depending on the integration’s role, the required output may be structured CSV, PECI-compatible XML, or an API payload. Both the format and the transport must fit what the destination needs, without Finance having to reformat the data by hand. A workflow that still requires someone to export data and reshape it has retained the spreadsheet problem inside another tool. The platform must fit the environment as it is, including any need to use file-based and API-based paths together.

How plan design determines whether the commission file is ever correct at the source

A valid file can carry an invalid payout without triggering a format rejection. This makes ambiguous plan logic more difficult to detect than a missing identifier or an unsupported field. If an accelerator, SPIF, or clawback rule allows more than one interpretation, the platform may calculate one result while Finance expects another. The export then faithfully carries the disputed number into payroll. Accuracy must begin with a plan that defines the calculation.

Multi-role deals expose this problem at the credit-allocation stage. Without clear rules for splitting credit across an SDR, AE, and SE, the resulting line items express only one interpretation of the deal. Disputes then create retroactive adjustments after the original payout has entered the payroll process. Timing rules create a related problem when a plan pays at booking, invoicing, or cash collection without aligning that trigger to the payroll period. Those entries must be staged by hand or held for later, which can cause more errors when reconciling at period-end.

Plans that have not been run against historical data leave payout outliers and edge cases to emerge in production, where corrections may follow submission. Plan simplicity matters for the same reason. A plan that a rep cannot explain in straightforward terms is more likely to leave calculation boundaries unclear.

How structured commission software eliminates the manual steps that corrupt payroll files

Manual commission workflows separate calculation from submission through exports, formula application, field mapping, and format conversion. Each step creates an opportunity for the payroll file to diverge from the intended calculation. Spreadsheet formula drift is a primary example because a user can overwrite a formula cell without warning. That change can propagate incorrect results across a column of rep records while leaving the final file structurally valid. Structured commission software makes payroll-ready output a direct result of the calculation workflow.

When deal data is exported by hand at set times, there is a latency gap between deal activity and the data used to calculate commissions. Pulling deal data from the CRM as the source of truth closes that gap. Clawback automation shows how the same architecture handles a correction without manual file editing. When a CRM event triggers a clawback, the platform records the deduction, assigns it to the correct pay period, and includes it in the next payroll file.

The controls around those calculations matter as much as their automation. Shadow accounting occurs when reps maintain separate spreadsheets to check Finance’s figures, with disputes sometimes surfacing only after submission. Those disputes can require retroactive corrections and a resubmitted file. Audit trails and locked pay periods make the submitted calculation defensible through logged approvals and a fixed period record. A spreadsheet version history that may have been overwritten does not provide the same evidence.

Security and compliance requirements that govern commission file transfers to ADP and Workday

Commission files contain compensation figures and employee identifiers, and some integrations also include SSNs or tax IDs. They therefore carry the data handling and breach notification obligations associated with payroll records. The security of the calculation platform is part of the security of the transfer because that platform generates the record sent to payroll.

SOC 2 Type II certification is a baseline requirement for platforms handling this data because it addresses whether controls operate effectively over time. For organizations with European sales reps, GDPR applies independently of SOC 2. A SOC 2 report does not prove GDPR compliance or take the place of its breach notification obligations. Those obligations include notifying supervisory authorities within a strict deadline and notifying affected individuals when risk is high. Workday publishes SOC reports for its services and supports GDPR globally, so it is important to check how the commission platform meets those same security needs.

Access controls must protect this sensitive data with MFA, least-privilege access, and network segmentation. Pay transparency requirements in states including California, New York, and Illinois also give compensation records legal significance through requirements for pay scales, salary ranges, and disclosure of commission-based roles. The commission audit trail consequently serves as more than an operational history. Platform evaluation should address both protection of the file and the evidence behind its contents, rather than treating security as a review after integration design.

A pre-submission checklist for validating a commission file before the payroll run

Field-level validation. Match every employee ID exactly to ADP’s File Number or Workday’s worker identifier, checking for trailing spaces and format differences. Verify that base commission, accelerators, SPIFs, and clawbacks each carry their distinct earnings codes. Confirm the ADP company code identifies the correct legal entity or that the Workday pay group is correctly specified. Check department codes where rates depend on role or territory, and make sure the file’s start and end dates match the payroll period exactly.

Amount-level validation. Check the export line by line against the commission platform’s record of the calculation. Validate attainment against quota records before generating the file so that accelerators and SPIFs apply only to qualifying reps. Check that each clawback matches the original commission payment, belongs to the correct rep, and falls in the period when the deduction is due. Stage retroactive adjustments in the correct period and flag them for Finance review before including them in the live file.

Integration routing validation. Confirm whether the specific tenant accepts API delivery or an SFTP file drop, and match the platform configuration to that route. For Workday outbound payroll feeds, confirm PECI is used, as PICOF is end-of-life. Run ADP’s pre-transmission error checks before submitting the file. In Workday 2026R1 environments, verify standardized payroll vendor identification in the Import External Payroll Results template.

Security and approval validation. Check that the commission platform meets the security requirements for payroll data, including SOC 2 Type II and any GDPR obligations that apply. Check MFA, least-privilege access, and network segmentation for the systems involved. Check that the file being submitted is backed by logged approvals and locked pay periods.

Migration validation. For teams moving from spreadsheets to a commission platform, run at least one full pay period in both systems in parallel. Reconcile the outputs line by line before cutting over and removing the spreadsheet safety net.

More in ERP and CRM Integration