Fixing mistakes

Nearly everything here can be undone. Knowing which lever to pull — and which not to — saves a lot of anxiety at month-end.

They’re listed below roughly in order of how routine they are.

A rate was wrong, and you’ve already committed

Just fix the rate card. Revenue is worked out at the moment the export is read, not frozen at commit, so correcting the service picks it up everywhere. There’s nothing to re-commit.

This is the most common “problem” and it isn’t really one.

The wrong site, already committed

The collections need moving to the right site rather than deleting. This touches the bookings, the jobs that follow them, and the staged import records that form the audit trail — so raise it rather than attempting it from the grid.

Preventing it is much cheaper: see the site-mapping warning in Reviewing a batch.

Uncommitting a batch

A committed batch can be unwound — the jobs are deactivated, the emptied bookings and runs are removed, the staged lines are cleared, and the batch returns to ready so you can fix and re-commit.

Removed work doesn’t bill: deactivated jobs and trashed bookings are excluded from the Xero export.

Correcting one invoice in a multi-invoice month

An invoice that’s locked and says it needs a developer

Leave it alone. The message means jobs were created but not all lines were marked as committed, so the invoice is deliberately barred from committing again.

Don’t re-commit, and don’t delete the lines. The first would bill the work twice; the second would destroy the record of what your supplier charged you. Raise it with support with the invoice reference — the lock is doing its job.

Things that are currently manual

• Bin-delivery charges aren’t priced automatically yet. Those lines come through unpriced and are typed into the Xero draft by hand.
• Supplier bills — what you owe the subcontractor — are worked out per line but still raised manually in Xero.