Britixo CRMBritixo CRM Enterprise Help Centre
Accounting & Bookkeeping · How-to guide

Ignore, delete or restore bank-feed rows

Handle feed rows that are duplicates, informational or imported incorrectly without concealing genuine bank activity.

Audience: Senior accounting staffFeature: Feed row lifecycleModule v1.4.5
Feature pathAccounting → Banking → Banking Feeds
Before you beginThis guide follows Accounting and Bookkeeping module version 1.4.5. The required access is Accounting Banking: Edit or Delete. A related screen can remain hidden when an optional module is inactive, a source record is in an ineligible status, the selected account is inactive or the user is not an assigned approver.

What this feature does

Handle feed rows that are duplicates, informational or imported incorrectly without concealing genuine bank activity. It forms part of Britixo Enterprise CRM's Accounting & Bookkeeping module and uses the module's permission-aware controller, status and mapping flow rather than a generic spreadsheet process.

How the module flow works

The module offers bulk ignore/delete confirmation messages, bank-transaction delete and rule-undo actions. Some restore actions relate specifically to reconciliation.

A row that appears duplicated may be a pending transaction replaced by a posted transaction; compare identifiers, dates and amounts.

If excluding the row causes the statement balance not to reconcile, the decision is incomplete.

Step-by-step workflow

  1. Open the feed row and verify it against the official statement.
  2. Check for an existing duplicate import or pending-versus-posted replacement.
  3. Use Ignore for a legitimate non-posting row supported by policy.
  4. Use Delete only for an erroneous local record and with approval.
  5. Restore or undo when the decision was wrong.
  6. Reconcile the statement total.
  7. Document any excluded row that affects audit review.

Important fields and decisions

IgnoreMarks a row as not requiring Accounting posting while preserving review context.
DeleteRemoves a local bank transaction record through a restricted action.
Restore or undoReturns supported rows or reconciliation state for review.
ReasonShould explain why the row does not represent a ledger event.
Duplicate evidenceMust be confirmed against bank identifiers and statement totals.

What happens after completion

After the action is saved, Britixo keeps the Accounting record connected to its source and updates the visible status or ledger data supported by this workflow. Review the saved result rather than relying only on a success message. Where the action posts accounting data, total debits and credits must balance and the accounts must match the approved mapping or manual selection.

  • Open the saved record and confirm its final status.
  • Review the source reference and every debit and credit line where ledger data was created.
  • Use the relevant register, ageing, reconciliation or report to verify the wider effect.

Controls, checks and common mistakes

  • Never ignore unexplained withdrawals or deposits.
  • Do not delete bank evidence to force reconciliation.
  • Review pending and posted duplicates carefully.
  • Keep an approval trail for destructive actions.
  • Use the least destructive correction available and record the reason for material changes.
  • Do not bypass a permission, approval or closed-period control by changing unrelated data.
Accounting and data safetyDeletion, reset, void, refund, mapping, journal and reconciliation actions can change financial history. Use approved access, retain supporting evidence and validate the result in the General Ledger or relevant control report.
Browse connected topics:bankingreconciliationcheckreportapprovalmappingdouble-entryPlaid
Review and edit banking feeds →Reconcile a bank account →Reopen or restore a bank reconciliation →Use transaction and account audit reports →Banking workspace overview →Create and manage an Accounting bank account →