Britixo CRMBritixo CRM Enterprise Help Centre
Accounting & Bookkeeping · How-to guide

Create and manage accounting classes

Add optional classes for segmenting transactions and reporting across departments, locations or other approved dimensions.

Audience: Finance administratorsFeature: ClassesModule v1.4.5
Feature pathAccounting → Settings → Class
Before you beginThis guide follows Accounting and Bookkeeping module version 1.4.5. The required access is Accounting Settings: View, Create, Edit or Delete. 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

Add optional classes for segmenting transactions and reporting across departments, locations or other approved dimensions. 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 provides class table, create/edit/delete and lookup actions and listens to class-related hooks from several integrations.

Classes can improve management analysis but incomplete assignment can make class-based comparisons misleading.

Whether a specific transaction form displays class depends on the code path for that source type.

Step-by-step workflow

  1. Define the reporting question the class will answer.
  2. Open Settings → Class.
  3. Search for an existing equivalent class.
  4. Create the class with a clear name and hierarchy.
  5. Assign it to a controlled journal or source record.
  6. Run a report that includes class context, where supported.
  7. Deactivate obsolete classes after reviewing history.

Important fields and decisions

Class nameUse a stable business label.
Parent or hierarchyUse only where the interface and reporting design support it.
Active statusControls future selection.
Transaction assignmentClass is available only on forms and integrations that implement it.

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 use classes as a substitute for ledger accounts.
  • Keep the class list short and governed.
  • Do not change historical class meaning.
  • Train users on when class is required.
  • 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:reconciliationChart of Accountsjournal entrycheckbudgetproject budgetreportapprovalclassmappingdouble-entry
Create and edit a journal entry →Create and edit a project budget →Accounting report centre overview →Chart of Accounts overview →Create and edit a Chart of Accounts account →Import a Chart of Accounts →