this scenario is quite common and can be handled with the right configuration.
Use a single integration role with access to all subsidiaries
Ensure the role has permissions to post transactions across those subsidiaries
Apply subsidiary-based mapping logic (e.g., employee, department, or expense data) to route entries correctly
Since data from Concur is centralized, the NetSuite Concur integration layer (often via middleware like Celigo) dynamically assigns the correct subsidiary during processing.
Overall, this is not a system limitation—it’s a matter of proper role setup and integration mapping.
