.png)
ADP Global Payroll Integration Guide
Connect ADP Global Payroll with HR, workforce, finance, and operational systems through approved REST APIs, selective event notifications, and orchestrated payroll workflows.
ADP Global Payroll integration options at a glance
ADP Global Payroll is primarily integrated through product- and country-specific REST APIs using JSON representations. These APIs can support worker data, payroll inputs, payroll outputs, pay statements, and organizational information when enabled for the customer’s ADP subscription. ADP also provides event-notification capabilities for selected products and events, while some payroll operations may be asynchronous or cycle-based. Martini can authenticate with OAuth 2.0, consume ADP endpoints, receive supported notifications, map and validate payloads, submit payroll inputs, poll documented status resources, and schedule reconciliation workflows. File exchange and SOAP should be treated as implementation-specific or unconfirmed rather than assumed capabilities.
| Integration point | Supported by ADP Global Payroll? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | ADP provides REST and JSON-oriented APIs for supported worker, payroll input, payroll output, pay statement, and organizational use cases. Availability depends on product, country, tenant, and approved API subscriptions. | Martini can consume REST endpoints, supply parameters and authenticated payloads, transform JSON, validate responses, and route results through workflows. |
| Webhooks / outbound callbacks | Limited | ADP provides event-notification capabilities for selected products and events, but coverage should not be generalized to every Global Payroll object or event. | Martini can expose an API endpoint or use a workflow trigger to receive supported notifications, deduplicate them, and retrieve the authoritative ADP resource. |
| Bulk / async / batch APIs | Limited | Payroll operations may be asynchronous or organized around payroll cycles and processing states. Bulk and status operations depend on the specific ADP API. | Martini can submit a request, persist its identifier, poll a documented status endpoint, and publish completed results with bounded retries. |
| Authentication | Yes | ADP developer APIs generally use OAuth 2.0 with application credentials, access tokens, scopes or permissions, tenant context, and product-specific approval. | Martini can store credentials and tokens in environment configuration or managed secrets and use them in authenticated workflows over HTTPS. |
| File / attachment APIs | Not confirmed | File-based payroll exchange may exist in selected ADP products or customer implementations, but a universal Global Payroll file or attachment API was not confirmed. | Martini can process files when an explicitly documented ADP exchange is available, but the mechanism must be validated for the customer deployment. |
| SOAP APIs | Not confirmed | Older ADP products may expose legacy interfaces, but a current product-specific SOAP interface for ADP Global Payroll was not confirmed. | Martini can consume SOAP services when an applicable documented endpoint is confirmed, but new designs should use the enabled ADP REST APIs. |
| Database access | No | Direct access to ADP Global Payroll internal databases is not an expected standard customer integration method. | Martini should use supported ADP APIs, event notifications, or explicitly documented exchange mechanisms instead of direct database access. |
| SDKs | Not confirmed | ADP provides developer resources and API documentation, but an official SDK for a particular Global Payroll API was not confirmed. | Martini does not require an ADP-specific SDK to consume documented HTTP APIs and can create reusable API workflows from the definitions available to the customer. |
How ADP Global Payroll exposes data and business events
ADP REST APIs
ADP exposes REST and JSON-oriented APIs for supported HCM and payroll use cases, including worker data, payroll inputs, payroll outputs, pay statements, and organizational information. The available resources depend on product subscription, country, tenant configuration, and API approval.
Martini implementation pattern
Martini implementation pattern: a workflow obtains or uses an OAuth 2.0 token, calls the relevant ADP endpoint, follows documented pagination, validates the response, maps the ADP representation to a canonical model, and writes or submits the result to the target system.
Implementation sequence
ADP Event Notifications
ADP supports event-notification capabilities for selected products and events. These notifications are selective and may identify a changed resource without containing its complete authoritative representation.
Martini implementation pattern
Martini implementation pattern: expose a controlled endpoint or workflow trigger, validate and deduplicate the notification, retrieve the current ADP resource through REST, and then process the authoritative data rather than relying solely on the event payload.
Implementation sequence
ADP Asynchronous Payroll Processing
Payroll processing may be asynchronous or organized around payroll cycles and processing states. Exact submission, bulk, and status operations vary by the enabled API.
Martini implementation pattern
Martini implementation pattern: submit a validated payroll request, persist the ADP request identifier, poll only documented status resources with bounded backoff, and publish the completed result or route a terminal failure for review.
Implementation sequence
ADP Scheduled Reconciliation
Scheduled reconciliation remains important because event coverage, delivery, payload detail, and retry behavior may vary by API and tenant. It can compare worker, payroll, or result counts and identify missed events.
Martini implementation pattern
Martini implementation pattern: schedule a workflow for the relevant payroll cadence, retrieve changed or completed resources using checkpoints, compare key identifiers or totals with the downstream system, and raise actionable exceptions.
Implementation sequence
Common ADP Global Payroll integration patterns
Pattern 1: Synchronize workers from an HR system
When to use this pattern
Use this pattern when Workday, SAP SuccessFactors, Oracle HCM Cloud, or another HR platform is the source for worker lifecycle and organizational changes that must be represented in ADP Global Payroll.
Integration direction
Example Mapping
| ADP Global Payroll Field | Canonical Field | Target Field |
|---|---|---|
| workerId | worker.externalId | Worker identifier |
| employmentStatus | worker.status | Employment status |
| effectiveDate | assignment.effectiveDate | Effective date |
| department | organization.department | Department |
Martini implementation pattern
Martini retrieves changed workers, normalizes country and payroll-group variations, validates effective dates and required identifiers, applies create-versus-update rules, and submits the supported ADP requests. Stable source keys and stored outcomes prevent duplicate changes during retries; rejected records are routed for correction.
Martini capabilities used
- API consumption
- workflows
- data mapping
- business rules
- secrets management
- error handling
Pattern 2: Submit time and earnings as payroll inputs
When to use this pattern
Use this pattern when an approved time, workforce-management, or compensation system must send payroll-period inputs to ADP before a payroll cutoff.
Integration direction
Example Mapping
| ADP Global Payroll Field | Canonical Field | Target Field |
|---|---|---|
| employeeId | worker.externalId | Worker identifier |
| payPeriod | payrollPeriod.id | Payroll period |
| hours | payrollInput.quantity | Hours or quantity |
| earningCode | payrollInput.code | Earning code |
Martini implementation pattern
Martini retrieves approved source transactions, validates payroll period, worker, code, currency, and cutoff rules, transforms them into the enabled ADP payroll-input model, and submits the request. It persists transaction keys and ADP request identifiers, retries only safe transient failures, and routes validation or rejection responses to operations.
Martini capabilities used
- scheduled workflows
- API consumption
- data transformation
- validation
- idempotency controls
- error handling
Pattern 3: Deliver payroll outputs to finance
When to use this pattern
Use this pattern when completed ADP payroll results must become journal-ready summaries, cost allocations, or employer-cost data in a finance platform such as NetSuite.
Integration direction
Example Mapping
| ADP Global Payroll Field | Canonical Field | Target Field |
|---|---|---|
| payrollPeriodId | payroll.periodId | Accounting period |
| earningsTotal | payroll.earnings | Earnings amount |
| deductionsTotal | payroll.deductions | Deductions amount |
| costCenter | allocation.costCenter | Department or class |
Martini implementation pattern
Martini detects or schedules retrieval of completed payroll output, waits for documented processing states, maps amounts and dimensions to the finance model, and applies balancing and period controls before writing to NetSuite. Payroll-period keys and posting status prevent duplicate journal-ready results.
Martini capabilities used
- workflow orchestration
- API consumption
- mapping
- business rules
- scheduled processing
- monitoring
Pattern 4: Process ADP events with reconciliation
When to use this pattern
Use this pattern when selected ADP event notifications should provide near-real-time responsiveness while scheduled reconciliation protects against missed or incomplete event delivery.
Integration direction
Example Mapping
| ADP Global Payroll Field | Canonical Field | Target Field |
|---|---|---|
| eventId | event.correlationId | Correlation ID |
| resourceId | source.objectId | ADP resource reference |
| processingStatus | payroll.status | Case status |
| errorDetail | exception.message | Case description |
Martini implementation pattern
Martini receives a supported notification, validates and deduplicates it, retrieves the current ADP resource, and updates the target application. A separate scheduled workflow compares identifiers or totals and creates an operational exception when an event appears to have been missed. Sensitive payroll values are minimized or masked in cases and logs.
Martini capabilities used
- API exposure
- webhook consumption
- workflow orchestration
- scheduled reconciliation
- data mapping
- error handling
Applications commonly integrated with ADP Global Payroll
ADP Global Payroll can be integrated with named HR, workforce, finance, service-management, and identity products when the customer has the relevant product subscriptions and API access. The exact objects, countries, payroll groups, and directions should be confirmed during solution design.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Workday | Synchronize worker, organizational, and employment data between an HR system of record and payroll operations. | Workday → Martini → ADP Global Payroll | Martini consumes worker and employment changes from Workday, applies effective-date and country-specific mappings, validates required fields, and submits the approved ADP API requests with idempotency controls. |
| SAP SuccessFactors | Exchange employee master data, employment changes, and organizational attributes with payroll processing. | SAP SuccessFactors → Martini → ADP Global Payroll | A scheduled or event-driven Martini workflow retrieves changed employees, maps organizational and employment attributes to the enabled ADP resources, routes validation failures for correction, and records request outcomes. |
| Oracle HCM Cloud | Synchronize worker and assignment data and return payroll results or costing information. | Oracle HCM Cloud → Martini → ADP Global Payroll | Martini orchestrates outbound worker synchronization and inbound payroll-result retrieval, separating effective dates from processing dates and transforming ADP output into Oracle HCM-compatible structures. |
| UKG Pro | Transfer employee, workforce, time, or payroll-related data where UKG Pro is used for HR or workforce management. | UKG Pro → Martini → ADP Global Payroll | Martini retrieves approved workforce or time data, applies payroll-group rules and cutoff checks, submits supported payroll inputs, and tracks rejected or asynchronous transactions. |
| ServiceNow | Create HR cases or operational tasks when payroll exceptions, worker events, or processing failures require action. | ADP Global Payroll → Martini → ServiceNow | Martini receives or retrieves ADP exceptions and processing outcomes, masks sensitive payroll values, applies routing rules, and creates or updates ServiceNow cases with correlation identifiers. |
| Salesforce | Synchronize employee-related business data, support cases, or partner and workforce information where Salesforce is an operational platform. | ADP Global Payroll → Martini → Salesforce | Martini maps selected ADP worker or status data to Salesforce objects, applies field-level filtering, and uses retries and duplicate detection for updates. |
| NetSuite | Send payroll summaries, journal-ready values, cost-center allocations, or employer-cost information to finance. | ADP Global Payroll → Martini → NetSuite | Martini retrieves completed payroll outputs, aggregates or transforms earnings, deductions, taxes, and cost allocations, then writes finance-ready data to NetSuite with payroll-period controls. |
| Microsoft Entra ID | Provision, update, or deprovision workforce identities based on worker lifecycle changes. | ADP Global Payroll → Martini → Microsoft Entra ID | Martini retrieves authorized worker lifecycle changes, applies identity policy and effective-date rules, and invokes the target identity APIs while recording correlation and retry state. |
How to build a ADP Global Payroll integration in Martini
Objective
Establish approved access to the customer’s ADP Global Payroll APIs and confirm the product, country, tenant, payroll groups, scopes, and environments in scope.
Instructions in Martini
- Register or obtain the approved ADP developer application and customer authorization
- Configure OAuth 2.0 credentials, scopes, endpoints, and tenant context
- Store secrets and tokens in Martini environment configuration or managed secrets
- Confirm test and production access before processing payroll data
Objective
Select an event-driven, scheduled, or API-led entry point based on the ADP capability and payroll operating calendar.
Instructions in Martini
- Use a workflow trigger for supported ADP event notifications
- Use a scheduler for reconciliation, payroll-cycle processing, or polling
- Use an API endpoint when another application initiates the transaction
- Define checkpoints and correlation identifiers for each trigger
Objective
Obtain the authoritative ADP resource or source transaction while preserving pagination, request context, and processing identifiers.
Instructions in Martini
- Receive and validate supported event notifications
- Call the relevant ADP REST resource for complete data
- Follow documented pagination and continuation parameters
- Persist request identifiers and last successful checkpoints
Objective
Coordinate calls, asynchronous status checks, transformations, target writes, and exception paths in a maintainable Martini workflow.
Instructions in Martini
- Separate validation, submission, polling, and result handling stages
- Apply bounded backoff to transient failures and asynchronous polling
- Route terminal business errors to an operational correction path
- Keep country- and payroll-group-specific rules explicit
Objective
Transform ADP JSON and source-system data into a canonical model and the target application’s schema without losing payroll semantics.
Instructions in Martini
- Map actual ADP objects such as Workers and Payroll inputs
- Preserve effective dates, payroll periods, currencies, codes, and identifiers
- Validate required fields, country-specific attributes, and payroll cutoffs
- Mask sensitive values in diagnostics and operational messages
Objective
Submit approved payroll inputs or deliver worker, payroll-output, and reconciliation results to downstream applications.
Instructions in Martini
- Apply create-versus-update and duplicate-prevention rules
- Write only after validation and required business checks succeed
- Record target identifiers, ADP request identifiers, and processing status
- Use period and source-transaction keys for repeatable writes
Common ADP Global Payroll data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Workers | Synchronize employee and worker demographic, employment, organizational, and work-assignment information. | Workday, SAP SuccessFactors, Oracle HCM Cloud, Microsoft Entra ID | Martini retrieves or receives changes, applies effective-date and country-specific mappings, validates required fields, and uses stable worker identifiers for idempotency. |
| Payroll inputs | Submit earnings, deductions, adjustments, time-related values, and other payroll-period inputs. | ADP Global Payroll, UKG Pro, workforce-management and time systems | Martini validates payroll-group rules and cutoffs, transforms source transactions, submits supported API payloads, and stores request identifiers and outcomes. |
| Payroll outputs | Distribute calculated payroll results, summaries, earnings, deductions, taxes, employer costs, and allocations. | NetSuite, Oracle HCM Cloud, reporting platforms, finance applications | Martini retrieves completed results, handles asynchronous states where documented, transforms totals and dimensions, and prevents duplicate posting by payroll period. |
| Pay statements | Provide worker-level pay statement and pay-result information where enabled by the relevant ADP product. | Employee portals, HR applications, case-management systems | Martini retrieves authorized data, applies privacy filtering and masking, and delivers only the fields required by the target process. |
| Organizational units | Represent employing entities, business units, departments, locations, and related organizational structures. | Workday, SAP SuccessFactors, Oracle HCM Cloud, finance systems | Martini synchronizes reference data with pagination and checkpoints, then applies lookup and crosswalk rules for downstream mappings. |
| Worker employment or work assignments | Carry employment status, position, job, location, and effective-dated assignment information. | HR platforms, Microsoft Entra ID, ServiceNow | Martini distinguishes effective dates from transaction dates, routes lifecycle changes, and records source versions or correlation keys. |
Authentication and security considerations
OAuth 2.0 and application approval
ADP developer APIs generally use OAuth 2.0 with a client identity, secret, access token, scopes or permissions, tenant context, and product-specific approval. The exact flow and any certificate or transport requirements must be confirmed for the subscribed Global Payroll APIs.
Protect payroll information
- Store ADP credentials and tokens in Martini environment configuration or managed secrets.
- Use HTTPS/TLS and least-privilege API permissions.
- Restrict access to Martini APIs, workflows, and operational logs.
- Mask personal, banking, tax, and payroll values in diagnostics.
- Apply retention and environment-separation controls for test and production data.
Operational considerations for ADP Global Payroll integrations
API limits and pagination
Do not assume unlimited calls or a universal ADP rate limit. Use controlled concurrency, respect Retry-After when supplied, apply exponential backoff, and follow documented pagination or continuation parameters while preserving checkpoints.
Payroll reliability
Payroll submissions require idempotency, cutoff awareness, and careful handling of asynchronous states. Persist source transaction keys, ADP request identifiers, event IDs, and outcomes. Retry only safe transient failures and avoid resubmitting an unknown transaction without checking its status.
Data and schema variation
Worker, employment, and payroll attributes vary by country, legal entity, currency, tax regime, payroll calendar, and API package. Keep mappings explicit and monitor ADP versioning or schema notices. Test validation, rejection, correction, and reconciliation paths before production payroll runs.
Why use Martini instead of scripts or point-to-point integrations?
Centralized orchestration
Martini coordinates ADP API calls, source-system retrieval, transformations, business rules, target writes, asynchronous polling, and reconciliation in maintainable workflows rather than distributing logic across scripts.
Reusable integration assets
Teams can separate credentials, mappings, validation, country-specific rules, and error paths from core orchestration. This supports repeatable patterns across worker synchronization, payroll inputs, payroll outputs, and event-driven processing.
Operational control
Martini provides a place to implement idempotency, checkpoints, bounded retries, sensitive-data handling, monitoring, and exception routing. It can also expose controlled APIs for inbound requests and supported ADP notifications.
Frequently asked questions
ADP Global Payroll is primarily integrated through approved, product- and country-specific REST APIs using OAuth 2.0 and JSON. These APIs can support worker data, payroll inputs, payroll outputs, pay statements, and organizational information. Selected ADP products and events may also provide event notifications, while some payroll operations are asynchronous or cycle-based. File exchange and legacy interfaces must be confirmed for the specific customer deployment.
Yes. Martini can consume the customer’s approved ADP REST APIs, use OAuth 2.0 credentials, receive supported ADP event notifications through an exposed endpoint or workflow trigger, orchestrate asynchronous processing, and map ADP data to HR, finance, workforce, service-management, or identity applications.
No dedicated ADP Global Payroll connector is required. Martini can integrate using ADP’s confirmed native mechanisms, primarily its approved REST APIs and, where enabled, selective event notifications. Martini can provide the workflow orchestration, authentication configuration, mapping, validation, retry, and reconciliation logic around those interfaces.
Lonti does not charge an additional per-connector or per-vendor fee to integrate ADP Global Payroll. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from ADP, cloud infrastructure, or other third-party systems based on subscription, usage, and deployment model.
Use the approved ADP REST APIs for current integrations, selecting resources that match the customer’s product, country, tenant, and payroll groups. Use event notifications where the required event is supported, and combine them with authoritative resource retrieval and scheduled reconciliation. Do not assume GraphQL, a universal SOAP interface, bulk operations, or a universal file API.
ADP provides event-notification capabilities for selected products and events, but they are not a universal stream for every Global Payroll object. Martini can receive a supported notification, deduplicate it, retrieve the current ADP resource, and process the authoritative representation. Scheduled reconciliation remains advisable for payroll-critical flows.
A Martini workflow can use scheduled or event-driven processing, submit supported payroll inputs, persist the ADP request identifier, and poll documented status resources when processing is asynchronous. Synchronization should preserve payroll periods, effective dates, cutoff times, processing states, and country-specific mappings, with checkpoints for repeatable reconciliation.
Martini can distinguish validation, authentication, throttling, transport, and server errors; retry only transient or documented-safe failures; and route rejected payroll inputs for correction. Stable keys based on worker, payroll period, effective date, input type, and source transaction help prevent duplicates. Request identifiers, outcomes, event IDs, and checkpoints should be retained for audit and recovery.
Related Martini documentation
API Workflows
Workflows
Reliability
Connect ADP Global Payroll with Martini
Use Martini to build secure, maintainable ADP Global Payroll integrations for worker synchronization, payroll inputs, payroll outputs, event handling, and reconciliation.