Support and Operations

Payroll Infrastructure is managed: Everee handles most of the compliance and supports your customers' payroll directly. This page covers who does what once companies are live, and what to watch so your integration keeps working.

Who does what

Everee	You
Tax rule updates, tax remittance and filing	The screens your customers use: onboarding, workers, pay, approval and reporting
Garnishment and retirement remittance	Sending complete worker records and each run's pay
New hire and termination reporting	Approving runs, and acting on blockers and funding that needs action
Payroll support for your customers, through Everee Customer Success	Telling workers about their pay, and fixing returned deposits. See After payroll

Getting help

Payroll issues (a worker's pay, taxes, a returned funding debit, a notice from a tax agency): your customers are supported directly by Everee Customer Success. Transfer the issue to Everee rather than handling it yourself.
Integration questions: email [email protected], and include the X-Request-ID from the response if you have it. To see exactly what Everee received for a recent call, use the Request Log API. See Diagnosing a failed request.

Announcements

Everee publishes technical announcements, such as API releases, deprecations, maintenance and security notices. As a partner, you receive them once, at your partner webhook endpoints, not once per company. Read them with the Announcements API. See Announcement Events.

Emails to your technical contacts

Everee emails your technical contacts about your partner account:

Keys: when a key is claimed, and when a rotated key is scheduled to stop working. See Getting your partner API key.
Company-creation limits: when you reach a Sandbox limit (at most once a day), or create 100 Production companies in a rolling 7 days. See Limits on creating companies.

Keep your list of technical contacts current with your Everee contact, so these reach someone who can act on them.

Keeping your integration healthy

Handle webhooks reliably. Verify every event, skip duplicates by id, and read the current state rather than trusting the order events arrive in. See Building a webhook handler.
Watch requirements. Open requirements block payroll. Calculate runs early, and act on requirement.created as it arrives rather than on payroll day.
Watch deadlines. A run that isn't approved by its approvalDeadline, or whose funding isn't fixed by its processingBlockedDeadline, doesn't pay on time. See Running payroll and Funding payroll.
Look after your keys. Store partner and company keys as secrets, and rotate a partner key if it may have been exposed. Manage each company's keys with the Company API keys endpoints.
Clean up Sandbox. Retire Sandbox companies you no longer need, so you stay under the limit.