Keep the seven records for each client pay run together in one folder or index, from approval through W-2 reporting detail.
Key takeaways
- Keep the approval, calculation, register, W-4 basis, deposit confirmation, Form 941 support, and W-2 detail together.
- Match the calculation, register, and deposit before closing the folder.
- Give missing items a visible status and assign a reviewer.
- Test whether someone else can trace a bank withdrawal through the run's records.
Payroll files for a small-firm client tend to spread out. The register sits in one export, the bank confirmation sits in an inbox, the employee's W-4 is a scanned PDF from years back, and the year-end forms live in a different folder again. When a client asks why a net amount moved, or a notice arrives weeks after a pay run, whoever answers has to hunt through all of them.
Consider a common case. A client asks why one employee's take-home pay is lower this month than last month. The payroll system shows the net figure, but the answer may depend on a change somewhere else: a new W-4 that arrived late, a bonus paid in the same run, or a deposit that was matched to the wrong period. If the file for that run holds the approval, the calculation, the register, and the W-4 basis together, the reviewer can follow the explanation. If those pieces live in four different places, the reviewer must find and match them first. The gap is not about effort. It is about where the evidence sits.
This guide is for two groups. Operations leads run the pay runs and need a process that people can follow on a busy day. Partners answer for the results and need to be able to pull up any run without a phone call. Both groups benefit from the same structure, because a folder that works for the person filing it also works for the person reviewing it.
Why one trail beats scattered files
Payroll is a chain of steps, and the Intuit guide describes its basic shape: "Payroll taxes are paid by employers and employees through the payroll process." The same guide explains that employers send withheld taxes, along with employer portions, to the taxing agencies. Withholding and sending payments touch different records, and they often happen in different systems on different days. A pay run is the point where those steps meet. If the file for that run does not connect them, every later question starts from scratch.
The Beancount guide states the goal in one line: "That makes it possible to trace the bank withdrawal to the payroll register, tax deposit, Form 941, and eventual Form W-2." Tracing from a bank line to the annual form is the real test. If your setup cannot do that for a run from last quarter, the trail has a gap somewhere, and it is better to find it now than during a notice.
Partners feel this most when a client changes banks, switches payroll providers, or hands the account to someone else. The person who ran the last pay run may have moved on, and memory is a poor filing system. Good files let the next person follow the chain without asking anyone.
There is also a quieter benefit. When the trail is complete, staff stop reconstructing history from memory, and the questions they do answer are the ones that matter. Partners spend less time asking where a file went and more time reviewing whether the numbers are right. A consistent structure also makes it easier to onboard a new team member, because the folder itself teaches the sequence of the work.
The seven records in each trail
The Beancount guide gives the records below as the set to retain together. Each item answers a different question: what was paid, what was withheld, what was sent, and how it was reported.
- Approval. The sign-off that a pay run may go ahead, covering hours, salary changes, and any bonus or commission. Keep who approved it, when, and what they approved.
- Calculation. The worksheet or system output that turns approved inputs into gross pay, withholding, and employer amounts. Save the version used for the final run, not a draft.
- Payroll register. The detail for each employee in the run. A register is only one piece of proof. The Beancount guide warns that "A payroll register that shows $1,100 of federal income tax does not prove that Social Security, Medicare, FUTA, and state taxes were handled." Check the register against every tax line, not just one.
- W-4 basis. The W-4 the withholding was calculated from, with its date. A new W-4 is how an employee asks for different withholding, and the Taxpayer Advocate Service advises submitting it to the employer as soon as possible. Keep the form in effect on the pay date, and file any replacement with the run it affected.
- Deposit confirmation. Proof that the tax money reached the agency, matched to the run's totals. Keep the bank line next to it so the match can be seen.
- Form 941 support. The working papers behind the Form 941 return, with the run's totals marked so they can be found quickly.
- W-2 reporting detail. The figures for each employee that later feed the annual Form W-2. Where a run carries amounts for a special code, keep the year-to-date figures with it. The Beancount guide gives a 2026 example: "The cumulative data needed for 2026 W-2 code TT is being retained."
Read in order, the seven records form a chain. The approval authorizes the calculation. The calculation produces the register. The register supports the deposit confirmation, and the Form 941 support draws on the same run totals. The W-2 reporting detail then carries the figures for each employee toward the year-end form. If a link is missing, the chain breaks at that point, and every record after it becomes harder to trust.
Keeping the seven records together does not mean they must share one file type. A PDF of the approval, a spreadsheet of the calculation, and an export of the register can sit side by side. What matters is that each one carries the run's identifiers, so a reader can find it from the folder without guessing. Where a record cannot be saved as a file, such as a portal screen, save a dated screenshot or a printed report and file that instead. The aim is a complete set, not a perfect format.
Comparing ways to file a pay run
Firms usually land on one of a few filing patterns. The table offers an illustrative comparison of the main options. None is perfect, but each suits a different mix of clients and staff.
| Approach | How it works | Strength | Weak spot |
|---|---|---|---|
| One folder for each pay run | All seven records saved under one run ID | Complete by design and easy to hand over | Relies on people filling every slot |
| Folders by record type | Each record type kept in its own folder across all runs | Simple to set up and easy to scan by type | Tracing one run means opening seven folders and matching dates |
| Payroll system only | Reports and exports held inside the payroll provider's system | Little manual filing | Records follow the vendor's format and may be hard to export |
| Shared index sheet | One row for each run with links to each record | Quick overview and easy search | Links break when files move, and the sheet needs an owner |
Whichever pattern you pick, the test stays the same: could someone who was not part of the run follow the chain from approval to Form W-2 in one sitting? A common mix is a single folder for each run for the core records, with a system export filed alongside, which keeps the trail complete without much extra work.
When choosing, look at three things: who will file the records, who will need to find them, and how the client's payroll provider exports data. A firm with one or two people doing payroll may do well with a single folder for each run. A larger team may need the index sheet so that partners can search across clients. A portal-only approach works best when the provider can export a complete copy on demand, and it fails when exports leave out pieces.
The index sheet deserves a note of caution. It is only a map. The files it points to must stay in place and keep their names, or the sheet becomes a list of broken links. Checking the links at each run close takes little time and prevents that drift.
Building one folder for each pay run
Start with a naming rule that every person on the team follows. A practical pattern is client name, pay period, pay date, and a sequence number, so that the files sort in date order and two runs for the same period do not collide. Put the seven records in a fixed order inside the folder, and keep a checklist at the top that lists each record, its status, and who filed it.
For example, a file for a regular run might be named with the client's short code, the period end date, the pay date, and a sequence number, so that a corrected run is visibly a later run and not a replacement hidden under the same name.
The checklist is the part people skip, so make it hard to skip. A run is not closed until every line has a status, even if the status is "not applicable" with a short reason. Missing items should be visible on the day they go missing, not discovered later.
Match the numbers before the folder is closed. The register totals should agree with the calculation, and the deposit confirmation should agree with the tax lines in the register. These checks are quick, and they show gaps while the details are still fresh. Use the client bank reconciliation guide when reviewing the bank side of the match.
Lock the folder once it is closed. Copies can be made for the client, but the original should stay unchanged. If a correction is needed, record it as a new entry that points back to the run it fixes, so the history stays readable.
Assign roles inside the team so that nobody is both the only preparer and the only checker of a run. One person builds the folder, a second person runs the matching checks, and a partner signs off on the checklist. Small firms may not have three people for every run, but even a rotating reviewer adds a second pair of eyes. Write the roles into the procedure so they survive staff changes.
Illustrative example: check a deposit difference
Suppose the calculation and register each show an illustrative tax total of $50, but the deposit confirmation shows $60. Keep the folder open, compare the bank line with the confirmation, and check which run each record belongs to. Record the cause of the difference before closing the folder. These amounts illustrate a matching check, not a tax calculation.
Handling supplemental pay and changed withholding
Bonuses, commissions, and overtime often follow their own calculation, so their records need extra care. Keep the approval for each supplemental payment in the same folder as its calculation, not in a separate email thread. A run that mixes regular and supplemental pay should show both in the register, so a reader can tell which amount came from which calculation. The Beancount guide on withholding for bonuses, commissions, and overtime covers that side in more depth.
Changes to withholding need the same care. When an employee gives you a new W-4, the date it was received and the pay run where it first applied both belong in the file. The W-4 basis record should show which version drove each run, so a later question about one paycheck can be answered from the file alone. For related review, see the guide to withholding before payroll.
The Taxpayer Advocate Service points to the withholding estimator as the starting point: "If you think you need to make changes to your withholding amount, the withholding estimator gives you the information you will need to fill out a new Form W–4, Employee’s Withholding Allowance Certificate." Taxpayer Advocate Service For your files, that means any estimator output or worksheet can be kept with the W-4 basis, so the reason for a change is recorded next to the change.
Keeping the trail through year end
The trail has to survive the year. The W-2 detail in each run is what makes the annual forms traceable, and it only works if the run files were complete when they were made. Ask the client's provider what data it keeps and how to export it, then store a copy with the firm's own files.
At year end, the run files do most of the heavy lifting. Before forms are produced, pull the W-2 reporting detail for each run and check that the totals match the year's registers and deposits. Any run that cannot be reconciled should be raised early, while the details are still fresh, because reopening a closed year is usually harder.
Test the chain once a year on a sample run. Pick one pay run, start from a line on the bank statement, and follow it through the deposit, the register, the Form 941 support, and the W-2 detail. If each step can be found without a phone call, the trail is working. If one step needs a call, note it and fix the folder that caused it.
Decide retention rules with the client and your own advisor, and write them into the engagement file. This post does not set retention periods, because those depend on the firm and the client's situation.
When a client moves to a new provider or a new partner takes over the account, the handover should include one folder for each pay run, the index sheet, and a short note on any open corrections. The new team can then continue without rebuilding history from bank statements.
Making the habit stick
A simple rollout works in three passes. In the first, move the current client's most recent pay run into the new folder and fill in whatever is missing. In the second, do the same for the prior quarter's runs, starting with the ones that have open questions. In the third, make the folder the default for every new run and retire the old shared drive locations once the team trusts the new layout.
Measure progress in plain terms. Count how many runs in the last quarter have a complete checklist when the run closes, and how many needed a follow-up question. Track both numbers for a few months. When the first number rises and the second falls, the habit is working, and the team can see it without anyone having to argue the point.
Today, start with one client and one pay run. Build the folder, run the checklist, and time how long it takes to answer a question from the file alone.
Related guides: Account deletion for firm records: 3 checks before removal · Check 8 state reporting steps before payroll starts · Apply the 22% flat rate before a client bonus payroll.
Questions about payroll records
Must every record use the same file type?
No, the records can use different file types as long as the run's identifiers connect them. Keep the approval, calculation, and exports easy to find from the same folder or index.
Does the register prove all taxes were handled?
No, the register alone does not prove that every tax was handled. Review the calculation and deposit evidence alongside it.
What should happen when a closed run needs correcting?
Record the correction as a new entry that points back to the original run. Preserve the original so the history stays readable.