5 min

8 Feb, 2026

Unreconcile and Redo in Xero: What Actually Happens

23.png

What’s Actually Happening

Unreconcile and Redo in Xero feels like a small fix. You spot a transaction coded to the wrong account, click unreconcile, correct it, and reconcile again. The bank balance still matches, so it feels resolved.

But when people search “what happens when you unreconcile in Xero” or “does unreconcile affect BAS,” it’s usually because something shifted after the change. The BAS report looks different. The GST payable moved. The reconciliation summary doesn’t match what it did before.

Unreconciling a transaction doesn’t just break the match to the bank line. It temporarily removes the ledger entry that was created during reconciliation. When you redo it, you are effectively rebuilding that entry, and if anything changes in the process, the reporting changes too.

Where It Breaks

The most common issue is GST coding. If you unreconcile and change the account code, the tax rate may default differently. Even a small shift from GST on purchases to GST-free or vice versa will change the BAS report.

It also affects timing. If the transaction date or coding is adjusted, it may move between reporting periods. That can alter GST totals in the current BAS and sometimes in prior periods if backdated.

If you are working during a bank feed disruption and manually adjusting transactions after a CSV import, unreconcile and redo can compound duplicate issues. The reconciliation screen may still look clean, but the transaction layer underneath has changed.

This is why files that felt stable suddenly feel unpredictable after several adjustments.

The Takeaway

Unreconcile and Redo in Xero is not dangerous, but it is powerful. Every time you use it, review the GST tax code, the account selection, and the transaction date before reconciling again. Don’t assume the system will apply the same treatment as before.

Reconciliation confirms the bank matches. It does not confirm the reporting stayed the same. If you treat Unreconcile and Redo carefully, your BAS remains stable. If you use it casually during busy periods, small shifts can turn into bigger reporting issues later.