Payroll accounting is the work of recording compensation correctly in the general ledger: gross wages split by function, employee withholdings held as liabilities, employer taxes and benefits recorded as their own expenses, and the whole thing reconciled against what actually left the bank. For most software startups it is the largest expense line by far, which makes it the most expensive place to be sloppy.
It is also, in practice, the most common source of ledger mush. The payroll provider debits one lump sum, someone books it to a single "Payroll" account in G&A, and from that moment the company cannot answer what R&D actually costs. This guide covers the accounts, the entries, and the two mechanisms, the clearing account and the accrual, that keep payroll clean.
What accounts does payroll touch?
More than one, which is the point. A single payroll run moves through:
- Wage and salary expense, by function. R&D, sales and marketing, and G&A ranges in your chart of accounts, because the functional split is what investor-grade reporting is built from.
- Employer tax expense. Social Security, Medicare, and unemployment contributions the company pays on top of gross wages.
- Benefits expense. The employer share of health insurance and any retirement match.
- Payroll liabilities. Employee withholdings (income tax, the employee share of payroll taxes, benefit deductions) that the company holds briefly and remits; they are the employees' and government's money, not an expense.
- Payroll clearing. A staging account that receives the provider's lump-sum debit and gets emptied as the components are recorded.
What does the journal entry for a payroll run look like?
A simplified run with $50,000 of gross wages across a ten-person team:
| Account | Debit | Credit |
|---|---|---|
| Wages Expense - R&D | $28,000 | |
| Wages Expense - S&M | $12,000 | |
| Wages Expense - G&A | $10,000 | |
| Employer Payroll Tax Expense | $4,200 | |
| Benefits Expense | $3,800 | |
| Payroll Liabilities (employee withholdings) | $11,500 | |
| Payroll Liabilities (employer taxes/benefits payable) | $8,000 | |
| Cash (net pay) | $38,500 |
Debits total $58,000 ($50,000 gross wages + $4,200 employer taxes + $3,800 benefits), and so do the credits: $38,500 of net pay leaves the bank now ($50,000 gross minus $11,500 withheld), while the $19,500 of withholdings and employer amounts sit in liabilities until remitted, at which point the remittance debits the liability and credits cash. The exact splits come from your payroll provider's register for the run; the structure is what matters. Gross wages are the expense, net pay is what hits cash immediately, and the difference lives in liabilities until remitted. One journal entry per run, with the functional split preserved.
Why use a payroll clearing account?
Because the bank feed and the payroll register speak different languages. The bank shows two or three lump withdrawals; the register shows forty components. Booking the lump directly to an expense account loses the detail; booking the detail directly against the bank amounts invites mismatches.
The clearing account resolves both: the bank withdrawal debits payroll clearing, the detailed entry above credits it, and the account returns to zero every run. A clearing balance that is not zero is an early-warning light, something was withheld, remitted, or recorded incorrectly, caught within days instead of at year-end. Reconciling it is a standard line in the month-end close checklist.
How do payroll accruals work?
Pay periods ignore month boundaries. When a two-week period ends July 3 but June's books are closing, the June days have been earned and not yet paid, and accrual accounting wants them in June:
| Date | Account | Debit | Credit |
|---|---|---|---|
| Jun 30 | Wages Expense (by function) | $14,000 | |
| Jun 30 | Accrued Payroll | $14,000 | |
| Jul 1 | Accrued Payroll | $14,000 | |
| Jul 1 | Wages Expense (by function) | $14,000 |
The reversal on day one of the new month lets the normal payroll entry post in full when the run actually pays. Without the accrual, months with three pay dates look catastrophic and months with two look great, and neither is telling you anything real about burn.
What goes wrong most often?
- One lump "Payroll" account in G&A. The classic. It makes functional reporting impossible and quietly breaks every metric that depends on knowing what R&D or S&M costs.
- Contractors mixed into wages. Contractor payments are not payroll; they carry different tax and reporting obligations and belong in their own accounts.
- Withholdings booked as expense. Employee withholdings are a pass-through liability. Booking them as company expense overstates costs and breaks the clearing reconciliation.
- No accrual policy. See above; burn becomes a function of the calendar instead of the business.
- Benefits invisibility. The employer share of benefits often posts on different dates than wages and gets miscategorized, understating true compensation cost per function.
How does an AI finance team handle payroll accounting?
The mechanical layer, which is nearly all of it, automates cleanly. At Futureproof, you import your payroll provider's report (CSV exports from Gusto or Rippling), and the agents generate the full journal entry: wages split by department and function, employer taxes and benefits separated, withholdings parked as liabilities, and the clearing account reconciled against the bank withdrawals, with anomalies flagged for review rather than absorbed silently. It runs on the same ledger as the rest of the bookkeeping, inside the $1,000 per month flat plan.
What stays with you is what should: compensation decisions, contractor-versus-employee judgment calls (with your counsel), and approval of anything unusual the agents flag.
FAQ
What is payroll accounting? Recording compensation correctly in the ledger: gross wages as functional expenses, withholdings as liabilities, employer taxes and benefits as their own expenses, reconciled against actual bank activity.
Is payroll an expense or a liability? Both, in parts. Gross wages, employer taxes, and benefits are expenses; employee withholdings and amounts not yet remitted are liabilities until paid out.
What is a payroll clearing account? A staging account that absorbs the payroll provider's lump-sum bank withdrawals and is emptied by the detailed payroll entry. It should return to zero every run; a residual balance signals an error.
Why accrue payroll at month-end? Because pay periods cross month boundaries. Accruing earned-but-unpaid days keeps each month's compensation cost, and therefore burn, tied to reality instead of to the pay calendar.
The bottom line
Payroll accounting is a structure problem, not a math problem: the right accounts, a functional split, a clearing account that zeroes out, and an accrual at the boundary. Get the structure right once and the largest expense in the company becomes its most legible line instead of its murkiest.
Start a 14-day trial of Futureproof, no credit card required, and turn your payroll register into clean functional entries automatically.
