Ignore, delete or restore bank-feed rows
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Handle feed rows that are duplicates, informational or imported incorrectly without concealing genuine bank activity.
What you’ll accomplish
Handle feed rows that are duplicates, informational or imported incorrectly without concealing genuine bank activity. It forms part of Pixie CRM 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 it 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.
Follow these steps
- Go to the feed row and verify it against the official statement.
- Check for an existing duplicate import or pending-versus-posted replacement.
- Use Ignore for a legitimate non-posting row supported by policy.
- Use Delete only for an erroneous local record and with approval.
- Restore or undo when the decision was wrong.
- Reconcile the statement total.
- Document any excluded row that affects audit review.
Settings to check
Check it worked
After the action is saved, Pixie CRM 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.
Common mistakes to avoid
- Never ignore unexplained withdrawals or deposits.
- Do not delete bank evidence to force reconciliation.
- Check 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.