Sending Pay to Everee

Everee pays workers for the earnings you send it. This guide helps you choose the right API for each kind of earning, shows what a typical submission looks like, and explains what happens between you sending an amount and the worker getting paid.

Before you start, workers need to exist and be onboarded. See Onboarding and managing workers.

Which API should I use?

It depends on who's being paid, and what you know about the amount.

Hourly wages always go through the Timesheets API, even when you've already classified the hours, because overtime and other hourly rules affect how wages are calculated and shown on the pay stub. Payables is for everything else.

The Timesheets API is covered in Time and attendance. The rest of this guide covers payable items, and what's common to both.

How pay flows through Everee

How fast a worker gets the money after approval depends on how they're paid. Everee pays by direct deposit, or by the Everee Pay Card, which can be paid instantly.

Paying flat amounts with payable items

A payable item is one amount for one worker, under a pay code. You provide the amount, because payable amounts are often calculated by rules Everee doesn't manage.

POST https://api.everee.com/integration/v1/payables

{
  "externalId": "client_123::emp-1042::on_time_bonus_20261016",
  "externalWorkerId": "emp-1042",
  "label": "On-time bonus, October",
  "payableModel": "PRE_CALCULATED",
  "payCode": "BONUS",
  "type": "bonus",
  "amount": { "amount": 150.00, "currency": "USD" },
  "timestamp": 1792000000,
  "workLocationId": 1234,
  "costCenters": [{ "type": "clientId", "value": "290" }]
}

• externalId is an idempotency key. It must be unique within the company. Send the same one again and Everee updates the payable if it hasn't been paid yet, or rejects the request if it has. Build it from stable data, like a client, a worker, and a date, and never from a timestamp or random value. See Guide to the Payables API for why this matters.
• payCode is a default pay code like BONUS, COMMISSION, REIMBURSEMENT, or CONTRACTOR, or the apiKey of one of your own. List pay codes returns every pay code available to your company, including the pay codes of your leave types. Use those to pay out leave.
• workLocationId decides the tax jurisdiction for an employee's wages. If you leave it out, the worker's default work location is used.
• costCenters tag the amount so you can allocate costs later. See Reconciling payroll and posting to your GL.
• To send many at once, use Create payables (bulk).

Employees and contractors are paid differently

Employees. Do nothing more. Payable items are included in the employee's next regular payroll payment.

Contractors. Contractors don't have a regular payroll cycle, so nothing is paid until you call Request ASAP payout. Call it after you've sent all of a contractor's payable items and before a payroll admin starts approving payments. If you call it too early, items you send afterward wait for the next payout request. If you call it after approval, the items miss that run.

POST https://api.everee.com/integration/v1/payables/payment-request

{}

With no parameters, the request processes every unpaid payable item of your contractors, and leaves employees' items for their regular payroll. That's what most integrations want. To limit it, send externalIds, workerIds, or externalWorkerIds.

Paying as soon as possible

To pay an employee's payable item without waiting for payroll, use the same payout request, with includeWorkersOnRegularPayCycle set to true. The items are processed into payments separate from regular payroll. A payroll admin approves them separately, and once approved they're locked and won't be paid again in the next regular payroll.

This suits items like expense reimbursements and advances. Whether it's right for you depends on your workflow, your workers' expectations, and cash flow, so limit the request to specific payables with externalIds, or to specific workers, rather than turning it on for everyone.

Following a payment to the end

Know when someone is paid

Subscribe to these webhook events instead of polling:

A returned deposit isn't the end of the story. The worker is asked to fix their bank details, and Everee retries the deposit under the same paymentId. A payable stays PAID throughout, so use the events to follow the outcome. See Returned deposits and retries.

Check where a payable is

• Get a payable by your externalId.
• List payables, or list unpaid payables for one worker, to find what's still waiting.

Reconcile

Once a pay date has finished processing, retrieve its payments to tie out wages, taxes, and net pay to your own records. See Reconciling payroll and posting to your GL.

Changing or removing an amount

Until an amount is paid, you can change it freely.

Corrections adjust a worker's pay after the fact, which is why you have to opt into them each time. An unintended correction can't be sent by accident.

Common mistakes

• Paying hourly employees with payables. Send hours to the Timesheets API, so overtime and pay stub rules apply.
• A random externalId. A retry then creates a duplicate and the worker is paid twice.
• Forgetting the payout request for contractors. Their payables sit unpaid.
• Not setting workLocationId. The amount is taxed using the worker's default location, which may not be where they worked.
• Polling for payment status. Use payment.paid.

When a call fails and you can't see why, see Diagnosing a failed request.

Next steps

• Time and attendance
• Reconciling payroll and posting to your GL
• Guide to the Payables API