How it works
Payroll audits, Dayforce reports and exports, and Excel work, with the scope and price set up front.
Three kinds of projects, run the same way. You send the source material, we agree the scope and price before work begins, and you review the result at handoff. Reports and exports typically ship within one week. Payroll audit timing is set with the quote. Either way, your data stays under your control: before we connect, you see the exact fields we need, and we pull only what was approved.
Payroll audits
Registers in, findings log out.
- 01
Send the registers
You send the payroll registers and reports for the period under review, plus anything your team already questions. Scope and price are set per audit before any work begins.
- 02
We audit every line
Pay vs. time, deductions, voids, and special pays, checked across every entity and employee in scope. Questions go to one point of contact on your side.
- 03
Get the findings log
Every finding comes back in a log with the supporting document listed per flag, so payroll can confirm and close each item without digging.
Dayforce reports & exports
Five steps, no surprises.
- 01
Send the carrier specification
Upload the carrier's spec as PDF, Word, Excel, or CSV. We map every required, optional, and conditional field.
- 02
Review the exact Field Request
Before any connection, you get the precise list of Dayforce fields the project needs. Your administrator approves it first.
- 03
Create a dedicated read-only login
Your administrator sets up a non-personal Dayforce account used only for this project, with read-only access, and can remove it when the work is done.
- 04
We pull the codes securely
We retrieve only the approved plan, carrier, option, and coverage codes. A permission check runs before the first data pull, and you see the result.
- 05
Test within one week
You receive the export definition, a validated test file, and clear test instructions, ready for your carrier.
Your administrator also gets a detailed setup guide before we connect: the exact role, authorizations, and field checkboxes to use.
Security standard
Narrow access you can verify.
- A dedicated account, never an employee's everyday login
- Read-only access at every step
- Only the fields the carrier file needs
- The exact field list shown before we connect
- Sensitive fields excluded unless the carrier requires them
- Credentials stored separately from project files
- No credentials or employee data in the delivered file
- API activity restricted to approved carriers and dates
- A permission test before the first data pull
- Access removed when the project is complete
The goal is simple: get the codes needed to build the export, without taking access to data the export does not need.
What we need from you
For carrier-file exports: five things, then we start.
- 01The carrier specification
- 02A carrier contact for case-specific values the tenant does not store
- 03The dedicated read-only Dayforce account
- 04The carrier reference code for the first connection
- 05One administrator to review the Field Request and test the finished file
Once those are ready, the standard delivery target for an export is one week. Custom report builds need only the report spec and a sample of the data.
Excel consulting
Excel cleanup and automation.
- 01
Send the workbook and what's wrong
Send the file with a short note on what is broken or what you need it to do.
- 02
Get a fixed quote
Scope and price are set before any work starts.
- 03
Get the fixed file back
Usually inside a week, and you review it before the work is closed out.
Start a project
Have an audit or a file to build?
The one-week target applies to reports and exports. Payroll audit timing is set with the quote. Actual timing depends on project scope, carrier responsiveness, and specification quality.