Meet the Authors

Key Takeaways What you need to know
  1. Basware plans to acquire Trustpair, extending its AP controls from invoice approval into payment fraud prevention.

  2. Trustpair verifies supplier bank accounts during onboarding, account changes, and before payment authorization.

  3. SAP finance teams could gain an additional pre-payment verification layer across AP, treasury, and vendor master data workflows.

Basware, which describes itself as the market leader in Invoice Lifecycle Management, has signed a binding agreement to acquire Trustpair. The deal would extend Basware’s platform beyond invoice processing into supplier bank-account verification and payment fraud prevention.

Under the arrangement, Basware would confirm that an invoice is legitimate and approved, while Trustpair would confirm that payment reaches the intended supplier. Trustpair is expected to continue operating and going to market independently as a Basware company once the deal closes, and customers will not need to change providers or systems.

Extending AP Controls Beyond Invoice Approval

Trustpair’s platform validates that a bank account belongs to the intended supplier at three points: when a supplier is onboarded, when account details change, and before a payment is authorized. The company applies this validation across more than 190 countries, drawing on a database of more than 10 million validated supplier-to-bank-account pairs built over nine years. Trustpair also describes continuous monitoring of supplier data and screening of payment files before funds move, rather than reconciling problems after a transaction settles.

Explore related questions

Basware and Trustpair described the combined model as covering the full transaction, stating the deal “will deliver the industry’s first invoice lifecycle assurance covering the complete end-to-end transaction: Basware confirming an invoice is legitimate and approved, Trustpair confirming payment reaches the intended supplier.” The companies also said the acquisition will give customers “a new level of invoice-to-payment assurance and advance the ‘Perfect Invoice’: every invoice complete and authentic, and every payment fully validated.”

Following the acquisition, Trustpair will draw on Basware’s shared intelligence, spanning 2.5 billion invoices and 20 million suppliers, to strengthen its validation models. Vendor impersonation and business email compromise schemes often target the interval between invoice approval and payment execution in accounts payable operations, a gap that a bank-verification layer of this kind is designed to close.

Pre-Payment Verification Moves Into SAP Finance Workflows

Basware integrates with SAP environments to manage invoice receipt, processing, and compliance, helping SAP finance teams meet country-specific e-invoicing mandates. Trustpair already works with customers running SAP alongside other ERP, procurement, and treasury systems, including Oracle and Kyriba.

SAP customers could see fraud checks extend beyond invoice approval into the payment execution stage once the acquisition closes. Trustpair’s practice of screening payment files before funds move reflects a shift toward flagging fraud risk before a payment run completes.

In SAP S/4HANA and SAP ERP environments, vendor master data and bank-account changes typically move through configurable approval workflows, a pattern relevant to where a third-party verification step would need to align with existing payment run processes. SAP customers running centralized treasury or payment execution functions commonly combine ERP-native controls with external verification tools, a pattern that bears on how this integration might fit into existing payment workflows.

What This Means for SAPinsiders

  • Fraud checks would move earlier in the payment cycle. SAP finance and treasury teams may need to align payment run scheduling with an added pre-payment verification step. Existing payment execution workflows built around ERP-native approval could require adjustment to accommodate the additional check point.
  • Vendor master data management gains new scrutiny. AP and vendor master data teams may need updated procedures for handling flagged supplier bank-account changes surfaced by a verification layer. Governance over who approves flagged changes could become a defined step in the vendor onboarding process.
  • Invoice and payment fraud coverage now come combined. SAP customers evaluating AP automation platforms may weigh combined invoice legitimacy and payment verification as a single procurement consideration going forward. This could shift how finance leaders compare vendors that currently offer only one half of that coverage.

Events

29Oct
SAPinsider Summit New Orleans 2026New Orleans, Louisiana, United States
View All