Adjustments to Management Ledger Pipeline
Note:
Before using this process, users must confirm that direct posting to Management Ledger is permitted under their organization’s policy and approval controls. The Adjustments to Management Ledger pipeline has been introduced to address data inconsistencies that may occur during journal ingestion from upstream systems after General Ledger processing is complete. The pipeline helps maintain Management Ledger data consistency without requiring manual adjustments, offsets, or downstream corrections.
Drill-down Behavior
Journals processed through the Adjustments to Management Ledger pipeline are not sourced from Accounting Hub and do not pass through the standard decomposition process. As a result, these journals will not appear in drill-down views that trace journals from AHCS/ERP into AFCS journal processing. They remain visible within Management Ledger balances and reporting outputs generated from the results layer.
Prerequisites
It is mandatory to populate the following columns in the Stage Accounting Entries before executing the Adjustments to Management Ledger pipeline.
- Unique Entry Identifier
- As of Date
- Accounting Entry Intent Indicator
- Transaction date
- Posting date
- Account Currency Amount
- Account Currency Code
- Local Currency Amount
- Process Date
- Debit Credit Indicator
- Local Currency Code
- Legal Entity Code
- General Ledger Code
- Code Combination Identifier
- Ledger Identifier
- Account Number
- Current Batch Number
- Channel Code
- Party Identifier
- Account Branch Code
- Account Standard Code
- Original Entry Identifier
- Account Product Code
- Data Source Code
- Data Origination Code
- Organization Unit Code
- Business Unit Code
- Location Code
- Project Code
- Record Creation date
To execute the Adjustments to Management Ledger pipeline, please follow the steps below: