Accounting & Bookkeeping · How-to guide

Review, correct or delete converted transactions

Inspect linked accounting details and use the least destructive supported correction when a conversion is wrong.

Audience: Senior accounting staffFeature: Conversion maintenanceModule v1.4.5

Feature pathAccounting → Transactions → select source group

Before you beginThis guide follows Accounting and Bookkeeping module version 1.4.5. The required access is Accounting Transactions: View/Edit/Delete as applicable. 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

Inspect linked accounting details and use the least destructive supported correction when a conversion is wrong. 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 has source-specific delete-conversion and transaction delete actions plus bulk actions. Their availability depends on permission and source type.

Deleting the source record, deleting the accounting conversion and reversing the economic event are different actions. Use the action that matches the approved correction.

If the wrong mapping affects many records, stop automation, correct the mapping and agree how historical entries will be handled.

Step-by-step workflow

Open the source transaction and its accounting detail.
Identify whether the source data, mapping or conversion status is wrong.
Correct the source or mapping first.
Use the module's supported delete-conversion action only with authorisation.
Reconvert the source if appropriate.
Compare old and new ledger results.
Record the correction reason and rerun affected reports.

Important fields and decisions

Source recordThe operational document that generated the entry.

Converted recordThe module's accounting transaction and ledger lines.

Delete conversionRemoves the accounting representation but may not remove the source.

Re-conversionShould occur only after correcting source data or mappings.

Audit referenceExplains why a correction was made.

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 delete a conversion merely to force a dashboard number.
Do not leave a live source permanently unconverted without explanation.
Respect closed periods.
Use a journal adjustment when policy prohibits rebuilding history.
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:invoice reconciliation check report approval mapping double-entry sales accounting payment credit note expense purchase warehouse payroll

Was this guide helpful?

Review, correct or delete converted transactions

What this feature does

How the module flow works

Step-by-step workflow

Important fields and decisions

What happens after completion

Controls, checks and common mistakes

Related guides