Reverse factoring and supply chain finance
One buyer you underwrite deeply. Three hundred suppliers you have to onboard without a queue.
This is written for the funder running the programme: the bank desk, the specialty finance company, the factor whose largest debtor asked whether their suppliers could be paid early. Not for a corporate treasury shopping for a payables tool, and not for a supplier looking to join somebody else’s programme.
Called payables finance by treasuries, supply chain finance by the market, and confirming across Spanish speaking Latin America, where we have customers and where the local word is the one that belongs on the screen.
Programme CONF-04 · buyer Astilla Comercial · confirming
Supplier pipeline · every state carries its blocking reason
- Invited312InfoProgramme agreement sent in the supplier's own language
- Identity cleared268AvailableSanctions posture recorded, evidence captured at run time
- Bank details held41HeldHuman only hold. No machine may release these
- Stalled17StalledOldest 11 days. Blocking requirement named on every file
- Active on offers204AvailableUptake measured per supplier and per tenor
Buyer limit utilisation 71% · approved payables unsettled 0 · last underwriting run 2 days ago
The inversion
Everything you learned in factoring points the wrong way here.
The mechanism is simple to describe and unforgiving to operate. A buyer approves a supplier invoice for payment at its ordinary maturity. That approval converts a trade payable into something close to a confirmed obligation of a creditworthy company. The funder offers the supplier payment now, at a discount priced off the buyer’s credit rather than the supplier’s, and is repaid by the buyer at maturity.
The credit question collapses to one name. You are not assessing three hundred small suppliers. You are assessing one large buyer, repeatedly, and every supplier you add increases operational and compliance load rather than credit exposure.
The operational question expands to three hundred. Identity, bank details, tax documentation, sanctions posture, agreement execution, and a support relationship in whatever language the supplier works in. A programme fails at onboarding far more often than it fails at credit.
Dilution mostly disappears, and approval integrity replaces it. The disputes and short pays that make factoring dilution difficult have already been settled inside the buyer’s own approval process. What matters now is that the approval is genuine, that its withdrawal conditions are understood, and that the set off terms in the programme agreement are recorded rather than remembered.
Concentration is the product
In factoring, exposure under one debtor name across several clients is a warning. In a confirming programme it is the design. The whole book leans on one obligor and that is what you sold.
Which changes what monitoring has to do. Deep and continuous on one name, with payment velocity, utilisation against the programme limit and every material event triggering a fresh underwriting run that is versioned and openable, rather than an annual review and a hope.
Programme operations
Six things a programme lives or dies on.
Buyer approval as evidence
The approval that converts a payable is held as the evidence for the funding, with its source, its timestamp and its amount. Every downstream figure opens back onto it.
Supplier onboarding as a pipeline
States rather than folders. Identity, bank details, tax documents, sanctions posture and agreement execution each carry their own state and their own blocking reason.
Bank details under a human hold
The single most expensive detail in the programme. The machine may stop the payment and never release it. A named person releases, under four eyes, with the reason recorded.
Early payment offers
Offer, discount at the date of acceptance, acceptance and settlement held as one linked record per invoice, so uptake by supplier and by tenor is a measurement rather than an impression.
Programme limit and utilisation
Utilisation against the buyer's limit and against your own facility, reported continuously with availability compression and days to zero on the current trajectory.
Settlement at maturity
Buyer settlement reconciled against the approved payables it discharges, with an unsettled approved payable becoming an exception that has an owner rather than an aging line nobody watches.
The cycle
From an approved payable to a settled programme.
The same five movements, repeated at whatever volume the buyer's payables run at.
- Approval
The buyer approves, and the payable becomes financeable
Approved payables arrive from the buyer's environment and are held with the approval as evidence rather than as a data load. An amount that does not match the invoice it references is an exception before it is an offer, because a discrepancy discovered after a supplier has been paid is a conversation with your largest client.
- Offer
The supplier is offered payment now, priced off the buyer
The discount is computed from the tenor remaining to maturity and the programme pricing, and the offer is presented in the supplier's own language and currency where the programme runs across borders. What the supplier sees is what the platform recorded.
- Acceptance
Acceptance is per invoice, and it is a decision the supplier owns
Some suppliers take every offer, some take one in five at quarter end, and the difference is the economics of your programme. Acceptance is linked to the offer that produced it, at the price that stood on the day, so nothing is repriced retrospectively.
- Payment
Funds are released to the supplier under the ordinary controls
Payment files are generated for the rails your bank accepts, release control sits in front of them and the delivery wall stops a test from reaching a real supplier. Every release records the actor, the evidence and the policy version into an audit record that cannot be mutated.
- Maturity
The buyer settles, and the programme reconciles itself
Settlement is matched against the approved payables it discharges, with the original remittance preserved as evidence and never posted silently. Buyer payment velocity feeds straight back into the underwriting run on the one name the whole programme depends on.
Against classic factoring
Same platform, opposite assumptions.
If your team runs both products, this is the table worth putting in front of them, because the habits do not transfer.
| Dimension | Classic factoring | Reverse factoring |
|---|---|---|
| Credit assessed | The client, plus a fragmented debtor population | The buyer, one name, continuously and deeply |
| Concentration | A warning to be managed and reported | The intended design of the programme |
| Dilution | A live risk measured against the client's own history | Largely settled inside the buyer's approval before funding exists |
| Verification | Prove the receivable is real and undisputed | The buyer's approval is the proof. Approval integrity replaces verification |
| Onboarding volume | A handful of clients, underwritten carefully | Hundreds of suppliers, onboarded operationally at pace |
| Notification | Sometimes withheld, and constrained everywhere when it is | Inherent. The buyer created the programme and the supplier joined it |
| Failure mode | A client that deteriorates, or a debtor that disputes | The buyer fails, or the onboarding queue stalls and uptake never arrives |
What goes wrong
Programmes rarely fail loudly. They stall.
Straight answers
What a programme owner asks first
Reverse factoring, supply chain finance, payables finance, confirming. Are these the same thing?
Close enough that arguing about it wastes a meeting, and different enough that the words matter in a contract. Reverse factoring is the mechanism: a buyer approves an invoice, and a funder pays the supplier early against the buyer's promise. Supply chain finance is the wider category the mechanism sits inside. Payables finance is what a corporate treasury calls it, because the programme lives on their payables side. Confirming is what it is called across Spanish speaking Latin America, where the confirming line is a mature product and the vocabulary on screen should be the local one.
Whose credit is actually being underwritten?
The buyer's, and that single fact reorganises the whole operation. In classic factoring you underwrite the supplier and monitor a fragmented debtor population. Here you underwrite one obligor deeply, monitor them continuously, and then onboard hundreds of suppliers who each represent an operational and compliance question rather than a credit question. The concentration risk is total and deliberate, which is exactly why the buyer needs to be re underwritten on every material event rather than annually.
How is dilution risk different in this product?
It is largely removed, and that is the commercial point. Once the buyer has approved the payable, the amount is confirmed and the ordinary sources of dilution in factoring, disputes, short pays, credit notes and returns, have already been resolved on the buyer's side before the funding decision exists. What replaces dilution risk is approval integrity: whether the approval is genuine, whether it can be withdrawn, and what the programme agreement says about set off. The platform holds the approval as the evidence and keeps the agreement terms alongside it.
Can suppliers be onboarded without a queue forming?
Onboarding is the operational bottleneck in every programme, so it is treated as a pipeline with states rather than as a folder of applications. Identity, bank details, tax documentation, sanctions posture and the programme agreement each hold their own state, and the file moves when its next requirement is satisfied. Bank details specifically sit under a human only hold, in onboarding as everywhere else. A supplier who has stalled for eleven days is visible as a stalled file with a named reason, not as an absence somebody notices later.
Does every supplier have to take the early payment offer?
No, and the economics of a programme depend on which ones do. Suppliers choose per invoice, and the platform holds the offer, the discount at the date of acceptance, the acceptance itself and the settlement as one linked record. Uptake, by supplier and by tenor, is measurable, which is what tells you whether the programme is working or whether you have onboarded three hundred suppliers who never use it.
What happens at maturity if the buyer does not pay?
It is the event the whole product is exposed to, so it is monitored rather than assumed away. Buyer payment velocity is measured continuously, an approved payable that has not settled is an exception with an owner, and utilisation of the programme limit is reported against the facility. FactorFox does not replace your legal position or your recovery decision. It makes sure the deterioration reached a named person early, with the approval, the invoice and the agreement clause already assembled.
Related
Bring us a programme that is not converting.
We will model the buyer, the onboarding pipeline and the offer to acceptance chain against a demonstration book, and show you where uptake is actually being lost.