Payroll Ledger: What It Is and How to Create One
What a payroll ledger is and how to build one. Every column you need, a worked example with the employer tax rows most homemade ledgers leave out.
Payroll Ledger
Every column you need, the employer-tax rows nobody includes, and how to build one from scratch
The first payroll ledger I built was a Google Sheet with six columns: name, hours, rate, gross, taxes, net. It felt complete. It balanced. Every number tied to every other number.
It was also wrong in a way that took me a full quarter to notice. I had built a ledger that tracked what came out of my employees' paychecks and nothing that tracked what payroll cost me. There was no column for my matching Social Security, none for my matching Medicare, none for unemployment tax. So when I budgeted from that sheet, I was underestimating my own payroll cost by roughly eight percent, every month, quietly.
A payroll ledger is not hard to build. It is easy to build badly, because the columns you omit are invisible until they are expensive. This guide covers what a payroll ledger is, how it differs from the register and journal and general ledger people confuse it with, exactly which columns it needs including the ones nobody includes, a fully worked example, how to reconcile it, and when the spreadsheet stops being good enough.
What Is a Payroll Ledger?
A payroll ledger is the cumulative record of what a business pays its employees over time. One row per employee per pay period, showing what they earned, what was withheld, what you owed on top, and what they actually took home.
The word that matters in that definition is cumulative. A pay stub tells you about one paycheck. A payroll ledger tells you about a relationship over time, and it is the accumulation that gives it its value: the year-to-date totals that drive your quarterly filings, the history you produce when someone disputes a paycheck from eighteen months ago, and the cost trend that tells you what your team actually costs.
Payroll Ledger vs Register vs Journal vs General Ledger
These four terms get used interchangeably across the internet, including by payroll vendors who should know better. Here is the actual distinction, which mostly comes down to what each one is organized around.
If you take one thing from this section: the register is a period, the ledger is a history, the journal is an accounting entry, and the general ledger is the whole company's books. They describe the same underlying money at different levels of aggregation and from different vantage points. A small business genuinely needs the ledger. It gets the register automatically from any payroll system. It needs the journal only when the payroll data has to land in accounting software.
The Columns You Actually Need
A useful payroll ledger has six families of columns. Miss any one of them and the ledger becomes decorative rather than useful.
The single most consequential design decision is breaking things out rather than lumping them together. One gross column is easier to build and useless in a dispute. Regular, overtime, bonus, and commission as four columns takes ten extra seconds and answers the question a wage claim will actually ask. The same logic applies to deductions: a single deductions column tells you nothing, while a column per deduction traces each one back to the authorization that permits it.
The Employer Tax Columns Nobody Includes
This is the section I wish someone had put in front of me before I built that first spreadsheet. Employer payroll taxes are not deductions. They are not subtracted from anyone's pay. They are an additional amount the business owes on top of gross wages, and if your ledger does not have columns for them, your ledger does not know what payroll costs.
Four employer taxes belong in the ledger for a typical small business.
| Employer Tax | Rate and Base | What to Watch |
|---|---|---|
| Social Security (employer share) | 6.2% of wages, up to the annual Social Security wage base. For 2026 the wage base is $184,500. | The obligation stops for an employee once their year-to-date wages cross the wage base. This is why the YTD gross column matters: without it you keep withholding and matching past the cap. |
| Medicare (employer share) | 1.45% of all wages, with no wage base limit. | There is no cap, so this one never stops. Note also that the additional 0.9% Medicare tax on high earners is withheld from the employee only. There is no employer match on it. |
| FUTA (federal unemployment) | 6.0% on the first $7,000 of each employee's wages, commonly reduced to an effective 0.6% by the state unemployment credit. | Paid entirely by the employer and never withheld from employee wages. Reported annually on Form 940 rather than quarterly. |
| SUTA (state unemployment) | Varies by state and by your experience rating. | Your rate is not fixed. It moves based on your claims history, which means the same wage costs different employers different amounts. |
Per IRS Topic No. 751, the Social Security rate is 6.2 percent each for employer and employee, and the Medicare rate is 1.45 percent each, with no wage base limit on Medicare. Wage bases update annually, so treat any figure here as something to verify each January rather than hard-code forever.
How to Create a Payroll Ledger
Build it in this order. The sequence matters, because each group of columns depends on the one before it.
A Fully Worked Example
Here is one employee, one biweekly pay period, calculated all the way through to what the paycheck actually cost the business. Income tax withholding is illustrative, since it depends on the employee's W-4.
Look at step four versus step six. The employee sees $1,512.52. The business spent $2,327.38. Those two numbers are separated by about 54 percent, and a ledger that stops at net pay only ever shows you the first one.
Note also what happens with the Social Security column as the year goes on. At $2,150 biweekly, this employee earns roughly $55,900 a year, comfortably under the wage base, so the 6.2 percent applies all year. A higher earner would cross the base partway through the year, and both the withholding and your matching obligation would stop at that point. Your ledger has to know that, which it only can if the YTD gross column exists.
The Monthly Per-Employee View
The same data, pivoted. Instead of organizing by pay run, organize by person: one sheet or one view per employee, showing each month down the rows and the same columns across.
This is the view you want in three specific situations, and each one arrives eventually. When an employee asks about their pay history, you produce this rather than digging through twenty-six pay runs. When you prepare a W-2, the annual totals are already summed. And when you need to know whether someone has crossed the Social Security wage base, the running YTD gross is right there in the column.
If you are building this in a spreadsheet, the practical structure is one master sheet with every row, plus per-employee views generated from it with a filter or pivot rather than maintained by hand. Maintaining twenty separate employee sheets by hand is how transcription errors get in, and a transcription error in a payroll record is not a typo, it is a discrepancy between what you paid and what you recorded paying.
How to Reconcile Your Payroll Ledger
A ledger you never check is not a record. It is a guess with formatting. Three reconciliation checks, every pay period, and none of them take more than a few minutes if you do them on time.
| Check | What You Compare | What a Mismatch Means |
|---|---|---|
| Net pay to bank | Total net pay in the ledger for this run against the total actually withdrawn from your account. | Someone was paid an amount other than what the ledger says. Find it now, because in three months you will not remember which of the two figures was right. |
| Taxes to deposits | The tax amounts in the ledger against what you actually deposited to the IRS and the state. | Either you under-deposited, which accrues penalties, or you over-deposited, which is your cash sitting somewhere it should not be. |
| Ledger to Form 941 | Quarterly totals in the ledger against what you reported on Form 941. | Your filing and your records disagree. One of them is wrong, and the IRS will be working from theirs. |
| YTD continuity | This period's YTD totals against last period's YTD plus this period's amounts. | A formula broke, or a row was edited retroactively. YTD drift is silent and compounds, and it usually surfaces at W-2 time when it is most expensive. |
| Headcount | Number of rows this period against the number of people you actually paid. | Someone was missed, or a terminated employee is still in the ledger. Both are worth catching in the period they happen. |
The general rule is that a discrepancy found in the same pay period takes minutes to fix, and the same discrepancy found at year end becomes a reconstruction project across twenty-six pay runs. The reconciliation is not the tedious part of payroll. It is the part that prevents the tedious part. The quarterly check against IRS Form 941 is the one that matters most, because that filing is what the IRS will be working from if your numbers and theirs ever diverge.
Common Payroll Ledger Mistakes
| Mistake | What Goes Wrong | The Fix |
|---|---|---|
| Omitting employer tax columns | The ledger tracks what came out of employee pay and nothing about what payroll costs the business. Budgets run roughly 8 to 10 percent optimistic. | Add employer Social Security, Medicare, FUTA, and SUTA columns, plus a total employer cost column. Budget from that column, not from gross. |
| One lumped gross column | You can see what someone was paid but not why. When a wage claim asks about overtime specifically, the ledger cannot answer. | Break gross into regular, overtime, bonus, and commission. The FLSA requires overtime earnings to be recorded separately anyway. |
| No year-to-date totals | You cannot tell when an employee crosses the Social Security wage base, so you keep withholding and matching past the cap. | Add YTD gross, YTD tax, and YTD net columns, and let them drive the wage-base logic rather than checking by hand. |
| Reconciling at year end instead of each period | Errors compound silently across twenty-six pay runs and surface when you are trying to produce W-2s. | Three checks every period: net to bank, taxes to deposits, YTD continuity. Ten minutes now beats a week in January. |
| Editing historical rows in place | The ledger no longer reflects what you actually paid at the time, which is precisely what a payroll record is supposed to preserve. | Never overwrite a historical row. Add a correcting entry with its own date, so the record shows both what happened and what fixed it. |
| The ledger lives on one laptop | The person leaves, the laptop dies, or the file gets overwritten, and years of payroll records go with it. | The ledger belongs somewhere the business controls and can retrieve from, independent of any individual employee or vendor subscription. |
The last one is not a spreadsheet mistake, it is an organizational one, and it is the one that actually destroys companies' records. The payroll records guide covers what happens when you cannot produce records in a wage dispute, and the answer is worse than most owners assume.
How Long to Keep a Payroll Ledger
Two clocks run at once, and most guides mention only one of them.
Under the FLSA, per DOL Fact Sheet #21, employers must preserve payroll records for at least three years, while the records that wage computations are based on, meaning time cards and wage rate tables, must be kept two years. Separately, per IRS employment tax recordkeeping guidance, all employment tax records must be kept at least four years after the tax becomes due or is paid, whichever is later.
When the Spreadsheet Stops Working
A spreadsheet payroll ledger is legal. The FLSA prescribes no particular form for payroll records, so Excel and Google Sheets are both perfectly acceptable. The question is not whether it is allowed. The question is when it stops being safe.
Four things break, in roughly this order as a company grows:
| What Breaks | When | Why It Matters |
|---|---|---|
| Formula integrity | Around 10 to 15 employees | A dragged formula misses a row, or an absolute reference should have been relative. The sheet still balances, so nothing looks wrong, and the error propagates into YTD totals. |
| Version control | As soon as more than one person edits | Two people work on different copies. Both are now authoritative and neither is. There is no way to know which reflects what you actually paid. |
| Retrievability | Immediately, if the file lives on a laptop | Payroll records must be producible on request. A spreadsheet on a departed bookkeeper's machine is not a records system, whatever it contains. |
| Audit trail | Always | A spreadsheet does not tell you who changed a historical row or when. In a wage dispute, an unexplained edit to a past pay period is worse than no record at all. |
The honest guidance is that a spreadsheet is fine at five employees, workable at fifteen with discipline, and a genuine liability at thirty. The failure mode is not that it stops calculating. It is that it keeps calculating confidently while being wrong, which is the worst possible property for a payroll record to have.
This is the gap FirstHR is built around. Employee profiles hold the compensation arrangement and classification so the pay basis is a record rather than a memory. Document management keeps the payroll ledger, the tax filings, and the deduction authorizations somewhere the business controls and can actually retrieve from, rather than on the laptop of whoever ran payroll last. And e-signature captures the authorizations behind every deduction, so each column in the ledger traces back to a document.
FirstHR is not a payroll engine. It does not calculate your withholding or file your 941, and that work belongs with your payroll provider. What it holds is the record and document layer around payroll, which is precisely the layer that goes missing when a provider changes or a bookkeeper leaves. The running payroll guide covers the full pay cycle this ledger records, and the payroll forms guide covers the filings your ledger has to reconcile against.
Frequently Asked Questions
What is a payroll ledger?
A payroll ledger is the cumulative record of what a business pays its employees over time. Each row captures one employee for one pay period: hours worked, gross pay broken out by type, every deduction taken from their wages, the employer taxes the business owes on top, and the resulting net pay. Unlike a single pay stub, a payroll ledger accumulates. It carries running year-to-date totals, which is what makes it useful for tax filings, audits, budgeting, and answering questions about what someone was actually paid two years ago.
What is the difference between a payroll ledger and a payroll register?
The practical difference is the time axis. A payroll register is a snapshot of a single pay run: everyone who got paid this period, with their gross, deductions, and net. A payroll ledger is cumulative and carries running year-to-date totals, so it shows one employee across many periods. Many payroll vendors use the two terms interchangeably, which is why the distinction feels murky online. If you need to see this pay run, you want the register. If you need to see the history, you want the ledger.
How do you create a payroll ledger?
Start with a row per employee per pay period and build the columns in order: employee name and ID, pay period dates, regular and overtime hours with their rates, gross pay broken out by earning type, each employee deduction on its own column, net pay, then the employer tax columns for your matching Social Security and Medicare, FUTA, and state unemployment. Add year-to-date running totals for gross, taxes, and net. Then reconcile it against your bank statement and your tax filings every single period, because a ledger you never check is not a record, it is a guess.
What columns should a payroll ledger include?
At minimum: employee name and identifier, pay period start and end dates, pay date, regular hours and rate, overtime hours and rate, gross pay separated into regular, overtime, bonus, and commission, each employee deduction listed individually (federal income tax, Social Security, Medicare, state and local tax, benefit premiums, retirement, garnishments), net pay, and then the employer tax columns: employer Social Security, employer Medicare, FUTA, and state unemployment. Add year-to-date totals for gross, each tax, and net.
Does a payroll ledger include employer taxes?
It should, and this is the single most common omission in homemade ledgers. Employer taxes are not deducted from an employee's pay. They are an additional cost the business owes on top of gross wages: the employer share of Social Security at 6.2 percent, the employer share of Medicare at 1.45 percent, federal unemployment tax under FUTA, and state unemployment tax. If your ledger only tracks what came out of employee paychecks, it is understating the true cost of payroll by roughly 8 to 10 percent.
What is a general ledger in payroll?
The general ledger is your company's complete accounting record across every account, and payroll is one of the things that posts into it. The payroll ledger is the detailed operational record of who was paid what; the general ledger is where that information lands in accounting terms, as journal entries with debits and credits. Wage expense gets debited, cash and tax liability accounts get credited. The payroll ledger is the detail behind the summary that appears in the GL.
Can I keep a payroll ledger in Excel or Google Sheets?
Yes, and most small businesses start there. A spreadsheet is legally acceptable, since the FLSA prescribes no particular form for payroll records. The practical limits arrive as you grow: formula errors compound silently, version control breaks when more than one person edits, year-to-date totals drift out of sync with actual filings, and the file usually lives on a single person's laptop. A spreadsheet is fine at 5 employees and increasingly dangerous at 30.
How long do you need to keep a payroll ledger?
Longer than most people think, and two clocks run at once. Under the FLSA, payroll records must be preserved for at least three years, while the records that wage computations are based on, such as time cards, must be kept two years. The IRS separately requires employment tax records to be kept at least four years after the tax becomes due or is paid, whichever is later. Rather than tracking multiple clocks, keep everything at least four years, which satisfies both.
How do you reconcile a payroll ledger?
Three checks, every pay period. First, confirm total net pay in the ledger equals the total actually withdrawn from your bank account for that run. Second, confirm the tax amounts in the ledger match what you actually deposited and what appears on your quarterly Form 941. Third, confirm year-to-date totals in the ledger still tie to the prior period plus this one. Discrepancies found in the same period take minutes to fix. Discrepancies found at year end become a reconstruction project.
What is a monthly payroll ledger per employee?
It is the same ledger data organized by person rather than by pay run: one view showing a single employee's gross, deductions, employer taxes, and net across each month of the year, with running totals. It is the view you want when an employee asks about their pay history, when you are preparing a W-2, or when you need to know whether someone has crossed the Social Security wage base and your matching obligation has stopped for the year.