How GL Segmentation migration works
Know how GL Segmentation migration works
This is how migration works:
Extraction: Your current GL Segmentation V1 settings are automatically collected. Each segment and mapping tied to transaction types is identified and prepared for transformation.
Transformation: The system applies predefined rules to transform V1 segments into the V2 format. Duplicate or equivalent fields across transaction types (e.g., invoice tax vs. debit memo tax) are merged into unified segments, making the setup cleaner and easier to maintain.
Draft Mode: The new V2 segments are loaded into your environment in Draft mode. This ensures that nothing is enforced immediately, and you can safely validate the results before they impact future Journal Runs.
User input: You will need to review the migrated segments, configure GL code mappings, and correct any gaps or blanks left by the system. This step ensures that the migrated setup reflects your specific accounting practices.
Publishing: Once reviewed and adjusted, you can publish the segment set. After publishing, the new configuration becomes active, and all future Journal Runs will follow the GL Segmentation V2 rules.
If V2 is enabled but no segment set is published, new Journal Runs will be blocked until publishing is complete.
Activities to do
For accurate migration, do the following activities:
Review draft segments: Confirm that migrated segments look correct and align with your business rules.
Adjust & map: Make necessary edits, configure GL code mappings for each segment, and fill in any gaps.
Publish: Finalize and publish the segment set to activate it for future Journal Runs. This ensures your accounting entries are consistent and ERP-ready.