Tax automation software Romania: what we build, and why it is needed
Romanian tax reporting software is written on an assumption: that the data starts in a Romanian accounting system, with a Romanian chart of accounts and Romanian document types. For a Romanian company that assumption holds. For a foreign group, a marketplace seller or a company with a warehouse and a logistics provider, it does not. The data exists and is complete — it is simply in the wrong shape, in another language, under another coding scheme.
That gap is where custom tools earn their place. Every month a finance team spends days moving data between systems by hand is a month of avoidable errors, and manual reformatting is exactly the kind of work that breaks quietly when the person who did it is on holiday.
We are a tax practice that writes its own software. Not a software company that also does tax, and not an accounting firm that buys a licence. That combination is the reason the tools do what the filing actually requires rather than what a specification assumed.
UITdesk: our own product for e-Transport
UITdesk — uitdesk.ro is our product for RO e-Transport.
RO e-Transport requires a UIT code to exist before the vehicle leaves, for movements in scope: goods on the high fiscal risk list, vehicles from 2.5 tonnes, consignments over 500 kg or over RON 10,000, and international transport regardless of the goods. The code is valid for a limited number of days and the declaration has to be made in advance. A company moving one truck a week can live with a web form. A company moving thirty cannot.
UITdesk handles the declaration and the codes, including generation from a file rather than one form at a time, so that a day’s dispatches become one operation. We built it for our own client work, and it is available directly to companies that only need the tool. The underlying obligation is described on the RO e-Transport page, and the mechanics of the code itself in the article on the UIT code.
SAF-T mapping and generation
The D406 file is the hardest Romanian filing to produce from foreign data, because it demands the full accounting picture in a Romanian structure.
Our mapping tool takes what you have — an export from SAP, Oracle, NetSuite or Dynamics, a local Romanian package, or trial balances and journals in Excel — and transposes it: accounts onto the ANAF reference chart, VAT rates onto the codes in the official nomenclature rather than percentages, document types onto the required categories, partners onto records with valid identifiers. The mapping is configured once at onboarding and reused every period, and new accounts or codes are flagged before generation rather than discovered at rejection.
The validation tool then checks the file before it reaches ANAF: consistency between sections, trial balance against journal, existence of partners and accounts, identifier formats. The official validator runs last, and the file is submitted only with zero errors.
Declaration generators from Excel
Not every problem needs an integration. A large part of what we automate is the last mile: a spreadsheet that already holds the right data, and a declaration that needs it in a specific structure.
- Declarations generated from Excel — the data prepared in a workbook you already maintain, converted into the required file for submission.
- XML output in the exact structure a system expects, including e-invoicing and reporting formats, with the field-level validation that stops a file being rejected after upload.
- PDF generation from a data sheet: certificates, statements, recurring documents, produced in one pass instead of a mail-merge that has to be checked line by line.
- Reconciliations run as a tool rather than by eye — a listing against a return, a return against the ledger, a platform export against the invoices issued.
The test we apply is not technical sophistication. It is whether the same manual sequence runs every month. If it does, it should be a tool.
From spreadsheet to dashboard
Reporting built in Excel by successive additions reaches a point where nobody is sure which sheet is authoritative. The fix is usually not a new platform. It is turning the workbook into something that refreshes from the source and presents the result.
We build reporting dashboards on top of accounting and operational data: margins, cash position, receivable ageing, the operating indicators that matter to the business, refreshed on a schedule rather than rebuilt by hand. The reporting content itself is designed with our financial advisory work, so the dashboard shows the figures a decision needs rather than everything the system can produce.
Presentation websites
We also build presentation websites — small, fast, well-structured sites for companies that need a credible online presence rather than a platform. It is the same discipline applied to a different output: written rather than assembled, with the structure, the metadata and the language versions planned before anything is designed, and handed over with what is needed to keep it running.
How a project runs
- We watch the current process. Not a specification meeting — the actual sequence, with the actual files, including the steps nobody documents.
- We define the output precisely. The structure required, the validations that must pass, and what “done” looks like for one period.
- We build and run it in parallel with what you do today, for at least one full cycle, and compare the results line by line.
- We run the filings; you run what is yours. Tax returns stay with us: we run the cycle and you receive the filed returns and the receipts. Reporting tools for internal documents and dashboards — and UITdesk for UIT codes — your team can operate itself.
What we do not do is build a reporting tool that only we can operate and then charge for the dependency: if your team runs a tool, it gets the documentation that goes with it. The wider filing context is on the tax compliance page.
