Skip ahead to the main page
Partner Huddle
Pages

Payroll setup checklist: 5 checks before a first run

Partner Huddle Editorial Team · Published · 12 min read

Before a client's first payroll, confirm tax accounts, unemployment tax settings, funding, employee records, and the pay calendar with a test run.

Key takeaways

  • Match tax account details to registration notices.
  • Check unemployment settings and carried-over wages.
  • Confirm funding deadlines and backup approval access.
  • Review employee records and explain test-run differences.

Taking over a client's payroll is one of the most useful services a small accounting firm can offer. It is also one of the easiest places to make a mistake that shows up on a paycheck, a tax notice, or an angry call from an employee. Use the first run to check how every piece of the setup works together.

Start by checking basic setup details. Possible mistakes include an account number nobody checked, a pay date that falls on a holiday, or a deduction that was entered once and never tested. This post walks through five setup items to confirm before the first payroll goes out. None of them is complicated. Each one is worth a few minutes of checking with the client and the payroll system before any money moves.

The advice is written for partners and operations leads who may be handling payroll for a client for the first time. Adjust the details to your client, your states, and your software. Where this post points to a specific rule, the link goes to the source behind it. Where the advice is general, check the current requirements yourself before you rely on it.

1. Confirm the client's tax accounts and registrations

Before anything else, confirm that the employer has the tax accounts it needs and that the payroll system is set up to use them. Payroll involves several layers of tax. Confirm reporting requirements for federal income tax withholding, Social Security and Medicare taxes, and federal unemployment tax. Check which state and local registrations apply.

Ask the client for copies of its registration notices instead of relying on memory or on a spreadsheet someone built years ago. Check that the legal business name, the federal employer identification number, and the state account numbers match what the client's records show. Resolve any mismatch between the legal name and the number on file before making deposits or filing. It is easy to catch before the first run and frustrating to fix after.

Next, confirm who holds the logins. The client should know which portals hold its tax accounts, who has access to each one, and whether your firm has been granted the access it needs to make deposits and file returns on the client's behalf. If the answer depends on one person who is leaving next quarter, fix that now, while the previous provider or the client's staff can still help.

Finally, confirm the cutoff between the old payroll and the new one. Find out which pay periods the prior provider handled and which ones belong to you. A first run that includes wages already paid by someone else can double-count year-to-date totals, and those totals then flow into withholding and wage reports. Write the cutoff down, along with the date of the last payroll run by the prior provider, so the starting point is never a guess. Use the client intake checklist to organise the handoff.

2. Check the unemployment tax setup, including FUTA

Include unemployment tax in the setup review, alongside net pay. The federal piece is called FUTA. The Paychex explainer on FUTA describes the purpose of the program this way: the Federal Unemployment Tax Act established a program to assist states in covering unemployment benefits for workers who lose their jobs through no fault of their own.

The same source makes a point that is worth repeating to any client who thinks of unemployment tax as a minor line item. It says these taxes "may be one of the smaller payroll taxes, but they fund a key safety net and come with rules employers can't ignore." Smaller does not mean optional, and a missed setting in the first run can carry into the next filing period. The same article notes that an employer may be responsible for paying this tax annually, so the setup should be right from the start rather than corrected later in the year.

For the first run, confirm several things:

  • Whether the client is treated as an employer for federal unemployment purposes this year. Check the applicable coverage criteria rather than assuming the answer from last year's return.
  • Whether the state unemployment account is active and whether the client has received its current notice from the state. Enter the rate the state has assigned, not the rate someone remembers from a previous year.
  • Where each employee works. If anyone works from another state, or moves between states during the year, ask the client and check where that person's wages should be reported before the first run. Include remote employees in that review.
  • Whether wage totals carried over from the prior provider are correct. Check carried-over wages against the applicable unemployment tax rules. Compare those totals to the prior provider's final report before you accept them.

If you are not sure about any of these points, put the question in writing to the client and keep the answer in the file. A short email that says "we confirmed this rate with the state notice dated..." is far more useful later than a verbal assurance.

3. Confirm how the money moves: funding and direct deposit timing

Check funding before scheduling the first run. Ask the client how payroll will be funded, when the funds need to be in the account, and who approves the transfer. Those three questions sound simple, but the answers often differ from what the client assumed.

Payroll providers handle funding in different ways. One provider's public FAQ lists several options: "expedited 2-day direct deposit for qualifying customers, standard 4-day direct deposit, payroll prefunding, or customer-initiated funding through bank wires or instant payments." The lesson is not about any single company. It is that the timing depends on the option chosen, and that some faster options are available only to certain customers. A client who expects money to arrive the day before payroll on a plan that takes several days will feel the gap on pay day.

For the first run, confirm the following:

  • The funding method the client will use, and what the provider requires to set it up. Does the method require approval or separate enrollment, and can that be completed before the first pay date?
  • How many days before the pay date the funds must be available. Confirm this against the provider's current documentation rather than a rule of thumb you picked up on another account.
  • Who approves each transfer, and what happens if that person is out. Name a backup approver and make sure that person has the access needed to act.
  • That bank details are entered correctly on the client's side. If the provider offers a verification step for the account, use it before the first live run. Read account numbers from a voided check or the bank's official letter, not from an email thread.
  • That every employee's direct deposit information was collected directly and verified. Routing and account numbers should be entered by the employee or confirmed with them, not forwarded from an old message or a photo of a document. This is a privacy issue as well as a payment issue.

Write down the funding schedule for the first three pay periods, not only the first one. Once the process has run a few times, it becomes routine. Until then, the calendar is what keeps a small timing gap from becoming a missed payroll.

4. Verify every employee record before the first check

Each employee record is a set of decisions that drives the paycheck. A wrong filing status, a stale pay rate, or an incorrect hire date will flow into every calculation that follows it. The first run is the best time to review these records line by line, because after that the errors become history that has to be corrected.

Start with identity. Each employee's legal name and Social Security number should match the paperwork the employee provided, exactly as written. Resolve discrepancies before submitting wage reports. Next, confirm each person's classification with the client. Confirm full-time or part-time, hourly or salaried, and exempt or nonexempt status and the applicable payroll treatment. Do not assume any of these from the job title. Check the applicable classification rules before accepting a manager or contractor label.

Then check the pay rate and its effective date. Use a signed offer letter or the client's approved change notice as the source. Last year's spreadsheet is not a source. If the rate changed recently, confirm that the change took effect on the right date and that the prior provider's final payroll reflects it.

Review the withholding elections each employee has submitted, both federal and state, and any local forms that apply. Confirm that the forms are on file and that the system has the same elections. An employee who gave the client a new form in the spring may still have the old one loaded in the software.

Confirm the work and home addresses as well. Check the applicable state and local tax and wage-reporting requirements using those addresses and the employee's work arrangements. An address that is out of date by a single move can change the tax picture for the whole year.

Next, reconcile the year-to-date figures. Ask the prior provider for a final payroll register or a year-to-date report, and compare gross wages, taxes withheld, and deductions for each employee against the most recent pay statement the employee has. Decide which figures carry over and document the decision. If the numbers do not match, do not paper over the difference. Find the cause first.

Check benefit enrollments too. Ask the client for the current enrollment list for each health, retirement, and insurance plan, and compare it with what the payroll system is deducting. Someone who enrolled during open enrollment, or who dropped coverage after a life event, is easy to miss when the file came from a different provider. Confirm the employee's share and the employer's share separately, because a mix-up between them shows up quickly in the employees' pay.

Finally, check employment status for anyone who has left. Before marking former employees inactive, confirm outstanding payments and how the system handles inactive records. Check applicable final-pay requirements for any employee whose last day falls near the first run. If someone left during the prior provider's last cycle, confirm whether that final check was issued and whether it is reflected in the year-to-date figures you accepted. For a focused review, use the employee file checks.

5. Set the pay calendar, deductions, and a test run

The last item ties the rest together: the pay schedule, the recurring deductions and benefits, and a trial run before live checks go out.

Start with the pay calendar. Confirm the pay frequency, the start and end dates of each pay period, and the pay date for each run. Check every pay date against weekends and holidays, since a pay date that lands on a non-business day can change when funds must move. Confirm that the cutoff for hours or changes matches how the client actually collects its time records. A cutoff set a few days off from the client's real timekeeping habits will cause a late correction every period.

Next, review deductions and benefits. These include retirement contributions, health premiums, and any other recurring items the client has agreed to. For each one, confirm the amount, the start date, whether it is taken before or after tax, and who approves changes. If an employee has a wage garnishment, get the order details and the deadlines from the client in writing, and check the order against applicable requirements before setup.

Confirm the source of the hours as well. Find out whether time comes from a timekeeping system, a spreadsheet, or a manager's email, and who approves it before payroll is processed. The first run should not depend on a file that only one person knows how to open.

Then run a test. If the payroll system supports a preview or parallel calculation before the live run, use it. Compare gross pay, taxes, deductions, and net pay for each employee against an independent calculation or against the client's last paycheck. Differences are not always errors, since the first run may legitimately differ from the old one because of the cutoff, a raise, or a new deduction. Every difference should have a reason, and the reason should be written down.

Once the test is clean, send the register to the client and ask for written approval before you finalize the run. A signed or emailed approval protects both sides. It also gives the client a moment to notice something you missed, such as a bonus that was never entered or a leave of absence that should not be paid.

It also helps to set a simple timeline that works backward from the pay date. Decide when the client's hours must be final, when the register will be ready for review, when the client must approve it, and when funds must be available. Put each step on the calendar with a named owner. Late approvals or unclear ownership of the hours file can delay the first run.

Finally, put the recurring dates on a calendar. That includes the deposit dates, the filing deadlines, and the year-end forms that the client will need. The first run is when those dates become real, and the calendar is what keeps them from being forgotten after the excitement of a smooth first payroll has passed.

Illustrative example: resolve an hours difference

An illustrative test register shows 80 hours, but the approved time record shows 40 hours. Check the pay-period dates and the imported file before changing either record. Document the cause, correct the entry if needed, and repeat the comparison before requesting approval.

Before you release the first run

None of these five items is hard on its own. The risk comes from skipping one because the others looked fine. Taken together, they give you a clear answer to the question that matters most before a first payroll: does the client have the accounts, the money, the employee records, the calendar, and the approvals needed to pay people correctly?

Keep a single file for the engagement. Put the registration notices, the list of who has access to each account, the funding schedule, the reconciled year-to-date figures, the test register, and the client's written approval in one place. If something goes wrong in the next quarter, that file can help you investigate the cause.

A first run is a chance to set the standard for the whole relationship. Clients who see a careful, documented start tend to trust the rest of the work. Today, open the engagement file and list unresolved setup questions with an owner and a deadline.

Questions before the first run

What if carried-over totals do not match?

Resolve the difference before accepting the starting figures. Keep the explanation in the engagement file.

What if the system has no test option?

Compare the proposed payroll against an independent calculation before release. Keep the comparison with the register for client review.

Sources