Skip to content
English
  • There are no suggestions because the search field is empty.

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)

How to Set Up Dissection Restrictions

Enhanced GL Dissection Controls are configured using Custom Data. Each Custom Data record defines whether a specific dissection field can be changed after a transaction has been posted.
This setup allows agencies to either:
  • Prevent a field from ever being changed after posting, or
  • Prevent changes only for specific transaction types
These settings apply automatically when users use Dissect on posted GL transactions.
 

Step 1 – Create a Custom Data Record

  1. Go to Custom Data → Browse.
  2. Click New Custom Data.
  3. In Custom Data Type, select the dissection field you want to control.
    Examples:
    • GL Dissection block Supplier change
    • GL Dissection block Employee change
  4. Set the record to Active = True.
  5. Click Save.
Once created, the system will use this record to determine whether changes to that field are allowed during Dissect.
 

Option 1 – Block All Changes to a Field

Use this option if a field should never be changed after a transaction is posted.
How to configure
  • Create a Custom Data record as described above.
  • Leave all other fields (such as GL Account or Text) blank.
Result
  • Any attempt to change this field using Dissect will be blocked.
  • Users will see a message explaining that the change is not allowed.
Example
  • An agency decides that Supplier should never be modified after posting to ensure GL and subledger reporting always remain aligned.

Option 2 – Block Changes for Specific Transaction Types

Use this option if a field should generally be changeable, except for certain transaction types.
 
How to configure
  • Create a Custom Data record for the appropriate dissection field.
  • In the Text field, enter the name of the transaction type you want to restrict
    (for example: Supplier Invoices).
  • Save the record.
Result
  • Users can change the field on most transactions.
  • Changes will be blocked only when the transaction type matches the value entered.
Example
  • Allow Supplier changes on journals.
  • Block Supplier changes on Supplier Invoice transactions to protect invoice integrity.

What Users Will Experience

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

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