trimix.
CLOUD ACCOUNTING

SLOGA Books

In development

Documents, accounting and obligations in one workspace.

We are developing SLOGA Books for smaller businesses and accounting firms that want to connect source documents, bookkeeping, sales invoices, banking, employees and reporting. The aim is to make it clear what is ready, what is missing and what needs to happen next.

Discuss SLOGA Books development
sloga.Period workspace
Example company

A clear next step.

Example tasks before closing a period

Documents
Bank
Payroll
What needs attention
A source document is missingAdd source
A payment needs matchingReview
Payroll inputs need completingComplete inputs
Documents → Books → ReportsA planned connected accounting workflow
Interface concept · In development

Accounting as a connected workflow.

An invoice supports an accounting entry, a payment settles a liability, and payroll feeds the books and reports. We are building Books around these connections: the aim is to complete supported business events and accounting periods clearly, while retaining originals, checks and the basis for each result.

In development

SLOGA Books is in development and is not finished. The following describes its purpose and planned functional scope, rather than an already available complete accounting system.

What we are building in SLOGA Books

Connected areas from everyday documents to financial year-end.

01

Everyday business

Connect the documents, invoices and bank movements behind your daily work.

  • Source documents and sales
  • Bank imports and reconciliation
  • Company context and access
The result

A planned shared view of daily business events.

Explore capabilities

Source documents and sales

Planned functions include invoice and receipt intake, retention of originals, duplicate checks and links to accounting entries. Sales includes simple outgoing invoices, numbering and linked corrections.

Bank transactions and reconciliation

We plan agreed CSV and camt.053 statement imports, matching payments to invoices, partial payments, fees and an overview of outstanding payables and receivables.

Several companies and controlled access

An owner works in their company’s context; an accounting firm needs a client portfolio view and then works within the selected legal entity. Accounting and payroll access are assigned separately.

02

People and payroll

Bring the inputs for employee records and payroll into the same workflow.

  • Employees and employment history
  • Working time and absences
  • Payroll, contributions and allowances
The result

A planned path from employee inputs to payroll results.

Explore capabilities

Employees and payroll

The planned scope covers employee and contract records, working time, absences, payroll calculations, deductions, contributions and payslips. The first localisation also includes annual and winter regres payments.

03

Books and reporting

Follow business events through the books to period closing and reports.

  • Ledger, balances and fixed assets
  • Taxes and structured e-invoices
  • Closing and official reporting
The result

A planned accounting cycle with checks and source links.

Explore capabilities

Accounting books

We are developing a double-entry model: chart of accounts, journal, general ledger, trial balance, opening balances, traceable corrections and open items.

Fixed assets

Planned functions include an asset register, accounting treatment and separate accounting and tax depreciation for the supported business profile.

Taxes and required reports

VAT-period preparation, tax records and reports follow the country localisation. The first Slovenian version’s development scope includes DDV-O, DDPO, REK-O and the annual AJPES package.

Period closing

Review document completeness, bank reconciliation, calculations and exceptions before closing a month or year. Unknown or missing information must remain visible as an open issue.

E-invoices and official sources

Plans cover structured e-invoices for agreed eSLOG or European standard profiles, alongside an official source library with versions and links to validated calculation rules.

The intended journey from document to closed period

Example: a smaller business manages documents, employees and regular obligations in one environment.

01

Set up the business

Establish its profile, supported transactions, opening data and required permissions.

02

Handle daily events

Receive documents, issue invoices, import statements and collect payroll inputs.

03

Review and approve

Prepare results, complete missing facts and execute permitted actions with checks and confirmations.

04

Close and report

Review completeness, resolve exceptions and prepare the relevant reports or export files.

Two ways of working

Business owners and their teams

We plan an overview of documents, obligations and deadlines, understandable requests for missing facts and a link from each business event to its result.

Accounting firms

The intended experience combines a view of several clients, prioritised exceptions and company-specific accounting actions, with separate data permissions.

One connected workspace.

In development
Example company
Documents
Bank
Payroll
Example next actions
Review a document
Complete payroll inputs
Interface concept · In development

AI for supported tasks, with verifiable results.

The development goal is for AI to complete a supported accounting task to a verified result, rather than merely suggest an answer. Calculations and rules run in verifiable software; missing facts, unclear rules or insufficient permissions block the dependent action. Achieving this goal still requires subject-matter testing. User approvals, payments and external report submission remain separate actions.

A European focus. Country-specific accounting rules.

A shared foundation, country-specific requirements

  1. Shared accounting core

    Documents, books and closing

  2. Country rules

    Local accounting and tax requirements

    SI
    SloveniaIn development
    Additional country packScope and validation required
  3. Local reports

    Forms and reporting formats

Each localisation needs its own rules, formats and validation before use.

Architecture concept · In development

First localisation

The first version is being developed for smaller Slovenian service businesses within an agreed profile. This is the initial use case, rather than a limit on the product’s long-term direction.

Other European countries

The intended architecture separates the shared accounting core from country rules, tax calculations and forms. Each additional localisation requires its own scope and validation before use.

Current status

The application is in development. Module availability, a correct financial calculation, a prepared export file and actual acceptance of a report are separate stages that require separate checks.

Questions about development

DEVELOPMENT QUESTIONS

Your needs shape the discussion.

Documents
Rules
Reports
Which business profile?
Which country requirements?
Discuss the intended use case
Development concept · In development
Can I already use Books for complete accounting?

No. SLOGA Books is not finished. We can discuss your business needs during development, but we do not present the complete accounting scope as ready for use.

Will it only work in Slovenia?

The product has a European direction. Its first localisation is Slovenian; other country support must be separately developed and validated.

Does Books require SLOGA Flow?

No. Books and Flow are developed as independent products. Books has its own planned source-document intake; belonging to the same family does not imply that synchronisation is already available.

Will the application make payments and submit reports itself?

Preparation, checking, approval, export, payment and external submission are distinct actions. We do not promise automatic payments or direct submission to every government system.

What does your business need from accounting?

Tell us about your country, business profile and the tasks you would like to simplify.

Discuss SLOGA Books development