Enhanced GL Dissection Controls

Overview

The Enhanced GL Dissection Controls help organizations manage what information can be changed when using the Dissect action on posted General Ledger transactions.

These controls are designed to protect reporting accuracy by preventing certain dissection fields such as Client, Job, Supplier, or Department from being changed after a transaction has been posted, while still allowing limited, controlled corrections where appropriate.

Why This Matters

The Dissect function allows authorized users to make limited updates to posted GL transactions without reversing or unposting them. While this provides flexibility, some changes can cause GL results to no longer align with subledger or source transaction reporting.

Enhanced GL Dissection Controls allow agencies to:

Protect the integrity of GL and subledger reporting
Prevent changes to sensitive fields after posting
Apply consistent rules across all users
Maintain audit confidence while allowing approved corrections

Where You’ll See This

These controls apply when using:

Accounting → General Ledger → Transaction Search → Dissect

When a user attempts to change certain dissection fields using Dissect, the system will automatically check whether that change is allowed. If not, the change will be blocked and a message will be displayed.

What Can Be Restricted

Enhanced GL Dissection Controls can be used to restrict changes to the following fields:

Department
Journal Description
Job
Client
Product
Employee
Task Type
Supplier

Each field can be restricted independently, giving agencies flexibility to allow some changes while blocking others.

How the Controls Work (High Level)

The system checks agency‑defined rules before allowing a change:

Option 1 – Block Changes Completely

An agency may decide that a specific field should never be changed after posting.

Example:
Supplier should never be modified on posted transactions.

Result:
Any attempt to change Supplier using Dissect will be blocked.

Option 2 – Block Changes for Specific Transaction Types

An agency may allow a field to be changed in general, except for certain transaction types.

Example:
Allow Job changes for journals, but block Job changes for Supplier Invoices.

Result:
Users can change the Job on some transactions, but not on Supplier Invoices.

What Users Will Experience

If a change is allowed, it will save normally.
If a change is restricted, the system will display a message explaining that the change is not permitted.
If multiple transactions are selected, and any one of them is restricted, the change will not be applied.

**What This Feature Does Not Do**

It does not require dissection fields at the time of posting
It does not replace GL Account required dissection rules
It does not change user security or access permissions

For required dissection rules at posting time, see:
Require Dissection on GL Accounts