A control that lives outside the tool doesn't get followed
In many treasuries internal control is written in a policy and exercised by email: someone asks for authorization, someone else replies "approved", and the operation happens in a spreadsheet anyone can edit. When the audit comes, piecing together who decided what, and with what information, takes days.
FLIQO keeps control inside operations: the second signature, segregation of duties, permissions and the record of every change all happen where the work is done.
Dual control on critical decisions
High-impact decisions aren't applied on one person's say-so. One person proposes, a different person reviews the change and approves or rejects it. This covers, among others:
- Activating, replacing or retiring the company's liquidity band.
- Authorizing an additional, temporary limit on a counterparty, with its regularization date.
- Reopening a closed accounting period, opening a future one or closing one early.
- Changing an investment's accounting classification.
- Settling, buying back or reopening a debt issue.
Whoever requests cannot approve their own request. A single rejection is enough to stop it, and each type of operation declares how many signatures it requires. The approver sees the change before and after, and the decision takes effect in the same act in which it's recorded: either both stand, or neither does.
Approvers are notified when a request is pending, and the requester is notified when it's resolved.
Segregation of duties
Some duties are best done by different people, and FLIQO lets you separate them:
- Estimating and recording what happened: a role can load the forecast without being able to record actual transactions, which stay with treasury or come in from the bank.
- Deciding and executing: in FX quotes, whoever awards the deal doesn't settle it. In investments, the front office records the deal and hands it over, and it's activated only after it's received.
- Releasing and sending to the bank: transfers between accounts can be run by one team or two. With two, whoever releases a transfer doesn't send or confirm it.
Each company decides whether to turn these separations on. A small treasury can operate with one person without being asked for a signature nobody else can give.
Each person sees and does only what's theirs
Permissions are assigned by role, and each permission is a concrete capability: viewing the forecast, loading transactions, reconciling, approving. So you don't have to build each role permission by permission, FLIQO includes treasury job profiles, such as treasurer, approver, auditor or budget analyst, to use as a starting point. If a role later drifts from its profile, the screen flags it.
Beyond the role, access can be limited in two ways:
- By department or area: a person can see only their unit's accounts and transactions. Company-wide figures, like the forecast, stay complete for whoever has permission on them.
- By account: an account can be restricted to the roles that need it, with view, operate or administer access. Anyone without access doesn't see it in lists or totals.
Who made each change, and when
The activity log brings together on a single timeline what happened in the company: transaction reclassifications with the old and new value, matches made by hand or automatically, dual-control requests and decisions, and changes to users, roles and permissions.
Changes to users, roles and permissions are kept with their author, the date, and the before and after. Every sign-in attempt, successful or not, is recorded, and an account is temporarily locked after several failed attempts. Each company decides how long it keeps its history.
What's closed doesn't get changed
When an accounting period is closed, the processes that accrue interest or freeze valuations stop writing to it. Each month opens automatically; anything outside the routine, such as reopening an earlier month, requires a second signature.
Valuations and controls frozen on a date aren't overwritten: running them again that day adds a new version and keeps the previous one. The figure reported on closing day is still available a year later.
Daily consistency checks
Every day FLIQO reviews each company's data for inconsistencies that aren't visible at a glance. For example, an account that used to receive the bank statement and whose latest balance was keyed in by hand, a transfer between accounts missing one of its two legs, or an expired approval still pending. Findings are recorded so someone can fix them.
Aria follows the controls too
Aria answers only with the data the person asking is allowed to see. When an action requested from Aria changes data, such as applying reconciliation matches, Aria proposes it and the person confirms it in the chat. The action is recorded with who approved it.
Frequently asked questions
Can more than one approval be required?
Yes. Each type of operation sets the minimum number of signatures, and the requester can ask for more in a particular higher-risk case, never fewer.
Can an auditor review without changing anything?
Yes. The auditor job profile comes with read-only access to operations and to the activity log.
Are views logged?
No. Changes and sign-ins are logged. Logging every view would create a volume that makes it hard to find what matters.
Do approvals arrive by email?
They arrive in FLIQO's notification center. Each person can also get a copy by email if they turn it on in their preferences and the company has its outgoing email set up.