The Dayforce integration hires your candidate in Dayforce without anyone re-typing their details. When a candidate is ready, someone on your team opens Send to Dayforce, checks a form that Pinpoint has already filled in from across the requisition, the offer and their onboarding answers, and submits it. Pinpoint creates or updates the employee record in Dayforce and sends their documents across.

It works in three directions of travel that matter day to day:

Documents collected during hiring and onboarding - CV, signed offer letter, background check results, onboarding paperwork - are sent to the employee's Dayforce record too.

Which lists you need to supply. Pay groups, security roles, languages, time-off entitlement policies, onboarding policies, HR policies, ethnicities, emergency contact relationship types, federal filing statuses, countries, and states/provinces. Everything else - employment statuses, pay classes, pay types, positions and locations - Pinpoint reads from Dayforce for you. Your implementation contact will collect these at the Data Mapping Workshop.

A hiring manager creates the requisition. Custom fields on it - things like Location, Org Unit and Position - offer options that came from Dayforce, so only values Dayforce recognises can be chosen.

Your hiring process runs as normal. At offer stage, custom fields on the offer - Pay Class, Pay Group, Pay Type, Employment Status and similar - are again filled in from Dayforce-sourced options by whoever creates the offer.

Once hired, the candidate goes through Pinpoint Onboarding, where you collect what you couldn't ask earlier: tax details, direct deposit, emergency contact, home address, and anything else you need in Dayforce.

When onboarding is complete, the onboarding manager clicks Send to Dayforce. Pinpoint assembles a form from everything it already knows - across the requisition, job, application, offer and onboarding answers - so most of it is already filled in.

A callout at the top tells you what's about to happen. Net-new hire means Pinpoint found nobody matching in Dayforce, so a new employee record will be created.

Below it, the form is grouped into sections so it's quick to check: Identity, Employment, Work Assignment, Onboarding & HR Policies, Demographics, Custom Fields, Home Address, Contacts, Emergency Contact, Federal Tax (US), Direct Deposit and Onboarding Documents. Fields marked (optional) can be left blank.

Review it, fill any gaps, and submit.

Submissions are processed straight away. If Dayforce rejects something, the reason appears next to the field it relates to, so you can correct it and submit again without starting over. Once it succeeds, the employee record is created or updated in Dayforce and the documents are sent.

There are three places, and you can use whichever suits the situation:

When you open Send to Dayforce, Pinpoint looks the person up in Dayforce using their Dayforce Employee ID and adapts to what it finds:

In both of those cases the form tells you what it found and what it's going to do, and shows a Current Dayforce record summary - their status, their last work assignment, their pay, their original hire date, and which details are already on file and will be kept. Under each field, an "In Dayforce: ..." hint shows the value currently held, so you can see exactly what you're about to change.

Only the fields you actually fill in are applied. Anything you leave blank stays as it is in Dayforce.

You get the full hire form, and on submit Pinpoint reactivates the employee and applies whatever you've filled in. Details already on file - their home address and Social Security Number, for instance - are kept unless you deliberately set them again.

For an internal mover the form is deliberately cut right down, because you're changing a work assignment rather than hiring someone. You'll see only:

Nothing else about the employee is touched - no address, emergency contact, tax or direct deposit fields are even shown.

Matching relies on the Dayforce Employee ID or SSN being on the candidate's record in Pinpoint. If it isn't there, Pinpoint has no way to know they already exist and will treat them as a new hire.

This means Dayforce already holds an employee with that Social Security Number. Nothing is created, so there's no duplicate to clean up. To update that existing employee instead:

Pinpoint will now recognise them as a re-hire or internal mover and update the existing employee.

Pinpoint only ever matches on the Dayforce Employee ID, never on Social Security Number. If you want re-hires matched automatically across a large existing workforce, ask about the optional one-time employee import, which puts Dayforce Employee IDs onto your Pinpoint candidate records.

Any file attached to the candidate can be sent - typically their CV, the signed offer letter, background check documents and onboarding paperwork. Pick them in the Onboarding Documents section of the form before you submit.

A couple of things worth knowing:

Pinpoint refreshes lists from Dayforce on a recurring basis - your org structure, locations, positions, employment statuses, pay classes and pay types, and any custom fields you've mapped. Those values become the options on your Pinpoint custom fields.

The practical effect: when a hiring manager fills in a requisition or an offer, they can only pick things Dayforce will accept, so submissions don't fail later over a value that was never valid. There's nothing to maintain by hand - if you add a location in Dayforce, it turns up in Pinpoint.

This is the part that makes the difference between a form your managers breeze through and one they retype every time.

Out of the box, Pinpoint only pre-fills what it knows about every candidate:

Everything else starts blank - Social Security Number, pay, position, work location, security role, policies, emergency contact, federal tax, direct deposit, and any custom fields.

Anything left unmapped has to be typed by hand on every single hire. Mapping those fields to onboarding answers, offer fields or custom fields - which is exactly what the Data Mapping Workshop is for - means the form arrives filled in and the manager only reviews and submits. It's faster, and it removes retyping mistakes on the fields where mistakes hurt most: Social Security Number, bank details and tax withholding.

Work through this with your Customer Success Manager. The default mapping is fine for a first test, but a production rollout should map the post-hire data you're already collecting in onboarding.

I was asked to reopen the action.

The person's status in Dayforce changed while the form was open, so the form no longer matched reality. Close it, open Send to Dayforce again, and the form will be rebuilt from Dayforce's current record.

A dropdown is missing options, or is empty.

For lists Pinpoint reads from Dayforce, check the value exists in Dayforce. For the lists you supplied at the Data Mapping Workshop - pay groups, roles, policies, ethnicities, relationships, filing statuses, countries, states - the options are the ones you gave us, so send your Customer Success Manager the additions.

A document hasn't appeared on the employee record.

Give it a little time - Dayforce imports documents on its own schedule after Pinpoint hands them over. If it still hasn't arrived, check with your Customer Success contact that file transfer details are configured.

Q: Does this work with Recruiting as well as Onboarding?

A: Yes. You can send a candidate from onboarding, from their application once they're in the Hired stage, or automatically with a stage action.

Q: Can I send someone to Dayforce more than once?

A: Yes. Sending again updates the existing employee rather than creating a second one, as long as their Dayforce Employee ID is on their Pinpoint record.

Q: What happens if I leave a field blank for a re-hire?

A: It's left untouched in Dayforce. Only the fields you fill in are applied.

Q: Do I have to fill in the whole form every time?

A: No - and if you are, the mapping is worth revisiting. See Getting the form to fill itself in.

Q: Can we automate it completely?

A: A stage action can trigger the export automatically. Bear in mind that anything not mapped is still blank, so full automation only makes sense once your mapping is complete. We recommend using manual “review → fill gaps → submit” for a few months and when the process becomes just “submit”, then it’s time to automate.

Every field the Send to Dayforce form can send, in the order it appears. "Pre-filled by default" means Pinpoint fills it in without any mapping work; everything else can be pre-filled by mapping it at the Data Mapping Workshop. Please check with your Customer Success contact for the up-to-date list of fields (as we add more fields every now and then).

Any additional Dayforce custom fields (Employee Properties) agreed at the Data Mapping Workshop appear here as their own fields. None are pre-filled by default.

This section only appears if your integration is set up with file transfer details.