trimix.
SL/EN
Let’s talk
Applications/SLOGA Evidenca
BANK OPERATIONS AND FINANCIAL INSIGHT

SLOGA Evidenca

MVP · pilot onboarding by agreement

From a bank statement to numbers you can explain.

SLOGA Evidenca brings statement imports, transaction review, accounting categories and reporting into one place. It is designed for businesses that want to understand money coming in and going out, with every reported amount connected to its source transactions.

Enquire about SLOGA Evidenca
sloga.Category report

Behind every number.

Select a category to see its source operations.

Category total → Source transactions
Source operationsDEMO
  • Software subscriptionDEMO-011
    €240
  • External servicesDEMO-012
    €1,000
Category total€1,240
Interactive illustration · sample data

The explanation behind each number stays close.

Spreadsheets show amounts, but their explanations often get lost in separate files and messages. Evidenca keeps each transaction together with its company, account, period, category and comment. This makes it easier to explain an unexpected report total and pick up where the previous reviewer left off.

What working with bank operations covers

A controlled workflow from imported statements to classified records.

01

Import with control

Review a bank statement before its transactions enter your working records.

  • Supported camt.053 XML files
  • Preview, confirm or cancel
  • Duplicate checks and batch history
The result

A confirmed set of imported bank operations.

Explore capabilities

Import with preview and confirmation

Upload a file, review the parsed data and then confirm the import. Cancelling the preview creates no bank operations. Batch history and diagnostics help you review what was imported.

Protection against repeated operations

Processing includes duplicate checks when files are uploaded again. The aim is to prevent a repeated statement from creating a second copy of the same transactions.

02

Add business context

Give each operation an understandable category and explanation.

  • Categories and counterparties
  • Accounts and opening balances
  • Company, year and comments
The result

Transactions that the next reviewer can understand.

Explore capabilities

Transaction review and classification

Open an operation, assign or correct its accounting category and add a comment. The classification stays understandable for the next person reviewing that record.

Categories and reference data

Maintain accounting categories, counterparties, legal entities and bank accounts in the same environment. An account can have an opening balance for a specified date.

A clear working context

The organisation, legal entity and reporting year determine the records you are reviewing. Archiving reference records helps keep daily work clear while preserving business context.

03

Understand each total

Move from a category amount back to the transactions behind it.

  • Amounts grouped by category
  • Source operations behind each total
  • Review and correct classifications
The result

A report whose numbers can be explained.

Explore capabilities

Reports with a route back to source

Reports aggregate amounts by accounting category. If a total is unexpected, inspect the operations behind it and check their classification.

How a bank transaction review works

Example: a finance team prepares a category-based view of cash movements.

01

Upload a bank statement

Export a supported XML file from the bank and upload it.

02

Review and confirm

Check the batch data; confirmation creates operations, cancellation does not.

03

Classify and explain

Assign categories, review counterparties and add the comments you need.

04

Explore the report

Review category totals and return to the transactions behind each amount.

For teams that need to understand the same numbers

Owners and finance staff

For a view of money in and out, understandable accounting categories and a structured monthly review of bank transactions.

Accountants and operational managers

For a shared understanding of transactions: the operation, category and explanation stay connected rather than scattered across spreadsheets.

A category suggestion supports a decision; it does not make it.

The current MVP offers category suggestions using deterministic rules. It does not call an external AI provider. Suggestions are not saved automatically: a user reviews, changes if needed and explicitly saves the classification. More advanced AI classification is a separate development stage.

Imports, local formats and implementation scope

From a bank file to confirmed operations

  1. Bank export

    Manual camt.053 XML upload

  2. Format check

    The specific bank and XML variant

  3. Import preview

    Review the parsed data

  4. Confirm import

    Create the reviewed operations

The supported bank export is checked before onboarding.

Illustration of the manual statement-import workflow

Supported statements

The core workflow uses manual camt.053 XML imports. Before onboarding, we check the specific bank and its export format; support for the standard alone does not establish compatibility with every bank variant.

A European market

The need for organised bank records extends beyond a single country. Implementation availability depends on the organisation, banks, formats and customer’s business environment.

Current scope

The MVP has been verified in the development environment. Direct PSD2 or bank synchronisation, automatic AI classification and public self-service registration are outside the current MVP.

Common questions

BEFORE ONBOARDING

Understand the source.

Which bank?
Which export format?
Check a sample statement together
Topics for an initial conversation
Does Evidenca connect directly to my bank?

The current MVP uses files that you export from your bank and import manually. Direct bank synchronisation is outside this scope.

What happens if I cancel an import?

You can cancel the preview without creating bank operations. Operations are created only after you confirm the import.

Is this a complete accounting system?

Evidenca focuses on bank operations, classification and category reporting. It does not present a complete general ledger, payroll or tax submission as part of its scope.

How does onboarding start?

We first review a sample bank export, your categories, legal entities and way of working. The pilot and access arrangements are agreed together.

Put your bank transactions in context.

Tell us which banks and formats you use, and what you need to understand from the data.

Enquire about SLOGA Evidenca

Explore the SLOGA family

Independent applications for different parts of your working day.

SLOGA Flow

Source-document review and preparation for accounting.

SLOGA Books

An accounting workspace in development.