Topic starter
09/07/2026 1:40 pm
TL;DR: B2B payment fraud often emerges after onboarding, where spend behaviour, vendor relationships, approval workflows, reimbursements and subscription management create control gaps, according to SumSub and the ACFE's 2026 Report to the Nations, which found organisations lose 5% of annual revenue to fraud and wait a median 12 months to detect it. Continuous visibility and enforcement across the payment lifecycle matter more than verification alone.
Editorial analysis by NHI Mgmt Group, based on content published by SumSub: “The hidden risk stack in B2B payments: from onboarding to spend abuse”.
By the numbers:
- Organisations lose 5% of annual revenue to fraud, according to the ACFE's 2026 Report to the Nations cited by SumSub.
- The median time before fraud detection is 12 months, according to the ACFE's 2026 Report to the Nations cited by SumSub.
Key questions
Q: What breaks when B2B payment fraud controls stop at onboarding?
A: Controls fail because they only assess initial trust, not how approved vendors, employees, or subscriptions behave later.
Q: Why does post-onboarding fraud create such large losses and long detection delays?
A: Because it hides inside legitimate business workflows.
Q: What are the signs that payment fraud controls are too weak or misapplied?
A: Warning signs include rising chargeback rates, clusters of small test transactions, repeated use of the same devices or accounts, and growing false-positive declines that turn away good customers.
Practitioner guidance
- Embed controls into payment workflows Block or route exceptions before money moves by enforcing thresholds, vendor change checks, and approval routing inside the payment path.
- Correlate identity and transaction data Join vendor records, approver identity, reimbursement history, and transaction events so suspicious spend patterns can be detected in context.
- Monitor for recurring fraud patterns Watch for threshold splitting, duplicate vendors, unauthorised spend categories, shadow subscriptions, and repeated reimbursement anomalies.
Bottom line: B2B payment fraud often exploits trusted relationships and routine finance processes rather than initial onboarding failures.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
09/07/2026 1:44 pm
Post-onboarding fraud is a lifecycle governance failure, not a verification failure. Initial screening can remove many high-risk actors, but it does not govern what approved parties do once they are inside the payment stack. That is why reimbursement abuse, duplicate vendor payments, and SaaS sprawl keep recurring. The discipline needed here is continuous entitlement oversight across finance operations, not a one-time trust decision.
A question worth separating out:
Q: How should finance and identity teams share accountability for payment fraud?
A: Finance teams should own payment rules, approval logic, and exception handling, while identity and access teams help ensure those rules are tied to verified people, vendors, and roles. The key is a shared operating model where vendor changes, approver access, and transaction monitoring are correlated. Without that split ownership, fraud gaps fall between teams.
👉 Read our full editorial: B2b payment fraud grows after onboarding, where controls fail