Basware buys Trustpair because approving the invoice no longer tells you who gets the money

The control Basware is buying does not touch the invoice. Trustpair, founded in 2017 and a Nacha Preferred Partner, checks that a bank account actually belongs to the supplier attached to it, and runs that check at supplier onboarding, whenever account details change, and again before a payment is authorised ^[9]. Two of those three moments are events in the vendor master, not in the approval queue. Basware CEO Jason Kurtz states the failure mode plainly: a finance team can do everything right on the invoice and still send the money to the wrong bank account ^[13]. It is the belief Trustpair was built around, in Baptiste Collot's phrasing, that approving the right invoice is not enough if the money ultimately reaches the wrong account ^[14].

The survey numbers in the announcement describe demand that has not converted into purchases. Citing the Association of Certified Fraud Examiners, Basware says 75% of anti-fraud professionals reported an increase in generative-AI document fraud and forgery over the past two years, while 7% said their organisations were more than moderately prepared to detect or prevent AI-powered fraud ^[4][5]. That is a 68-point gap between the people who see the problem and the people who claim a defence ^[1]. The announcement carries no purchase price ^[16], which makes the gap easier to assert than to value.

Basware's contribution to the combined product is history, and the pooled record works out to roughly 125 invoices per supplier ^[2]. That density is the part that could plausibly improve detection: a payee with hundreds of settled invoices behind it has a baseline, and a first-time payee is just a claim about an account number. Whether invoice history materially sharpens account-ownership validation is asserted here rather than shown.

Then there is the shape of the company after close. Trustpair keeps its team and platform and continues selling across SAP, Oracle, Coupa, Zycus, Ivalua, Jaggaer and Kyriba ^[10][14], while Basware claims the first end-to-end invoice-to-payment assurance in the market, on the back of 40 years spent protecting the invoice ^[13]. Both hold at once only if the end-to-end version is something Basware's own installed base buys and everyone else keeps buying one half of it. IDC research director Kevin Permenter calls the capabilities complementary and the gap between onboarding and payment a growing one ^[15], which is a fair reading of the product logic and says nothing about integration.

The number doing the heaviest commercial work is the weakest sourced. An estimated 8% of global revenue lost to fraud each year appears with no attribution attached ^[3], sitting next to survey data that is credited precisely. It is not needed: regulators in the US, UK and EU are already moving responsibility for stopping bad payments onto the businesses releasing them ^[7], and that shift in obligation is what changes budgets.