Invoice factoring can be structured with recourse or without recourse. In a recourse arrangement, the seller may have to take back or repay a receivable that the customer does not pay. In non-recourse factoring, the factor absorbs specified credit losses, but only within the contract’s definition of a covered event.
The label is useful. The detailed exclusions matter more.
What factoring changes
A factor purchases or finances receivables and may also manage collections. The UK HMRC finance manual distinguishes full-service factoring, recourse factoring, agency factoring and invoice discounting. The UK government likewise describes invoice finance as funding that uses invoices owed to a business as security.
These forms can look similar in a platform interface. Their economics differ when an invoice is late, disputed or reduced.
In a recourse structure, the factor can generally require the seller to repurchase or replace a receivable after a contractual trigger. That trigger may be an ageing threshold rather than a final conclusion that the buyer cannot pay.
In a non-recourse structure, the factor takes defined buyer credit risk. The agreement can still leave fraud, disputes, returns, invoice errors and breaches of warranty with the seller.
Non-recourse therefore does not mean that every unpaid invoice becomes the factor’s loss.
Separate credit failure from a commercial dispute
This distinction is the centre of the contract.
A buyer may fail to pay because it is insolvent. It may also withhold payment because goods were not delivered, the quantity was wrong, a service was rejected or a credit note is pending. The second group is usually a commercial dispute rather than pure buyer credit risk.
A product flow should capture the reason for non-payment, not only the number of days overdue. Useful statuses include:
- awaiting buyer approval;
- approved but unpaid;
- partially paid;
- disputed;
- reduced by credit note;
- returned or reversed;
- subject to a covered credit event;
- recourse due.
An operations team should be able to see which contractual rule moved the invoice into each status.
Dilution can change the financed balance
Dilution is any event that reduces what the buyer owes: a return, discount, rebate, tax correction, credit note or dispute. It can arise after an advance has been paid.
The integration therefore needs events for invoice amendments and credit notes, not just invoice creation and payment. The agreed response may reduce availability, increase a reserve, request repayment or place the invoice into exception handling.
Do not hard-code one response across funding partners. Store the policy version used for the decision.
Collections determine how much control the factor has
HMRC’s categories also differ in who collects from the buyer. In full-service factoring, the factor may manage the sales ledger and collection. In agency factoring, the seller can collect as the factor’s agent. In invoice discounting, the seller commonly retains the customer relationship.
That choice affects account instructions, reconciliation and the buyer experience. The contract should answer:
- Where must the buyer send funds?
- Can the seller change those instructions?
- Who contacts an overdue buyer?
- Who handles an invoice dispute?
- How are combined and partial payments matched?
- What happens if money reaches the seller’s old account?
The answer should also appear in operational procedures. A clause that is not reflected in payment routing is a weak control.
Recourse needs an executable workflow
A recourse trigger should create a defined sequence:
- Flag the receivable and pause new availability if required.
- Send the contractual notice.
- Calculate the repurchase or replacement amount.
- Apply reserves or set-off only as the agreement permits.
- Record the seller’s response.
- Reconcile the repayment, replacement invoice or exception.
- Preserve the audit trail.
Product teams should test the boundary cases. A partial payment may reduce the recourse amount. A credit note may change the balance before the trigger. A buyer can pay after recourse has started.
The servicing system must keep these events in order.
Non-recourse still needs exclusions and evidence
The agreement should name the covered credit events and the proof required. Insolvency may have a formal definition. A prolonged default may have a waiting period. Political-risk or concentration limits may sit outside the cover.
The seller’s warranties also matter. A factor can reject a loss if the receivable was fictitious, previously assigned, related-party, disputed before funding or outside eligibility.
The customer journey should not market this as blanket protection. Show the covered risk, important exclusions and the claims process in plain language.
Model availability through a borrowing base
The OCC’s asset-based lending handbook explains the borrowing base and control over cash proceeds as core asset-based lending controls. An invoice-finance product can apply the same operating discipline even when its legal form is a purchase rather than a loan.
Availability may start with eligible receivables and then subtract concentration limits, reserves and ineligible amounts. Every change needs a source event and a reproducible calculation.
Keep separate identifiers for the seller, buyer, invoice, advance, collection and allocation. A bank reference alone is not enough because buyers can pay several invoices in one transfer.
For the platform-level data flow, see embedded invoice financing. For repayment posting, use the loan payment allocation guide.
