A forecast that is never checked against the bank loses its value
The cash forecast says what should happen. The bank statement says what did. When the two live in separate files, nobody knows whether a supplier payment went out on the expected date, whether a customer's payment arrived in full or whether the bank charged a fee nobody had planned for. The gap shows up at month end, when the actual balance doesn't match the forecast and it's no longer easy to say why.
FLIQO compares every transaction on the statement with what was forecast and shows what came through, what didn't and what arrived unplanned.
The statement goes in exactly as the bank sends it
Statements load in the standard formats most banks can export: MT940, camt.053, MultiCash or CSV. FLIQO recognizes the format from the file's content, so you don't have to specify it, and the same bank can send one format for one account and another for a different one.
A single file can carry several accounts. FLIQO splits out each account's transactions and balance and assigns them to the right account. If the file includes an account that doesn't exist in FLIQO yet, its transactions are not loaded and the import says so.
Loading the same file twice doesn't duplicate anything: FLIQO recognizes it was already loaded and rejects it.
The bank's balance is the starting point
When the statement carries the account's closing balance, that balance is recorded as the account's observed balance on that date. The forecast starts from it.
That balance is marked as reported by the bank. A later template upload or a manual entry for the same day doesn't replace it, and that upload reports where it kept the bank's balance.
Every actual transaction against what was forecast
When the import finishes, FLIQO looks for the forecast item that matches each actual transaction: same direction, same currency, a nearby date and a similar amount. How much date and amount difference is acceptable is the company's call, with a general setting and a different one for the categories that need it. Rent, for example, allows little difference, while daily sales vary more.
Matching doesn't require the bank transaction to be classified. A transaction that arrived without a category can be matched with a forecast payment that has one.
When automatic matching isn't enough, it's done by hand. A forecast payment the bank executed in two or more parts is linked to all of them, and any link can be undone.
Transfers between your own accounts close themselves
Before comparing against the forecast, FLIQO checks whether a statement transaction corresponds to a transfer between the company's own accounts that was recorded but not yet executed. If it finds one, the transfer moves to executed and the statement transaction isn't loaded a second time.
If two pending transfers have the same amount, on the same account and the same day, FLIQO doesn't pick one at random: it flags the case for someone to resolve.
What came through, what never arrived and what wasn't planned
The reconciliation screen sums up the period in four figures:
- Fulfillment: how much of the forecast amount found its actual transaction.
- Forecast that never arrived: planned items that didn't show up at the bank. It may be a late collection, a postponed payment or something that won't happen.
- Actual that wasn't planned: what the bank moved that wasn't in the forecast. If it recurs, like a fee or an automatic tax, it's worth adding to the plan.
- Pending classification: how much of the actual transactions doesn't have a category yet. It's informational and doesn't block reconciliation.
Fulfillment is also shown by category, so you can see which kinds of flows the forecast gets right and which ones drift.
Classifying without slowing operations down
Statements don't carry categories: they carry a date, a description and an amount. FLIQO always separates inflows from outflows, and when classification rules are set up it assigns the matching category. Whatever no rule recognizes stays unclassified, counts toward the balance like any other transaction and can be reclassified later, one at a time or in bulk.
Asking Aria
You can ask Aria to propose matches for a period or an account, how confident it is in each one and what date and amount difference each has. Aria proposes and you confirm: no link is created without an approval in the chat, and each one records who approved it.
Frequently asked questions
Do I need to connect the bank to reconcile?
No. The file the bank exports from its portal is enough, in any of the standard formats.
What happens if an actual transaction doesn't look like anything forecast?
It stays as unplanned actual. You can link it by hand to the forecast item it belongs to, or leave it as an inflow or outflow that wasn't in the plan.
Do bank transactions have to be classified before reconciling?
No. Reconciliation works with unclassified transactions. Classifying them improves the by-category analysis, but it isn't a requirement.
Can I change the tolerance after reconciling?
Yes. The new tolerance applies to subsequent matches. Existing ones are kept, and can be undone to match again under the new criteria.
Who can see each account's transactions?
An account can be restricted to the roles that need it. Anyone without access doesn't see its transactions in reconciliation, and anyone who can't operate it can't load a statement that includes it.