Fibady classifies each entity's bank transactions, ties them to the books and projects cash by day, week and month. You see how much you have, what comes in and out, how much you can really draw counting credit lines and advances, and how many months of runway are left. Per entity and for the group.
How are bank transactions classified?
With cascading IF / THEN rules you define with priority (counterparty, description, amount, account), with a preview of how many transactions each rule reaches before applying it. When the system detects a repeated pattern it proposes the rule and you accept or discard it. Whatever no rule reaches stays "Unclassified", counted in the Control Centre.
What is the difference between direct and indirect cash flow?
Indirect starts from profit and adjusts for non-cash items and working-capital changes: it comes from the books and explains why cash changed. Direct starts from actual receipts and payments in the banks: it is the one you forecast with. Fibady produces both and checks that they tie. More in the glossary: direct vs indirect cash flow.
How does financing enter the forecast?
Invoice advances, credit lines, loans and their maturities are recorded in the financing module and show up in the projection: real availability (cash plus undrawn), financial cost and repayment calendar. It is the piece no other FP&A tool in this segment offers inside the cash flow.
How Fibady does it
- Statements from the ERP or uploaded separately (Excel or CSV with template); bank, cash, card and crypto accounts
- Cascading classification rules with priority, preview and automatic suggestions
- Daily, weekly and monthly projection with rules (6 methods) and alternative plans
- Runway and burn rate per entity and group
- Financing: advances, credit lines, real availability
- Reconciliation between direct cash flow, indirect cash flow and bank balance
Statements arrive via API with Odoo and Holded when the ERP holds them. If you are comparing with a treasury-only tool, see Fibady vs Agicap.