Credit decisioning on the whole loan file.
Every document read and checked for tampering, the cash flow worked out, hidden debt found, then your credit policy run on all of it.
Three ways in.
The same credit policy runs on whatever the file is made of.
Your systems
Your loan management system, core banking and origination front end.
40+ lending integrations, plus an API
Bureaus and registries
Credit bureaus, company registries, identity and sanctions checks, banking data.
Pulled when your policy needs them
The documents
Statements, passbooks, financials, filings, payslips. Scanned, photographed or handwritten.
Uploaded, emailed or watched in a folder
Six checks on every file.
All done before a credit officer opens the application, with the page and line behind every number.
Document reading
Reads the file the borrower actually sent.
- Every value traced to its page and line
- Several banks combined into one view
Document fraud
The statement that balances because someone made it balance.
- Metadata, typography, image and arithmetic checks
- Held for a credit officer, never auto-rejected
Cash flow
What the account actually did.
- Average daily balance, inflows, volatility, negative days
- DSCR worked out from statements, not declarations
Bounced payments
The check that came back, and the one that came back twice.
- Bounced payments separated from reversals
- Events ordered across overlapping statements
Hidden debt
The debt on the form is rarely the debt on the account.
- Every repayment stream, lender by lender
- Declared debt held against what is actually being repaid
Borrower checks
The file checks out. Do the people?
- Company verified against the registry
- Sanctions, watchlist and PEP screening on directors and owners
Your credit policy, running itself.
- Hard gates. One condition each, on any value in the file.
- Scorecard. Your weights and bands, or your own model.
- Outcomes. Approve, approve with conditions, or route to a credit officer.
- Every version kept. A March decision still explains itself in November.
Score 78, grade B
| Hard gate | Observed | Condition | |
|---|---|---|---|
| Months of bank data | 12 | ≥ 6 | Pass |
| NSF events, 12 months | 2 | ≤ 3 | Pass |
| Negative days | 4 | ≤ 10 | Pass |
| DSCR | 1.6× | ≥ 1.25× | Pass |
| Leverage | 2.1× | ≤ 3.0× | Pass |
“Our team used to spend hours per application: reading bank passbooks, checking numbers by hand, reconciling documents. Now Floowed reads the documents, runs our credit policy, and surfaces a decision in minutes.”
Where we go deeper.
Questions
Does Floowed replace my loan management or origination system?
No. It works alongside them over 40+ lending integrations and an API, runs the credit case and writes the outcome back with its evidence.
Does AI make the credit decision?
No. Agents read and check the file and chase what is missing. Your credit policy decides, in a deterministic policy engine, versioned, so every outcome can be explained later.
Can I use my own score or model?
Yes. Bureau scores, alternative-data scores and your own model come in as inputs, and your policy weighs them with hard gates and your scorecard.
What happens to a document that looks tampered with?
It is flagged with the signals behind it and held for a credit officer, never auto-rejected.
How do I start, and what does it cost?
Start free with $80 of credits, no card and no sales call. Custom lending setups, with your credit policy and integrations built with our team, are quoted.
Run your credit policy on every file.
Start free with $80 of credits, or talk to us about your book.