ADP Workforce Now job costing can send costs to the wrong project even when every employee is paid correctly. That happens when a timecard carries one job code, payroll uses a different cost number, or finance posts the wages to a default department. The paycheck is correct. The project margin is misleading. Teams that want an experienced partner can look at Ignite HCM’s payroll compliance.
ADP Workforce Now job costing depends on a chain of decisions that begins before the first time entry. The business must decide how to identify work, which team maintains the codes, how payroll should distribute earnings, and which amounts accounting should receive. The software can support that process, but available fields and steps depend on the company’s Workforce Now setup and timekeeping products.
This guide covers the configuration choices, documented payroll settings, test cases, and reporting checks. It also separates the labor allocation recorded for payroll from the fuller labor cost a finance team may need for a job. That difference matters when overtime, benefits, and employer taxes affect project profitability.
TL;DR:
ADP Workforce Now job costing starts with a consistent job and cost-code structure. Employees or managers capture hours against the approved work, payroll distributes earnings using the configured cost number or department method, and accounting maps those results to the right project. ADP documents automatic percentage allocation, manual paydata allocation, and temporary cost or department values for supported Workforce Now arrangements. Timekeeping labor charge codes and payroll cost numbers require an agreed mapping. Test divided shifts, overtime, corrections, and general ledger totals before relying on project reports. Exact screens, APIs, and available features depend on the account and product generation.
What Job Costing Tracks in Workforce Now
Job costing assigns labor activity and related expense to a defined piece of work. That could be a construction contract, a maintenance order, a client project, or a production task. Its purpose is to show how much labor was used and, when the accounting rules are applied, how much that work cost. A department allocation answers a different question: which operating unit should carry the expense.
ADP Workforce Now labor allocation can distribute payroll earnings and hours by cost number or department in configurations described in ADP’s payroll documentation. Time collection may add more detail, including jobs or work orders. ADP states that its workforce management tools can track hours against jobs, projects, and cost centers, which supplies useful context before payroll calculates earnings.
Think of 3 layers. Timekeeping records where the work happened. Payroll determines the amount owed and may distribute earnings across configured categories. Accounting decides which general ledger account, job, or cost center receives the expense. Each layer has its own rules. A valid job number on a timecard doesn’t guarantee a job-level journal entry in finance.
ADP payroll job costing often requires a mapping between these layers. For example, a field technician may record 6 hours on Job 410 and 2 hours on Job 415. Payroll could use the submitted time to calculate 8 paid hours. The finance system then needs a rule that posts the right wages to each job instead of the employee’s default department. These figures are an illustration, not an ADP customer case.
Labor allocation and full job cost are not identical. Wages are usually the starting amount. Depending on company policy, project expense may also include employer payroll taxes, insured benefits, workers’ compensation, or other labor burden. Those additions must be calculated and posted under approved accounting rules. Don’t assume they follow wages automatically.
What You Need Before Starting the Setup
The first ADP Workforce Now labor allocation decision is which products and permissions the employer has. Timekeeping functions can differ between Workforce Now customers. A next-generation timekeeping environment may also expose different screens and interfaces from an older environment. A procedure copied from another client’s system may fail even when both call the product Workforce Now.
Package availability matters. ADP’s current package comparison lists time and attendance with its Premium package while describing payroll and general ledger features across its main packages. Customers can have separate arrangements and add-ons. Verify the contract, enabled timekeeping functions, payroll company codes, and any accounting connector before editing production settings.
An ADP labor distribution setup project should begin with a working inventory. Record every payroll company, pay group, current department, active job, pay code, source timesheet, accounting segment, and integration owner. Include who can create codes, who can enter time, and who can approve changes. Without clear ownership, old codes may stay active while new codes appear in only 1 system.
Confirm the Data That Finance Actually Needs
A controller may ask for labor by project and phase, while payroll currently reports only by department. Those are different levels of detail. Agree on the minimum result before choosing a cost-code design. Decide whether reports must show actual hours, gross wages, overtime premiums, loaded labor expense, or some combination. Identify which result comes from ADP and which is created later in accounting.
ADP Workforce Now cost centers may be represented through payroll cost numbers, organizational data, or configured accounting dimensions, depending on the client’s setup. Don’t use those terms as interchangeable labels in an implementation document. Create a field map showing each value’s official name, source system, allowed format, and destination. The map becomes the reference for testing.
Before continuing, obtain a safe test environment or another approved test method, current configuration documentation, representative employee records, and sample accounting output. Establish a payroll freeze window for changes that might affect the live pay cycle. A setup is ready to begin when payroll and finance agree on the same expected result for a sample employee who works on 2 jobs.
How to Design Job Codes and Cost Centers
The code structure should reflect the way costs will be reviewed. A flat job list may work for a services business that invoices by client project. A contractor may need a project, phase, and activity code. A manufacturer might need plant, work order, and task information. Adding every possible dimension makes time entry harder, so retain only fields that support a real reporting or approval requirement.
In ADP Workforce Now job costing, use stable identifiers rather than job names as matching keys. A project can change its display name without changing its accounting identity. A code such as PRJ-410 is easier to reconcile than a name that different managers type differently. The exact format is a business choice, not a required ADP code pattern.
| Field | Illustrative Value | Business Meaning |
| Project | PRJ-410 | Client contract or internal job |
| Phase | ELEC | Electrical work stage |
| Activity | INST | Installation labor |
| Department | OPS | Employee’s operating unit |
| Payroll cost number | C410 | Configured payroll allocation value |
| GL segment | 6100-410 | Labor expense account and job segment |
Control New, Closed, and Changed Jobs
Define a single source of truth for job status. Finance or project operations should approve a new job before timekeepers can use it. Active codes should be available only to the employees or groups that need them where the chosen product supports that restriction. Closed work should stop accepting new time without destroying historical records.
ADP Workforce Now cost centers should also have clear effective dates when organizational changes affect payroll results. An employee moving to a new department shouldn’t rewrite the costs of work already approved in an earlier pay period. Test the date behavior in the actual configuration rather than assuming that an updated employee profile will handle every past transaction.
A good code dictionary includes each identifier, description, owner, status, accounting destination, and valid use. Keep rejected or unmapped values in an exception report. The code dictionary is the foundation for ADP payroll job costing because payroll and finance can’t reconcile work that they identify differently.
How to Configure Job Selection in Timekeeping
Time entry is where job data is easiest to capture and where mistakes can multiply. An employee who moves between work orders needs a way to record the change when it occurs. If a supervisor adds the job information days later, payroll may still run correctly, but project hours can become unreliable. Start with the least demanding entry process that still captures the required detail.
Employees can transfer between jobs, as ADP’s time and attendance guidance describes clocking and transfer options for employees changing departments, locations, or jobs. It doesn’t establish that every client has the same transfer screen. Confirm whether your workers use a web timesheet, mobile workflow, kiosk, clock, or imported time records, and test the available job selection controls in that environment.
For ADP Workforce Now labor allocation, a time record should identify the employee and work date, the hours or punches, and the approved labor charge values needed by payroll. A job code alone may be insufficient if pay depends on work location or labor classification. Conversely, payroll may not need a project phase even though finance does. Document both cases before deciding which fields must travel to payroll.
Set a Practical Approval Rule
The supervisor should check job assignments while the work is fresh. Require exceptions for missing codes, work posted to a closed project, unsupported combinations, and hours entered against a job the employee wasn’t assigned. Allow authorized correction with a reason and audit trail. Avoid silently replacing an invalid job with a default account, since that can hide the very errors the system was meant to reveal.
A clear review pattern separates employee time approval from financial allocation approval. The supervisor confirms that the work occurred. Payroll confirms payable hours and earning rules. Finance confirms that approved charge codes point to the right projects. In a smaller company, 1 person may perform more than 1 task, but the checks should remain distinct.
The ADP labor distribution setup should define what happens when time arrives late. Decide whether the source time record can be corrected before payroll cutoff, whether an approved pay adjustment is required later, and how the original job cost entry will be reversed. An undocumented late-change process produces reporting differences that can be difficult to investigate after month-end close.
How to Set Up Payroll Labor Distribution
ADP labor distribution setup uses payroll company settings to determine how certain earnings and hours are distributed. This is the point where an implementation must follow the correct Workforce Now product version rather than a generic online screenshot. ADP’s public documentation includes specific menu paths for a supported Payroll Data Input configuration. Those paths are documented examples; they haven’t been confirmed as identical in every 2026 tenant.
For payroll distribution, ADP’s Payroll Data Input guide, ADP describes opening Setup > Payroll > Company Options, choosing the payroll company, and setting Labor Distribution and Allocations to Cost Number or Department Number as appropriate. It also documents entry of temporary cost and department values through columns on the Paydata page. The configuration must match the kind of input being submitted.
Choose Cost Number or Department Distribution
Use cost-number distribution when the company’s payroll design assigns expense to defined cost numbers. Department distribution is appropriate when departments are the configured allocation unit. The right choice depends on the reporting requirement and existing payroll setup. It should never be changed in production merely to make a single test file work.
ADP Workforce Now cost centers might need more detail than one payroll department can express. In that case, determine whether a cost number can carry the required reporting key or whether additional job data must be passed to accounting. Confirm how payroll company codes affect validation tables. A cost number that exists for one company may not be valid for another.
Understand the 2 Documented Allocation Methods
ADP describes automatic allocation by percentage for dividing an employee’s hours and earnings regularly among designated cost numbers or departments. The percentages should total 100%. It also describes manual posting in Paydata, which lets a payroll user direct entries to configured allocation positions when the default distribution doesn’t reflect the work.
These methods answer different business needs. A headquarters employee with a stable agreed split between 2 operating units may suit percentage allocation. A field employee who moves across jobs each day needs a time-based or approved manual process that reflects those changes. Don’t assign a fixed percentage simply because it is easier to configure.
The correct ADP labor distribution setup also addresses the interaction between automatic and manual settings. ADP’s guide documents allocation-position rules that vary when only one method, or both methods, are enabled. Those position values are technical validation rules, not project identifiers. A payroll integration must follow the configured rules instead of guessing which numeric position to send.
Before saving the design, identify how errors appear to the payroll reviewer and whether rejected entries leave earlier valid values unchanged. Run the first checks with a nonproduction payroll cycle or an approved test process. Changes to company distribution settings can affect more than the employee used for a demonstration.
How to Assign Employee Allocations and Paydata Values
Company options establish the method; employee records and paydata determine how that method affects a particular payroll. A fixed allocation entered on an employee profile can be useful for recurring distributions. A temporary value in a paydata batch can reflect a specific pay period. Mixing the 2 without a rule can send correct earnings to an unexpected destination.
For batch entries, ADP’s paydata input examples confirm that supported batches can carry temporary cost numbers, temporary departments, and allocation information. The full guide also describes employee allocations under People > Employment > Employment Profile > Corporate Groups > Allocations. Before using that path, check the interface available in your account and whether the profile already contains established allocations.
ADP Workforce Now labor allocation should distinguish a standing assignment from a temporary override. An employee may belong to Department 200 for organizational purposes but work on Project 410 this week. Determine whether the time record, the payroll cost number, or a manual approved entry should take precedence. The rule must be explicit so that a user doesn’t unintentionally replace project cost data with an employee’s home department.
For ADP payroll job costing, document a test for 1 employee with 100% assigned to 1 cost number and another whose earnings split across 2 valid numbers. Confirm that the total distribution equals the original earnings. Then enter an invalid value to see the actual error response. A successful test checks both acceptance of correct values and rejection of incorrect ones.
How to Connect Time, Payroll, and Job Data
An integration should move only the information each destination requires and preserve enough identifiers to trace a transaction. Timekeeping may send paid hours and labor codes to payroll. Payroll calculates earnings. A later payroll output or accounting extract may then carry financial results to another application. One-direction data flow isn’t guaranteed, and a nightly sync may be too late for a payroll cutoff.
For reference-data uploads, ADP’s labor charge code API provides a documented interface for uploading configured labor charge values, including metadata and upload-status operations. The existence of that interface doesn’t mean an administrator can use it without the correct product, credentials, and access. Confirm the supported endpoints for the client’s timekeeping generation and whether code creation is managed by an integration partner.
For API permissions, the Workforce Now API catalog explains that integrations require an approved developer arrangement and that API availability varies by use case. It also notes restrictions on certain payroll output APIs. Build an integration plan around the endpoints and permissions ADP confirms for the client, rather than assuming a public API list represents an enabled subscription.
ADP labor distribution setup work should specify how each system handles changed codes. A job may be renamed in accounting while its identifier stays stable. A completed job should stop appearing for new time entries, but its old cost records must remain available. Establish an agreed schedule for code updates and a failure alert when a value cannot reach the destination.
ADP Workforce Now cost centers also need translation rules when the same cost value isn’t used everywhere. Keep a mapping table with valid dates and owners. If a transfer fails, the team should be able to identify the original time entry and the rejected destination value without searching through untracked spreadsheets. Test retries to ensure an attempted correction doesn’t create duplicate earnings.
How to Map Labor Cost Into the General Ledger
The accounting result should be designed before the first payroll export. Start by identifying the debit accounts for direct labor and overhead, then define the balancing entries the accounting system expects. Decide whether project cost sits in a dedicated GL segment, project subledger, or both. The organization should be able to explain how a job number in timekeeping becomes a finance reporting value.
For accounting exports, ADP’s payroll feature guide describes a general ledger interface that creates an import-ready file of payroll journal entries. That confirms an accounting export capability, but it doesn’t prove that every project segment or labor-burden rule is supplied by default. The employer must verify the fields included in its actual export and the receiving accounting application’s import rules.
A practical ADP Workforce Now job costing example starts with a $1,000 gross wage total assigned across 2 jobs. If approved job hours and rates produce $600 for one job and $400 for the other, the wage expense distribution should reconcile to $1,000. This is an illustration. The actual payroll may have overtime or other earning types that require a more detailed rule.
Reconcile Payroll Expense Before Posting
Compare the payroll register with the sum of the wage journal lines before importing them to the general ledger. Confirm that the same payroll company and pay period are in both reports. An accurate total with incorrect job segments still fails the job-cost test, so reconcile by cost number or project as well as at company level.
ADP payroll job costing may also need a reconciliation for employer taxes and benefits after the wage entries are posted. Finance can assign those costs by an approved burden rate or an actual expense allocation, but the chosen method should be documented. Don’t label a wage-only report as total labor cost. Maintain a clear difference between paid hours, gross earnings, and fully loaded job expense.
How to Handle Overtime and Labor Burden
ADP Workforce Now job costing assignments don’t determine legal overtime. An employee who works on 3 jobs in a single workweek doesn’t begin a new overtime clock at each job. Payroll must apply the employee’s workweek rules and applicable pay requirements first. Accounting can then distribute the resulting expense under an approved project costing method.
The Department of Labor’s overtime fact sheet explains the federal rule that covered nonexempt workers generally receive at least 1.5 times their regular rate for hours over 40 in a workweek. State rules and special industry requirements may be different. A timekeeping job switch should never be used to reset that calculation.
Where an employee works at different rates during the week, the Department of Labor’s construction wage FAQ describes the weighted-average calculation commonly used in certain covered cases. Employers also need to check whether a specific statutory alternative or contract rule applies. Test the payroll result separately from the project’s allocation of overtime premium expense.
A finance policy might charge overtime premium to the job that requested the extra work, spread it across jobs, or treat some premiums as overhead. That is a costing decision and may be limited by contracts or grant rules. ADP Workforce Now labor allocation won’t decide the accounting treatment without configured rules and valid data. Preserve the calculation that links hours, earnings, and final charged cost.
Labor burden requires the same care. A project manager may want employer payroll taxes and benefit contributions added to wage cost. The amounts and timing can differ from a standard percentage assumption. Document whether reports use estimated burden for operational tracking or actual posted expense for the final financial result, and reconcile differences under the company’s accounting policy.
How Construction and Certified Payroll Change the Setup
Construction work may require job and phase codes alongside labor classifications, union rules, or prevailing wage rates. The coding model must preserve the type of work actually performed. An employee’s usual title might not be enough if the worker performs a different classification on a covered project. This is one reason construction job costing often requires more detail than ordinary departmental reporting.
ADP describes job-level labor support in its construction offering, but a buyer must check which features and partner arrangements are included. Separate third-party products may add certified payroll or accounting functions. Their descriptions shouldn’t be treated as features included with every Workforce Now contract.
For covered federal and federally assisted construction work, the Department of Labor’s WH-347 instructions explain the weekly certified payroll requirement and the need to record hours by applicable labor classification. The form itself is optional if an equivalent compliant submission is used. Those records can require a different level of detail from a company-wide payroll register.
An ADP labor distribution setup serving these jobs should test project location, classification, hours, wage rates, and fringe treatment before preparing any required certification. Job costing codes support that review, but coding alone doesn’t prove the correct prevailing wage was paid. Keep the underlying timesheets and wage determinations available for review by the people signing the required statements.
Where workers move between covered and noncovered projects, reconcile the workweek totals across every job. Don’t calculate payroll based only on the hours appearing in a single project’s report. The finance department can prepare separate project cost entries after payroll has applied the correct wage rules.
How to Test and Reconcile the Setup Before Go-Live
Successful ADP Workforce Now job costing tests must follow transactions from their source to accounting. Choose a test payroll period and create cases based on real pay policies without exposing unnecessary live employee data. Capture expected results before anyone sees the system output, then compare them with actual time, payroll, and journal records.
The Department of Labor’s recordkeeping guidance lists essential employee wage and hour records, including daily and weekly hours for covered nonexempt workers. Job allocation data may be needed for internal finance or a contract even when it isn’t a separate federal recordkeeping field. Keep the required wage records intact while testing how job details are added.
| Test Case | Expected Result | Reviewer |
| Employee works on 1 job | All eligible wage cost reaches that job | Payroll and finance |
| Employee splits time across 2 jobs | Hours and earnings match approved split | Supervisor and payroll |
| Invalid project code | Entry is rejected or flagged for review | HRIS administrator |
| Overtime across multiple jobs | Legal pay is correct and premium follows policy | Payroll specialist |
| Retroactive correction | Original and corrected charges are traceable | Finance controller |
| Closed job or late code change | No silent posting to an unrelated default | Project owner |
For ADP Workforce Now job costing, compare 3 checkpoints: approved hours, payroll earnings, and accounting charges. The total at each checkpoint may use different units, but its relationships should be documented. Hours should reconcile with paid and unpaid classifications; earnings should reconcile to the payroll register; job wage entries should sum to the approved labor expense total.
Run negative tests as well. Try a cost number not in the validation table and an allocation with an invalid percentage total. Confirm the error is visible to a responsible reviewer. Test whether a correction can be entered after time approval but before payroll finalization. Document which changes need a separate payroll adjustment after the cycle closes.
Don’t approve production solely because the first sample paycheck is correct. ADP Workforce Now cost centers may still be wrong in the general ledger. Require signed acceptance from payroll and finance, with unresolved differences assigned to owners and a decision on whether each defect blocks the launch.
How to Fix Allocation Errors and Keep Codes Current
Most allocation investigations should begin with the first place the wrong value appears. If the timecard identifies an incorrect job, inspect employee selection and supervisor approval. If time is correct but paydata is wrong, check the field map and payroll distribution setting. If payroll is right but the GL is wrong, inspect the export and import mapping before altering wages.
For current technical guidance, ADP’s API guide directory lists product-specific payroll and time integration documentation, including entries updated in 2026. That is a better place to confirm current interface scope than relying on an old integration example. Some setup screens described in older public guides may differ from the client’s interface, so an administrator should check the account’s current support materials.
ADP payroll job costing needs an exception log that names the pay period, employee or transaction reference, submitted cost value, expected value, error, approver, and correction method. Protect employee details in approved storage. Assign responsibility for reviewing unresolved errors before every payroll cutoff.
A monthly control should compare active project lists with authorized job records, identify charges to closed projects, review default or unassigned cost values, and reconcile payroll totals to accounting. Trend repeated corrections by cause. A code that causes the same error each period points to a configuration or training problem, not a one-time payroll exception.
Keep ADP Workforce Now cost centers under change control. New codes need approval and a tested accounting destination. Old codes should be retired according to a documented effective-date rule. Any major change to time entry or payroll mapping should repeat representative end-to-end tests before it becomes part of a live pay run.
What Makes the Setup Reliable Over Time?
A reliable ADP Workforce Now job costing process gives payroll and finance the same answer about where labor belongs. That requires an owned code list, documented distribution rules, a tested route from time to payroll, and an accounting check after each run. One setting cannot replace these controls.
ADP Workforce Now labor allocation is most useful when temporary changes don’t overwrite the meaning of permanent employee assignments. ADP labor distribution setup should preserve the distinction between payroll department and actual project work. ADP payroll job costing should report what was charged and make corrections traceable. ADP Workforce Now cost centers should stay aligned with accounting definitions as projects open and close.
The final decision is whether the system can explain a cost from the original approved work to the reported expense. If a project manager questions a labor charge, the answer should be supported by the time entry, the payroll result, and the posted accounting record. That is the standard worth using before the process is considered complete.
Frequently Asked Questions
Does ADP Workforce Now Support Job Costing?
Yes, ADP Workforce Now job costing can combine configured payroll distribution with job-related time records and accounting mapping. The exact level of project detail depends on enabled products and integrations.
What Is the Difference Between a Cost Number and a Job Code?
A payroll cost number identifies a configured allocation destination. A timekeeping job code identifies the work recorded. ADP Workforce Now job costing needs a tested mapping when those values differ.
Where Are Payroll Labor Distribution Settings Found?
Older ADP documentation describes Company Options under Payroll setup, with Labor Distribution and Allocations choices. Confirm the current menu and permissions in your specific Workforce Now account.
Can Labor Be Split Across Multiple Jobs?
Yes, when the setup supports the required allocations. ADP Workforce Now labor allocation can involve percentages or paydata postings; actual time-based job splits also require appropriate time capture and mapping.
Do Automatic Allocation Percentages Have to Equal 100%?
Yes. ADP’s documented automatic percentage method requires the distribution to total 100%. The correct payroll position and validation rules also depend on the company’s enabled allocation methods.
Can a Payroll Cost Number Override an Employee’s Department?
A configured temporary cost number can affect paydata distribution. The result depends on company settings and the employee’s allocations. Test the intended precedence before using overrides in production.
Is Job Costing Included With Every Workforce Now Package?
No universal job-level workflow is documented for every subscription. ADP Workforce Now job costing may require timekeeping features, correct payroll settings, and an accounting connection beyond core payroll.
Can Timekeeping Codes Be Uploaded by API?
ADP documents labor charge code upload operations for supported environments. Access depends on the specific product, approved integration credentials, and configured labor charge fields.
How Are Job Costs Sent to Accounting?
The payroll general ledger interface can produce journal files. ADP payroll job costing still requires agreed mappings for job identifiers and rules for any labor burden added by finance.
Why Does Payroll Match but the Project Report Differ?
The paycheck can be right while labor is assigned to the wrong project. Check time codes, payroll cost values, GL mappings, pay-period dates, and accounting adjustments in that order.
Does Labor Allocation Calculate Overtime Separately by Job?
No. Applicable overtime rules generally use the employee’s workweek. ADP Workforce Now job costing should distribute legally calculated earnings according to an approved project costing policy.
Can Workforce Now Handle Certified Payroll Projects?
Supported configurations and partner services can help, but required wage classifications and reporting must be verified. The employer remains responsible for correct project records and applicable certified payroll submissions.
Should Salaried Employees Use Percentage Allocations?
A stable split may suit some salaried employees. Where accurate project hours are required by contract or accounting policy, a fixed percentage may be inadequate and needs further evidence.
Who Should Approve Job Cost Corrections?
The work supervisor should confirm the actual assignment, payroll should verify earnings, and finance should approve the project expense treatment. Keep a traceable correction record.
How Often Should Job Costing Be Reconciled?
Review errors before each payroll submission and reconcile payroll labor expense after each run. ADP Workforce Now job costing also benefits from periodic checks on closed projects and inactive codes.

2 thoughts on “ADP Workforce Now Job Costing and Labor Allocation Setup”