Accounting mapping setup overview
Connect CRM source records and optional modules to the correct debit and credit accounts before automatic conversion is enabled.
What this feature does
Connect CRM source records and optional modules to the correct debit and credit accounts before automatic conversion is enabled. 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 module has dedicated table and save actions for tax, payment-mode, expense-category, item and item-group mappings, plus integration-specific setting screens.
Automatic conversion hooks use these mappings when invoices, payments, expenses, credit notes and supported module records change status.
When the same wrong account recurs, correct the mapping rather than manually editing every resulting transaction.
Step-by-step workflow
- List every transaction type the organisation uses.
- Open Mapping Setup and complete General mappings first.
- Map control accounts, income, expense, tax, cash and bank accounts.
- Complete active optional-module tabs.
- Save each mapping group and verify active status.
- Convert one controlled record from each source type.
- Inspect the debit and credit lines and correct the mapping before broad automation.
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
- A saved mapping is not proof that the accounting treatment is correct.
- Avoid mapping multiple unrelated transaction types to one account.
- Keep deactivated accounts out of mappings.
- Document changes that affect automatic conversion.
- 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.