Independent verification of every asset in the pool
Appointed by the lender, the originator, or both, Feesable verifies that the assets exist, that the pledge is exclusive, that collections came from the expected payer and that disbursements reached the borrower. Continuously, and again before every funding event.
Illustrative interface. Figures are examples, not client data.
Why now
Verification was standard practice. Deal velocity quietly replaced it
For most of the last decade, reps and warranties did the heavy lifting. Audits ran annually. Reconciliation was a quarterly exercise, often manual, often sampled. Financial covenants kept the ratios looking sensible so that lenders did not have to inspect every line item.
That model is being re-examined, and the originators who get ahead of it are finding the answers are also a competitive advantage.
- Loan tape emailed monthly
- Sampled review, 5% of the pool
- Reconciliation quarterly, by hand
- Findings weeks after the event
- Cross-facility pledge unchecked
- Read from source systems continuously
- Every asset tested, every run
- Reconciled inline with the borrowing base
- Exceptions raised the same day
- Exclusive pledge enforced across facilities
Not a substitute for trust, but the foundation that makes trust durable, and hence scalable.
What we verify
Four questions, answered against an independent source
Does the asset exist?
Each receivable is matched back to evidence outside the originator's ledger: the payment record, the executed agreement, the bank movement, the registry entry.
Existence, ownership and amount, checked at loan level
Is the pledge exclusive?
The collateral registry holds one authoritative allocation per asset across every facility and forward-flow program. A second pledge is rejected at the point it is attempted, not discovered later.
Cross-facility loan-level integrity, enforced not reported
Did the money come from the borrower?
Collections are matched to the payer of record at the payment rail, so a ledger that balances internally is not mistaken for cash that actually arrived from the expected end payer.
Verified at the rail, not just in the books
Did the funds reach the borrower?
Disbursements are confirmed delivered to the verified borrower account, closing the loop that fictitious-asset schemes depend on being left open.
Advance to destination, evidenced end to end
Beyond these four, tape-level anomaly review looks for patterns a rule would not catch: vintage distributions that shift without explanation, obligor behaviour that does not fit, document sets that are internally inconsistent. This is the one part of the platform where machine learning is used, and it sits alongside the calculation rather than inside it.
Engagement
How the appointment works
Verification is a scoped mandate, agreed in writing, with the evidence and the exception path defined before the first run. Nothing about it depends on the originator also being a Feesable customer.
Scope and appointment
Appointed by the lender, the originator, or jointly. The scope names the asset classes, the checks, the evidence sources and the reporting cadence.
Connection
Warehouse-native where the data stack allows, with first-class support for CSV, SFTP and spreadsheets where it does not. Read-only, least privilege, provenance recorded per field.
Continuous runs
Checks execute inline with the borrowing base calculation and again as a gate before each funding event. Exceptions open with an owner, an age and an escalation path.
Reporting to the counterparty
A verification statement per funding event, an exception log, and an append-only audit trail that an agreed-upon-procedures audit can work from directly.
Scope a verification mandate
Lenders and originators are both welcome to start the conversation. Tell us the facility and the asset class, and we will come back with a scope and an evidence plan.