GL Segmentation migration
Moving to GL Segmentation V2
GL Segmentation V2 offers tenant-level, ERP-compliant segmentation with migrated V1 settings in Draft mode for review, mapping, and publishing, improving consistency and reducing manual effort.
With V2, segmentation becomes a tenant-level feature, ensuring all journal entries follow a consistent format and integrate seamlessly with ERP systems.
This migration is designed to bring more structure, reduce manual effort, and improve data integrity across your accounting operations.
To know how GL Segmentation migration works, see here.
Key benefits
Here are the key benefits of GL Segmentation migration:
ERP alignment: GL Segmentation V2 ensures journal layouts conform to ERP standards. This makes it easier to export, reconcile, and integrate data with your existing ERP and financial reporting tools. By aligning closer to industry practices, your accounting becomes smoother and more audit-ready.
Simplified segmentation: Instead of maintaining different segmentation rules for each transaction type, V2 allows you to manage segments centrally at the tenant level. This simplification reduces complexity, lowers maintenance overhead, and ensures consistent rules are applied across all transaction types.
Accuracy & consistency: V2 introduces automated identification of unique segments and consolidates duplicate values that existed in V1. This ensures that one consistent version of each segment is applied across different transaction types, improving accuracy and reducing the risk of errors during reporting.
User control: Although much of the migration process is automated, you retain full control. The migrated settings are placed in Draft mode, giving you the opportunity to review, adjust, and confirm mappings before publishing. This allows you to customize the final configuration to match your unique business needs.
Auditability & transparency: The migration process is logged, so you have a complete trail of what was migrated, how it was transformed, and any changes made before publishing. This provides confidence that the migration process is compliant, reliable, and fully auditable.
Key considerations
Keep the following key considerations in mind during GL Segmentation migration:
Segment limit: Migration supports up to 30 unique global segments. If more exist in your V1 setup, only the first 30 will migrate; additional ones will need to be handled manually.
No historical data migration: Existing journal entries will not be modified; the new configuration only applies to future runs.
Manual review required: Some segments may not automatically map perfectly, especially custom or incomplete fields. These will need manual attention before publishing.
Journal Runs: Existing Journal Runs continue unaffected, but once V2 is enabled, all new Journal Runs require a published V2 segment set.