Treasury lives between systems
Invoices and accounting live in the ERP, balances and transactions in the banks' portals, and questions come in by email or chat. Treasury spends the day copying from one to another, and every copy is a chance for a figure to go stale or get pasted wrong.
FLIQO doesn't replace any of those systems. It reads what they already produce, delivers what each one needs and keeps a record of every exchange.
From the ERP to the forecast
Connectors read the report exactly as the ERP exports it, without first reshaping it in a spreadsheet. The same file provides the transactions and the catalogs it carries: categories, classifications, departments and areas. Catalogs are filled in and never deleted by a load that doesn't include them.
Each load is either forecast items or actual transactions, and whoever loads it declares the period it replaces. Before confirming, FLIQO shows how many records will be replaced and how many of them had been edited by hand. What's already reconciled is kept, and what another FLIQO feature generated, like a recurring item or the two legs of a transfer, isn't touched. Loading the same file again leaves everything as it was.
When it finishes, a receipt compares the rows in the file with the rows that were loaded and explains every difference. A load is never reported as correct while hiding a shortfall.
Each transaction records which system it came from and who owns it in that system, so update reminders reach whoever actually maintains the data. If your system doesn't have a connector yet, the same information comes in through FLIQO's Excel template.
Loads that don't get lost
When you upload a file, FLIQO stores it, confirms it was received and processes it on its own: there's no need to keep the tab open. If processing is interrupted, it resumes by itself, with a limit on attempts so a problem doesn't keep repeating unnoticed.
A tray shows the status of each file and tells two cases apart: a file that was read and doesn't fit that source, which needs to be fixed, and a system failure, which is retried. The original file is kept exactly as it arrived, so a load can be repeated without asking whoever uploaded it to send it again.
From the bank to FLIQO
Statements come in the standard formats banks export: MT940, camt.053, MultiCash or CSV. FLIQO recognizes the format from the content and splits out the accounts when a file carries several. Balances can also come in through an Excel template when a bank doesn't deliver a statement in time.
From FLIQO to the bank
Each bank wants transfers its own way, and the company sets up how to deliver them without programming:
- A file for the bank's portal, delimited or fixed-width, with the column order, date and amount formats, and the header and trailer each bank asks for.
- An ISO 20022 payment message, with each bank's profile: version, how the bank and the account are identified, and the codes its guide requires.
- An instruction letter as a PDF, in the company's own wording, ready to sign.
Before a format is saved, a preview shows it with sample data. If a piece of data is missing when a batch is exported, FLIQO doesn't generate the file and lists everything that's missing at once. When the bank replies with its ISO 20022 acknowledgment, FLIQO reads it, shows what was accepted and what was rejected with its reason, and updates each transfer on confirmation.
From FLIQO to accounting
Investment events, such as placement, interest accrual, collection, sale or recognized impairment, go out as journal entries. The company defines the accounts, and an event without a configured account isn't exported. Each event produces its debit and its credit, and a file that doesn't balance isn't issued.
Each batch moves from generated to sent to received by the accounting system, or to rejected with its reason. What you download later is exactly what was sent.
Your corporate assistants, with FLIQO's data
A read-only API lets the company's corporate assistants answer liquidity questions with current data: cash flow, funding needs, compliance with the liquidity policy, scenarios and counterparty limits. Answers come from the same calculations as the screens, so they say the same thing as the dashboard.
The API doesn't create, change or delete anything: no external system can move money or change a setting through it. It authenticates with the company's corporate sign-in or with the application's own credential, and answers only what that person or application is allowed to see. Its contract is published in the OpenAPI standard, which integration tools read directly.
Frequently asked questions
Do we have to change ERP or bank?
No. FLIQO reads the files your systems already produce and delivers the ones each of them already knows how to receive.
Does FLIQO connect directly to the bank to send payments?
Not today. FLIQO generates the file or letter the bank receives through its portal or usual channel, and reconciles the result when the acknowledgment or the statement arrives.
What if the ERP report groups by accounting date?
The load works, but the forecast ends up shifted: FLIQO uses the day the money moves. It's worth confirming with whoever prepares the extract that the report uses the payment or collection date.
Can we correct just part of a period that was already loaded?
Yes. When loading, you declare the date range being replaced, and whatever falls outside that range isn't touched.
Who can download the files for the bank?
Only whoever runs the bank submissions. The files carry the full account number, which other users see with only its last four digits.