Understanding Project Estimate Writeback's default entity mapping for multi-entity organizations

Created by Damien Zwillinger, Modified on Thu, 29 Aug at 6:34 PM by Harry Lewis

Applies to

Velixo NX
Sage Intacct

Summary

In multi-entity shared companies, Velixo does not require you to specify an entity ID to load data or write data back to Sage Intacct.

During the data refresh process, you will always receive all data that you have access to, including entity-private records.

When writing back to Sage Intacct, Velixo smartly determines the entity where the record needs to be created based on the combination of dimension values used.

If none of the used dimensions is entity-private, the record is going to be created at the top level.
If each of the used dimensions are entity-private in the same entity, the record is going to be created as entity-private as well.
If the used dimensions are entity-private in at least two different entities, Velixo will detect this situation and return an error.

Scenario example

Project Estimates and Employees starting with 1 (i.e. 100, 101, 102,..) are created at the Top-level entity
Project Estimates and Employees starting with 2 (i.e. 200, 201, ...) are private to Entity A.
Project Estimates and Employees starting with 3 (i.e. 300, 301, ...) are private in Entity B.

The below behavior applies when creating a new Project Estimate from Velixo, which automatically works out the entity it should map to by default:

New Project Estimate with Employee dimension value: 100 - the new Project Estimate is created at the Top level (because employee 100 is at the Top level)
New Project Estimate with Employee dimension value: 200 - the new Project Estimate is private to Entity A, i.e., automatically mapped to Entity A
New Project Estimate with Employee dimension value: 300 - the new Project Estimate is private to Entity B, i.e., automatically mapped to Entity B
New Project Estimate with lines for Employees 100 and 200 - the new Project Estimate is private to Entity A, i.e., automatically mapped to Entity A as although Employee 100 is at the Top-level, Employee 200 is private to Entity A
New Project Estimate with lines for Employees 200 and 300 - this scenario cannot be created; it is not allowed by Sage Intacct as Employee 200 and Employee 300 are private to different entities.