Reverse an accidental posting batch

Stop posting and define the exact affected rows before trying to recover an accidental bank-feed batch.

Identify What Posted

1. Open Fast Coding, then select Posted.
2. Use the posting date and search to identify the affected company and rows.
3. Record the company, bank register, date range, row count, amounts, coding, and posting source.

Do not assume every row on the same date belongs to the same action. Rule matches, individual posts, and other company activity can appear beside the batch you are investigating.

Use The Supported Recovery Path

LedgerHQ currently has row-level Undo; it does not have a customer-facing multi-select or batch-Undo screen.

For a small, exact set:

1. Open the company’s Bank Feeds and select Posted.
2. Open one affected row, click Undo, and confirm.
3. Repeat only for the other rows you verified belong to the accidental set.

For a broad or uncertain set, create a support ticket and include the exact scope you recorded above. Do not include bank credentials, full account numbers, or one-time codes.

Verify Recovery

Confirm that balances no longer include the incorrect postings and each undone bank row is back in Ready with its coding retained. Review reports and the register for the affected dates.

Do not create a separate offsetting journal entry. It can hide the original feed-owned mistake instead of returning those bank rows to review. For the single-row recovery details, see Undo a posted bank transaction.