Division Exception Report — Complete User Guide — Two Accounts Web

A comprehensive, report-centric guide covering how a user reaches Reports > Division Exception Report, every field on the report, how the figures are calculated from the general ledger, and how the report supports segment control and reporting.

Table of Contents

1. What Is the Division Exception Report?
2. Prerequisites Before You Can Run It
3. Making the Report Appear in the Navigation
4. Related Configuration in Settings
   • Creating Divisions
   • Division Tracking on Accounts
   • Assigning Divisions on Transactions
5. Creating the Report — Step by Step
6. Field-by-Field Guide
7. How Each Value Is Calculated
   • What Counts as an Exception
   • Grouping and Summing
   • The Amount Column and the Total Row
   • Drilling Into the Transactions
8. Sample Data and Output
   • Sample Setup
   • Step-by-Step Calculation Walkthrough
   • Report Output
   • Verification
9. Effects on the Rest of the System
10. Behaviour Nuances and Cautions
11. Accounting Standards Considerations

1. What Is the Division Exception Report?

The Division Exception Report reveals Profit and Loss (income and expense) transactions that were recorded without being assigned to any Division during a chosen period. In a business that tracks performance by division (branch, department, or segment), every income and expense should normally be attributed to a division. This report lists the amounts that were not — the “exceptions” that may need to be allocated or corrected.

The report answers the question: “Which profit-and-loss amounts in this period were posted without a division, and how much is unallocated on each account?”

Key characteristics of this report:

• It is period-based — you provide a From Date and a To Date.
• It covers Profit and Loss accounts only — income and expense, not balance-sheet accounts.
• It shows only unallocated amounts — transactions already tagged with a division are excluded.
• It is read-only and drillable — the totals can be clicked to list the underlying unallocated transactions.

2. Prerequisites Before You Can Run It

1. At least one Division must exist (created under Settings > Divisions). The report only appears once a Division has been created — a division-untracked business has nothing to check against.
2. There must be Profit and Loss transactions in the period whose Division is blank, for the report to show any rows. If every P&L item is division-assigned, the report shows no rows for the period.
3. The report reads the general ledger, so all relevant sales, purchases, receipts, payments, and journal entries must be posted.

3. Making the Report Appear in the Navigation

Unlike most reports, the Division Exception Report is not controlled by a navigation switch in the Customize Menu. Instead, it appears automatically whenever the business has at least one Division record.

1. Ensure at least one Division has been created (Settings > Divisions). See Section 4.1.
2. The Division Exception Report then becomes visible under the Reports area, in the Divisions category.

4. Related Configuration in Settings

4.1 Creating Divisions

Where: Settings > Divisions.

Divisions are named segments of the business (for example branches, departments, or product lines) used to break down income, expenses, assets, and liabilities. Each Division has:

4.2 Division Tracking on Accounts

Where: Applicable Profit and Loss and Balance Sheet accounts.

Accounts that support division tracking allow each transaction line to carry a Division. Profit and Loss accounts (and most Balance Sheet asset/liability accounts) enable this tracking. The Division Exception Report uses that tracking field to tell whether a P&L transaction is allocated — those with a blank division are flagged as exceptions.

4.3 Assigning Divisions on Transactions

Where: Sales invoices, purchase invoices, receipts, payments, journal entries, and other record screens.

Where an account offers a Division field, filling it attributes that amount to a division. Leaving it blank leaves the amount unallocated — and, if it is an income or expense, it is exactly the kind of item this report brings to your attention.

5. Creating the Report — Step by Step

1. Ensure at least one Division exists (Settings > Divisions).
2. Open the Reports area from the navigation bar.
3. Scroll to the Divisions category and select “Division Exception Report.”
4. The system shows the list of previously created reports (each identified by its From Date, To Date, and Description).
5. Click the “New Report” button.
6. Enter the From Date — the first day of the period (required).
7. Enter the To Date — the last day of the period, inclusive (required).
8. Optionally enter a Description — a free-text label for your own reference (for example “Unallocated items for Q1 review”).
9. Save. The new report is added to the list, ordered by its From Date.
10. Open (View) the report to display the unallocated income and expenses computed for that period.

6. Field-by-Field Guide

6.1 Fields You Set When Creating the Report

6.2 Columns Shown on the Report

The report is displayed in the same structure as the Profit and Loss Statement: it shows the Profit and Loss groups/categories in their normal order, and under each group only those accounts that have a non-zero unallocated balance in the period.

7. How Each Value Is Calculated

7.1 What Counts as an Exception

A transaction is counted as an exception if all of the following are true:

• its amount is non-zero;
• its account is a Profit and Loss account (income or expense);
• its date is within the report period (on or after From Date and on or before To Date); and
• its Division is blank (no division was assigned).

Any transaction with a Division assigned is excluded from this report, because it is not an exception. Balance-sheet accounts and zero-amount lines never appear.

7.2 Grouping and Summing

For each Profit and Loss account:
   Amount (account) = sum of base-currency amounts of all qualifying unallocated entries in the period

The accounts are then laid out under the Profit and Loss groups they belong to,
in the chart-of-accounts order. Accounts with a zero sum are not shown.

7.3 The Amount Column and the Total Row

Amount = the net balance per account, using the ledger Debit/Credit convention:
         income (credit) items and expense (debit) items are shown on their own sides.

Total = the algebraic sum of all listed amounts
        (= total unallocated income credits  +  total unallocated expense debits, net)

7.4 Drilling Into the Transactions

Clicking an account’s Amount opens the individual general-ledger transactions that make up that figure — every unallocated, non-zero entry on that account dated within the period. This lets you identify exactly which invoices, payments, or journal lines need a division. The drill-down applies the same criteria as the report (account, period, no division).

8. Sample Data and Output

The following example uses base currency BDT and two divisions to illustrate.

8.1 Sample Setup

Profit and Loss transactions during the period (BDT):

8.2 Step-by-Step Calculation Walkthrough

Step 1 — Identify qualifying transactions. From the general ledger, select entries that are non-zero, on Profit and Loss accounts, dated 01-Jan-2026 – 31-Mar-2026, with a blank Division. These are the five marked “shown” above. The Dhaka/Chittagong allocations and the Utilities line are excluded.

Step 2 — Sum by account.

8.3 Report Output

Division Exception Report — for the period 01-Jan-2026 to 31-Mar-2026

8.4 Verification

Unallocated income (credits):   100,000.00 + 40,000.00 = 140,000.00
Unallocated expenses (debits):  130,000.00 + 30,000.00 = 160,000.00

Total (net) = 140,000.00 - 160,000.00 = (20,000.00)  ->  shown as a net debit of 20,000.00  ✓

Cross-check per account (only unallocated entries, by date):
   Sales Revenue     ->  15-Feb 100,000.00                         =  100,000.00 Cr  ✓
   Service Income    ->  20-Feb  40,000.00                         =   40,000.00 Cr  ✓
   Salaries & Wages  ->  03-Mar 130,000.00                         =  130,000.00 Dr  ✓
   Rent              ->  12-Mar  30,000.00                         =   30,000.00 Dr  ✓

Excluded because allocated/not-P&L/non-period:
   Sales Revenue (Dhaka 120,000, Chittagong 30,000)  -> division set, not an exception
   Utilities (Chittagong 18,000)                     -> division set, not an exception  ✓
   (Allocated amounts remain in their division segment reports.)

9. Effects on the Rest of the System

The Division Exception Report is derived and changes nothing. Its value is in how it relates to the rest of the system:

10. Behaviour Nuances and Cautions

• It is a management/control report, not a statutory statement. It is designed to help ensure completeness of segment attribution, not to present a regulated financial position.
• Requires divisions to exist. With no Division records the report is hidden; deleting all divisions hides it again.
• Profit and Loss accounts only. Balance-sheet transactions (even with a blank division) never appear; this report concerns income and expenses.
• Blank division is the trigger. Any non-zero P&L entry without a division in the period is an exception; entries with a division are deliberately excluded.
• Only accounts with exceptions are shown. A P&L account whose entire balance is division-assigned does not appear, even if other accounts in the group do.
• Amounts are net per account. Both debits and credits on the same account are summed into a single net figure.
• Drill-down uses the same rules. The transactions opened from an Amount match the report’s account, period, and blank-division criteria.
• Read-only. The report posts nothing; correcting an allocation is done on the original transaction (assigning a division) and re-running the report.
• Zero rows hidden. Accounts whose unallocated sum is zero never appear, so an empty/few-row report means good attribution.

11. Accounting Standards Considerations

Although this is a management control report, it supports practices that align with recognized reporting principles.

11.1 Operating Segment Reporting — IFRS 8

Requirement: Entities report segment information that reflects how operating decisions are made, with income and expenses attributed to reportable segments.

Alignment: Divisions provide the segment framework. This report ensures that the income and expenses feeding those segments are complete, so that segment figures are not understated by unallocated activity. It is the quality control that makes segment reporting reliable.

11.2 Completeness and Faithful Representation — the IASB Conceptual Framework

Principle: Useful financial information must be complete, so that nothing material is omitted.

Alignment: By surfacing unallocated revenue and expense, the report supports the completeness of management accounts. Users can confirm that all profit-and-loss activity is accounted for within a division (or consciously retained as central/unallocated).

11.3 Internal Control and Reconciliation — bas of good practice / IAS 1 object

Principle: An entity needs processes that make its financial records reliable and reconcilable.

Alignment: The report acts as an exception/exception-management control: a routine check that every income and expense is either assigned to a division or deliberately left unassigned, and that the sum of assigned plus unassigned equals the general ledger. This supports the reliability objective behind IAS 1’s fair-presentation requirement.

11.4 Not a Legal-Entity Consolidation

Scope note: Divisions are internal segments, not separate legal entities. Inter-division tracking within a single legal entity does not of itself consolidate or deconsolidate financial statements; legal-entity consolidation is governed by IFRS 10 and is separate from this report.

End of Division Exception Report Guide