SAP Business One and Dayforce integration

What moves between them

The primary flow is Dayforce into SAP Business One. After each payroll period, ml-connector reads Dayforce employee records (hire dates, terminations, rehires, job assignments) and pay summary data (gross pay, deductions, taxable amounts) and maps that information into SAP Business One's journal entries and dimension values. Employee headcount in SAP Business One reflects Dayforce hires, terminations, and job changes, and each pay period's labor costs are allocated to the correct profit center and GL account. Reference data such as profit centers, dimensions, and job codes are validated in both directions so payroll lines land on valid SAP Business One GL accounts.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the SAP Business One side it accepts the full customer Service Layer URL per deployment, establishes a B1SESSION after login, and reuses that session across all calls within the 30-minute window before re-authenticating. On the Dayforce side it requests a Bearer token from the token endpoint, handles the one-hour expiry by re-requesting tokens before they expire, and refreshes the client-specific optimized URL daily via GET /V1/ClientMetadata to avoid redirect overhead. Because both systems are pull-only, ml-connector polls on a schedule tied to your payroll calendar. Payroll summary data and employee records are read from Dayforce with the filterUpdateDateRangeMin and filterUpdateDateRangeMax parameters to capture only records changed since the last sync, then mapped to profit centers and GL accounts in SAP Business One's chart of accounts. Profit centers and job codes are mapped first, so every payroll line lands on a valid GL account and dimension that already exists. ml-connector backs off and retries on Dayforce rate limits and tracks the OAuth token expiry so a token refresh does not cause an outage. Every record carries a full audit trail.

A real-world example

A mid-sized services company runs SAP Business One for accounting, purchasing, and vendor management across three regional offices. The company uses Dayforce for payroll and HR across all offices and departments. Before the integration, the accounting team received a payroll summary email from HR after each pay period and manually allocated labor costs across the company's profit centers and GL accounts in SAP Business One, often discovering mismatches between Dayforce employee counts and SAP Business One headcount records during month-end close. With the integration in place, employee hire dates, terminations, and job assignments from Dayforce flow into SAP Business One automatically, keeping headcount aligned, and each payroll period's costs post into the correct profit center GL accounts without re-keying, eliminating the manual allocation step and letting accounting close books faster.

What you can do

• •Sync Dayforce employee records into SAP Business One to keep headcount, hire dates, and terminations aligned across both systems.
• •Read Dayforce payroll summaries and post labor cost journal entries into SAP Business One's general ledger, allocated to the correct profit centers and GL accounts.
• •Map Dayforce jobs and organizational units to SAP Business One dimensions and job codes so payroll expenses land on valid accounts.
• •Authenticate SAP Business One with session tokens and Dayforce with OAuth 2.0 Bearer tokens, managing re-authentication and token expiry automatically.
• •Poll both systems on a schedule tied to your payroll calendar with full audit trail and error replay.

Questions

Which direction does data move between SAP Business One and Dayforce?

The main flow is from Dayforce into SAP Business One. Employee records, hire dates, terminations, and pay summary data move from Dayforce into SAP Business One, where they are mapped to GL accounts, profit centers, and journal entries. Reference data such as profit centers and job codes are validated in both directions to ensure payroll allocations land on valid SAP Business One dimensions.

Why does ml-connector need to refresh the Dayforce client-specific URL daily?

Dayforce provides an optimized client-specific URL via GET /V1/ClientMetadata that must be refreshed at least once per day to avoid redirect overhead on every API call. ml-connector caches the URL and calls ClientMetadata daily to ensure it stays current without adding latency to regular sync operations.

How does ml-connector handle the different authentication models on each side?

SAP Business One uses session tokens: a login call returns a B1SESSION cookie that remains valid for 30 minutes, and ml-connector reuses that session for all calls within the window. Dayforce uses OAuth 2.0 Bearer tokens that expire in one hour: ml-connector requests a new token before expiry to prevent outages and stores credentials encrypted so users do not need to paste sensitive keys into the configurator.