Reset Accounting configuration or data safely

Understand the module's reset actions and use them only in an authorised recovery or pre-production process.

What this feature does

Understand the module's reset actions and use them only in an authorised recovery or pre-production process. 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 controller contains reset_data, reset_accounts, reset_account_detail_types and reset_income_statement_modifications. These are materially different actions but all can alter configuration or reporting.

This help centre does not instruct users to bypass confirmation or server backups. Use the organisation's change-control procedure.

For ordinary mapping or transaction errors, use targeted correction workflows instead of reset.

Step-by-step workflow

1. Stop and identify the exact reset action.
2. Confirm the environment is not live or obtain written approval.
3. Create and verify a database backup through the approved platform process.
4. Export required reports and configuration evidence.
5. Run the narrowest reset action once.
6. Validate Chart of Accounts, mappings, transactions and reports.
7. Restore immediately if the result exceeds the approved scope.

Important fields and decisions

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 test reset actions on live data.
• Do not assume a reset has built-in rollback.
• Do not reset accounts with posted history casually.
• Restrict direct URLs and permissions.
• 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.

Related guides