UlúApp
The holder uploads documents, AI checks them against customs and tax rules, and your team decides. You also run each operation up to the Value Declaration.
The Customs Law reform removed liability exclusions from Article 54: inaccurate information from the importer no longer clears you. And each client’s file still lives in emails, spreadsheets and folders, in the hands of very few people.
Mexican Customs Law, reform DOF Nov 19, 2025, in force Jan 1, 2026 · RGCE 2026, rule 1.4.14
Six steps in one place. Every step records who did what.
Pick their profile (importer, exporter, trading company, intermediary, correspondent, supplier or one your brokerage creates) and UlúApp builds the document list that applies, with its legal basis. If your portfolio lives in Excel, bring it in at once.
They get a link and a one-time code by email. They upload from the phone, sign your brokerage’s forms with their e.firma right there and always see what’s missing and how to fix it.
It checks each document against Mexican customs and tax law, extracts its data and flags what doesn't match between documents.
Approving or rejecting is always a person's call, with the file in view. If rejected, the holder gets the reason and how to fix it.
Reminders before each expiry and a heads-up to the person in charge if the client doesn't answer. Certificates the tax authority sends to your brokerage's mailbox are filed in the right file on their own.
Your Word forms fill themselves with the client's data and keep their design. The complete file downloads as a single archive, with an index of statuses and expiry dates.
Every control exists so a machine error is caught before it reaches operations.
Articles of incorporation, powers of attorney and contracts go to human review by system rule, not by setting: nobody can skip it.
Only monthly renewals can be approved automatically, and only if a person already approved one, the reading has 0.9 confidence or more, the tax ID matches and the date is in the month. It ships off, and any approval can be sent back to review.
If the company name, tax ID or address doesn't match between two documents, UlúApp flags it and someone confirms or corrects it.
If automatic review stops, the dashboard says so and the document goes to manual review. Your team keeps working.
In the text sent to the model, RFC, CURP, emails, accounts and pedimentos are swapped for placeholders using format rules; names are detected by labels and a stray one may slip through. What classification learns stays in your brokerage.
The holder signs in with their signed link and a 6-digit code valid for 10 minutes with 5 attempts. Documents are served through short-lived links.
Every sensitive action is logged with who and when, without the document contents or the tax ID.
Each document a person approves teaches the system to classify the next ones better. Learning never approves or rejects on its own.
Console captures with sample data. Each brokerage dresses it with its own logo and colors.
Dashboard: the day’s figures and what comes first
UlúApp hands your pedimento system the data ready to use. AI prepares, a person decides and everything is logged.
AI proposes the tariff code and NICO from the description and spec sheet, with the rules behind it. Your classifier confirms or corrects.
It gathers items, values and additions with the DOF exchange rate and estimates duties, so you know how much advance to request.
It fills in what UlúApp already read from the invoice and pedimento, brings what repeats from the client’s previous one and takes you to each missing field. Direct VUCEM submission is still in testing: today you file there and keep the folio here.
It compares documents, goods and inspection and tells you what to fix: packages that don’t add up, a missing receipt, an item without a tariff code.
A board with each operation by stage, from documentation to release. Your team moves the card and the client gets notified.
The office prepares the pre-inspection or examination and your people in the yard capture evidence from the phone.
What each client owes or has in favor, with advances, payments on their behalf and fees, invoiced separately. And every day it checks your clients against the SAT lists.
This month against last: clearance times, examinations, money and the stage where each operation gets stuck.
UlúApp was born with the Injoy team, a customs and transport brokerage in the port of Veracruz, around its holders, its document catalog and its validity periods. Everything specific to a brokerage lives in configuration, so your file comes out the way your regulator asks. Today we offer it to a few brokerages, with close support.
The name comes from San Juan de Ulúa, the fortress in the port of Veracruz, the historic gateway of Mexico's foreign trade.
No. UlúApp prepares the data and gives you a file with your system's columns. The pedimento is still prepared and validated where you do it today.
Not yet. Direct submission is still in testing. Today UlúApp builds the Value Declaration, you file it in VUCEM and keep the folio here.
They're an estimate for requesting the right advance. The official amount is the pedimento's.
In the text sent to the model, RFC, CURP, company names, emails, phones, accounts and pedimentos are swapped for placeholders using format rules. This is pseudonymization: a stray name may slip through. What classification learns stays in your brokerage and isn't shared with others.
Yes. Clients, operations and balances import from Excel.
The price is given in the diagnosis or by our sales team. Request access and we will write to you.
Where it is used
Leave your details and we will write to activate your access. Tell us what is most urgent so we know where to start with you.
Requesting access is free and carries no commitment · We reply by email
