Deltek and Dayforce integration

What moves between them

The main flow runs from Dayforce into Deltek Vantagepoint. After each pay run, ml-connector reads the payroll journal report from Dayforce and posts the labor cost lines into Vantagepoint as journal entries, mapped to the matching GL accounts and organizations. Employee records flow the same direction so the Vantagepoint employee hub reflects Dayforce hires, terminations, and rehires. Dayforce organizational units and positions are aligned so payroll allocations land on valid Vantagepoint organizations. Dayforce holds no AP, invoice, or vendor data and its journal report is read-only, so ml-connector never writes financial entries back into Dayforce.

How ml-connector handles it

ml-connector stores both credential sets encrypted and obtains a Dayforce Bearer token with the password grant and fixed client ID, caching it and re-requesting before the one-hour expiry, and it refreshes the client-specific service URL from ClientMetadata once a day so high-volume reads skip the redirect layer. On the Deltek side it accepts the full tenant deltekfirst.com URL, database name, and password-grant credentials per customer, refreshes the bearer token before it expires, and requires the API user to have accounting and administrator roles so journal entries are allowed to post. Because Dayforce has no GL endpoint, the labor totals are pulled from a payroll journal report the customer configures in Dayforce, with Dayforce organizational units mapped to Vantagepoint organizations and GL accounts first so every line references a dimension that already exists. Neither side pushes signed events, so ml-connector polls on a schedule tied to your payroll calendar, using Dayforce filterUpdateDateRangeMin and filterUpdateDateRangeMax for changed employees and cursor paging on reports, and page-based paging on Deltek. Dayforce keys employees by XRefCode and Vantagepoint has no idempotency key, so ml-connector checks for an existing entry before posting, backs off and retries within Dayforce's per-tenant rate limit, and replays any record whose downstream call fails.

A real-world example

A mid-sized engineering and consulting firm with around 400 staff runs Deltek Vantagepoint for project accounting, billing, and finance, and uses Dayforce for payroll and HR across four offices. Before the integration, accounting ran the payroll register in Dayforce every pay period and typed the labor totals into Vantagepoint by hand as a journal entry, then spent the first days of month-end close reconciling headcount against the labor accounts in the ledger. With Deltek and Dayforce connected, each pay run's journal report posts into Vantagepoint automatically, allocated to the organization for each office, and employee changes keep both systems aligned. Close starts with the labor accounts already reconciled, and the manual re-keying is gone.

What you can do

• •Post Dayforce payroll journal data into Deltek Vantagepoint as balanced journal entries after every pay run.
• •Keep the Vantagepoint employee hub aligned with Dayforce hires, terminations, and rehires.
• •Map Dayforce organizational units and positions to Vantagepoint organizations and GL accounts so payroll lands on valid dimensions.
• •Bridge Dayforce's password-grant token and daily service URL with Deltek's tenant URL and password-grant token.
• •Poll on a schedule tied to your payroll calendar, with duplicate checks, retries, error replay, and a full audit trail on every record.

Questions

Which direction does data move between Deltek and Dayforce?

The main flow is Dayforce into Deltek Vantagepoint. Payroll journal data and employee records move from Dayforce into Vantagepoint, while organizational units are aligned so allocations match. Dayforce has no AP or vendor data and its journal report is read-only, so ml-connector does not write financial entries back into Dayforce.

How does ml-connector get GL data out of Dayforce when there is no GL endpoint?

Dayforce exposes no standalone GL account or payroll journal endpoint. The customer configures a payroll journal report in Dayforce that outputs earnings, taxes, and deductions with GL account codes and cost dimensions, and ml-connector pulls that report through the Reports API after each pay run. Those lines are then mapped to Vantagepoint GL accounts and organizations and posted as a journal entry.

Do Deltek and Dayforce push events, or does the connector poll?

Both systems are effectively poll-based for this pairing. Vantagepoint webhooks carry no HMAC signature and Dayforce has no signed outbound webhooks, so ml-connector reads on a schedule tied to your payroll calendar. It uses Dayforce date-range filters to fetch only changed employees and checks for an existing entry before each Vantagepoint post, since Vantagepoint has no idempotency key.