Pay Run Warnings in QuickBooks Advanced Payroll: Setup and Meanings

Pay run warnings in QuickBooks Online Advanced Payroll are easy to overlook, because the setting sits inside each pay schedule rather than at the top of the payroll menu. The placement matters. These alerts can surface the moment a pay run is created, or partway through the run itself, and one of them stops a payment file from being produced at all. Knowing which warnings are switched on, and what each one means, turns the pay run screen from a source of surprises into a working checklist.

The warning that blocks a BACS file

Most alerts are informational. The payment details warning is not. When BACS details have not been provided for a run, QuickBooks will not generate a payment file for it, and payroll teams paying through the software must supply those details before the run can complete. If you pay staff outside QuickBooks, the warning can be ignored, because there is no file to produce. That distinction is the first thing to settle when the alert appears. The fix is either a quick data entry task or nothing at all.

Which warnings can you switch on?

QuickBooks checks each run against a long list of conditions. These are the alerts it can raise:

• Missing payment details. BACS details are absent, so no payment file can be generated for the run.
• Leave beyond the accrued balance. An employee is set to take more leave than they have accrued.
• Birthday in the pay period. An employee’s birthday falls inside the run, so their rate of pay may need review.
• Work anniversary in the period. The anniversary of an employee’s start date falls inside the run, which may again call for a rate review.
• Negative net pay. An employee’s net amount has dropped below zero.
• Previously terminated employee. Someone who has already been terminated, and is inactive, still appears in the run.
• Outstanding expense for a terminated employee. A terminated employee is still owed a reimbursement from an expense inclusion and has appeared in the run.
• Expired qualification. An employee’s qualification expired during the pay period.
• Duplicate earnings lines. The same timesheet line has produced more than one earnings line with matching units, pay rate, total and note.
• Expense without a tax code. An expense in the run carries no tax code. This one only applies where the business connects QuickBooks to an online journal service.

Setting warnings for a pay schedule

The controls live in Payroll Settings, under Pay Schedules. The steps are short:

1. Open Payroll Settings and select Pay Schedules.
2. Choose the schedule you want to change.
3. Select the pencil icon beside pay run warnings.
4. Tick the alerts you want to see on that schedule, and untick the ones you would rather hide.
5. Close the window with the X.
6. Select Save.

The choice applies to the schedule, not the whole company. A weekly schedule for hourly staff can keep the birthday and anniversary alerts switched on, while a monthly salaried schedule runs quieter. Unticking a warning does not repair any underlying record. It only stops the message from appearing on that schedule’s runs.

The mistakes the list is built to catch

Grouped together, the alerts guard against three kinds of trouble. Pay accuracy sits at the centre: duplicate earnings lines, a negative net figure, and rate reviews prompted by a birthday or a work anniversary all change what an employee is actually paid. Leaver hygiene is the second group, covering terminated employees who reappear on a run and reimbursements still owed to them. The last group is record quality, which covers expired qualifications and expenses captured without a tax code.

Reading a warning when it appears

When a warning shows up as you create or run a pay run, select the warning itself. QuickBooks expands it and shows the detail behind the alert, which usually identifies the employee and the condition that triggered it. Work from there. Some warnings call for a correction before payment, such as missing BACS details. Others are simply a prompt to review a rate of pay before the figures are committed. Closing the alert without acting on the underlying record leaves the same problem waiting on the next run.