Payroll Software Compatible With Xero: Choose the Route, Check the Entries
Updated: 5 days ago
A payroll connection earns its place in your Xero setup when finance can explain what it posted, where the money went and how an exception gets repaired. A successful connection screen answers a smaller question: the two services can communicate. It does not show that your wage expense, liabilities, reporting detail or month-end cutoff are right.
Start with one representative payroll run and follow it into the accounting records. Keep the approved payroll report, the resulting Xero transactions and the related cash movements together. Then repeat the exercise with a changed earning, a reporting split and a failed or repeated delivery. Those results give you a basis for accepting a connector, choosing another route or budgeting for a controlled manual process.
U.S. employers using Xero accounting can use the examples below to review a proposed connection. Product names and payroll arrangements differ by country. The examples are fictional bookkeeping illustrations, and the acceptance record is a tool to use with your payroll and accounting reviewers, not a claim that any named service has been tested here.
Selecting payroll for a Xero business includes more than the accounting connection. Use SelectSoftware Reviews' free software-selection service to identify payroll candidates, then ask those vendors to demonstrate the specific Xero route.
Table of contents
Choose the actual Xero payroll route
Ask the seller to identify the product you would buy, the organization it would connect to and who runs payroll. The answer now needs more precision than “Xero works with Gusto.” Xero announced U.S. Xero Payroll, powered by Gusto, in August 2026, with payroll operated inside Xero for eligible customers. That is a different arrangement from running payroll in a separate Gusto account and sending its accounting results to Xero.
Xero's subscription guidance tells subscribers to review the payroll product's features and decide whether it fits before adding it to their plan. Confirm current account eligibility with the provider. Keep the setup instructions, support commitments and configuration choices attached to the particular route you select.
For a separate Gusto account, the published Xero connection documentation describes bills and manual journals, with availability tied to the Xero edition. It also describes selectable posting dates and consolidation settings. Treat those as configuration choices to demonstrate in the account you will use. A screenshot from another customer's organization does not establish your purchased configuration.
OnPay is another documented route. Its Xero setup guide describes a bill or manual-journal choice, account mapping, tracking categories and automatic or selected historical pay-run exports. The bill route can create different levels of detail and approval states. Ask the demonstrator to show which choices are included for your Xero subscription and payroll setup, rather than treating every connection as an identical journal feed.
A controlled export and import can also be a workable accounting route when the payroll service provides suitable reports and Xero supports the intended import. Confirm the actual file and import method before selecting it. Assign preparation, review and duplicate prevention to named people; “manual fallback available” is incomplete without that work being designed.
Keep the shortlist tied to the workload. A straightforward business may value a simpler supported route. A company needing several reporting dimensions, unusual deductions or complex corrections needs evidence at those points before it can judge convenience. Judge each payroll route by the evidence your finance team needs to approve and maintain the accounting result.
Specify the accounting object before the connection
Write down whether the result is a bill, a manual journal or a set of entries with separate payment records. Include its initial status: draft, approved, posted or another state shown by the product. Identify who performs any remaining approval. “Sent” and “available in a report” can describe different stages of the accounting process.
Xero's developer guidance describes payroll integration through manual journals or accounts-payable bills. Neither label establishes the whole bookkeeping treatment. An imported bill may interact with payment entries and a bank reconciliation; a journal may require a clearing-account treatment. Have the accounting reviewer explain the complete path for the proposed configuration, including liabilities the connector does not separately represent.
Choose the Xero organization deliberately. Record its legal entity and organization identity, the payroll company and the bank account used for funding. Similar organization names are an avoidable source of mistakes. Ask who can connect, disconnect or change the integration, and what happens when the person who authorized it leaves. Use authorized accounts and the service's supported access controls; do not share one person's login as the continuity plan.
Agree on a mapping version before sending the representative run. For each relevant earning, employer cost, deduction, reimbursement and settlement amount, specify the destination account and any separate adjustment. Distinguish employee deductions from employer benefit expenses. They may relate to the same benefit but represent different accounting amounts.
An automatically suggested account is a starting point for review. Check the account's purpose and type with finance, not just its familiar name. Also test an item introduced after initial setup. Gusto's documentation says optional default mappings can route new categories, while detailed mappings are required. A new earning that silently lands in an overly broad account can produce a technically successful sync and a weak report.
A balanced journal can still misstate payroll
Balancing debits and credits checks arithmetic. It does not establish completeness, the correct period or the absence of a second entry. Compare the accounting result with the approved payroll report before looking for a convenient bank-feed match. Otherwise an apparently tidy cash reconciliation can conceal omitted costs or duplicate expense.
Consider a fictional run with $12,000 of gross wages, $900 of employer payroll taxes, $2,500 of employee tax withholding and $500 of employee benefit deductions. Net pay is $9,000: $12,000 minus $2,500 minus $500. Assume no other items, fees or employer benefit contributions. Total payroll expense in this simplified illustration is $12,900, not the $9,000 employees receive.
One illustrative accrual entry debits wage expense $12,000 and employer tax expense $900. It credits net-pay clearing $9,000, tax liabilities $3,400 and benefit deductions payable $500. Both sides total $12,900. The $3,400 combines employee withholding and employer taxes for this example; your actual accounts and provider settlement may separate them. This is not a claim that a named connector produces this entry.
Suppose the employer's bank then shows a $9,000 net-pay withdrawal, a $3,400 tax withdrawal and a later $500 benefits payment. Finance needs to account for how those movements settle the recorded amounts. Creating a fresh $9,000 wage expense from the bank feed after the original payroll expense was recorded would duplicate that portion of the expense. Matching or clearing must follow the approved accounting design.
Now change the example: the provider withdraws one combined amount, charges a service fee separately or retains funds before settlement. The bank totals no longer line up with the same individual lines. Obtain the provider's withdrawal breakdown and show the bridge. Do not force an unexplained difference into payroll expense to make the screen reconcile.
Keep three comparisons visible: payroll amounts to accounting amounts, accounting balances to their settlement evidence, and the expected transaction set to what actually exists. Differences need an explanation tied to a specific item. A reconciliation policy may define who investigates timing and rounding, but it should not let an unexplained posting difference disappear merely because the total is small.
The example separates payroll expense from settlement. The bank movement must be matched to the recorded obligation without creating the same expense again.
Prove the reporting detail your finance team uses
A correct total can still land entirely in the wrong department. Before the demonstration, choose one report finance actually uses and identify the detail it needs. Examples include wages by location, labor cost by service team or employer costs by department. Ask whether the desired result belongs in account codes, tracking categories, payroll reports or a separate allocation process.
Use a split that would expose missing detail. In a fictional example, the $12,000 wage total belongs $7,200 to Production and $4,800 to Administration under the employer's approved allocation. A result showing $12,000 in an unassigned category fails that requirement even though the overall wage account is correct. If employer taxes are also allocated 60/40 by policy, the $900 illustration becomes $540 and $360. That allocation is an assumption, not a tax calculation rule.
Inspect both the posted lines and the resulting report. A payroll department name in the source file does not prove the corresponding Xero report can filter it. Test a person who changes departments or works in two assignments during the same pay period. Determine whether the connection carries a split, uses one assignment or requires a reviewed allocation outside the feed.
Gusto's separate connector currently describes one consolidation method and one Xero tracking category per consolidated grouping. Its project consolidation uses Gusto projects and does not integrate with Xero Projects. If you need combined department-and-project reporting, request a demonstration of that exact result instead of assuming a feature named “projects” satisfies it.
More detail also creates a confidentiality choice. Employee-level entries can reveal compensation to people with accounting access. Decide which users need that detail and whether summarized postings plus restricted payroll reports meet the need better. Test ordinary users' views as well as the administrator's. Keep sensitive sample reports within the authorized review group, using synthetic data wherever a safe demonstration permits it.
Put payroll and accounting dates on the same receipt
Record the pay-period dates, employee pay date, employer funding date and accounting entry date separately. Then identify which one drives the connector's posting date. These dates can differ legitimately, but the differences must fit the accounting policy and reporting period. The moment data arrived in Xero is another date; it is not automatically the period to which the cost belongs.
Consider a fictional pay period ending September 30, with wages paid October 2 and funding withdrawn October 1. A pay-date posting lands in October. Finance may need a September accrual under its accounting policy. An end-of-period setting may produce a different result. Show which amount the integration records and how any separate accrual is reversed or otherwise reconciled so the same wages are not expensed twice.
Do not assume that choosing a date setting calculates a complete accrual. A period spanning two months may need an allocation the payroll feed does not provide. Ask the accountant to state the treatment and evidence required. Save the approved date setting and an example report across the boundary, rather than documenting only that the payroll appeared eventually.
Check the interaction with a closed accounting period before go-live. Agree who decides whether a correction affects an earlier period, requires a current-period adjustment or needs the period reopened under the organization's policy. The payroll operator should not discover that decision while repeatedly trying to sync an entry rejected by an accounting lock.
During a payroll provider switch, define the earliest run the new connection may send and the latest run already recorded through the previous route. Historical exports deserve the same attention as the first new run. A convenient backfill can recreate transactions finance entered during implementation. Preserve a list of covered runs and the corresponding Xero records before enabling automatic delivery.
An integration limitation may change which payroll services belong on your shortlist. For free software-selection guidance, you can speak with SelectSoftware Reviews. Ask the shortlisted vendors to substantiate their own accounting and support capabilities.
Find the existing entry before sending a retry
A timeout can mean the request failed, the response was lost or the accounting entry exists while its receipt is missing. Before retrying, search for the original run and inspect any resulting transaction. Record the payroll reference, destination IDs, status and amount. Avoid using only a date and total when two legitimate runs could share them.
Ask the provider to explain how its supported retry behaves. Does it update an existing entry, create another one, reject a repeat or need an operator to choose? Demonstrate the answer in a safe test environment where available. If a supported live exception is the only evidence available, agree the safeguards with the provider and accounting reviewer before acting. Do not deliberately disrupt a real payday to test a connector.
Gusto documents that journal re-sync updates the existing journal, while changing transaction type creates a new transaction and requires treatment of the earlier bill or journal to avoid duplicates. That is a reason to obtain route-specific repair instructions. It is not permission to reverse an entry or remove a bank match without accounting review.
If finance creates a manual replacement during an outage, give the run an explicit manual-posted status and retain its Xero IDs. Assign one owner to prevent the automatic feed from later creating the same accounting result. The repair is complete when the record explains which entry remains authoritative, which entry was corrected and how settlement now ties out.
Separate accounting delivery from employee payment. An accounting sync error does not, by itself, prove wages failed to arrive. Likewise, fixing a journal does not authorize a second wage payment. Investigate payroll delivery using its own evidence and deadlines. Keep the bookkeeping workaround from accidentally becoming a duplicate cash disbursement.
Search for the accounting result before another send. Keep both original and replacement references, and investigate employee payment separately.
Complete a Xero Posting Receipt
Copy the following receipt for each acceptance run. Attach evidence or restricted-access references in the blanks. Use an ordinary run plus the exceptions relevant to your business; a clean normal run alone cannot approve an untested reporting split or recovery route. Keep the record short enough that another reviewer can follow the money without repeating the demonstration.
Run identity: ______. Record the payroll company, run reference, pay-period range and pay date. Include the approved report version and identify whether this is a demonstration, test run or actual payroll. Do not put employee bank details or full tax identifiers in the receipt.
Connection scope: ______. Name the purchased payroll product, Xero organization, connector or import route, accounting object type and initial status. Reference the account permissions and the approved mapping version, including defaults for newly introduced items.
Accounting output: ______. List the destination transaction IDs and status for every expected object. Attach the posted lines or equivalent evidence and explain any difference between the expected and actual number of entries. A successful transmission message is supporting evidence, not the output itself.
Amount bridge: ______. Record gross wages, employer costs, deductions, net pay and the expected accounting totals for this run. Explain provider fees and amounts handled outside the feed. Identify the exact line responsible for any variance rather than recording only “balanced.”
Reporting result: ______. Name the report and required categories, and attach the demonstrated split. State any limitation on employee, department, job, location or project detail. If a separate allocation is required, identify its preparer and review evidence.
Period treatment: ______. Record the source dates, actual posting date and accounting period. Reference any accrual, reversal or historical-backfill boundary. Include the approved response if the intended period is locked.
Cash settlement: ______. Reference the bank withdrawals and provider breakdown that explain settlement. Identify outstanding clearing or liability balances and their expected resolution dates. A remaining balance needs a reason and an owner, not an automatic zero-balance adjustment.
Recovery result: ______. Describe the tested or provider-confirmed retry and correction behavior, the retained destination entry and any manual fallback. Show how a repeated send or a late automatic delivery is prevented from duplicating a manual posting.
Reviewer decision: ______. Choose Accept, Accept with documented recurring work, or Do not enable. Name the reviewer, unresolved issue owners and the next check date. Required evidence missing means the relevant requirement is unproven; do not average it away with strengths elsewhere.
Run the acceptance session without moving real money
Agree with the provider which demonstration or test facilities are supported and what they can establish. Some screens can show mapping without creating a transaction; others may require a real connected organization. Identify the limit before the session. Do not submit fictitious employees, tax filings or bank instructions into live payroll merely to obtain an accounting example.
Give the demonstrator a small request list: the ordinary run, one newly introduced earning or deduction, a required allocation, a month boundary and a repeat-delivery or correction explanation. Use synthetic values where appropriate. Include only exceptions your business actually needs, such as manual checks, reimbursements, contractors or voided payroll. Ask what is unsupported and which team would handle it.
For each result, distinguish observed evidence from a promise. “Shown in demonstration,” “confirmed in current support documentation” and “not yet verified in our organization” are different statuses. If a seller cannot safely demonstrate a recovery, ask for the documented process and a supported validation plan. Record the remaining risk instead of writing that the connector passed.
Bring payroll and accounting into the same session. Payroll can validate the run's earnings, deductions and payment meaning; finance can inspect accounts, periods, reporting and cash settlement. Where a third-party implementer maintains the connection, include that person in the recovery discussion. A handoff between vendors needs an owner who can follow the case to resolution.
Finish with a concrete list of evidence still missing and a date for resolving it. If a critical reporting result or repair route remains unproven, defer enabling the accounting feed or use an independently approved temporary accounting process. Plan separately for paying employees on time; integration acceptance is not a reason to ignore wage-payment obligations.
Price the recurring work after the first close
Evaluate the connection after a real accounting close, not only after installation. Count the work that remains: approvals, report exports, allocation entries, clearing investigations, new-item mapping and support follow-up. A reviewed manual process may be reasonable at low volume; the same steps can become impractical when runs, entities and adjustments multiply.
Compare the service price with implementation effort and continuing review time, using your own workload rather than a promised saving. If every run needs a spreadsheet allocation, include its preparation, checking and maintenance. If a connector limitation prevents a required report, decide whether the alternative report is acceptable before signing. A lower subscription does not resolve a missing operating capability.
After a change to the chart of accounts, department structure, earning types, payroll service or posting model, repeat the affected parts of the receipt. Keep the previous mapping version and the first run using its replacement. That record lets finance tell a real change in costs from a changed classification.
Choose the route that supplies the accounting result your team can maintain. Accept an embedded or separate connection when its demonstrated output, reporting and recovery fit the business. Accept a manual route only when its recurring work has an accountable owner and review. If the required evidence cannot be produced, keep the compatibility claim open and use it to narrow the purchase decision.
If the recurring accounting work exceeds your team's capacity, reconsider the payroll service as well as the connector. Ask SelectSoftware Reviews about alternative payroll services through its free advisory service. Leave approval of the accounting treatment with your accountant and the provider.
Explore the Decision Guides library.
See the Payroll Operations & Controls hub.
About the author
Ben Scott writes and maintains payroll decision guides for founders and operators. His work focuses on execution realities and how decisions hold up under growth, complexity, and controls and documentation pressure. He works hands-on in HR and leave-management roles that intersect with payroll-adjacent workflows such as benefits coordination, cutovers, and compliance-driven process controls.
