ADP and Workday cost center drift broke general ledger (GL) tie?outs; a rules layer mapped codes and routed exceptions

Overview

A healthcare provider’s Finance team saw persistent payroll?to?general ledger (GL) variances because ADP exports and Workday cost centers were not aligned. Off?cycle runs, retro pay, and outdated worker attributes caused entries to land in suspense, while reconciliations depended on spreadsheets and email. Intelligex built a reconciliation pipeline that standardized payroll data, mapped earning and deduction codes to GL accounts, aligned employee attributes to Workday cost centers, and flagged variances automatically. Exceptions were routed to HR or Finance with audit trails and maker?checker approvals. Variances were addressed at the source, payroll journals posted with fewer corrections, and role?based approvals captured clear accountability—without changing ADP, Workday, or the ERP.

Client Profile

• Industry: Healthcare provider network
• Company size (range): Multi?facility footprint with centralized Finance and distributed HR operations
• Stage: ADP for payroll processing; Workday for HCM and cost centers; GL in Workday Financials (or existing ERP); reconciliations managed through spreadsheets and email
• Department owner: Finance & Accounting (Payroll Accounting and Controllership)
• Other stakeholders: HR Operations, Workforce Management, IT/Integrations, Internal Audit, FP&A, Cost Accounting, Shared Services

The Challenge

Payroll entries rarely landed cleanly in the GL. ADP exports carried earning and deduction codes that were not consistently mapped to accounts; Workday cost centers and worker attributes drifted with org changes; and off?cycle runs introduced timing differences. Retro adjustments posted to current periods without clear ties to original pay periods. When cost centers were inactive or missing, entries defaulted to suspense and were cleared manually. Reconciliations stitched ADP files, HR reports, and GL activity in spreadsheets, and root?cause analysis started over each pay cycle.

Ownership and timing did not line up. HR corrected worker cost centers after payroll cutoffs; Finance updated mapping tables late in the cycle; and IT moved files on varying schedules. Variances appeared as totals that did not match across gross?to?net, employer payroll taxes, benefits, and cash disbursements. Exceptions circulated in email with screenshots rather than with structured reason codes, and approvals for suspense clearings were hard to trace during audits.

Why It Was Happening

Root causes were inconsistent master data and ungoverned reconciliation logic. ADP exports used payroll dimensions and codes that did not map one?to?one with the GL structure. Cost centers and positions in Workday changed without a synchronized crosswalk to payroll elements. Retro and off?cycle runs produced timing differences that were not flagged or summarized. Without a canonical schema and a policy?aware variance engine, the team relied on manual joins and analyst memory to explain breaks and route fixes.

Responsibilities were diffuse. HR owned cost center assignments and worker attributes, Payroll ran the cycle, Finance mapped accounts and posted journals, and Audit reviewed after the fact. No shared workflow tied the data together, enforced mapping rules with effective dating, or routed exceptions to the right owner with evidence.

The Solution

Intelligex implemented a payroll?to?GL reconciliation pipeline with a controlled rules layer and exception workflow. ADP payroll data flowed into a canonical schema that aligned with Workday cost centers and GL accounts. Mapping tables handled earning and deduction codes, employer taxes, and benefits. A variance engine compared payroll totals to journalized amounts and cash activity, flagged breaks with reason codes, and routed exceptions to HR or Finance. Maker?checker approvals captured sign?off on mapping changes and suspense clearings. The approach leveraged ADP developer patterns (ADP Developer Portal) and Workday Financial Management for GL (Workday Financial Management), while keeping the existing pay cycle intact.

• Integrations: ADP payroll exports via API or SFTP; Workday worker, position, and cost center masters; GL journals and actuals from Workday Financials or the existing ERP; notifications to collaboration tools for routed exceptions.
• Canonical payroll schema: Standardized fields for pay group, pay period, employee/position, earning and deduction codes, employer taxes and benefits, work and home cost centers, locations, projects/grants, and cash disbursement references.
• Mapping and crosswalks: Finance?owned mappings from ADP earning/deduction codes to GL accounts; cost center crosswalks between ADP and Workday with effective dating; alias tables for legacy codes.
• Variance engine: Comparisons across gross?to?net, employer taxes/benefits, cost center distributions, retro/off?cycle timing, and cash postings; tolerance and reason codes for rounding and known patterns; retro tie?backs by original pay period.
• Exception routing: Breaks classified and routed to HR (worker attributes, inactive cost centers) or Finance (account mapping, suspense clearing) with evidence bundles; due dates and owners recorded.
• Approvals and governance: Maker?checker for mapping changes and suspense clearings; effective?dated rule updates with review; immutable logs for audits.
• Journals and tie?outs: Generation or validation of summary journals by pay group and entity; tie?out to payroll cash disbursements and payroll tax remittances where applicable.
• Dashboards and audit: Pay?cycle posture, exception aging, mapping changes, and unresolved breaks by entity and cost center; exportable evidence packs with source lines, mappings applied, and approvals.
• Security and privacy: Role?based access; masking for sensitive employee identifiers; full access and change logs.

Implementation

• Discovery: Cataloged pay groups, export formats, and cutoffs; inventoried earning/deduction codes and current mapping tables; reviewed Workday cost center design and worker attribute changes; sampled typical variance patterns and suspense clearings; gathered audit and controller comments.
• Design: Defined the canonical schema and identity keys; authored mapping and crosswalk rules with effective dating; specified variance checks, tolerances, and reason codes; designed exception routing paths and maker?checker roles; planned dashboards and evidence exports.
• Build: Implemented data ingestion from ADP; integrated Workday masters; developed mapping services and the variance engine; built exception queues and approval workflows; wired journal validation and tie?outs; assembled dashboards and notifications.
• Testing/QA: Ran in shadow mode: reconciled recent pay cycles while legacy reconciliations continued; compared breaks and resolutions; tuned mappings, tolerances, and routing; exercised HR and Finance exception paths with real cases.
• Rollout: Enabled exception queues and journal validations for selected entities and pay groups first; retained spreadsheet reconciliations as a controlled fallback; expanded coverage as variances declined and teams trusted routing; activated mandatory maker?checker for mapping edits after training.
• Training/hand?off: Delivered sessions for Payroll Accounting, HR Ops, and Controllers on queues, mappings, approvals, and dashboards; updated SOPs for retro/off?cycle handling and suspense clearance; transferred ownership of mappings, tolerances, and dashboards to Finance Ops under change control.
• Human?in?the?loop review: Established a cadence for rule updates and recurring exception analysis; decisions recorded with rationale and effective dates.

Results

Payroll postings aligned with GL expectations. Variances surfaced within the pay cycle and were routed with reason codes and evidence to the right owner. HR corrected worker cost centers and positions before journals posted, and Finance adjusted mappings under change control rather than via late entries. Retro and off?cycle differences were summarized clearly, and cash tie?outs referenced the same source data.

Close activities became predictable. Suspense usage reduced as cost center and account issues were addressed at the source, and approvals for any required clearings were captured with who, what, and why. Controllers saw pay?cycle posture in dashboards, and Internal Audit pulled consistent evidence packs rather than reconstructing emails. ADP, Workday, and the pay schedule remained unchanged; the addition was a governed reconciliation layer that made ownership and outcomes clear.

What Changed for the Team

• Before: Reconciliations lived in spreadsheets and inboxes. After: A governed queue flagged variances with owners, reason codes, and due dates.
• Before: Cost center fixes landed after journals posted. After: HR corrections were routed during the pay cycle with linkbacks to Workday.
• Before: Mapping edits happened ad hoc. After: Finance managed earning/deduction to GL mappings with effective dating and approvals.
• Before: Retro and off?cycle differences were opaque. After: Variance summaries tied adjustments to original pay periods and cash activity.
• Before: Suspense clearings lacked traceable approvals. After: Maker?checker captured decisions and evidence for audit.
• Before: Controllers asked for status snapshots. After: Dashboards showed pay?cycle posture and exception aging by entity and cost center.

Key Takeaways

• Define a canonical payroll schema; align ADP outputs with Workday cost centers and GL structures.
• Let Finance own mappings under change control; version earning/deduction to account rules with effective dates.
• Route exceptions to the source; HR fixes worker attributes, Finance adjusts mappings, both with evidence.
• Summarize retro and off?cycle timing; tie adjustments back to original periods and cash posts.
• Enforce approvals; maker?checker on mappings and suspense clearings strengthens controls.
• Integrate, don’t replace; keep ADP and Workday and add a governed reconciliation pipeline and dashboards.

FAQ

What tools did this integrate with? Payroll data flowed from ADP via API or SFTP (see the ADP Developer Portal). Worker, position, and cost center masters came from Workday, and GL journals and actuals were read from Workday Financial Management (overview at Workday Financials) or the client’s existing ERP. Notifications and dashboards used the company’s collaboration and BI tools.

How did you handle quality control and governance? Mapping tables and crosswalks lived under Finance change control with effective dating. The variance engine applied documented tolerances and reason codes. Maker?checker enforced approvals on mapping edits and suspense clearings. Every import, mapping change, variance flag, route, and approval was immutably logged with source line references.

How did you roll this out without disruption? The pipeline ran in shadow mode first, reconciling recent pay cycles while the team continued spreadsheet methods. Differences were compared and rules were tuned. Coverage began with selected entities and pay groups, and expanded as accuracy and trust increased. Mandatory approvals for mapping edits were enabled after training.

How were retro and off?cycle runs handled? Retro adjustments were tied to original pay periods in the canonical schema and summarized separately from current?period payroll. Off?cycle runs were identified by pay group and timing, reconciled with cash disbursements, and flagged with reason codes so journals and tie?outs reflected intent clearly.

How did exceptions reach the right owner? Variances were classified at detection. Worker attribute or cost center issues routed to HR with links to the employee and position. Account mapping or suspense issues routed to Finance with the ADP code and proposed GL mapping. Each task carried due dates, comments, and attachments, and status was visible in dashboards.

How were sensitive employee details protected? The pipeline masked personally identifiable information not needed for reconciliation and limited access through role?based permissions. Logs recorded who accessed what and when. Evidence packs included only the fields required for audit and review.