In many organizations, financial procedures are thoroughly documented. There are manuals describing how to build a cash forecast, reconcile bank transactions, check counterparty limits or approve certain transactions. The activities are known, so are their owners and, sometimes, the conditions that must be met before moving on.
But when the day starts, a difficulty shows up: knowing how a process should work isn't the same as knowing where it stands.
A procedure may say that estimates are recorded first, then actual transactions are imported and finally everything is reconciled. But the document doesn't say which activities are already done, which are still pending or what information is holding things up. That gap between the procedure and its execution is one of the challenges of financial management.
1. The procedure describes the work, but doesn't show its status
Traditional flowcharts represent activities, decisions and sequences. They're useful for documenting processes, training people and assigning responsibilities. But most share a limitation: they're static.
A diagram can show that a reconciliation has to be completed before certain information is validated, but it doesn't say whether that reconciliation was done today. Nor does it tell you whether transactions are still pending, approvals are missing or a condition needed to move on hasn't been met yet.
That's why it helps to tell two things apart:
- The documented flow explains how a process should unfold.
- The operating flow tells you what's happening while it runs.
The first helps you understand the procedure. The second helps you manage it.
2. From a static flowchart to a flow connected to data
Picture a reconciliation process with five activities:
- Record estimated transactions.
- Import actual transactions.
- Reconcile the differences.
- Validate the resulting information.
- Check forecast accuracy.
A traditional flowchart would show those activities joined by arrows. But what if the actual transactions haven't been imported yet? Or there are transactions still to reconcile? Or a forecast proposal is still waiting to be validated?
In a flow connected to operating data, those situations become visible: some steps show as completed, others as in progress and others flag that they need attention.
- 1Record estimatesCompleted
- 2Import actualsCompleted
- 3ReconcileIn progress
- 4Validate the forecastNeeds attention
- 5Check accuracyPending
The picture stops merely explaining a sequence and starts showing which conditions have been met and which need someone to step in. The flowchart is no longer just a map of the work; it becomes a guide for doing it.
3. Not every user takes the same path
A finance team brings together people with different responsibilities. An analyst records information and reconciles transactions. A treasurer focuses on the cash position, forecasts and financing decisions. A risk officer reviews concentrations, limits and exposures. An auditor looks at controls and evidence.
Even on the same platform, they don't need the same screens or the same sequence of activities. Forcing them all through a single procedure adds needless complexity; giving each role a suitable guide brings order to the work.
That doesn't mean everyone invents their own controls. Institutional procedures remain the shared reference, while personal routines adapt to each user's responsibilities. Standardization and personalization don't have to be at odds.
4. How FLIQO workflows work
FLIQO includes visual flowcharts for organizing and moving through activities on the platform. Each flow groups a sequence of steps tied to a process or a role, and there are two kinds:
- Company flows. Set up by administrators and available to every member of the organization. They establish shared paths, such as a reconciliation, getting a company up and running or a financial control.
- Personal flows. Every user can create their own, visible only to them, to organize their routine without changing the institutional flows.
Flows are customized by picking the activities, changing their order and renaming them to match the company's terminology. An organization might prefer "Record projected collections" over "Record estimates", for example. That flexibility brings the tool closer to how people understand and carry out their responsibilities.
On top of that, every step is a shortcut to its screen. Users don't have to dig through menus to find the next activity: they move forward from their own map of the work.
5. Colors communicate the status of the process
In FLIQO's flowcharts, the color of a step tells you where it stands:
- Green — Completed: the activity has met its verifiable conditions for the active period.
- Blue — In progress: there is information, but some condition is still missing.
- Yellow — Needs attention: something needs review or a specific action.
- Gray — Pending: the data the step depends on doesn't exist yet.
When an activity has an automatic check, its status comes from querying the company's actual information: for example, whether there's a liquidity band in force, whether transactions remain unreconciled or whether forecast proposals are waiting for validation. Some steps also show a short indicator that helps interpret their situation.
One point needs to be clear: not every activity has an automatic check. Some tools are always available for consultation and show in green by default. A green step isn't always evidence that the activity was carried out.
That distinction is key to reading the flowchart correctly. A visual indicator is useful when you understand what condition it represents and where its limits lie.
6. Dependencies: check the conditions before moving on
In financial processes, the order of activities isn't always a matter of preference. Some tasks need information that has to exist beforehand: there's no point reconciling actual transactions that haven't been loaded, or validating a forecast without what's needed to review it.
FLIQO workflows recognize certain dependencies between activities. When a user tries to open a step whose prerequisites haven't been met, the platform warns them and tells them which activities to complete first. That way, certain operating rules are built into navigation itself: it doesn't just point out what should come first, it keeps an activity from being started from the flow without its prerequisites.
Workflows aren't a universal process automation engine, nor do they, on their own, guarantee compliance with every financial control. Their purpose is to bring order to the paths of work and connect them with the conditions the platform can verify.
7. One process, different ways to organize it
Consider three examples.
The treasury analyst might have a personal flow that starts by reviewing estimates, moves on to importing actual transactions and ends with reconciliation and variance analysis. The goal is to organize an operating routine.
The head of treasury might use a flow built around reviewing the cash position, checking forecasts, examining liquidity conditions and weighing the day's financial decisions. The path is geared to oversight and analysis.
The platform administrator might rely on a company flow to set up master data, define accounts, establish financial parameters, organize permissions and check the conditions needed to start operating.
In all three cases, the flows use features FLIQO already has; what changes is how they're organized for each purpose. And each user can only add the steps they have access to, according to their permissions and the modules enabled for their company.
8. Personalizing the work without losing governance
Being able to create personal flows is an advantage, but it calls for telling operating freedom apart from institutional authority. A user can organize their path, pick activities and adapt labels. That doesn't mean they can change the organization's official procedures or gain extra permissions.
- Company flows are managed by authorized roles.
- Personal flows are private and only their owner can change them.
- The step catalog respects the permissions that already exist on the platform.
Personalizing navigation doesn't change access rules. Everyone organizes their work without altering the responsibilities the company has defined, a balance that matters especially in finance, where operating flexibility has to coexist with clear controls and responsibilities, as described in treasury internal controls.
9. From navigating screens to working by process
Many enterprise applications organize their features into modules and menus. That structure is necessary, but it means you have to know where each tool lives. And real work doesn't always follow the structure of the software: people think in activities.
- What do I need to review?
- What information do I need?
- What do I still have to complete?
- What comes next?
Flowcharts bring the digital experience closer to those questions. Instead of starting by looking for a screen, users start by choosing the process they need to run. That matters especially for people who are new to an organization, change roles or use certain tools only occasionally, and it reduces reliance on informal knowledge about how to get around the application.
The direction is clear: bring software closer to the way work is actually organized.
10. Operational intelligence also needs to understand the work
Digital transformation tends to focus on integrating data, automating calculations and building indicators. All of that matters. But an organization also needs to know how the activities that produce and use that information relate to each other.
A dashboard can show a variance. An alert can flag a problem. An artificial intelligence tool can help make sense of its possible causes. But people still need to know which activity comes next, what information has to be available and what conditions must be met to move forward.
FLIQO workflows add a layer that complements financial intelligence: the visual organization of activities and how they relate to operating status. They don't replace institutional procedures or formal control systems; they make part of that logic more visible and accessible in everyday work.
An organization doesn't improve only when it understands its figures better. It also improves when its people better understand the work it takes to produce, verify and use them.
FLIQO: operational liquidity intelligence
FLIQO combines financial information, analysis, conversational artificial intelligence and operating organization tools to support liquidity management. Its visual workflows let you organize activities by process or by user, go straight to each feature and check the verifiable status of certain steps.
It isn't only about knowing what needs to be done. It's about each person knowing where to start, what needs attention and how to keep going.
Anticipate liquidity. Understand the figures. Decide with confidence.
