Cost codes must be mapped on a location base
That is a must have. We have uploaded now 388 pages of coste codes just for one entity, with the onboarding of a new entity we will get +500 pages. We must map the cost codes to a location base, this is the only validation what we can do. We have to ensure, that users can use only valid cost codes for their entity. Otherwise they could also use a valid cost code from the USA, Singapore or Switzerland which we do not want.
Request: Mapping codes per location
-
Katja Anacker
commented
Implement the ability to map cost codes to specific locations/entities so that users can only see and select cost codes that are valid for their own entity.
Problem
For one location, we have uploaded over 388 pages of cost codes. With the onboarding of a new entity, this will grow to 500+ pages.Currently, there is no validation to restrict cost code usage by location or entity. This means:
• A user in Germany could select a valid cost code belonging to the USA, Singapore, or Switzerland
• There is no mechanism to prevent cross-entity cost code usage
• The only validation we can apply is mapping cost codes to a location — but this functionality does not exist in the tool todayThis creates a compliance risk and undermines financial accuracy across the organization.
Proposed Solution
• Allow administrators to map cost codes to specific locations/entities
• Users should only see and be able to select cost codes that are valid for their assigned location/entity
• Prevent cross-entity cost code selection entirely
• Support scalability as new entities are onboarded with their own cost code setsBusiness Impact
• 388+ pages of cost codes for one entity alone — growing to 500+ with new onboarding
• Without location-based mapping, invalid cost code usage cannot be prevented
• Compliance risk across multiple global entities (Germany, USA, Singapore, Switzerland, etc.)
• Critical for financial accuracy, audit readiness, and governance
• Essential for scaling the platform to additional entities