Main Concept Services Audit & Reporting SAF-T Connector Migration to Odoo Transfer Pricing Other Services Industries Contacts UA
Service 02

SAF-T Connector

A convenient platform for preparing SAF-T UA reports — independent of ERP systems, with turnkey implementation by LUCAS. Fast launch with a single partner responsible for the entire process.

Обговорити проєкт Усі послуги

About SAF-T Connector by LUCAS

SAF-T Connector is an ERP-independent solution for preparing SAF-T UA XML files from any accounting system: SAP, BAS/1C, Odoo, Microsoft Dynamics, custom ERPs or multiple data sources simultaneously. Installed on-premise, includes XSD validation and logical data checks, deployed end-to-end by the LUCAS team. Suitable for companies with large transactional data volumes, multiple accounting systems or planning migration to a new ERP.

What it is SAF-T Connector — LUCAS proprietary product for preparing SAF-T UA XML files
What it does Extracts accounting data from ERP, generates the SAF-T UA XML file, performs XSD validation and logical data checks
For whom Large taxpayers, companies with SAP, BAS/1C, Odoo, Microsoft Dynamics or multiple data sources
What sets it apart ERP-independent on-premise solution, fast processing of large data volumes, end-to-end implementation, competitive cost
Result SAF-T UA XML file ready for submission upon DPS request

SAF-T Connector is independent of your accounting system.

SAF-T Connector is a standalone product, not built into any ERP. We implement it independently: the client provides data access, and then LUCAS works autonomously — without creating internal project teams on the client's side.
ERP Independence

Connects to any data source

Unlike solutions tied to a single ERP, SAF-T Connector connects to SAP, 1C/BAS, Odoo, Microsoft Dynamics, and any custom systems. The solution can work with multiple data sources simultaneously.

Competing solutions are typically built inside a specific accounting system — and only work with it. SAF-T Connector is a standalone product that does not depend on where you keep your accounting records.

  • SAP, 1C/BAS, Odoo, Microsoft Dynamics
  • Any custom systems
  • Works with multiple data sources simultaneously
  • Connects via databases, APIs, or export files
Performance · Python

Fast processing of large data volumes

The SAF-T Connector algorithm is written in Python and optimized for processing large arrays of transactional data. For companies with high transaction volumes this means faster SAF-T UA XML generation, less load on the accounting system, and more stable processing of historical periods.

  • Optimized Python algorithm
  • Processing without load on the client's ERP
  • Stable processing of large historical periods
Validation

Series of data checks before submission

Automatic XSD validation and additional check layers detect errors before the file is submitted. Each error description is formulated in plain language — without technical jargon for the accounting team.

The result is a SAF-T UA XML file generated in accordance with the current structure and STS technical requirements, with preliminary data validation.

  • Automatic XSD validation
  • Additional data check layers
  • Each error described in plain language
  • SAF-T UA XML file per STS requirements
On-premise · Security

Data stays within client infrastructure

The system is installed on the client's server. Works without cloud data upload and without transferring accounting information to third parties. The solution does not require internet access.

  • Installed on client's server
  • No cloud data uploads
  • Does not require internet access to operate
  • Your data does not leave your infrastructure
Turnkey · 3–4 months

Implementation doesn't become the client's project

From the client's side, data access and responses to specific questions are sufficient. LUCAS takes on the main project load. Typical implementation timeline — 3–4 months, depending on the number of data sources, quality of accounting information, and client team availability.

  • Client provides data access and, if needed, accounting logic explanations.
  • LUCAS implements autonomously
  • No internal client project teams required
  • Ready product in 3–4 months
Single accountability zone

One partner responsible for the entire result

When one vendor supplies the product and another implements it, responsibility often gets diluted. LUCAS provides a single point of accountability for the product, implementation, methodology, and support.

  • One partner for product and implementation
  • Clear accountability zone
  • Competitive total cost of ownership
FAQ

What you should know.

Analysis of data sources, mapping the chart of accounts to the SAF-T UA structure, checking the quality of reference data. Without quality input data, even the best software will generate a file with errors.
The cost depends on the ERP system, number of data sources, and mapping complexity. Turnkey SAF-T Connector implementation starts from €9,900.
Typical errors occur not only at the XML or XSD schema level, but even before the file is generated — in the data structure, reference books, analytics, and mapping logic. The most common issues are related to insufficient transaction detail, incorrect links between documents, accounts, counterparties and tax data, as well as the accounting system not storing certain information in the format required for SAF-T UA. Errors can be avoided through prior data diagnostics, field mapping to SAF-T UA structure, test file generation, XSD validation, and logical consistency checks before official submission.
XSD validation checks whether the XML file conforms to the approved SAF-T UA technical structure. If the file fails technical or logical checks, the STS may reject the file and provide a list of identified errors in the receipt.
SAF-T UA cannot be submitted in Excel format — the file must be generated in XML according to the current STS XSD structure. Excel can only be used as an intermediate source or auxiliary tool, not as the final submission format. SAF-T Connector includes an Excel viewer for generated XML files with editing capabilities.
A built-in module typically works within a single ERP and depends on its data structure, performance, settings, and availability of required detail. This can be a limitation for companies with multiple systems, those that changed ERP during the reporting period, or those storing part of their data outside the main accounting system. SAF-T Connector works as a separate layer between accounting sources and SAF-T UA XML. It can consolidate data from multiple systems, apply unified mapping logic, perform preliminary validation, and generate the file regardless of which ERP is used for accounting.
SAF-T UA does not replace tax declarations and standard reporting. Declarations are filed in the usual manner, while SAF-T UA is generated as a separate XML file and is currently submitted by large taxpayers upon STS request during documentary audits.
SAF-T Connector is on-premise: installed on the client's server, data does not leave the infrastructure, no internet connection required.
3–4 months. After implementation, technical SAF-T generation typically takes from a few minutes to two hours, depending on the volume of data in your accounting system.
If the STS did not accept the file, you need to analyze the list of errors in the receipt, identify their cause, correct the data or file generation logic, and resubmit the SAF-T UA. SAF-T Connector has built-in technical checks that allow processing errors before submitting the report to the tax authority.

Ready to discuss SAF-T implementation?

Tell us about your accounting system — we will assess the scope of work and propose turnkey implementation terms.

Submit a request