About Magi
Magi converts your existing accounting software exports into valid SAF-T files automatically.
Magi was built out of frustration. And if you've spent any time with SAF-T, you already know exactly what that frustration feels like.
The reality of SAF-T in Bulgaria
The Bulgarian National Revenue Agency's SAF-T mandate doesn't just ask you to generate a file. It asks you to produce a single, unified, precisely structured XML document that combines your entire chart of accounts, every sales and purchase transaction, your inventory movements, your tax codes, your partner registry - all of it, mapped to a standard that took the NRA itself years to finalize.
And it asks you to do this from software that was never built for it.
Bulgarian accounting practice runs on a split reality. Your accounting data lives in one system. Your warehouse and inventory data lives in another. Your client's payroll might be somewhere else entirely. These systems don't talk to each other. They never needed to - until now.
So what happens in practice? An accountant opens three different exports. Starts reconciling them manually. Discovers that the account codes in one system don't match the nomenclature expected by SAF-T. Spends hours mapping them by hand. Produces an XML file. Runs it through a validator. Gets a green checkmark. Submits to the NRA. Gets back a list of technical error codes from the NRA - cryptic references to rule violations with no explanation of where in the data the problem is or how to fix it. Starts over.
This is not an edge case. This is every firm, every period, every client.
We're talking about a 40-hour week that quietly becomes a 60-hour one. Deadlines that slip to Sunday evening. Billable hours evaporating into work no client will ever pay for - because nobody invoices for XML reformatting. Senior accountants doing the job of a data engineer, with tools that were never built for it. And the particular, quiet dread of knowing that one miscoded account in a file with tens of thousands of lines could flag an audit - not because the accounting was wrong, but because of a mapping decision made under deadline pressure.
SAF-T is not just an administrative requirement. It is a deeply technical one. It demands an understanding of XML schemas, data validation rules, code mapping logic, and structured file formats that most accounting professionals were never trained for and should never have to learn. The NRA is asking accountants to become data engineers overnight. That is not reasonable. And it is completely solvable.
We have written about this in detail - the real SAF-T requirements, the validation traps, and what actually happens when you submit a file. Read our SAF-T articles →
What Magi does
Magi is a middleware platform. It sits between the software you already use and the SAF-T format the NRA requires.
You export your reports exactly as you always have - from Алма, Микроинвест, or whatever system your firm runs on. Magi takes those exports, cleans the data, reconciles the splits between accounting and warehouse, maps your codes to the correct SAF-T nomenclature, and validates the entire output before you ever submit anything.
That validation goes deeper than most tools. Magi validates not only against the official NRA XSD schema, but against the NRA's own business logic rules - the cross-section checks that determine whether a file will actually be accepted, not just whether it is structurally correct. A file can be perfectly valid XML and still be rejected by the NRA because the internal relationships between sections don't add up. Magi catches those failures before submission, not after.
You get back a file that is ready. Not probably ready. Not ready except for a few things you'll need to fix manually. Ready.
No new ERP. No expensive integrations. No retraining your team on software they don't need. No weekends spent manually editing XML.
The work that currently takes days takes minutes.
Who this is for
If you are responsible for SAF-T compliance - whether you run a small accounting firm managing twenty SME clients, or you are the chief accountant of a large enterprise with complex multi-system infrastructure - the problem is the same. The data is fragmented. The format is unforgiving. The deadline is real.
Magi is built for anyone who has looked at the SAF-T requirements and thought: there has to be a better way.
Who built this
My name is Milen Akaliev. I am a software engineer, the founder of Magi, and an accountant.
That last part matters more than it might seem.
My parents have worked as accountants in Bulgaria for over 35 years. Between them they have navigated every regulatory shift, every new NRA requirement, every system change that Bulgarian accounting practice has produced across three decades. They are not people who are easily overwhelmed by complexity. They have seen everything.
When the SAF-T mandate was announced, I watched them go through the documentation. These are experienced professionals who know Bulgarian tax law the way most people know their own address. And what they encountered stopped them cold. Not because of the accounting logic - they understood that immediately. But because SAF-T is not an accounting problem. It is a technical one. It requires understanding XML structure, schema validation, code mapping between incompatible nomenclatures, data reconciliation across systems that were never designed to speak to each other. Skills that have nothing to do with being a good accountant, and everything to do with being a software engineer.
I am both.
And I spent the better part of a year building Magi because of it.
Not a year of prototyping. A year of building against the actual NRA schema, handling the real export formats of real Bulgarian accounting software, mapping the edge cases that only appear when you process genuine accounting data from genuine Bulgarian firms. A year of understanding not just what the SAF-T specification says, but what the NRA system actually accepts - because those two things are not always the same.
I built Magi because I was in a unique position to - I understood the technical depth of the problem and I had grown up watching the human cost of Bulgarian accounting compliance up close. This is not a product built by a developer who read the NRA documentation. It is a product built by someone who watched two people with 35 years of experience look at SAF-T and realize they were being asked to do something they had never been trained to do, with tools that were never built for it, on a deadline that does not move.
That is the problem Magi solves. And it is personal.
We are currently onboarding our first firms.
If you need a practical, reliable path to SAF-T compliance before the 2026 deadline, we want to hear from you.
Get in touchYour data
Accounting files contain sensitive financial data - your clients' transactions, their partner registries, their tax positions. We understand the weight of what you are uploading and we treat it accordingly. Your data is processed securely, is never shared with third parties, and exists in Magi solely for the purpose of generating your SAF-T output.
If you have specific data handling requirements - as enterprise clients often do - we are happy to discuss them directly.
Where we are
Magi is currently onboarding its first cohort of accounting firms through a closed beta. Whether you manage five clients or five hundred, the conversation starts the same way.
Magi currently supports monthly SAF-T submissions. Annual and on-demand submissions are in development.
Ready to Simplify SAF-T Compliance?
Join Bulgarian accountants who are already preparing for SAF-T requirements with Magi
We respond within 2 business hours