Troubleshoot unconverted or incorrectly mapped transactions

Find why a source record did not convert or posted to unexpected ledger accounts.

What this feature does

Find why a source record did not convert or posted to unexpected ledger accounts. 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

Because the module supports many sources, the required mapping differs by workflow. An invoice needs receivable, income and tax mappings; an expense needs category, payment and tax mappings; a warehouse event needs inventory and cost mappings.

Status hooks are important. A draft or unapproved record may correctly remain unconverted.

If conversion code reports an exception, retain the record identifiers and server log evidence for technical support without exposing confidential financial data.

Step-by-step workflow

1. Open the source record and note its type, status, date and currency.
2. Check whether the transaction appears in the appropriate Accounting tab.
3. Review automatic-conversion settings.
4. Review all relevant mappings and account active status.
5. Check for an existing converted record or error indicator.
6. Correct one cause at a time and retest with a controlled record.
7. Use transaction and ledger reports to confirm the result.

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

• Do not repeatedly click Convert without diagnosing the cause.
• Do not map to a random account to pass validation.
• Do not remove duplicate protection without code review.
• Pause bulk automation when a systemic mapping error is found.
• 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