There is Never AP Bills as part of QB payroll. It never makes sense to make something and Void it, either. That is just spinning your wheels as busy work.
If this is paid, it is supposed to show as a Liability Check. That way, the Payroll Items are listed and that also flows the data to the accounting, to keep, for example, Payroll Liability Balance matched to the Payroll Reporting that lists by Payroll Item the specific amounts unpaid.
When someone Pays by manual Write Check, they break that relationship. You need to Find how they paid it. That is needed, so you know what they did wrong.
Example: If they Paid as Liability on the Expenses tab of a Write Check, you will Replace their check with your Pay Liability check, same date, amount and check #. Then, you Delete theirs. Then you can rereconcile the bank for the most recent ending balance, and Ignore the beginning balance and clear only these recreated transactions, and you get a difference of 0 and you are back on track. That's because they paid Liability, just not with the proper Tool.
If you see they paid it as Expense, that is a different problem. That made a mess in your Financial reporting and orphaned not only the Payroll Item, but also, the Payroll Liability balance, and double-reported the Expense, since this never was the employer's money or expense. In this example, and make sure you run this past your own CPA, you can make one Pay Liability Check for 2017, and select what still shows as needing to be paid. Then, click on the Expenses tab of this liability check and put the same total here as negative, and use the same Expense account they used. Now hit Recalc. You have a $0 check. You offset their error by this Lump Sum. The CPA might need to amend tax reporting, because of this error.
And make sure to run the Liability Balances report and for All Dates and Columns by Year, then by Quarter. Also, the Create Custom Liability Payment function is how you can Combine those differently Scheduled liabilities, if you need to use the Lump Sum Expense offset method.
Good luck. This is unfortunate.
