Create and manage accounting classes
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Follow this guide to add optional classes for segmenting transactions and reporting across departments, locations or other approved dimensions.
What you’ll accomplish
Add optional classes for segmenting transactions and reporting across departments, locations or other approved dimensions. It forms part of Pixie CRM 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 it 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.
Follow these steps
- Define the reporting question the class will answer.
- Go to Settings → Class.
- Search for an existing equivalent class.
- Create the class with a clear name and hierarchy.
- Assign it to a controlled journal or source record.
- Run a report that includes class context, where supported.
- Deactivate obsolete classes after reviewing history.
Settings to check
Check it worked
After the action is saved, Pixie CRM 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.
Common mistakes to avoid
- 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.