Accounting & Bookkeeping · How-to guide

Accounting & Bookkeeping module overview

Understand the complete Britixo Accounting & Bookkeeping workspace, its menu structure and how operational CRM records become double-entry accounting transactions.

Audience: Administrators, finance managers and authorised accounting staffFeature: Module overviewModule v1.4.5
Feature pathAccounting
Before you beginThis guide follows Accounting and Bookkeeping module version 1.4.5. The required access is Any Accounting permission; each submenu has its own 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

Understand the complete Britixo Accounting & Bookkeeping workspace, its menu structure and how operational CRM records become double-entry accounting transactions. 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 is organised around a double-entry ledger: every posted transaction must balance debit and credit values. The operational CRM record and the accounting transaction are connected, but they serve different purposes.

Menu options are permission-aware. A user may see the dashboard but not journals, settings or reports. Optional integration tabs are code-controlled and do not appear unless their source module is installed and active.

Britixo documentation uses the visible interface names; internal controller names and database identifiers are intentionally not exposed to end users.

Step-by-step workflow

  1. Open Accounting from the main staff sidebar.
  2. Start with Dashboard to review conversion and financial summaries.
  3. Open Settings and complete general settings, account structure and mappings before enabling automatic conversion.
  4. Use Transactions to review source records and their converted status.
  5. Use Banking and Reconcile to match bank activity to posted accounting entries.
  6. Use Reports to validate balances and investigate exceptions.

Important fields and decisions

Menu visibilityThe Accounting menu appears only when the staff role has at least one relevant module permission.
Source recordsInvoices, payments, credit notes, expenses and supported optional modules remain the operational source records.
Ledger recordsConverted transactions create debit and credit entries for reporting and reconciliation.
Conditional tabsPayroll, purchase, warehouse, manufacturing, Omni Sales and fixed-equipment screens appear only when those modules are active.

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

  • Confirm the organisation's base currency and financial year.
  • Restrict Settings and destructive permissions to authorised staff.
  • Test conversion on controlled records before enabling broad automation.
  • Reconcile opening balances before relying on financial reports.
  • 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.