Common Workflows Overview

How the pieces of the Everee API fit together, and which workflow guide to read first.

The API reference describes each endpoint. These guides describe how to combine them to get a job done: what to call, in what order, what to listen for, and what can go wrong.

Every integration follows the same lifecycle, whatever it's built for:

StepWhat happensGuide
1. Set upWork locations, approval groups, payroll calendars, pay codes, cost centersSetting up your organization
2. OnboardCreate workers, get them through onboarding, keep their profiles currentOnboarding and managing workers
3. Send payHosted payroll: shifts and classified hours for hourly employees, payable items for everything else. Payroll Infrastructure: items on a payroll runTime and attendance, Sending pay to Everee, Running payroll
4. Payroll runsPayroll is approved, Everee calculates and funds, workers are paidEveree admin portal (hosted payroll), or the Payroll Run API (Payroll Infrastructure): see Running payroll
5. ReconcilePayment data, payroll journal, cost segments, deduction reconciliationReconciling payroll and posting to your GL

Steps 1, 2, 3, and 5 are yours. In hosted payroll, step 4 belongs to Everee and your customer's payroll admins. In Payroll Infrastructure, you calculate and approve each payroll run through the API, and Everee funds it and pays the workers. No money moves until payroll is approved, so it's safe to send data early and often.


Where to start

If you're building...Start withThen
Something new, and nothing is set up yetSetting up your organizationOnboarding and managing workers
A hiring or onboarding flow, such as an ATSOnboarding and managing workersTime and attendance
A timekeeping or scheduling systemTime and attendanceSending pay to Everee
A platform that pays contractors or gig workersOnboarding and paying contractorsReconciling payroll and posting to your GL
Billing or accounting softwareReconciling payroll and posting to your GLSetting up your organization, for cost centers
A benefits or retirement administration platformSyncing benefit and retirement deductionsOnboarding and managing workers, to match workers
Paid time off administrationManaging leave and PTOTime and attendance

For the same scenarios told from the point of view of your business type, see Integrating with Everee.


Use webhooks instead of polling

Almost every workflow here has a moment where you wait for Everee: a worker finishing onboarding, a payment being paid, a report finishing. Instead of polling, subscribe to webhook events. The ones you'll use most:

EventWhat it tells youUsed in
worker.onboarding-completedThe worker is ready to be paidOnboarding and managing workers
worker.profile-updatedSomething on the profile changed; re-sync your copyOnboarding and managing workers
payment.paidA payment has been submitted for depositSending pay to Everee, Reconciling payroll and posting to your GL
payment.deposit-returnedA worker's bank returned a depositSending pay to Everee
report.completedA report you requested is ready to downloadReconciling payroll and posting to your GL
payroll-run.status-changedA payroll run was calculated, blocked, approved or paid (Payroll Infrastructure)Running payroll
requirement.createdSomething must be fixed before payroll can process (Payroll Infrastructure)Running payroll

See Implementing a webhook handler and Securing your handler before you go live.


When something goes wrong

If a request fails, or does something you didn't expect, the Request Log API shows what Everee received and what it answered, including the request body and the error response. See Diagnosing a failed request.


Did this page help you?