Apply or undo a banking rule
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Follow this guide to review rule output on feed transactions and reverse the rule assignment when it produced the wrong treatment.
What you’ll accomplish
Review rule output on feed transactions and reverse the rule assignment when it produced the wrong treatment. 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 controller includes an undo_banking_rule action. Undoing the rule assignment is not necessarily the same as reversing an already posted accounting transaction.
If the rule has already created or matched ledger activity, inspect the linked Accounting transaction and correct it through the supported transaction flow.
Rule changes should be tested against future feed rows before reactivation.
Follow these steps
- Go to the feed and filter rows with an applied rule.
- Check the statement description and supporting document.
- Verify the suggested treatment.
- If wrong, use Undo Banking Rule before posting where possible.
- Correct the rule conditions or deactivate the rule.
- Reclassify or match the row correctly.
- Check other rows affected by the same rule.
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
- Do not undo a rule without checking whether a transaction was posted.
- Check all historical rows from a faulty rule.
- Use correction procedures for closed periods.
- Do not recreate a rule with the same broad condition.
- 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.
