The Ariba Distinction

In our last post we addressed recent changes to the TRE invoice verification procedures. Two thoughtful and important comments have been posted in response and I’d call your attention to both.

The second of those comments, by Drew Hofler of The Ariba Supplier Network, highlights an issue that will (I hope) become increasingly important to all TRE Buyers.

Because a Seller that belongs to The Ariba Network brings added value to the table.

First of all--what is Ariba?

Quoting here from a press release:

“The Ariba Supplier Network is the world’s leading business collaboration platform, which combines technology and services to better match buyers and suppliers, automate transactions and optimize payments. Buyers and suppliers in 115 countries leverage the network to engage in transactions worth more than $110 billion a year and process one purchase order every two seconds. Leveraging the reputation and power of the Ariba Network, suppliers can lower the cost, risk and time associated with accessing capital.”

So, for our purposes, Ariba represents a VERY substantial volume of B2B receivables-creation, with a payment process that incorporates an automated, controlled, protected, invoice approval process.

Ariba and TRE have had a strategic alliance for some time now but the volume of Ariba invoices offered for sale on TRE has been minimal. That might be because of a lack of Ariba member education. It might be because the actual mechanics of uploading member invoices has not been as user-friendly as it might be.

In any event, Drew posted welcome news yesterday that I’d like to make sure to highlight. I quote from his comment to yesterday’s post…..

“This issue brings to light even more the value of invoices that are uploaded to the TRE platform directly from a supplier network such as Ariba. In the case of an Ariba supplier selling an invoice processed via the Ariba Network, both the issue brought up in the blog (verification) and the issue in the comment (quality of invoices/errors) are rendered moot.

1) Verification: When the next release of the Ariba Network (AN) comes out (4Q09), Ariba suppliers will be able to click a button and directly upload their approved invoices for sale to the TRE platform. Approved invoices are delivered directly to the AN from the Obligor's ERP, and are then transmitted directly to the TRE platform with no opportunity for the supplier to change any of the data contained within. Given the unbroken electronic chain of data, the need for verification is obviated.

2) Quality of Invoices & subsequent error correction: The nature of the Ariba Network is such that buyers/obligors set parameters up front that suppliers must meet in order for a submitted invoice to be considered in good order. This systematic quality control ensures that the vast majority of quality issues are filtered out before an invoice is even received by the Buyer/Obligor. So the issues brought up by Mr. Schmidt are largely removed for Ariba invoices.

Combine the above with the fact that eInvoicing via Ariba reduces invoice approval times down to an average of less than 5 days, and invoices sold by Ariba suppliers directly from the Ariba Network will offer TRE Buyers a qualitatively better option to reduce risk and extend returns.”

The critical issue to highlight in Drew’s comment, I believe, is that the Ariba system will actually provide a MORE robust verification process than had been offered by TRE even BEFORE its recent changes.

If I understand the mechanics of the network correctly—and I invite Drew to correct me or to amplify here—the invoices posted by an Ariba Seller will not only have been verified with respect to authenticity i.e. that there IS an invoice matching the Seller’s posting in the Account Debtor’s AP system, but the Account Debtor will have ACKNOWLEDGED that the goods provided have met the conditions of the agreement AND that the amount of the invoice is payable as and when indicated.

This provides a significant level of additional security to a TRE Buyer, which should result in preferential pricing of invoices originated by Ariba members.

A substantial increase in Ariba Seller activity would be a very good thing for TRE and, I suspect, for Ariba also. Let’s hope all interested parties work hard to make that happen!

An Inconvenient Essential--Part One

Among the essential numerical values that we learn in high school physics is the number that defines the speed of light. If we go on to other, non-scientific pursuits in our lives, it is likely that we’ll forget an important qualification in that definition. The number we learned represents the speed of light in a vacuum. In the presence of any source of friction, that speed cannot be reached.

In our last post we noted the desire of The Receivables Exchange to become a very large-volume platform. Growing from an initial transaction in late 2008 to a targeted $1 billion in volume in 2010 might not challenge the speed of light in literal terms but it comes close in financial terms. An essential element in its success must be the elimination of as much friction as possible.

We’ve already identified a few of the sources of friction usually encountered in purchasing individual invoices and the ways that TRE has devised to lessen their impact.

Now we need to address another major one: the issue of invoice verification. The buyer of a receivable needs to verify that the receivable is valid.

Most buyers of individual invoices will want assurances that: the Account Debtor acknowledges that it contracted to purchase the goods or services; that the goods or services have actually been provided; that they meet the criteria established in the contract; that the invoice being purchased states the correct amount due and the correct terms of payment; and, that the invoice is scheduled to be paid.

That’s a lot of friction! It’s often difficult or impossible to find anyone in a Debtor’s organization willing to sign-off on such assurances.

After the initial qualification of a client, the invoice verification process represents the major impediment to the speed of invoice purchase transactions. Given the need for TRE to minimize such impediments, it’s clear that this issue has had to be a focus of their operational design.

TRE has to have a process that provides appropriate comfort on the verification issue without causing so much friction in the system that it is impossible to meet their speed-of-growth and scale objectives.

The procedural solution is a compromise. Many of the typical elements of “full verification” are sacrificed, but the loss of those assurances is balanced by other elements of the TRE system.

What are the assurances that are sacrificed?

1) Neither TRE nor the Buyer has a direct relationship with the Account Debtor; so the Debtor does not provide either TRE or the Buyer with a direct assurance of the existence of a contract or purchase order.

2) The Debtor does not provide a direct assurance of the receipt of the goods or services.

3) The Debtor does not provide a direct assurance that the goods or services meet the requirements of the contract.

4) The Debtor does not provide a direct assurance that payment will be made.

In what ways is the sacrifice of those assurances balanced?

1) Prior to approving the invoices of a Debtor for posting on the exchange, TRE will investigate the history of transactions between the Seller and the Debtor to determine that a relationship does exist.

2) The history of the relationship between the Seller and Debtor will be examined to provide context for the analysis of invoices proposed for future sale.

3) The agreement of the Debtor to make all future payments to the TRE lock-box provides additional evidence of the validity of the relationship.

4) TRE will independently acquire contact information allowing it to access appropriate individuals within the Debtor organization who can verify that an invoice is “in the system for payment”.

5) TRE employs experienced fraud investigators to help it to detect any potentially fraudulent relationships or transactions.

The only piece of directly-sourced information regarding a specific invoice is that it is “in the Debtor’s accounts payable system”. That might seem to provide much less security than typically required by single-invoice buyers.

However, by the time a TRE Buyer sees that invoice posted for sale, the invoice will have been analyzed within the context of a great deal of previously-verified information about the relationship and the historical transactions between the Seller and the Debtor.

It’s certainly possible that, from time to time, specific invoices will prove problematic; and it is possible that the TRE verification process will have failed to uncover those problems in advance.

On the other hand, if such a problem occurs:

a) Within a verified pattern of transactions between the Seller and the Debtor,
b) In the presence of a continuing payment-direction agreement,
c) In the context of a security system that provides meaningful recourse, and
d) In an environment of a robust fraud-detection effort,

it is likely that a solution to an isolated problem can be found.

There is no guarantee that no losses will occur, but losses can occur when buyers obtain ALL of the typical assurances. Stuff happens!

There is a good argument to be made, I think, that the sacrifices made in the TRE verification system, for the sake of reducing friction and accommodating scale, are reasonable and that the apparent additional risks are balanced within the operational system of the exchange.

An important question remains, however, that will be addressed in our next post.

TRE itself, with its very aggressive growth goals, acts as its own verification agent. The question of potential conflict between growth goals and transaction quality goals has to be addressed.