How it works

From carrier spec to a test-ready file in one week.*

You stay in control of your Dayforce access from start to finish. We show you the exact fields we need before we connect, pull only the approved plan and carrier codes, and hand back a validated file your carrier can test.

The project, step by step

Five steps, no surprises.

  1. 01

    Send the carrier specification

    Upload the carrier's spec as PDF, Word, Excel, or CSV. We map every required, optional, and conditional field.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Five things, then we start.

Once those are ready, the standard delivery target is one week.*

Start a project

Have a carrier file to build?

Tell us what you need ↗

*Typical target for a standard-scope project. Actual timing depends on project scope, carrier responsiveness, and specification quality.