solutions

Solutions for the finance function

Accounting, planning and control subsystems we implement for finance and accounting teams. They work as parts of one system built on the UnityBase platform, rather than as separate applications between which data has to be carried by hand.

accounting core

Accounting and tax

The foundation where digitalisation of a finance function usually begins: source documents, assets, inventory and payroll in a single database.

01

Accounting and tax records

Fixed and intangible asset accounting, VAT settlements with counterparties and corporate income tax records. Statutory reporting is produced from the same data as management reporting.

02

Labour records and payroll

Personal employee accounts, working-time registration and automated payroll calculation from the recorded data. Results feed straight into postings, with no re-entry.

03

Inventory accounting

Materials and raw stock by storage location, goods receipt, transfers and movement control. Balances are visible at the moment of the transaction, not at period close.

04

Production accounting

Registration of production costs: direct material costs, issue of materials to production and cost attribution to accounting objects.

05

Costing and cost of goods

Planned product costing: definition of cost objects and value indicators against norms. Gives a basis for plan-versus-actual comparison, not only for closing the period.

planning and control

Money, contracts, procurement

The layer where finance stops registering events after the fact and starts influencing them before the payment is made.

06

Financial planning

Budget preparation, budgeting itself and control over execution of the approved budget. Limits are checked where the commitment arises, not during month-end reconciliation.

07

Contract management

A single database of signed contracts with automated tracking of performance and payment status. Finance can see what stands behind every scheduled payment.

08

Procurement management

Procurement planning, purchase requests and supplier contract management. A request is linked to a budget and a contract from the moment it is created.

industry-specific

Where general accounting is not enough

Areas with their own calculation logic that otherwise live in spreadsheets outside the system.

09

Vehicles and transport services

Vehicles, drivers, fuel types and fuel cards. Transport costs become a distinct accounting object instead of an "other" line.

10

Catering accounting

Recipes, costing cards and warehouse operations that account for raw material batches. Relevant for education, healthcare and plants with their own canteen.

adjacent areas

What finance touches every day

These subsystems belong to other departments, but their data ends up in financial documents — so they are worth planning up front rather than integrating later.

  • Electronic document managementdocument flow, access rights, central administration
  • Electronic contractsqualified e-signature and Mobile ID, paperless contracts
  • HR managementstaffing tables, personnel orders, employee records
  • KPI and appraisaltarget planning and performance calculation
  • Business analysisreport builder, personal reports, e-mail distribution
  • Business process managementform building, data validation, reporting

The list of subsystems follows A5.ERP by A5 Solutions, a member of the Intecracy Group international IT consortium. The system is built on the UnityBase platform. Source of the module list: a5erp.solutions.

platform

UnityBase — the foundation underneath

UnityBase is not another product in the list above but the platform layer beneath it: a full-stack JavaScript low-code / model-driven platform for enterprise applications. It is a joint development of Intecracy Group companies, in which InBase is a key but not the only developer. Open source since 2012.

One domain model

Domain metadata describes data, UI, API and system behaviour in one place. A new accounting area is therefore a change to the model, not a separate module that later has to be reconciled with the rest.

Who sees what

Role-based access control (RBAC) and row-level security (RLS) let you open exactly the cost centres a controller owns rather than the whole database. Commercial editions add ACLs and attribute-level protection.

Audit trail

Change history and security audit record who changed an amount, a status or a document attribute, and when. This is usually the first thing an internal or external auditor asks for.

Approval routes

BPM mechanisms describe the path a document takes before payment, including signing and a queue for deferred operations. Commercial editions integrate with Camunda BPM.

Exchange with adjacent systems

The REST API is generated from the same domain model; integrations include mail, Active Directory, SharePoint, DocuSign and OData in commercial editions. Exchange with banking and tax services is built on this layer.

Where it runs

PostgreSQL, Microsoft SQL Server, Oracle (including RAC), MySQL, SQLite3. Deployment in the cloud or on-premises where data-control requirements leave no alternative.

OpenUB / OE Apache License 2.0

The official platform site states a separate caveat on the use of Apache 2.0 parts by organisations related to the Ukrainian public sector.

Enterprise / EE commercial

Extended security, integration and authentication mechanisms. Recommended for high-load systems.

Defence / DE commercial

An edition for heightened security requirements: key-based authentication and work with certification authorities.

Capabilities differ between editions — the list above does not mean every mechanism is available in the free edition. We do not quote percentages of acceleration or savings before seeing your document volumes and current approval routes: in financial accounting those figures depend on the starting point, not on the platform. Platform details are at unitybase.info.

Fill in a short form — we will route your request to the right team and reply within one business day.