Detect duplicate payments across batches and time windows, flag unusually frequent payments to the same payee, enforce thresholds and extra approvals, verify beneficiary details, apply whitelist and blocklist rules, and require MFA for approvals.
Nomentia Payment Fraud Prevention keeps payments safe, verified, and governed by combining duplicate detection, frequent payee checks, configurable anomaly rules, and approval evidence into a single controlled process.
Duplicate Detection
Identify repeated payments before they are sent.
Frequent Payee Check
Detect unusual patterns or high-volume payments to the same beneficiary.
Rule Engine
Apply configurable checks for currency, country, and vendor anomalies.
Audit Trail & Comments
Store approval evidence, comments, and attachments in batches.
How does duplicate detection work across ERP and manual payments?
Duplicate detection checks imported ERP batches, manual entries, and treasury-generated payments against configurable rules, including fields, amount ranges, and time windows.
Can frequent payee checks be configured per country or currency?
Yes. Payment frequency thresholds can be configured per country, currency, or entity.
How are blocklists and whitelists maintained and updated?
Blocklists and whitelists are managed centrally. Users can flag trusted or risky payees, and rules can apply these lists during creation or validation.
Can thresholds vary by user, department, or payment type?
Yes. In Nomentia Payment Fraud Prevention, threshold rules can be applied at multiple levels and trigger additional approvals for high-risk transactions.
How is MFA enforced for high-risk approvals?
Approvals can require multi-factor authentication for high-value or sensitive payments, supported via enterprise SSO such as Azure AD, Okta, or ADFS.
Can rules trigger warnings, blocks, or extra approvals automatically?
Yes. Rule actions can include warnings, blocks, additional approvals, and notifications based on severity and anomaly type.
How are anomalies reported to approvers?
Approvers receive system, email, or mobile notifications with context and suggested actions.
Can fraud prevention rules run on ERP payment imports?
Yes. Fraud checks run on imported ERP batches and manual entries before execution.
Can approval evidence be stored with batch comments and attachments?
Yes. In Nomentia Payment Fraud Prevention, comments, attachments, and evidence can be stored at batch or payment level for audit and compliance.
Are alerts customizable by user or group?
Yes. Notification settings can be configured per user, approver group, or department.
How does the system reduce false positives?
Whitelist management, configurable rules, and frequency thresholds minimize unnecessary alerts while flagging true anomalies.
Can Fraud Prevention run standalone without the full suite?
Yes. Fraud prevention can operate independently, validating before execution, or integrate end-to-end with Payments.
How does audit logging capture fraud prevention actions?
Every rule evaluation, anomaly detection, approval, and override is logged with timestamps and user details.
Can it detect country- or currency-specific irregularities?
Yes. Rules can be tailored per country, currency, or entity for granular monitoring.
Customers rate Nomentia with 98% excellent feedback
Trusted software provider
Secure, Certified, European
Nomentia is certified against leading security standards for treasury data, with protective controls and auditability. Created and supported by Europe-based treasury and finance experts who understand local practices, processes, and regulatory requirements.
