Accounting & Bookkeeping · How-to guide

Remove invalid or wrongly mapped Accounting entries

Use the module's maintenance actions only after identifying the exact invalid record or mapping problem and protecting audit history.

Audience: Finance administratorsFeature: Accounting maintenanceModule v1.4.5
Feature pathAccounting → Banking / Transactions / Settings, according to the affected record
Before you beginThis guide follows Accounting and Bookkeeping module version 1.4.5. The required access is Relevant Edit/Delete permission. 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

Use the module's maintenance actions only after identifying the exact invalid record or mapping problem and protecting audit history. 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 includes remove_invalid_entries and remove_wrong_mapping actions in addition to source-specific delete conversion functions. These actions are technical maintenance tools and should be more restricted than routine transaction review.

An incorrect classification is not always invalid data. In an approved closed period, a correcting journal may be preferable.

When many transactions share the problem, test the corrected mapping on one record before processing the remainder.

Step-by-step workflow

  1. Identify the exact source and ledger records.
  2. Export the affected transaction detail.
  3. Correct the mapping or account status first.
  4. Use Remove Invalid Entries or Remove Wrong Mapping only when its scope matches the issue.
  5. Reconvert or post an approved correction.
  6. Re-run Trial Balance and relevant reports.
  7. Document the identifiers and reason.

Important fields and decisions

Invalid entryA local record that fails the module's integrity expectations.
Wrong mappingAn account mapping that generated incorrect classification.
Remove invalid entriesMaintenance action intended for specific bad records.
Remove wrong mappingClears an erroneous mapping relationship through a dedicated action.
Correction methodCan be delete-and-reconvert, journal adjustment or configuration repair depending on policy.

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

  • Do not run maintenance actions speculatively.
  • Do not remove evidence from a closed period.
  • Pause automatic conversion during systemic correction.
  • Verify bank and subledger balances after repair.
  • 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.