You will place a feed request with Pay Fusion via one of two avenues:
For the vast majority of feeds, we will need to obtain three pieces of data and/or credentials
Access/credentials to your HRIS Platform (UKG/iSolved/etc)
Master API User Guide
Allows us to connect to all clients.
Pros: Only have to set up once.
Cons: Technically less secure in that we have access to all groups.
Per-Client API User Guide
Allows us to connect to just one client.
Pros: Technically more secure in that we only have access to a single group.
Cons: Must set up each and every time we connect to another one of your clients.
Access/credentials to connect to the specific piece(s) of data from the aforementioned HRIS Platform (UKG/iSolved/etc)
Access/credentials to the vendor’s SFTP endpoint and/or API.
The vendor’s file specifications so we know what to build and how to format the data.
This is the next step after collecting the credentials to both the platform storing our client’s data as well as the platform we’re sending data to. This is to ensure we’re connected as soon as possible so that we can start building!
Please Note: You won’t have to do anything here!
We will then validate whether or not we have the right pieces of data that we need to carry out the feed. Most of the time, there will be no follow up here. Every now and again we’ll reach back out to your team and request something.
Examples include:
Pay Fusion will then focus on building the feed per the vendor’s file specifications.