🐉 Meet Pryo the Payroll Dragon
Nobody knows exactly where Pyro the Payroll Dragon came from.
Some believe he was born the first time someone coded wages directly to the Profit & Loss ledger.
Others believe he appears whenever a pay run date doesn’t match the bank account.
Pyro feeds on:
🔥 STP errors
🔥 SGC penalties
🔥 Incorrect payslips
🔥 Payroll clearing nightmares
Fortunately, Green Book has defeated him many times.
Orange Book usually summons him by accident.
Green Book’s advice?
Pyro the Payroll dragon can appear in a sudden flash of fire.He can hatch from a single payment date mismatched with a bank vault. He feasts when wages are miscoded to the wrong ledger. He grows into massive beasts when Single Touch Payroll files are left unreviewed.Fortunately, this financial monster is easily banished when you learn how to spot his tracks.
Wrong pay run dates in Xero are the single biggest payroll nightmare for small businesses, making payslips incorrect and completely wrecking your compliance. When you process a pay run covering the wrong week, or use a payment date that does not match when the cash actually leaves your business bank account, you trigger an administrative avalanche.
Why Wrong Dates in Xero Create Massive Payroll Problems
1. The Pay Period Doesn’t Match the Weeks Worked
- The Danger: Your employees cannot verify their hours.
- The Penalty: Providing misleading payslips violates Fair Work regulations.
- The Fix: If a calendar is incorrectly tracked, you must change your processing sequence or set up a new frequency entirely via the Xero Pay Frequencies Tool.
2. The Payment Date Doesn’t Match Your Bank Account
- The Danger: If you tell Xero you paid staff on Friday, but your business bank account shows the funds cleared on Monday, your bank reconciliation will not match.
- The Penalty: This reporting gap distorts your Single Touch Payroll (STP) filing and creates an absolute mess for your year-end reporting.
3. You Are Reconciling Directly to Expenses Instead of the Payroll Clearing Account
- The Danger: Doing this bypasses Xero’s built-in 804 Payroll Clearing Account (the tracking hub that holds onto your payroll data until the real money moves).
- The Penalty: Coding directly to expenses double-counts your wage costs! It leaves the actual pay run sitting as an unpaid liability in your system, which completely ruins your profit and loss statements and makes your bank reconciliation impossible to balance.
- The Fix: Apply the spent bank transaction directly against your 804 Payroll Clearing Account so it perfectly zeros out the auto-generated liability from your posted pay run.
- The Quick Catch: While standard Xero files default to 804 Wages Payable / Payroll Clearing, your specific chart of accounts may have been altered by a previous bookkeeper or accountant. It might be under a different name or number, but that critical clearing account is definitely in your system somewhere! Always hunt down your designated payroll liability account rather than guessing.
The Hidden Danger: Payday Super Compliance
How to Fix Date Errors in Xero
If you spot an error in a posted pay run, do not panic. You can fix it by following these clean steps:
- Review the Discrepancies: Compare your Xero Payroll Activity Summary against your general ledger bank feed.
- Utilise Unscheduled Pay Runs: To correct past period wage mistakes or reporting classifications, generate an Unscheduled Pay Run in Xero for that exact financial period.
- Adjust the Payment Date: Ensure the corrected payment date precisely reflects the real-world day the bank transfer cleared.
- Check your Reports: Make sure the 804 account balances, and review the other payroll reports to ensure they are now accurate.
- File with STP: Lodge the corrected pay run with the ATO to overwrite the bad data.
