Likidera Cash Flow Management
TR EN

Your financial data stays under your company's control

Likidera runs on your company's own server or computer. Bank statements, cash flow forecasts, counterparty details and the audit log are kept in your own database.

Where it runs

Which installation suits you?

You can use Likidera on a single computer, or install it on a server in your company network and work on it together with your finance team. You choose the setup at the start and can move to a different one when your needs change.

  1. your network

    Everything on one computer, inside your network.

    Use on a single computer

    The Likidera application and its database run on the same computer. It suits a single user and needs no network setup.

  2. your network

    One database on a server, reached from each computer on the local network, inside your network.

    Use through a server

    Likidera's server component and the database run on your company's server. Your finance team connects to it over the company network.

  3. your network

    A computer at a second office has only the application installed; it connects to the same server across the network. All of it inside your network.

    Use from a client computer

    Only the Likidera application is installed on the user's computer. It connects to your company's existing server; no separate database is needed on that computer.

Requirements
Likidera runs on Windows and uses Microsoft SQL Server as its database. Before installation, we check with your IT team that your infrastructure meets these requirements.
Backup
You take a full backup of the database from inside Likidera into a folder you choose. Each backup is listed with its date, size and location, and you can restore from the same screen when needed.

Once installation is complete and user permissions are set, your finance team runs the day-to-day work.

Likidera is not a cloud service.

Data security

Your data is protected by several layers of security

Alongside user permissions, data encryption, an audit log and protection against failed logins are in place. All of these measures run on your company's own infrastructure.

  • Encryption at rest

    Specific fields such as IBANs, tax numbers, e-mail addresses and phone numbers are encrypted in the database with AES-256 and decrypted in the application's memory when needed. Even if someone gains unauthorised access to the database or backup files, these fields are hard to read directly.

  • An audit log that tracks changes

    Changes to data and user permissions are recorded in the audit log. You can trace which information was changed, by whom and when, and what the previous value was. Financial records are voided, not deleted, so the transaction history is preserved.

  • Protection against failed logins

    After repeated failed login attempts, the user account is locked and the number of requests is limited. When an error occurs, the user sees a short message; the system's internal details are not shared.

Roles and permissions

Each user can do only what they are authorised to do

In Likidera, the screens each user can reach and the actions they can take depend on the role assigned to them. In the list below, each role also includes every permission of the roles above it.

  1. Viewer

    Can view the data but cannot change it.

  2. Analyst

    Can edit cash forecasts and create scenarios.

  3. Accountant

    Can enter transaction, receivable and payable records, and import bank statements.

  4. Manager

    Within their permissions, can delete records, close accounts and view the audit log.

  5. Admin

    Can manage users and system settings.

  6. Owner

    Has the widest permissions. Under the current rules, a user with the Owner role cannot be given a lower role.

User permissions are limited by set rules: an Admin cannot assign the Owner role to another user, and users cannot change their own role. Every role change is recorded in the audit log and can be reviewed later.

The product itself enforces these constraints.

Payment approval

Large payments go through a second approval

You can require approval from a second user for payments above an amount threshold you set. Payments below the threshold carry on as they do today. Every approval and rejection is recorded.

Payment record
Inside LikideraThe payment is matched to its invoice.
At your bankNone.
Second approval
Inside LikideraAn authorised user approves; the action is recorded.
At your bankNone.
Payment rejection
Inside LikideraThe reason for rejection is recorded.
At your bankNone.
Money transfer
Inside LikideraNot done.
At your bankDone.

Approving a payment in Likidera does not mean sending a payment order to your bank. Likidera does not connect to your bank and does not transfer money. The approval is an internal control and is recorded in the audit log.

Where are payments handled?

The person who records a payment cannot approve it; the records show who approved which payment.

Two people at a table, one turning the page of a printed document while the other follows it

Compliance

The product comes with tools that support your compliance processes

Likidera has features for classifying cash movements by activity type and controlling access to personal data. These features do not, on their own, make your company compliant; compliance depends on how the product is used and on your company's processes.

IAS 7 / TMS 7
Classifying cash flowsLikidera records cash movements transaction by transaction, and you can classify each one as an operating, investing or financing activity. Tax movements can be flagged separately.
IFRS 18
Preparing for financial reporting standardsThe category structure shows interest and dividend payments separately, and dividend payments are classified as financing activities. The classification and reporting requirements under IFRS 18 should be reviewed together with your company's accounting policies and how the application is configured.
KVKK
Protecting personal dataLikidera offers features for data encryption, managing access permissions, the audit log and handling data subject requests under KVKK, Türkiye's data protection law. Your company's KVKK policy and data processing practices decide how these features are used.
Likidera Data Subject Rights screen: a data-export request and a deletion request panel, for handling KVKK Article 11 requests

Privacy Notice (KVKK)

Likidera holds no certificate documenting compliance with the standards or regulations named on this page.

Installation and getting started

Your cash position, visible from day one

The installation wizard guides you step by step through setting up the database, the Owner account, the company profile and the bank accounts. You can choose your existing SQL Server for the database.

If you like, you can get to know Likidera with two companies that come with sample data before importing your real data. When you are done, you remove the sample data and start working with your own.

  1. Day one: the cash view

    The first bank statement is imported and your cash position appears.

  2. First week: completing the data

    Statements for the other accounts and the related financial data are imported; the first cash forecast is built from this data.

  3. First month: users and permissions

    User accounts and roles are set up, and the daily routine is settled to suit your needs.

Likidera Bank Accounts screen: the total cash position above the account list, each account with its bank, currency, type and balance

These timings show a sample installation plan. The actual time can vary with your company's infrastructure, how the data is prepared and your installation needs.

See Likidera run on your own numbers

In the demo, we load your bank statements and counterparty list together and look at your cash flow for the coming weeks in Likidera. We'll also give you a quote that fits your needs during the call.

What happens after a demo request?

Or reach us directly: +90 (212) 275 90 60 · info@caretta.net