Loan repayment detection and deeper bank risk signals
Existing loans detected straight from bank statements, NSF and negative-balance episodes tracked end to end, and a redesigned Decision scorecard.
Two of the most requested features are now live in every account, along with a redesigned Decision scorecard and tighter policy governance.
Loan repayments and amortisation, visible at last
Floowed now detects existing loans straight from bank statements. It picks up loan proceeds, identifies repayment streams, and maps out the cadence: typical repayment amounts, how regularly they hit, and any failed attempts along the way. Everything is laid out on a monthly timeline, and repayments are linked back to the proceeds they belong to.
The result: you can see how an applicant is servicing their existing debt before you decide to add to it. No more reconstructing amortisation behavior by hand from raw statement lines.
Bounced cheques and risk signals, in full detail
Bank risk analysis just got a lot sharper. NSF and negative-balance episodes are now tracked end to end: how long the account stayed negative, how deep it went, and whether (and when) it genuinely recovered. Bounced payments are properly separated from reversed incoming receipts, related cheque events are grouped together, and every event drills down to the underlying transactions.
Risk events are also ordered correctly across statements, even when dates overlap or statements arrive out of sequence. The story the timeline tells you is the story that actually happened.
A redesigned Decision scorecard
The scorecard got a full redesign: a compact decision summary, hard-rule results, and score metrics in one view, topped with a grade-band score gauge. Every row expands to show the detail behind the number, so you can go from headline decision to underlying evidence in one click.
Tighter policy governance
Applications processed on an older template version are now flagged with a clear warning, and you can re-evaluate them against the current version in one action. Template selection is also limited to versions with an active policy, so an application can't accidentally run against a configuration that shouldn't decision. The policy you write is the policy that runs, and now it's easier to prove it.
Improvements and fixes
- Workflow canvas stability: fixes for zoom, layout, and resizing behavior.
- Workflow-node configuration: direct edit access restored, and custom integration settings now save at the individual node level.
- Processor Schema Builder: longer-running processor tests are supported, with clearer errors when a test does fail.
- Faster processing and more reliable analysis across the board.