Nomentia Master Data Management

Master data built for treasury-scale complexity

Nomentia Master Data Management provides one authoritative master data layer with approvals and traceability, keeps operational reuse consistent across treasury, liquidity, forecasting, payments, reconciliation, and reporting, and supports integration through APIs and file interfaces.

erp-img (2)

Central system of record

Maintain users, roles, companies, bank accounts, hierarchies, and financial counterparties within a single, controlled master data layer.

Learn more

test

Embedded governance and approvals

Apply maker–checker controls, approval workflows, and audit trails to sensitive master data changes.

Learn more

master-data-img

Operational reuse everywhere

The same master data is used consistently across Treasury, Liquidity, Forecasting, Payments, Reconciliation, and Reporting.

Learn more

erp-img (1)

Integration-ready by design

Expose master data securely via APIs and file-based interfaces to ERPs, banks, and external systems.

Learn more

Contact us

FAQs Nomentia Master Data Management

What master data is managed in the system?

Users, roles, companies, company hierarchies, bank accounts, bank account hierarchies, financial counterparties, and administrative groups.

Is master data shared across all modules?

Yes. The same master data is used consistently across Treasury, Liquidity, Forecasting, Payments, Reconciliation, and Reporting.

Can customers maintain master data themselves?

Yes. Most master data can be maintained directly in the UI or via imports and APIs, subject to permissions and approvals.

Are approvals required for master data changes?

Yes. In Nomentia Master Data Management, sensitive changes can require maker–checker approval using the Inspector workflow.

Is there an audit trail for master data changes?

Yes. All changes are logged with user, timestamp, and before/after values.

Can master data be integrated with ERP systems?

Yes. Master data can be synchronized via APIs, files, or integration flows.

Can bank accounts be validated?

Yes. Validation rules such as IBAN checks are applied during creation and import.

How are user permissions controlled?

Permissions are defined by roles and scoped by company and bank account.

Can master data changes trigger downstream updates?

Yes. Changes publish events that can be consumed by connected systems.

Is MDM suitable for large, multi-entity groups?

Yes. The subsystem is designed for complex group structures with many entities, banks, and users.