Payroll from the bank feed
The Gusto or ADP draft is cash leaving. It is not the whole payroll story.
The Gusto or ADP draft is cash leaving. It is not the whole payroll story.
What This Is
A payroll provider usually takes one or two withdrawals: net pay, taxes, sometimes fees. Wages, employer taxes, and withholdings live on the payroll report, not on the bank line.
Tally holds payroll-provider rows as special work. It will not dump them into an expense to clear Fast Coding.
LedgerHQ files a payroll provider's rows, such as Patriot Software, Gusto, or ADP payroll, under one vendor even when the bank wording varies. Learned rules still follow the wording, so net pay, tax, and fee rows can each keep their own account.
Gusto connected? Use Payroll Setup
Book Gusto payroll with Payroll Setup splits each Gusto withdrawal from the payroll detail for you. Once setup is finished, use it instead of the report review below.
Why It Matters
If you code the draft to Wages, you miss taxes and you overstate net pay as the full cost.
Park the draft, then true it up from the report
Code the bank row to payroll clearing, or leave it unposted. Ask Tally to review a Gusto Payroll Journal Summary. Confirm the preview before anything posts.
For connected Gusto history, see Review payroll history. Reading payroll history does not run payroll or automatically reconcile a bank withdrawal.
How To Book It
- Do not code a Gusto, ADP, or Paychex draft to an ordinary expense. See How Tally codes your bank feed.
- Put the withdrawal against payroll clearing, or leave it waiting.
- Save the payroll report in company Files, under Payroll.
- Ask Tally to review the report. Map each category the first time.
- Confirm the preview. Tally posts a true-up, not a second cash movement.
Checklist
- The draft is not sitting in Wages by itself
- The report is in Files
- Wages and employer tax are on the books
- Cash moved only once