For credit investors, LPs, arrangers, and counsel evaluating receivables and supply-chain finance exposure or claims.
On May 15, the Amended Complaint in Western Alliance Trust Company, N.A. et al. v. Jefferies Financial Group Inc. et al. (NY Sup. Ct. Index 651389/2026, NYSCEF Doc 5) was filed. Seventy-one pages, twelve counts. One paragraph deserves close attention from anyone working in receivables or supply-chain finance.
Paragraph 70 alleges that defendants “had exclusive access to information concerning First Brands’ receivables through the PrimeRevenue software platform, which was maintained directly between First Brands and Leucadia,” and that they “nevertheless failed to verify the information available through that platform and instead provided false information on which Plaintiffs relied.”
The question this raises is not about PrimeRevenue. It is about how a well-designed buyer-led supply-chain finance program is supposed to work, and what happens when funders rely on platform-displayed data without engaging — or independently checking — the controls that would make the structure safe.
How buyer-led SCF is meant to work. PrimeRevenue’s published model is straightforward: the supplier sends invoices to the buyer through normal channels, the buyer approves the invoices, and the buyer (not the supplier) uploads approved payables data to the platform. Funders then advance against those approved invoices, with the credit decision based on the buyer’s confirmed promise to pay. A core control purpose of that architecture is an unconditional, buyer-side confirmation that the invoice is valid and approved for payment — confirmation that isolates the credit risk to the buyer and removes most of the seller-side fraud surface.
In my 2022 BCR Publishing review, Building and Managing Receivables Finance Platforms (https://bcrpub.com/publications/building-and-managing-receivables-finance-platforms), I described this directly: “Properly structured SCF platforms isolate credit risks by having an unconditional confirmation invoice valid and approved to pay, with multiple safeguards.” That is the design point. Without genuine buyer confirmation, an SCF program is structurally not what it claims to be.
What a well-configured buyer-led program looks like. Beyond the buyer-approval workflow itself, a well-configured buyer-led program — depending on how funders, servicers, and the technology provider arrange responsibilities — relies on two further protections that materially reduce the fraud surface: (i) verification of the identity of the buyer-side party uploading approvals, so that an impostor or a captive entity inside the seller’s organization cannot stand in for the genuine obligor; and (ii) document-level confirmation traceable back to the buyer’s accounts payable system, rather than reliance on the seller’s representation that an approval exists. Whether these are functions of the platform, the funder, or a third-party servicer depends on the program design — but in a properly configured buyer-led structure, somebody with no economic interest in the seller is doing them.
The seller-fraud surface is the framework that is meant to close. The same 2022 article identifies the standard seller-originated fraud techniques the SCF architecture is built to prevent: “fresh air” invoicing (selling non-existent invoices), duplicate or multi-pledged invoices, invoices from non-existent customers, and pre-delivery invoicing. The prevention methods — buyer verification, invoice verification (sample checking with buyers), central registers (UCC, where applicable), pattern analysis, and document analysis — are not novel. They have been in the practitioner literature for decades. In a properly run buyer-led program, the first two are built in by design.
What the public record now suggests about the First Brands case. Reporting on the court-appointed examiner’s findings indicates that the North American programs relied on manually produced spreadsheets uploaded to PrimeRevenue, that lenders typically did not see underlying invoices or independently verify data against First Brands’ internal records, and that Leucadia relied on invoice-level data presented in PrimeRevenue without independently obtaining or reviewing the underlying spreadsheets or invoice documents at the point of purchase.
PrimeRevenue, for its part, has stated on the record that it provides technology platforms — not credit underwriting or invoice verification — and that it was not the servicer in the AR-financing programs referenced by the examiner. There is no suggestion in the reporting of wrongdoing by PrimeRevenue. The operational question is therefore narrower and more important: how was the platform being used, was the receivables flow on the relevant program genuinely buyer-confirmed, and what independent checks did funders or servicers perform before advancing against the data being displayed?
On the currently reported facts, this looks less like a failure of a technology provider and more like a failure in how the program was configured, what protections were in fact engaged, and what independent verification funders performed against the data the platform displayed.
The broader pattern. Greensill’s structures ran through several SCF front-ends, including Taulia, and the well-documented questions there were about which receivables flowing through those rails represented genuinely buyer-confirmed payables versus prospective or future receivables dressed in SCF clothing — the same buyer-confirmation issue, in a different shape. The HPS / Carriox dispute involves allegations of fabricated telecom receivables, forged contracts, and fake invoices and emails, with HPS / BlackRock exposure reported in the hundreds of millions — again, a platform/data-room-versus-independent-verification question. The broader Jefferies private-credit and structured-finance story now spans First Brands, Water Station, Fat Brands, and Market Financial Solutions — different counterparties and different program structures, but recurring questions around what was verified, by whom, and against what.
Practical diligence questions for funders, LPs, and counsel. Six questions every receivables-finance allocation should be able to answer:
- Is the program designed so each financed receivable is genuinely buyer-confirmed, and is that confirmation independently retrievable — not a seller-uploaded representation displayed through the platform?
- Has the identity of the buyer-side approver been verified, traceable to the obligor’s genuine AP organization rather than to a captive or seller-controlled entity?
- Are buyer confirmations cross-checked against the obligor’s accounts payable records outside the platform, on a sample basis, by someone with no economic interest in the answer?
- Where do obligors remit, and who controls that account? (Independent of the platform.)
- What cross-platform or cross-program exposure does the seller have that is not visible on the platform the funder can see?
- Who, with independent economic incentives, is checking these things on a recurring basis — not at onboarding, but every month thereafter?
None of this is novel. Most of it has been in the receivables-finance practitioner literature for decades. The recurring lesson from each of the recent failures is that the framework existed, the tools existed, and in each case the protection that the architecture made available was either not engaged, not checked, or both.
I have written on these themes since 2007 (GARP Risk Review). More recent work includes the 2022 BCR Publishing review cited above, Receivables Platforms — Key Considerations (TRF News, https://tenzor.ca/receivables-platforms-key-considerations/), and the World Factoring Yearbook 2026 article covering Greensill, HPS/Carriox and First Brands. I have applied this framework in practice as co-founder of two receivables / supply-chain-finance platforms, including a recent cross-border receivables fintech, and have been quoted by Bloomberg and the Wall Street Journal on related structures.
A recent piece on the legal characterization of these structures — “When Courts Rewrite Factoring” (Tenzor, reprinted in BCR News) — is here: https://tenzor.ca/when-courts-rewrite-factoring/
#TradeFinance #ReceivablesFinance #SupplyChainFinance #PrivateCredit #DueDiligence #FirstBrands #Greensill
Igor Zaks, CFA — President, Tenzor Ltd. (tenzor.ca). Operational due diligence, working capital optimization, and forensic analysis for receivables and supply-chain finance disputes.