The first openly AI-based customs clearance system in Hungary
A familiar morning: the invoice is sitting in your inbox, the carrier is already pushing to load, and someone has to turn it into a customs declaration by tonight. From now on, most of that work is no longer done by a person: the system reads the invoice, works out the origin, and fills in the licenses. What is left for you is what was truly your job all along — review it, approve it, and off it goes to the Hungarian customs authority.
LRN HU26090700418
Net mass differs from the product master — awaiting approval
Verified — ready to file
Our mission
If you work in customs, you know this feeling well: at the end of the day you look back at your work and realize half of your time went into typing. Filling in forms, looking things up, copying data — routine operations that need none of your fifteen years of experience, yet they swallow the whole day. Meanwhile, good customs professionals are ever harder to find on the market, and ever more expensive. The usual answer is to hire one more person — months of advertising, with less and less success. We chose a different path.
We work so that customs clearance can be a real profession again, not mere administration. Let the machine take the monotonous, repetitive, error-prone tasks. And in the harder cases — the risks, the unusual situations, the judgment calls — let it stand next to you and give you solid ground. So you can spend your time on what made you choose this career in the first place: professional decisions, clients, and solutions.
Yes, we use artificial intelligence for this, and we say so openly — to our knowledge, we are the first on the Hungarian market to do that. If that makes us pioneers in such a conservative profession, so be it. But we also draw a precise line where the machine is not allowed to decide: whatever the law determines is never decided by AI.
Export — live today
Let’s start where your day starts: an invoice comes in. Most software then waits for someone to produce a data file from it first — an XML, a spreadsheet. We read the invoice itself, exactly the way you would, only in twenty seconds instead of twenty minutes. Whatever is unambiguous goes straight in; whatever shows a discrepancy is flagged and put in front of you.
Look at the card above: the partner, the items and the values came straight from the invoice, and the tariff code from your product master. By the time your coffee cools down, the assembled draft is ready. A single item differed from the master data — and the system highlighted exactly that one for you. The decision stays yours, without the burden of typing.
It handles far more than invoices: packing lists, licenses, EUR.1s, certificates of analysis, Excel line items — sixteen document types in total, each identified and processed by its own structure. We didn’t train it on a single template; we trained it to recognize on its own what it has been given.
The approved declaration goes straight into the AES system from here, and we track the whole journey: LRN, MRN, amendment or invalidation — you manage everything in one place. If the shipment arrives in the middle of the night, you can approve and file it from your phone; no need to sit down at a computer.
The typing goes to the machine. The decision stays with you.
Preferential treatment — live
The invoice is processed — but is the product actually originating? The preferential duty rate depends on it, yet in most places the answer comes from memory or from an inherited Excel sheet. Not here: origin determination is a question of law, so a strict list-rule engine runs behind it, not AI guesswork — to our knowledge, nobody else in Hungary offers this at such depth today. The system identifies the applicable agreement from the tariff code and the destination country, runs the rule on the product’s bill of materials, and puts the derived result in front of you. So you see the reasons behind the decision, not just a verdict.
The calculation formulas — the share of non-originating materials, the ex-works price, tolerance, cumulation — used to live in the spreadsheet of that one colleague who is on holiday exactly when you need them most. Now they run directly on the product’s data sheet, and if the calculation fails, you see precisely which condition wasn’t met.
If the result is positive, the paperwork is no longer your problem either: the EUR.1 is drafted with the official box layout, along with the invoice declaration, the REX, the A.TR and the non-preferential certificate with its chamber-of-commerce application. We also keep watching the expiry dates, so a REX authorization can never quietly lapse.
The supplier’s declaration is the most fragile point of the supply chain — a missing signature often only surfaces half a year later, during an audit. Here it is checked the moment it is uploaded: EORI number, signature, stamp and validity — before you build anything on top of it.
Because the system follows close to a hundred international agreements at once, it alerts you the moment a shipment would waste a tariff preference — before you quote your customer a price, not afterwards, when it is too late.
We do the math. You weigh the case.
Official certificates — live
After the declaration and the origin, we arrive at the part everyone likes to postpone: the licenses. Based on the tariff code, the system automatically recognizes which certificates the goods require and fills in the forms — always working from the same master data. That rules out typos and partner names spelled three different ways across the paperwork.
We started with veterinary certificates, because that is where the friction was worst — and the other official licenses are following one by one: everything your client used to struggle with and would have gladly handed to a professional long ago.
Manual bookkeeping ends where quantity quotas begin: a draft reserves the quota immediately, and filing finalizes it. Two transactions running in parallel can no longer consume the same quantity twice — and you don’t find out at submission time that the quota ran out.
The form fills itself in. Your client’s trust is built by you.
Already solved today
A shipment’s story neither starts nor ends with the declaration. Incoming mail, master data, consignment notes, deadlines and end-of-month reports — until now that meant five separate programs and sticky notes on the monitor. Now it is all on one central surface, built from the same data as the declaration itself. And if something crosses your mind at night, you don’t have to wait until morning in doubt: you check the system, and go back to sleep.
You open your laptop in the morning and last night’s invoice is already waiting among the prepared items: the system watches your mailbox and starts processing the attachment automatically. The era of manual forwarding is over.
For recurring invoice formats, configured templates run instead of guesswork — AI is deployed only where it is genuinely needed. For you, processing any familiar invoice is a single step.
Tariff code, composition, weights, dual-use classification, end use — whatever you record once keeps working for you automatically in every declaration and every origin calculation from then on.
EORI numbers are validated online, you can load even a thousand partners from Excel in one move, and the sanctions status is visible right on the partner’s data sheet. It is not your job to keep it all in your head.
The CMR consignment note is generated from exactly the same data as the declaration — so it cannot diverge from it, and you don’t have to type the address a third time.
You see the shipment’s exact route all the way to exit confirmation, and the MRN is one click away — so when someone calls asking about the status, you have a precise answer immediately.
Your dashboard immediately shows expired and stuck cases: tasks, deadlines and customs-authority errors in one place. It won’t be the client calling you about a delay — it will be you calling them to say everything is handled.
What went through on the first try, where things got stuck, which client moved how much volume — it is all there in ready-made reports you can export to Excel. The end of the month becomes an overview, not an accounting exercise.
Role-based permissions, with mandatory justification and logging on critical actions. When the auditor asks six months later, you don’t reconstruct events from memory — you show the log.
You see exactly who is working on what, and personalized views and column setups can be shared — the team moves in one direction without overwriting each other’s work.
Measures, conditions, footnotes and quota balances directly on the item page. No more juggling a dozen tabs of the EU browser.
We continuously screen names, company data and name variants against the EU sanctions list and the OFAC SDN database, refreshed daily. You will know the partner’s status is clean before the deal, not after.
The monotony is ours to carry. The craft stays yours.
Beta partners’ pricing is locked for the entire term of the contract — even as the feature list keeps growing.
Verification
At every demo there comes the moment when someone asks: fine, but what happens when the system gets it wrong? It is the most important question — because in the end a person answers for the declaration, not a machine. That is why verification is not built in as an option you can switch off, but as three layers of defense that cannot be bypassed.
The way you would have a colleague look over a high-stakes declaration: an independent, more complex model re-derives the expected result from the raw documents and shows the differences field by field. It overwrites nothing — it lays the analysis in front of you, and the decision is yours.
Origin is computed by a list-rule engine, TARIC measures come from the EU’s official database, and sanctions hits come from the official registers. AI reads and suggests — the legal conclusions are drawn by code, with source references you can present at any audit.
Critical discrepancies can only be resolved with the right permission and a mandatory justification — and the justification goes straight into the audit log. If the question comes up later why an item was let through, you don’t answer from memory: you show the log. That is the difference between uncertainty and preparedness.
We build our own database on closed infrastructure, so client data never reaches an outside third party. The AI inference pipeline can even run entirely on self-hosted models — that is merely a deployment decision. If this is a compliance question for you, say so and we will walk you through the details.
Not only for customs agencies
So far we have shown the system as if you were a customs agency. But there is another angle: you are the exporter, aiming at new markets. For you, the declaration itself is not the main question — it is everything that comes before it. Can the product be shipped at all, under what conditions, and what will it cost at the border? The system answers from the same product master it builds the declarations from, and your ERP is never touched.
Does your product qualify as originating under the applicable agreement, and can it claim preferential duty? You get the answer before you quote a price — not afterwards, when the difference would already be eating your margin.
Is the product subject to licensing, do restrictions apply, and what certificates does the destination country require? What used to be a week of emailing with a consultant is now right on the product’s data sheet — between two meetings, next to your coffee.
If you supply raw materials or components, your buyer’s origin calculation partly depends on you — and whoever provides solid ground there becomes a more valuable partner. We show you where you stand today and which market is worth building toward: from your own data, not from hunches.
For customs agencies
This is not yet another program your team has to spend weeks learning. It fits organically into your existing workflows and takes over exactly the tasks that used to consume the most time and energy.
For exporting companies
Every month you paid an external consultant for work the system does with the same precision from one uploaded invoice and your existing product master — at a considerably better price. You don’t have to adapt to the customs software: the system reads your data.
What comes next Looking for testers
So far we have talked about export — that module is live today, working with real clients. The next chapter is being written right now: import. The supplier uploads the product data themselves on a simple interface, and we gather the origin data, the restrictive measures and everything else needed before the goods enter the EU. So a potential problem does not surface at the border, but at the point where it is still simple and cheap to fix.
Precisely because there is an enormous amount of complex work between here and complete. We are building it to be genuinely helpful in the most intricate situations — and we are doing that together with the partners who join us now.
Whoever joins now shapes how the import module will work. Whoever arrives after the official release gets the finished product.
Industrial bearing · 8482 10 10 · CN
Not discovered at the border. The customs agent gets the full picture upfront.
Who is behind it
“We have logged your request, we shall see.” “There is no capacity for this at the moment.” “This cannot be solved in this form.” Anyone who has ever been a customer of a large software vendor knows these sentences — we went through it too, and at some point enough was enough. We did not want to found yet another software company; we wanted to give this profession its substance back. That is why development works differently here: what our testers ask for, we build — instead of filing it into minutes. Whoever joins us now does not get a support ticket number. They get us.
Fifteen years in customs brokerage. He is the one who knows this profession’s challenges precisely, and knows what a system must deliver for a customs agent to lean on it with a clear conscience.
Responsible for the software: bespoke codebase, own database, closed system. He is the one who answers every “that’s impossible” with: let’s see how it can be done anyway.
Quick answers
No — and that is not our goal at all. It takes over the form-filling, the searching and the data copying, so more time is left for decisions: analyzing risky items, handling special cases and supporting clients. The declaration is still approved and filed by a person.
The same party as today: the declarant. That is exactly why the system files nothing automatically. It prepares the data, flags the discrepancies and shows where each piece of data came from — approval is a human decision in every case, and the system logs it in detail.
It is not an AI estimate. Based on the tariff code and the destination country we determine the applicable agreement, then run its list rule on the product’s bill of materials: we check the share of non-originating materials, the ex-works price, tolerance and cumulation. The result is presented as a detailed derivation, not a bare yes or no.
Invoices, packing lists, licenses, EUR.1s, certificates of analysis, Excel line items and more — sixteen document types in total. It also verifies uploaded supplier’s declarations: existing EORI number, signature, stamp and validity.
Yes — the export declaration goes directly into the AES system, with full LRN and MRN tracking, including amendment and invalidation. If the shipment arrives at night, you can approve and file it from your phone; no computer needed.
No, and we hold to that fully. The system reads directly from your product master, so you never have to produce separate exports for it. Your ERP stays unchanged: we adapt to it, not the other way around.
We build our own database on closed infrastructure, and client data never reaches an outside third party. The AI inference pipeline can even run entirely on self-hosted models — it is merely a deployment decision. We are happy to go into detail, because this is a question that deserves it.
Yes. Partners are screened against the EU consolidated financial sanctions list and the OFAC SDN database with daily updates, including name variants and accent-stripped spellings. TARIC sanctions and dual-use flags appear on the item page as well — with clear hit, review and clean statuses.
Once the product master and partner data are loaded, the first declaration is usually ready within a few days. With beta partners we personally walk through the first weeks together — we are there for every question that comes up. That is precisely why the number of open seats is limited.
Beta partners get the export module and origin calculation at a preferential price, locked for the entire term of the contract. We give a concrete quote once we know your volumes — that is why the application asks for your expected number of monthly clearances, so the offer fits you precisely.
Your question is not here? Ask it in your application — and we will answer it personally.
You can still join
For us this is not a product launch — it is a mission: we want to change the way customs work is done. For that we are looking for partners, not mere users. Beta partners get the export module and origin calculation at a preferential price — locked for the entire term of the contract. In return we ask only this: use the system, and share what you experience. The missing features we will build together.
Sending failed. Write to us directly: [email protected] — with the same answers, and we will take it from there.
We received your application. We will read your message and get back to you personally within a few days — no automated replies.
3 seats open in the beta program
Join the betaIf you accept, Google Analytics builds anonymous usage statistics — that is how we learn what is clear on this page and what is not. If you decline, nothing loads from Google and no cookie is set on your device.