Build Pathways - SDK, Flows, & API

How do I decide how I want to build payroll on GEP?

Payroll is a very comprehensive product, involving multiple workflows and UI aspects that must be built in order for your customers to:

Provide all the inputs into payroll (e.g. employees, addresses, pay schedules, etc.)
Run the various types of payrolls (e.g. regular, off cycle, dismissal etc.)
Manage payroll and the associated data afterward.

An approximation of the most important workflows in a comprehensive payroll product can be found in our Flows list - see here and try them out!

Of course, this can be very time consuming to build. To cover this ground, GEP offers three approaches to building your payroll product, which you can mix-and-match for various aspects of your application - depending on your needs for each workflow:

Approach	Pros	Cons	Documentation
Custom (API only)	Full coverage for all of GEP’s capabilities Full customization of your application	Requires you to build the UI Requires understanding of individual endpoints	GEP API Reference
Flows via iframe	Fastest way to deploy any given workflow - all of the needed logic and API linkage already built in	Limited customizability beyond basic look and feel	List of available Flows via iframe Flow customization options
React SDK	Strikes the balance between Custom (API only) and Flows - enables more customization than Flows, and abstracts away logic around API endpoints	Workflows are limited but planned on our developer roadmap	See the other sections of this guide!