---
updatedAt: 2026-11-09T01:19:08.000Z
agentTools:
  projectIndex: https://developer.everee.com/llms.txt
---

# After Payroll

Show workers what they were paid, handle returned deposits, deliver pay statements and tax forms, and reconcile each run.

[Running payroll](https://developer.everee.com/docs/running-payroll) ends when a run is approved and the money moves. This page covers what comes next, for workers and for the company's finance team.

In Payroll Infrastructure, workers have no Everee login and Everee doesn't contact them. Your product is where they see what they were paid, get their pay statements and tax forms, and fix a bank account when a deposit comes back.

| To                                             | Use                                                                                    |
| :--------------------------------------------- | :------------------------------------------------------------------------------------- |
| Tell a worker they've been paid                | [Net payout events](#net-payouts), or the [Net Payouts API](https://developer.everee.com/reference/net-payouts-api-guide) |
| Handle a returned deposit                      | [Returned deposits](#returned-deposits)                                                |
| Show a worker's pay history and pay statements | The [Worker Payment History API](#pay-history-and-pay-statements)                      |
| Give a worker their W-2 or 1099                | [List worker files](#tax-forms)                                                        |
| Reconcile and post to the GL                   | [Reconciliation and accounting](#reconciliation-and-accounting)                        |

Funding holds and returned funding debits are covered in [Funding Payroll](https://developer.everee.com/docs/funding-payroll).

## Net payouts

A worker's net pay goes out as one or more **net payouts**: one per bank account when the worker splits their pay. Each payout has a `type`, such as `DIRECT_DEPOSIT`, a `netAmount`, and a `sendDate`: the banking day Everee sends it. For a direct deposit, `sendDate` is normally the run's pay date, and a retry has its own.

| `status`     | Meaning                                                                                                                                           |
| :----------- | :------------------------------------------------------------------------------------------------------------------------------------------------ |
| `PENDING`    | Not paid yet                                                                                                                                      |
| `PAID`       | Paid. A direct deposit is `PAID` when it's submitted to the bank, and can still be returned later. Other types are `PAID` once they're delivered. |
| `RETURNED`   | The payout came back, for example because the bank account was closed                                                                             |
| `SUPERSEDED` | Replaced by another payout, such as the retry of a returned deposit                                                                               |

A direct deposit that's `PENDING` or `PAID` also has `expectedClearingDate`: the day the funds are expected to clear against the worker's account, two banking days after `sendDate`. ACH doesn't confirm when a deposit clears, so this follows ACH's settlement timing, and a deposit can still be returned after it.

To read payouts:

* [List net payouts](https://developer.everee.com/reference/list-net-payouts), filtered by `payroll-run-id`, `payment-id`, `external-worker-id`, `worker-id` or `status`.
* [Retrieve a net payout](https://developer.everee.com/reference/retrieve-net-payout) by its `id`.
* [List a payroll run's payments](https://developer.everee.com/reference/list-payroll-run-payments). Each payment lists its payouts in `netPayouts`.

### Telling workers they've been paid

Subscribe to the net payout events. Each one carries the payout, so you don't need another call:

| Event                 | Use it to                                                                   |
| :-------------------- | :-------------------------------------------------------------------------- |
| `net-payout.paid`     | Tell the worker they've been paid, and how much went to which account       |
| `net-payout.returned` | Tell the worker a deposit came back, and ask them to fix their bank account |
| `net-payout.retried`  | Know a returned deposit is being sent again                                 |

A run stays `PROCESSING` until its direct deposits count as delivered. Meanwhile its `expectedPaidDate` is the day Everee expects to mark it `PAID` or `PARTIALLY_PAID`. A run is `PARTIALLY_PAID` when some payouts didn't reach the worker. [List its net payouts](https://developer.everee.com/reference/list-net-payouts) with `status=RETURNED` to find the ones waiting on a fix.

The payout includes the bank's routing number and the account's last four digits. Handle it as you would other payment details. See [Payroll Run Events](https://developer.everee.com/docs/payroll-run-events#net-payout-events).

## Returned deposits

A worker's bank can return a direct deposit after Everee sends it, most often because the account or routing number is wrong. Since Everee doesn't contact the worker, you do:

1. On `net-payout.returned`, tell the worker their deposit came back and ask for correct bank details.
2. Update the worker's bank account with the [Worker Direct Deposit API](https://developer.everee.com/reference/worker-direct-deposit-api-guide).
3. Everee retries the deposit as soon as possible, and sends `net-payout.retried`. The returned payout is now `SUPERSEDED`, and its `supersededByIds` names the retry.
4. The retry is a new payout on the same payment, with the original in `previousNetPayoutId`. Follow it until it's `PAID`, or returned again.

The payment keeps the same `paymentId` throughout. A payment split across accounts can be partly returned, so check each payout. See [Returned Deposits and Retries](https://developer.everee.com/docs/returned-deposits-and-retries) for the full flow and the related `payment.*` events.

## Pay history and pay statements

The [Worker Payment History API](https://developer.everee.com/reference/retrieve-a-workers-pay-history) gives you each worker's paid payments and their pay statement PDFs. Payments appear once they're processed for deposit.

| To show                                                         | Use                                                                                              |
| :-------------------------------------------------------------- | :----------------------------------------------------------------------------------------------- |
| A worker's list of payments                                     | [Retrieve a worker's pay history](https://developer.everee.com/reference/retrieve-a-workers-pay-history)                            |
| One payment in detail: earnings, taxes, deductions and deposits | [Retrieve a pay history item by ID](https://developer.everee.com/reference/retrieve-a-pay-history-item-by-id), with the `paymentId` |
| The worker's available pay statements, with year-to-date totals | [Retrieve a list of available pay statements](https://developer.everee.com/reference/retrieve-a-list-of-available-pay-statements)   |
| A pay statement PDF                                             | [Retrieve a pay statement](https://developer.everee.com/reference/retrieve-a-pay-statement), with the statement's `date`            |

Each takes the worker's `externalWorkerId`, or Everee's `workerId` if you don't use your own IDs.

* **A pay statement is a PDF behind a signed link.** The response has a `url` and an `expiresAt`. Request a new link each time a worker opens a statement, rather than storing it.
* **Pay history pages hold up to 20 payments**, and the API allows 25 requests per 10 seconds. See [Rate limits](https://developer.everee.com/docs/rate-limits).
* **The `paymentId` matches the Payment Data API**, where it's the payment's `id`.

## Tax forms

A worker's year-end tax forms, such as Form W-2 or Form 1099, are files on their Everee profile. Since workers can't log in to Everee, you deliver them.

[List worker files](https://developer.everee.com/reference/list-files) with the worker's ID, `document-type=TAXES` and the `tax-year`:

```http
GET /integration/v1/workers/files?id=emp-1042&document-type=TAXES&tax-year=2025
```

Each file has a `fileName`, `taxYear`, `publishedAt` and a `downloadUrl`. The URL is signed and expires, so list the files again for a fresh link when a worker opens one. Only files published to the company are listed.

For the company's own tax filings, [list company tax files](https://developer.everee.com/reference/list-company-tax-files) for a tax year. Each is `FEDERAL` or `STATE`, by its `jurisdictionLevel`.

To check year-end figures in a spreadsheet, run the [W-2 Details](https://developer.everee.com/reference/create-report-run-w2-details) and [1099 Details](https://developer.everee.com/reference/create-report-run-1099-details) reports.

## Reconciliation and accounting

The company's finance team needs to tie each run out and post it to the general ledger. You build that reporting in your product. Everee gives you three views of the same paid payments:

| To                                       | Use                                                                                                                                                               |
| :--------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Post payroll to the GL                   | The [payroll journal](https://developer.everee.com/reference/payroll-journal-guide), one balanced entry per funding                                                                                  |
| Report cost by client, job or department | The [cost segments](https://developer.everee.com/reference/payroll-cost-api-guide)                                                                                                                   |
| Check individual payments                | The [Payment Data API](https://developer.everee.com/reference/payment-data-api-guide), or the run's [payments](https://developer.everee.com/reference/list-payroll-run-payments)                                                        |
| Give finance a spreadsheet               | The [Reports API](https://developer.everee.com/reference/reports-api-guide), such as [Payments by Pay Date](https://developer.everee.com/reference/create-report-run-payments-by-pay-date) and [Funding](https://developer.everee.com/reference/create-report-run-funding) |

In Payroll Infrastructure:

* **Start from the run.** When `payroll-run.status-changed` says a run is `PAID` or `PARTIALLY_PAID`, read its payments, and [list the journal fundings](https://developer.everee.com/reference/list-payroll-journal-fundings) to post the new ones.
* **No tax liability line.** Everee withholds, funds and remits the company's payroll taxes, so the journal has no `Taxes` liability. Taxes withheld from wages are inside the gross wages and the cash funding, and employer taxes are `EmployerTaxes` debits.

See [Reconciling Payroll and Posting to Your GL](https://developer.everee.com/docs/reconciling-payroll-and-gl) for GL mappings, posting each funding, cost segments and common mistakes.

## Corrections after payment

To fix pay that's already been paid, or pay a worker outside the regular schedule, see [Corrections and Off-Cycle Runs](https://developer.everee.com/docs/corrections-and-off-cycle-runs).

## Tax filing and remittance

Everee handles tax remittance and filing for Payroll Infrastructure companies, along with garnishment and retirement remittance, and new hire and termination reporting. Your customers are supported directly by Everee Customer Success: transfer payroll issues to Everee. See [Everee Payroll Infrastructure](https://developer.everee.com/docs/payroll-infrastructure).