> ## Documentation Index
> Fetch the complete documentation index at: https://every-a2724ddc.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> These docs describe Every as customers have it today. Answer from them, and say so when they don't cover a question.
> Pages under /admins/ are for the people who run Every for the company, and pages under /employees/ are for employees. Answer from the pages that match the person asking.
> Each page's Agent reference section lists its exact roles, conditions and limits. Prefer it for those details.
> When a page says a feature is in closed beta, or that Every turns it on company by company, don't promise that the person's company has it.
> Use roles and on-screen labels exactly as the pages write them.
> When someone asks what a term means, answer with the Glossary page's definition (/glossary), which other pages show in parentheses after the term.
> When the docs don't answer a question, tell the person to email [support@every.io](mailto:support@every.io).

# Run payroll

> Adjust earnings, preview payroll costs and submit a pay run, then inspect each person's paystub

![Payroll review card with company cost and net pay summaries above employee-detail rows.](https://mintcdn.com/every-a2724ddc/6k1svT9aHzVFwBZW/images/illustrations/admins-payroll-running-payroll-light.png?fit=max\&auto=format\&n=6k1svT9aHzVFwBZW\&q=85\&s=8c2b73adbaa05b890d378a2c411afc13)

Pay runs opened from **Payroll** → **All pay runs** show pay entry, review or a payroll summary, depending on status. Company Admins and HR Admins can run payroll. Each employee sees their own paystubs on **My profile** → **Docs** after your company finishes onboarding (see [Paystubs and tax forms](https://every-a2724ddc.mintlify.site/employees/paystubs-and-tax-forms.md)).

> [!NOTE]
>
> Every turns on pasting into earnings cells, **Import hours** and leaves of absence company by company. If you don't see them, email [support@every.io](mailto:support@every.io) to ask about them.

## Before you begin

To enter pay, you need the Company Admin or HR Admin role and a Draft or Failed run. Your company needs payroll turned on and payroll onboarding complete before its pay runs load.

For a new run outside the regular schedule, first [create an off-cycle or bonus pay run](https://every-a2724ddc.mintlify.site/admins/payroll/off-cycle-payroll.md). For an employee's last paycheck, use [Run a termination payroll](https://every-a2724ddc.mintlify.site/admins/payroll/termination-payroll.md).

Have enough money available in your Every checking account by the run's **Run by** date. For your first payroll, send money to that account even if you selected **Plaid** during payroll funding setup.

## Adjust and submit a run

**1. Open the run**

On **Payroll** → **All pay runs**, select a Draft or Failed run.

**2. Check the run**

Review the run's dates: **Run by** is the due date and **Pay day** is the payday. The page also shows the number of employees and their total gross pay (What an employee earns before taxes and deductions come out).

**3. Open a person's pay details**

On **Earnings: Full Time** or **Earnings: Part Time**, select a person.

The tabs follow compensation frequency: nonhourly people are on **Earnings: Full Time**, and hourly people are on **Earnings: Part Time**. Contractors are on the same tabs. For contractors, overtime entry is disabled and there's no supplemental bonus entry.

**4. Enter pay**

In the pay details, enter the salary amount or hours for the run. On an earnings tab, you can also paste values into editable cells, or import hours for eligible hourly people from a CSV (see [Import hourly pay](#import-hourly-pay)).

**5. Save the pay details**

Select **Save**.

**6. Check deductions**

Review **Deductions**. Amounts are read-only. To manage company or individual deductions, see [Deductions](https://every-a2724ddc.mintlify.site/admins/payroll/deductions.md).

**7. Preview payroll**

Select **Preview payroll**. Without autopilot, the run shows Processing, then Pending once the preview succeeds.

**8. Confirm a manual run**

On an autopilot run, in the "Would you like to submit manually?" dialog, select **Proceed** to turn off autopilot for this run. The run shows Processing, then Pending once the preview succeeds.

**9. Review the totals**

Review **Total debited today**, **Direct deposits** and the tax totals. **Total debited today** is the total company cost of the run's paystubs. To ask when the debit posts, email [support@every.io](mailto:support@every.io).

**10. Inspect taxes**

Optional: point to a nonzero **Employee taxes** or **Company taxes** total to see its breakdown.

**11. Review each person's amounts**

Select **Company cost** or **Net pay** to see each person's amounts.

**Back** returns a Pending run to Draft for changes.

**12. Submit the run**

Select **Submit & schedule** when the run is Pending and the amounts are ready. The run changes to Submitted and opens its summary.

Select **Continue later** to leave an unfinished run and return to **All pay runs**.

![A Draft pay run on pay entry, with its dates, employee count and total gross pay above the Earnings tabs.](https://mintcdn.com/every-a2724ddc/lWATgPF1EqKKYfej/images/screens/admins-payroll-running-payroll-light.png?fit=max\&auto=format\&n=lWATgPF1EqKKYfej\&q=85\&s=6f811d37c7df7fd8ca79464bdc631292)

![A pay run in review, with Total debited today, Direct deposits and the tax totals above Company cost and Net pay.](https://mintcdn.com/every-a2724ddc/lWATgPF1EqKKYfej/images/screens/admins-payroll-running-payroll-review-light.png?fit=max\&auto=format\&n=lWATgPF1EqKKYfej\&q=85\&s=e57916ffb7a798b4291a2f1edc363930)

### Exclude a person

On a Draft run's earnings tab, you can select only rows with pay entered, completed onboarding and required information.

1. Select the person's row checkbox.
2. Select **Exclude**.

Every leaves the person out of this run, including its **Deductions** tab.

### Change pay run settings

On a Draft or Failed run:

**1. Open the settings**

Select **Payroll settings**.

**2. Change the fields**

Change any of these fields:

* On any run: **Pay day**, **Bonus tax rate** and **Salary overtime exempt**
* On runs other than regular runs, also: **Pay run name**, **Start date** and **End date**

**3. Save the settings**

Select **Save**.

![A pay run's Payroll settings sheet, with the pay day, bonus tax rate and salary overtime exempt fields and Save.](https://mintcdn.com/every-a2724ddc/lWATgPF1EqKKYfej/images/screens/admins-payroll-running-payroll-settings-light.png?fit=max\&auto=format\&n=lWATgPF1EqKKYfej\&q=85\&s=e1ad5f7d432c7fff0aa82a41ec0d8c9e)

**Salary overtime exempt** chooses whether you enter hours or an amount for salaried people who are exempt from overtime. In the **Payroll settings** sheet, **Open settings** opens your company's [Payroll settings](https://every-a2724ddc.mintlify.site/admins/payroll/settings.md).

**Add people** is available on Draft or Failed runs other than regular runs. To create these runs and add people, see [Create an off-cycle or bonus pay run](https://every-a2724ddc.mintlify.site/admins/payroll/off-cycle-payroll.md) and [Run a termination payroll](https://every-a2724ddc.mintlify.site/admins/payroll/termination-payroll.md).

## New hires and partial-period pay

When a new hire finishes onboarding with a pay schedule, Every checks the regular run covering their start date. If that run is Draft, Every generates the new hire's pay in that run.

If the covering run is no longer Draft, Every creates a separate Draft catch-up run for that period. The catch-up run uses the new hire's name and has autopilot turned off. Review and submit the catch-up run through the same steps as another pay run.

Every prorates partial-period base salary by working days, whether or not the person is exempt from overtime:

Normal pay for the period ÷ working days in the full period × the employee's counted working days.

Counted days are working days inside the pay period (The dates an employee's pay covers, such as two weeks or a calendar month), between the employee's start and end dates, while their compensation is in effect. Days recorded as inactive are excluded.

On regular runs, recorded leave-of-absence periods that overlap the run can reduce the counted working days. A canceled leave doesn't reduce the count.

## Import hourly pay

You can import a CSV for hourly people using **Single entry** or **Untracked** timesheets. Hourly people with no timesheet type set are also included. People using **Daily entry** timesheets are excluded.

The person's hire must be approved and they must be included in the run.

**1. Open the import**

On **Earnings: Part Time**, select **Import hours**.

**2. Download the template**

Select **Download template**.

**3. Fill in the hours**

Keep the employee IDs and names in the template, then enter each person's hours. Use one row per employee and numeric, nonnegative hours.

**4. Choose the file**

Select the filled-in CSV file.

**5. Open the review**

Select **Continue** to upload the file and review the matches.

**6. Review the matches**

Review **Potential issues** and **Successful match**.

**7. Inspect a row warning**

Optional: point to the warning marker beside an employee ID to see that row's message.

**8. Submit hours**

With at least one valid row, select **Submit hours**. The result shows successful imports, failed imports and imported hours. Skipped rows count as failed imports.

**9. Return to the run**

Select **Back to payroll** to inspect the run's hours and totals.

## What happens next

A Submitted or completed run shows its payroll summary. The header calls a completed run Complete; **All pay runs** labels the same state Paid. Select a person to inspect their paystub, including gross pay, taxes, deductions, company contributions and net pay (What an employee takes home after taxes and deductions).

![A completed pay run's summary, with its overview of totals debited, gross pay, taxes, deductions and net pay.](https://mintcdn.com/every-a2724ddc/lWATgPF1EqKKYfej/images/screens/admins-payroll-running-payroll-summary-light.png?fit=max\&auto=format\&n=lWATgPF1EqKKYfej\&q=85\&s=20474c1932c49c6218da0f513f654ddb)

On a Submitted run, **Make changes** is available only before its due date.

1. On the run's summary, select **Make changes**.
2. On an autopilot run, in the "Disable autopilot to make changes" dialog, select **Confirm**.

The run returns to Draft. Follow [Adjust and submit a run](https://every-a2724ddc.mintlify.site/admins/payroll/running-payroll.md#adjust-and-submit-a-run) again.

### Sync payroll to QuickBooks

Syncing a completed run requires QuickBooks to be connected with the **Every Bank Account** and **Reimbursement** defaults set. The required payroll categories must also be mapped (see [Accounting settings](https://every-a2724ddc.mintlify.site/admins/settings/accounting.md)).

With the connection and defaults ready, **Finish QuickBooks setup** on the run's summary appears if categories are missing. It opens **Settings** → **Accounting**. The HR Admin role on its own can't open that page, so ask a Company Admin to finish the mappings.

On the completed run's summary, select **Quickbooks Sync Now**.

If the sync fails, on the completed run's summary, select **Retry Quickbooks Sync**.

## Troubleshoot a run

* For "Payroll run not found", on **Payroll** → **All pay runs**, select an existing run. For "Error loading payroll run" or "Something went wrong loading this payroll.", refresh the page.
* For "Pay day is too soon. Choose a pay day at least 3 business days from today.", in the run's **Payroll settings** sheet, select a **Pay day** at least 3 business days away.
* For "Import failed", select **Start over** to begin another upload.

### Failed or delayed payroll

If your Every checking account doesn't have enough available money to cover the run, the run can show Failed. Before you submit it again, email [support@every.io](mailto:support@every.io) to ask how to cover the shortfall and resume the run.

On **Payroll** → **All pay runs**, check the run's status and payday. If **Payroll overdue** appears, tell employees that payday is delayed.

If an employee hasn't received a deposit on payday, open the Submitted or completed run's summary and select the person to review their paystub. Email [support@every.io](mailto:support@every.io) to ask about the missing deposit.

## Agent reference

**Where:** **Payroll** → **All pay runs**, then select a pay-run row. The run opens pay entry, review or the payroll summary according to status.

**Who:** Company Admins and HR Admins at a company with payroll turned on. Real run rows load on **All pay runs** after payroll onboarding is complete. A people-manager relationship alone does not grant access to **Payroll**.

### Facts

* Draft and Failed runs opened from **Payroll** → **All pay runs** show pay entry. Pending and Processing runs show review. Submitted and Complete runs show the payroll summary.
* A completed pay run has the header status Complete. **Payroll** → **All pay runs** labels the same status Paid.
* Pay entry for a run opened from **Payroll** → **All pay runs** shows **Run by**, the run's due date, plus **Pay day**, **Employees** and **Total gross pay**.
* Arrange enough available money in your Every checking account by the pay run's **Run by** date. For the company's first payroll, send money to your Every checking account even when **Plaid** was selected in payroll funding setup.
* In payroll review, **Total debited today** is calculated from the run's paystubs. Email [support@every.io](mailto:support@every.io) to ask when a payroll debit will post.
* A pay run can become Failed when the available money in your Every checking account does not cover the outstanding payroll payments. Email [support@every.io](mailto:support@every.io) before resubmitting to ask how to resolve the shortfall and resume the run.
* When **Payroll overdue** appears on **Payroll** → **All pay runs**, tell employees that payday is delayed. Check the run's displayed payday rather than relying on a previously planned date.
* For an employee's missing payroll deposit, open the Submitted or completed pay-run summary on **Payroll** → **All pay runs**, select the person to review their paystub and email [support@every.io](mailto:support@every.io) to ask about the deposit.
* **Earnings: Full Time** in a pay run contains people with nonhourly compensation. **Earnings: Part Time** contains people with hourly compensation. Contractors use the same earnings tabs according to compensation frequency.
* Selecting an eligible earnings row in a pay run opens the person's pay details. **Regular pay** holds base pay; hourly details include regular, overtime and double-overtime inputs where the person is eligible. **Save** saves the pay details.
* Contractor pay details in a pay run disable overtime and double-overtime inputs and omit supplemental bonus entry. Contractors do not appear on the run's **Deductions** tab.
* **Deductions** in a pay run contains included employees only and shows read-only benefit and post-tax deduction amounts. [Deductions](https://every-a2724ddc.mintlify.site/admins/payroll/deductions.md) covers managing company plans and individual deductions.
* On an earnings tab in a Draft pay run opened from **Payroll** → **All pay runs**, select eligible rows. Then select **Exclude** to leave those people out of the run. Selection requires pay entered, completed onboarding and required information. Selection is unavailable on **Deductions** and outside Draft status.
* **Preview payroll** on a Draft or Failed run without autopilot changes the status to Processing. An autopilot run opens the manual-preview confirmation before the status changes. A successful preview changes the pay run from Processing to Pending. Review shows **Total debited today**, **Direct deposits**, **Employee taxes** and **Company taxes**. Pointing to **Employee taxes** or **Company taxes** shows a breakdown of nonzero amounts. A tax total with no nonzero amounts has no breakdown.
* An autopilot run's **Preview payroll** action asks "Would you like to submit manually?" **Proceed** turns autopilot off for the current run while starting manual preview.
* **Company cost** and **Net pay** in payroll review show per-person amounts. **Back** on a Pending run returns the run to Draft. **Submit & schedule** on a Pending run changes the status to Submitted.
* **Continue later** in an unfinished pay run returns to **Payroll** → **All pay runs**.
* **Payroll settings** is available in a Draft or Failed run. Regular runs allow changes to **Pay day**, **Bonus tax rate** and **Salary overtime exempt**. Runs other than regular runs also allow **Pay run name**, **Start date** and **End date**. Select **Save** to save the settings.
* **Salary overtime exempt** in a run's **Payroll settings** chooses hours or an amount for salaried people who are exempt from overtime. **Open settings** opens company **Settings** → **Payroll**.
* **Add people** is enabled for Draft or Failed runs other than regular runs and disabled for regular runs. Creation and employee selection are covered in [Create an off-cycle or bonus pay run](https://every-a2724ddc.mintlify.site/admins/payroll/off-cycle-payroll.md) and [Run a termination payroll](https://every-a2724ddc.mintlify.site/admins/payroll/termination-payroll.md).
* Every turns on pasting into earnings cells and **Import hours** company by company. Editable earnings cells in a pay run accept pasted values. Companies with hours import access see **Import hours** on **Earnings: Part Time**.
* The hours import opened from a pay run uses **Download template**, CSV upload, **Continue**, review and **Submit hours**. The template contains employee IDs, names and a blank hours column.
* The hours template and import for a pay run include only hourly people using **Single entry** or **Untracked** timesheets or no timesheet type set. The person's hire must be approved, and the person must be included in the run. **Daily entry** rows fail with "No matching hourly employee in this payroll".
* Hours-import rows require one employee ID per row without duplicate employees and numeric, nonnegative hours. Review groups rows under **Potential issues** or **Successful match**, with a check or warning marker beside each employee ID. Point to a warning marker to see the row's message.
* **Submit hours** in a pay run's hours import requires at least one valid row. The result is **Success** or **Import completed with issues** and shows **Successful imports**, **Failed imports** and **Imported hours**. Skipped and failed rows count together as **Failed imports**. **Back to payroll** returns to the run.
* Selecting an employee in a Submitted or completed pay-run summary opens the person's paystub sheet with gross pay, employee taxes, company taxes, employee deductions, company contributions and net pay.
* **Make changes** on a Submitted pay-run summary is available before the run's due date. **Make changes** isn't offered on or after the due date. Without autopilot, the action returns the run to Draft. On an autopilot run, the "Disable autopilot to make changes" dialog opens. In that dialog, select **Confirm** to return the run to Draft. Complete pay-run summaries do not offer **Make changes**.
* On a Complete pay-run summary, QuickBooks sync requires a connection, the **Every Bank Account** and **Reimbursement** defaults set and the required payroll categories mapped. **Quickbooks Sync Now** requests journal entries; **Retry Quickbooks Sync** retries after a failed sync.
* **Finish QuickBooks setup** on a completed pay-run summary opens **Settings** → **Accounting** when QuickBooks is connected, the **Every Bank Account** and **Reimbursement** defaults are set and payroll category mappings are missing. Company Admins and HR Admins can open the pay run. Company Admins and Bookkeepers can complete the mappings in **Settings** → **Accounting**; the HR Admin role on its own can't open that page. A Bookkeeper, who can't open the pay run, opens **Settings** → **Accounting** directly.
* A missing run opened from **Payroll** → **All pay runs** shows "Payroll run not found". To open an existing run, on **Payroll** → **All pay runs**, select its row. When a pay run fails to load, the page shows "Error loading payroll run". For "Something went wrong loading this payroll.", refresh the page.
* In a pay run's **Payroll settings**, a **Pay day** whose due date would be in the past is rejected with "Pay day is too soon. Choose a pay day at least 3 business days from today."
* A failed CSV hours import from a pay run shows "Import failed" and offers **Start over**.
* New hires with a pay schedule are checked against the regular run covering the hire start date. A Draft regular run receives the new hire's pay items; a covering run that is no longer Draft causes a separate Draft catch-up run with autopilot turned off. The catch-up run uses the new hire's name and the covered pay period.
* Base salary on regular, termination and catch-up pay runs uses normal pay-period compensation divided by working days in the full period, multiplied by the employee's counted working days. The base salary calculation applies whether or not the person is exempt from overtime. Employment start and end dates and compensation effective dates bound the counted portion. Days recorded as inactive are excluded. Regular runs at companies with leaves of absence turned on also exclude eligible recorded leave days. The result rounds to 2 decimal places.
* On regular pay runs where Every has turned on leaves of absence for the company, recorded leave periods that overlap the run also reduce the base-salary working-day count. A canceled leave doesn't reduce the count. Days already excluded as inactive aren't subtracted twice.

### Questions people ask

* **Do I need to fund my first payroll if I selected Plaid?** Yes. Send money to your Every checking account before the first pay run, even when **Plaid** was selected during payroll funding setup.
* **What should I do if payroll fails because of insufficient funds?** Email [support@every.io](mailto:support@every.io) before submitting again. Ask how to resolve the shortfall and resume the pay run.
* **What if an employee hasn't received their deposit?** Open the Submitted or completed run's summary on **Payroll** → **All pay runs**, select the person to review their paystub and email [support@every.io](mailto:support@every.io) to ask about the deposit.
* **Why is Submit & schedule missing?** **Submit & schedule** is offered when the pay run is Pending. A Draft or Failed run first offers **Preview payroll**.
* **Can I change a regular run's dates?** Only its payday. In **Payroll settings**, a regular run's **Pay day** can change, but its name, **Start date** and **End date** can't.
* **Can I add people to a regular run?** No. **Add people** is disabled for regular runs and enabled for editable runs other than regular runs.
* **Can I edit deductions while running payroll?** No. The run's **Deductions** tab is read-only. For company plans and individual deductions, see [Deductions](https://every-a2724ddc.mintlify.site/admins/payroll/deductions.md).
* **Does a contractor need a different payroll flow?** No. Contractor rows use the same run's earnings tabs, separated by compensation frequency. The contractor pay-details sheet disables overtime inputs and omits supplemental bonus entry.
* **Can I change a completed run?** No. Complete pay-run summaries do not offer **Make changes**. A Submitted run offers **Make changes** on its summary before its due date. The action isn't offered on or after the due date. For an autopilot run, in the "Disable autopilot to make changes" dialog, select **Confirm** to return the run to Draft.
* **Why did an hours upload finish with issues?** **Import completed with issues** means some rows were not imported. **Failed imports** includes skipped and failed rows.
* **Why does a paid run say Finish QuickBooks setup?** The connection and the **Every Bank Account** and **Reimbursement** defaults are ready, but required payroll categories are missing. A Company Admin can use **Finish QuickBooks setup** on the pay-run summary to finish the mappings in **Settings** → **Accounting**. Bookkeepers can open **Settings** → **Accounting** directly. The HR Admin role on its own can't open **Settings** → **Accounting**.

### Not covered here

* When does payroll money leave your Every checking account or reach each employee, including after a failure? To ask, email [support@every.io](mailto:support@every.io).
* How do I resolve a payroll tax notice? To ask, email [support@every.io](mailto:support@every.io).
* Does my company have leaves of absence turned on? To ask, email [support@every.io](mailto:support@every.io).
* Does changing a company plan or individual deduction update a pay run that's already open? To ask, email [support@every.io](mailto:support@every.io).
* Does turning off autopilot at **Preview payroll** affect later runs on the same pay schedule? To ask, email [support@every.io](mailto:support@every.io).
* Does **Make changes** turn autopilot off for the current or later pay runs? To ask, email [support@every.io](mailto:support@every.io).


## Related topics

- [Create an off-cycle or bonus pay run](https://every-a2724ddc.mintlify.site/admins/payroll/off-cycle-payroll.md)
- [Deductions](https://every-a2724ddc.mintlify.site/admins/payroll/deductions.md)
- [Payroll and people reports](https://every-a2724ddc.mintlify.site/admins/reports/payroll-reports.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.