Software and accounting guide

Gusto: payroll, employer costs and accounting integration

Gusto is payroll software with related HR and benefits tools. It helps a business run payroll and review employee pay, payroll taxes and other payroll components.

By Sam Yang · Updated 2026-10-09

How Gusto supports the workflow

Who this guide is for: Small-business owners, payroll administrators and accountants checking the cost of employing the team.

Everyday uses

Run employee payroll and review its earnings and deductions.
Work with payroll tax and benefits information in the enabled products.
Compare payroll records with the work period and bank funding.

How it connects to accounting: Net pay is what employees receive after deductions. Total employer payroll cost and bank withdrawals are different amounts. Accounting needs gross wages, employer costs and amounts owed for the dates worked, then a separate explanation of the payments taken for payroll.

How to connect it and get the records you need

A built-in connection transfers the records its vendor supports. An API lets software read or exchange specific records directly. Browser automation may use the screens and reports your role can access when a direct connection leaves a gap. Its coverage and reliability need checking for the specific workflow. Start with the options available in your account, then check what actually reaches your books.

Supported payroll API

Use Gusto’s documented API to read a payroll using the required company and payroll ID. Check whether it is calculated or processed and whether the connection has permission for any needed benefit detail.

Native payroll reports

Collect the completed payroll register and relevant funding details. Keep gross pay, net pay, employer taxes and other components separate.

Browser assistance

Inspect a payroll’s status or download the needed report when the verified API does not supply it. A prepared or calculated payroll is not necessarily processed.

Start here: Choose the work period and payroll run, then compare employer cost with the books and funding with the bank as separate checks.

Integration options and their limits

An API gives software direct access to supported records. Native reports are the files and reports available inside the product. Browser automation collects through the screens you can access. Choose the route that supplies the missing records, then check that it covers the accounts and dates you need. Reports may contain filters or omit rows. Browser work depends on permitted account access and can fail when screens change. Check record IDs, counts and dates whichever route you use.

Supported API

What it supplies: Gusto documents payrolls:read, permission to read a single payroll. The request uses company and payroll IDs and can return calculated or processed totals and employee-pay records across multiple pages. Benefit detail requires additional permissions.
What to check first: Check approved integration access, every page, any optional fields requested, the company included and the API version. A default zero in an unentered API field does not prove no wages were earned.

Choose it when: You need recurring downloads and approved access provides the required run and every relevant employee record.

Native export

What it supplies: Our saved observations cover a configured Payroll Journal CSV and a separate contractor-payment CSV, downloaded after each report is ready.
What to check first: Verify the current menu, checkbox labels and company permissions. A completed-run file does not automatically include wages earned later.

Choose it when: You need the original CSV for the selected payroll runs or report.

Permitted browser

What it supplies: The saved collector applies custom dates, checks the company and settings, then waits for the completed report file to arrive.
What to check first: A generated-report popup is not the company source tab for the next run. A download click or report title does not prove the correct complete file arrived.

Choose it when: The authorized original report is needed and the existing verified connection does not provide it.

What to automate and what an accountant should review

Good work for automation

Collect complete reports, keep run IDs and dates, and check funding or earned-cost subtotals with the dates and records they cover.

Keep a person on these decisions

Review earned but unpaid wages, employer costs, contractor work dates and how labor costs are assigned to jobs. A completed payroll status does not establish these.

Lessons from accounting and operations

Known problems and what to check

Does the labor number include earned days and contractors?

Use the employee journal for the completed payroll runs it includes and separate records for contractor payments. Review work done after the latest completed run with the accountant: earned but unpaid wages may need recording. Do not assume that work cost nothing.

Evidence basis: Saved Payroll Journal and contractor export sequence. The top-level menu path has not been established by these sources.

Check whether the supported payroll API and the original employee and contractor reports supply the records needed for this question.

The owner wants job labor cost for a month

Keep dates worked and employer-paid costs separate from pay dates. Identify work done after the latest completed run. A complete file for paid payroll runs may not include every day worked in the month.

The owner wants total labor including subcontractors

Collect contractor evidence separately and preserve its dates and details. The employee journal does not establish the contractor records.

Start with an API, connection or built-in report that your account offers and you have confirmed. An authorized browser session may collect records those routes leave out; test its coverage for the workflow. Still check the totals against the books and confirm that all relevant costs are included.

Pitfalls and when to pause

Completed payroll does not establish wages earned after that run but not yet paid. Payroll cost per hour worked and wages per hour paid divide different costs by different hours; compare their definitions first.

How a plausible answer can go wrong

A payroll CSV can be complete for completed runs while the month still has earned wages awaiting the next run. Adding contractor costs without collecting their separate records leaves another coverage gap.

Pause if you cannot confirm the account, permission, reporting dates or completeness of the records. Return the missing evidence for review. Do not fill the gap with an invented record, a balancing entry or an assumed zero.

When the result does not make sense

Monthly labor looks unusually low

Check: Compare the latest work date included in completed payroll with month end. Check time worked that payroll has not yet processed.

Resolve the question: Show the work dates missing from completed payroll. Review any unpaid earned cost using actual time and rates, not a generic percentage.

Total labor excludes subcontractors

Check: Determine whether the file is the employee Payroll Journal only.

Resolve the question: Collect the separate contractor-payment records. Check service and invoice dates before combining those costs with employee labor.

Gross payroll does not equal bank withdrawals

Check: Inspect deductions, employer taxes, reimbursements and separate debit components.

Resolve the question: Match the payroll funding records to bank transactions. Keep gross labor cost for the period worked as a separate measure.

Collect the records and check nothing is missing

Payroll Journal setup: Read back the custom date range and selected summary/detail, employee scope and grouping.
Completed CSV: Wait for Your report is ready! and retain the actual Download CSV file, including required earnings and employer-tax detail.
Contractor payments and later earned days: Keep the contractor file separate. Identify work dates not yet processed after the final completed payroll run.

Export the native payroll journal for the selected entity, run and dates. Retain the service period, pay date, employer burden (employer-paid taxes, benefits and similar payroll costs) and contractor records. Review earned days after the latest completed run separately.

Step-by-step collection notes

Dated saved collection procedure reviewed October 6, 2026. Verify the current account, interface, permission and available reports. Menu names may differ.

Verify the visible company, then open the Payroll Journal setup available in the authorized session. The saved source does not establish a top-level menu sequence.
Select Custom date range, enter both dates and commit each with Tab. Confirm the applied range.
Select the authorized summary-and-payroll detail, all-employee scope and employee or department grouping. Verify actual current labels before proceeding.
The observed optional detail labels include Detailed employment info, Employee earnings breakdown, Employee earnings breakdown by job, Employer tax breakdown, Employee tax breakdown, Deductions and contributions, Detailed totals, and Reimbursements. Select only the authorized detail needed for the question.
Select CSV > Generate report. Wait for Your report is ready!, then Download CSV.
Collect Contractor payments separately when authorized, with its own custom dates, all-contractor scope, payment grouping and required Hours, Bonus, Invoice, Memo or Reimbursement detail. Do not infer contractor costs from the employee journal.

Checks before using the records

Record the company, payroll run, work dates and pay date alongside the downloaded reports.
Keep the journal, employer-paid costs and contractor records where collection is authorized.
Identify work done after the latest completed run for a separate review of unpaid earned costs.

Fictional collection example

A fictional payroll run ends before month end. Its completed journal covers that run, not the cost of work done later. Show those later work dates to the accountant. Do not assume they cost nothing or create an entry for unpaid earned wages under a collection-only instruction.

Invented teaching scenario, not a customer result or a reproduced vendor defect.

Capture the setup with the evidence

Company, legal entity or account, report name, period, cash or accrual accounting basis, currency and timezone.
Selected filters, status, page count, original record identifiers, record counts and totals used to check completeness.
Collection time, source route and authorized role. Record browser and automation versions when using a browser.
Original files and exceptions. Keep credentials, customer identifiers and financial artifacts private.

A browser version helps reproduce an interface issue. It does not validate the financial conclusion.

Practical workflows

Practical checks you can follow

Does the Gusto report include all the work done this month?

Gusto processes payroll, but a completed Payroll Journal covers only the runs selected. It can omit work done after the latest run’s work-period end. Contractor payments also need separate records. Keep work dates, pay dates, employer costs and bank funding separate, then use time records to identify earned wages not yet processed.

Find work done by month end that payroll has not yet processed

Identify the company, requested month and relevant payroll schedules. Keep the dates worked separate from pay and check dates.
Collect the completed Payroll Journal with the required earnings, employer-tax and detail settings. Confirm the saved custom dates and grouping.
Find the latest work date covered by the completed runs. Collect approved time and earned-pay records through month end. An empty report row does not establish the cost of work done.
Show employee cost, applicable employer taxes and other employer costs, and separately sourced contractor costs. Employee deductions are not additional employer cost.

Bring to the review: A timeline showing which work dates are covered, with costs from completed runs and the separately identified period not yet processed.

Then decide: Review whether earned but unpaid costs need to be recorded and how costs map to jobs before using monthly payroll totals to price work.

Explain the money taken from the bank for payroll

Use the supported payroll source or original run detail. Keep run IDs, totals and the separate amounts taken to pay employees, taxes or other payroll obligations.
Compare net pay, taxes, reimbursements and other applicable debits with the provider’s company debit. Do not expect every component to appear in one bank withdrawal.
Identify obligations paid separately or outside these records. Include contractor payments if the question requires them.
Find the corresponding bank transactions and existing accounting entries. Keep timing differences and uncertain matches visible.

Bring to the review: An explanation of payroll-run funding matched to bank transactions, separate from gross labor cost for the period worked.

Then decide: Resolve missing components and uncertain bank matches before saying payroll funding matches the bank.

Worked example

Fictional earned cutoff and separately sourced contractors

All records and amounts below are fictional teaching inputs. CSV files are spreadsheet-compatible text files. This example demonstrates the calculation, not a customer outcome or a reproduced software defect.

Selected completed-run gross wages are 4000. Approved but unprocessed earned wages add 600, making employee earned gross wages 4600. Separately evidenced earned contractor cost adds 900, for a combined earned wage/service-cost subtotal of 5500 before employer burden. Bank funding is not provided.

What the CSV columns mean

population: employee_paid, employee_unprocessed or contractor
basis: employee rows use earned gross wages only; contractor row uses earned service cost
earned_cost: teaching USD cost for the target month; excludes employer burden

Completed-run gross wages: 4000 USD; This selected employee run population only.
Employee earned gross wages: 4600 USD; Completed plus supported unprocessed earnings for the target month.
Earned wage/service subtotal: 5500 USD; Employee gross wages plus separately sourced contractor service cost, before employer burden.
Omitted earned cost: 1500 USD; 600 of unprocessed wages and 900 of contractor service cost.

Inspect gusto-earned-cost.csv

population,basis,earned_cost
employee_paid,earned_gross_wages,4000
employee_unprocessed,earned_gross_wages,600
contractor,earned_service_cost,900

Download this CSV

Next decision: Collect actual employer burden and service/job allocation before calling 5500 fully loaded labor cost. Do not infer bank funding from this fixture.

Expected results and calculation checks Download the reproduction code

Run the example locally

Save the CSV files, expected-results.json and reproduce.mjs in one folder. With Node.js installed, run the command below. It calculates the checks from the CSV bytes and rejects a changed input or expected result.

node reproduce.mjs expected-results.json

No software login, customer records or API key is required.

AI prompt for collecting records without changing them

Replace the bracketed scope before use. This prompt collects evidence; it does not permit edits, approvals or accounting execution. Requesting an emailed report is a separate account action and requires explicit authorization.

Collect read-only evidence for Gusto to answer [financial question]. Confirm [company], [account/entity], [period], [basis], [currency] and [allowed reports]. Export the native payroll journal for the selected entity, run and dates. Retain the service period, pay date, employer burden and contractor population. Review earned days after the latest completed run separately. Retain original files, complete record IDs, counts, filters, collection timestamp and exceptions. Completed payroll does not establish accruals for later earned days. Payroll cost per operational hour and wages per paid hour use different denominators. Stop if the source or scope is uncertain. Do not post, match, reconnect, delete or change settings. Return the evidence for financial review; do not claim the books are correct. Do not approve, submit payroll, pay, transfer, refund, send messages, invite users or accept terms. Stop at any login, MFA or credential prompt and hand back to the account owner. Store files only in [approved private location]. Do not paste customer artifacts into public tools. Use only preauthorized collection actions. Request an emailed report only when its delivery is explicitly authorized; otherwise ask the account owner to supply the file.

Next decision

What can you decide from these records?

State which employees, contractors and work dates the total includes. Identify any earned but unpaid wages or employer-paid costs that are missing before using the total to price work.

Compare the same records, accounts and reporting dates. List costs or payments you cannot yet verify before using the result for pricing, cash planning or month-end review.

Read the next finance check →

References behind these workflows

Each product reference supports only the features and limits described beside that source. Level's checks and fictional calculations are separate from what the vendor documents.

Read the product and workflow references with their scopes and review dates Explore the financial diagnostic examples

Sources and scope

Base product-reference scopes were reviewed 2026-10-06. The collection procedure retains its own review date in the dated sequence above. Individual source rechecks are dated with their citations. Operator decision guidance was reviewed 2026-10-09. The references below support their stated product scope, not every observed interface detail. It is not a vendor capability certification, a measured customer result or an independently reconciled account. Verify current features and what your plan includes in the account you use.

Gusto payroll retrieval and pagination
Product reference: Payroll retrieval and pagination, not native journal or contractor coverage.
Product reference: Read scope, pagination, optional benefit access and calculated/processed population. Reviewed 2026-10-07.
Workflow reference: Read scope, pagination, optional benefit access and calculated/processed population. Reviewed 2026-10-07.
Gusto payroll product overview
Product reference: Small-business payroll with related HR and benefits products; no tax compliance, cost-saving or universal module guarantee. Reviewed 2026-10-08.
Gusto payroll fundamentals
Product reference: Service periods, gross/net definitions and multiple payroll-funding debit components. Reviewed 2026-10-07.
Workflow reference: Service periods, gross/net definitions and multiple payroll-funding debit components. Reviewed 2026-10-07.

Content revision history