Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

ADP Workforce Now Pay Distribution Amounts

Austin Schwinn User

Connector name: ADP Workforce Now

Table name: Worker-Pay-Distribution

Column to add: distributionAmount.amountValue

API documentation link: https://developers.adp.com/apis/api-explorer/hcm-offrg-wfn/hcm-offrg-wfn-payroll-pay-distributions-v2-pay-distributions?operation=GET%2Fpayroll%2Fv2%2Fworkers%2F%7Baoid%7D%2Fpay-distributions#swagger

 

 

Additional details: The ADP Workforce Now Connector has the Worker-Pay-Distribution object in the connector, however it is missing crucial fields. The most important is the distribution amount field. In its current state, the connector can only return qualitative data but nothing quantitative. The connector returns that pay distributions have happened, but not the size of the distributions. This significantly reduces the usefulness of this connector object. Including the distribution amount would greatly increase the ability to use this connector object for reporting and decision making.

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Fivetran Fivetranner

    What the connector provides today

    The ADP Workforce Now connector already syncs ADP's pay-distributions endpoint (/payroll/v2/workers/{aoid}/pay-distributions) into two tables: WORKER_PAY_DISTRIBUTION and WORKER_PAY_DISTRIBUTION_INSTRUCTIONS (child tables of WORKER, added November 2025). These tables contain the setup/configuration side of pay distributions — deposit account details, payment method types, deposit order, and instruction references.

    The gap

    These tables do not include any quantitative amount fields. Specifically, the distributionAmount.amountValue field — which ADP's API returns and represents the configured dollar amount or percentage for each distribution — is not synced. As a result, customers can see that a worker has pay distributions configured, but not how much goes to each. This limits the table's usefulness for payroll reconciliation and reporting.

    What is being requested

    Add the distributionAmount fields (amount value and type) from ADP's Pay Distributions v2 API to the existing WORKER_PAY_DISTRIBUTION table. This is a new-column enhancement to an existing table — no new endpoint or table is required, since the connector already calls this API.

    Questions to confirm with the Interworks Team:

    1. Are the configured distribution amounts (what's set up in ADP's Pay Profile) what you need — or do you need the actual per-paycheck deposit amounts? These are different: configured amounts live in the pay-distributions API, while actual per-check amounts live in ADP's Pay Statements / Payroll Outputs APIs, which are a separate (already tracked) request.

    2. Are there any other fields missing from WORKER_PAY_DISTRIBUTION / WORKER_PAY_DISTRIBUTION_INSTRUCTIONS beyond the amount that you need?

    3. If a re-sync of the WORKER table is required to backfill the new columns, is that acceptable?

  • Austin Schwinn User
    • Edited
    Hello,
     
    Thank you for your follow up questions, below are my responses:
     
    1. Your explanation was very helpful and clarified some things for me. 
       
      What we actually need is per-paycheck earnings detail from ADP's Pay Statements / Payroll Outputs APIs. Specifically, the earnings lines for each pay statement (earning code, hours, rate, and amount), so we can separate regular pay from overtime. We don't use ADP timecards, so the existing time card tables don't cover this for us.
       
      Can you confirm that, as you understand it, the Pay Statements / Payroll Outputs request would cover this? Our requirement is:
       
      - Regular vs. overtime pay, with both dollar amounts and hours, for each employee paycheck
       

    2. No longer needed, I now believe we need the pay statement endpoint.

    3. Yes, that is acceptable

     

    Below are links to ADP Documentation for the Pay Statements Endpoints, in case these are helpful for the development efforts for that feature request:
     
     
     
     
    I hope these are helpful!

    Last note: I believe this feature request actually covers what we need