In Organization administration > Setup > Address setup, we can configure address formats and components (Street, City, State/Province, ZIP, Country, etc.). However, there is no configurable way to enforce mandatory address components (e.g., make State/Province required), which forces customers to use customisations or inconsistent user training to maintain address quality.

Proposed improvement

Add a standard configuration capability in Address setup to mark address components as Mandatory (required)

How it should work

• In the Address setup grid (Configure address component), add a boolean column: Mandatory.
• System validates on create/update of postal addresses:
• UI (forms) validation + data entity validation + import validation
• Prevent saving if a mandatory component is missing
• Provide clear error messages (e.g., “State/Province is required for Invoice addresses in France.”)
• Ensure it applies consistently across:
• Customer/Vendor/Global address book forms
• Data management imports
• Integrations (OData)

Benefits

• Eliminates avoidable customisations
• Improves compliance (e-invoicing/tax), delivery accuracy, and reporting quality
• Reduces master data cleanup and downstream posting/integration errors

Our company operates in Italy and wants to enforce that State/Province is mandatory for customer addresses. Today this can’t be done via configuration in Address setup. With this feature, it becomes a simple setup rule.