Account Classes
Account Classes let you tag revenue and expense transactions with a category — product lines, departments, projects, cost centres — so you can break down your Profit & Loss and other reports by class without creating a separate set of GL accounts for each category.
Enabling the Feature
Account Classes are an optional feature that must be turned on before they appear anywhere in the application.
- Open File › Business Features (see Business Features).
- In the Advanced section, check Account Classes.
- Click Save.
Once enabled, Account Class columns and fields appear on all supported transaction screens. Turning the feature off hides these fields but does not delete any data — turn it back on at any time and your classes reappear.
Creating Account Classes
Go to General Ledger › Account Classes to open the Account Class List, then click New to create a class.
Each class has three fields:
| Field | Description |
|---|---|
| Name | A descriptive name such as “East Region”, “Product Line A”, or “Marketing”. |
| Number | A short code for sorting and reporting. |
| Parent | Optional. Assign a parent class to build a hierarchy (e.g. “East Region” under “Regions”). |
For full field details, see Account Class Master.
The Key Rule: Income Statement Accounts Only
Account classes can only be applied to revenue and expense (Income Statement) accounts. They cannot be applied to balance sheet accounts (assets, liabilities, equity).
This rule is fundamental: classes are designed for profitability analysis, not for tracking where assets sit. The system enforces this automatically:
- Manual entry on a transaction screen — if you assign a class to a line that posts to a balance sheet account, Quasar displays an error and clears the class.
- Default class from a header field — when a transaction is saved, any default class is silently ignored for lines that post to balance sheet accounts.
Where Classes Appear
Once the feature is enabled, Account Class fields appear on the following transaction screens. Each screen supports classes slightly differently depending on its posting behaviour.
General Journal
The General Journal adds an Account Class column directly in the line items table. Every journal line that posts to a revenue or expense account can have its own class.
Cheques (Quick Pay Mode)
In Quick Cheque mode, each account allocation line gets an Account Class column. Vendor Cheque and Customer Cheque modes do not use classes because they post to AP/AR control accounts.
Payouts
The Payout screen has a default Account Class in the header that applies to all expense lines, plus a per-line Account Class column that can override the default for individual lines.
Card Adjustments
The Card Adjustment screen has a default Account Class in the header and a per-line Account Class column in the account lines table.
Item Adjustments
The Item Adjustment has a default Account Class on the Accounts tab and a per-line class in the items table. Classes are applied only to the expense account posting — the inventory (asset) side of the entry never receives a class.
If you use Adjustment Reasons, each reason can store a default account class that auto-fills when the reason is selected.
Tender Adjustments
The Tender Adjustment has an Account Class field that is applied to the expense account posting.
Vendor Invoices
On the Vendor Invoice, an Account Class column appears on item lines, but only for purchase-only items (Sold = N, Inventoried = N). These items are expensed directly and qualify for class tracking. Inventoried and sold items post to asset accounts and cannot have a class.
Vendor Claims
The Vendor Claim follows the same rule as the Vendor Invoice — the Account Class column is only available for purchase-only items.
How Classes Flow to the General Ledger
When a transaction with account classes is saved, Quasar records the class on each qualifying GL posting line. This means the Account Inquiry and financial reports can filter or group by class.
| Posting Type | Class Behaviour |
|---|---|
| Revenue / Expense accounts | Class from the transaction line is recorded. |
| Asset accounts (Inventory, Bank, AR) | No class — always blank. |
| Liability accounts (AP, Tax) | No class — always blank. |
| Equity accounts | No class — always blank. |
Analysing by Account Class
Once transactions are tagged with classes, the Account Class Analysis screen provides a powerful hierarchical drill-down into your financial data grouped by class. This is the primary tool for answering profitability questions like “How much revenue came from the East Region?” or “What were the total expenses for Project Alpha?”
For full screen details, see Account Class Analysis.
Access: Ledger section in the Navigation Sidebar, or Setup › Ledger › Account Class Analysis menu.
How the Drill-Down Works
The analysis screen presents your data in three progressively deeper levels. Each level answers a different question about your class-based financials:
| Level | What You See | Action |
|---|---|---|
| Top Level | All root account classes with Debit, Credit, and Net totals | Double-click a class to drill into it |
| Class Level | Child sub-classes (Type = “Class”) and individual GL accounts (Type = “Account”) within the selected class | Double-click a sub-class to go deeper, or an account to see transactions |
| Transaction Level | Individual journal entries posted to the selected account with that class | Double-click to open the transaction editor |
The Breadcrumb Navigator
As you drill down, a clickable breadcrumb trail appears at the top of the screen showing your current path (e.g. All Classes › Revenue › Sales › Retail). Each segment is clickable — click any level to jump directly back to it. The Back button navigates one level up.
Filter Controls
Use the filter bar at the top of the screen to narrow the analysis to a specific period or location:
| Filter | Purpose |
|---|---|
| Date Range | Quick presets (This Month, Last 30 Days, This Year, etc.) for fast selection of common reporting periods. |
| From | Custom start date for the analysis period. |
| To | Custom end date for the analysis period. |
| Store | Limit analysis to a single store (leave blank for all stores). |
Reading the Results
The columns displayed change depending on the drill-down level:
- At Top Level and Class Level: Number, Name, Debits, Credits, Net
- At Transaction Level: Type, Number, Store, Date, Memo, Debit, Credit
- A Totals row appears at the bottom of every level, summarising the visible data.
Practical Examples
Account Class Analysis is most valuable when your class hierarchy mirrors a real business dimension. Here are three common scenarios:
- Departmental Profitability — Create top-level classes for each department (Marketing, Operations, R&D). Drill into each department to compare revenue against costs and quickly identify which departments are most profitable.
- Project Costing — Create a parent class “Projects” with child classes for each active project (e.g. Project Alpha, Project Beta). Track expenses by drilling down through the hierarchy to see per-project spending and compare against budgets.
- Regional Analysis — Create classes for East, West, and Central regions. Compare revenue and expenses by region to discover geographic trends and allocate resources accordingly.
Account Class Setup Checklist
- Enable Account Classes in File › Business Features
- Plan your class structure (flat list or parent/child hierarchy)
- Create classes in General Ledger › Account Classes
- If you use Adjustment Reasons, assign default classes to each reason
- Begin entering transactions with classes assigned
- Use Account Class Analysis (Ledger › Account Class Analysis) to drill into totals by class hierarchy
- Run a Profit & Loss report filtered by class to verify the breakdown
- Chapter 4 — Plan and create your inventory items
- Chapter 5 — Configure additional stores if needed
- Chapter 27 — Reports & Analysis for additional reporting tools