Resolve the "UOM is not a valid UOM in Procore" Error when Importing from Sage 300 CRE®
Background
When attempting to import a budget or prime contract from Sage 300 CRE into Procore, the sync process may fail if a Unit of Measure (UOM) referenced in Sage 300 CRE is not recognized by Procore. This issue typically presents with one of the following error messages:
[UOM] for budget line Cost Code [Cost Code] Cost Type [Cost Type] is not a valid UOM in Procore[UOM] for Contract Line is not a valid UOM in Procore
This happens because the Unit of Measure (UOM) specified in Sage 300 CRE either does not exist in Procore's Unit of Measure Master List or does not match the formatting in Procore.
Steps
Use the steps below to resolve UOM validation errors when importing a budget or prime contract from Sage 300 CRE® into Procore.
UOM values are case-sensitive. The UOM entry in Procore must match the Sage 300 CRE value exactly. For example, HRS and hrs are treated as two separate UOMs in Procore.