Integrating AI with Argentine ERPs: Tango, Bejerman and DUX
Integrating AI with an Argentine ERP like Tango Gestión, Bejerman or DUX can be done through three paths: activating the native AI the vendor built into the system, connecting a custom AI layer through the APIs the ERP exposes, or, when there is no API, accessing the data through alternative routes (read-only database access, scheduled exports, AI document reading). All three paths are viable today; which one fits depends on what your specific ERP exposes and what you want to automate.
That is exactly the information missing from the internet. There is plenty of documentation about SAP, Dynamics or NetSuite (we cover them in our general AI + ERP integration guide); about the ERPs used by Argentine mid-market companies, what exists is the vendor selling its module or a partner selling the implementation. At Duotach we assess these integrations for real projects: we verify each vendor's official documentation, endpoint by endpoint when it exists, and build the integration layer when it does not.
Summary: what each Argentine ERP exposes for AI integration
This table did not exist anywhere public until now. It is the starting point for any integration decision:
| ERP | Vendor's native AI | Documented public API | Typical path for a custom AI layer |
|---|---|---|---|
| Tango Gestión (Axoft) | Yes: Tango AI + AI-powered PDF document import (Delta 5) | Partial: per-process APIs on the Delta platform (developer token) + Tango Tiendas REST API | Platform APIs depending on version and license; assessment with the partner |
| Bejerman ERP (Thomson Reuters) | Yes: 5 AI features since October 2024 | No public developer portal | Assessment with the vendor; in on-premise installations, read-only database access |
| DUX Software | Not its focus; the differentiator is the API | Yes: complete, public REST API (PRO and FULL plans) | Directly against the official API |
The quick read: DUX is the most open (end-to-end public API), Tango is the one that added the most native AI (and has been opening APIs with the Delta platform), and Bejerman added its own AI but keeps external integration closed, which in practice leads to the database route. Let's go ERP by ERP.
Automating Tango Gestión with AI: Delta 5, Tango AI and Axoft's APIs
Tango (by Axoft) is one of the most widely used ERPs among Argentine companies, and also the one that moved the most on native AI over the last year.
What Delta 5 brings in AI
According to the official Tango Gestión Delta 5 release notes, the version adds two AI pieces:
Tango AI: a chat built into the platform to query the system's data in natural language and receive answers as grids, text and charts. It supports multiple AI providers and models (you choose by cost, speed and precision), which queries each user can run is configured per role, and it can execute actions such as sending emails.
AI-powered PDF document import in the Purchases module: document registration is automated from the PDF, with configurable origins via email, folders or WhatsApp.
Two honest caveats. First: these features require being on Delta 5; if your Tango is an earlier version, the path starts by discussing the upgrade with your partner. Second: Axoft does not publish the conditions or costs of AI consumption in its open documentation; confirm them with your Tango provider before building the business case.
What APIs Tango exposes
Here is the part IT teams ask us about the most. Tango has two documented integration surfaces today:
Delta platform APIs. On the new platform, each process exposes a self-documented API that applies the same validations as a user operating by hand, according to Axoft's API release documentation. A developer token is required to use them. Delta 5 added, for example, order modification via API.
Tango Tiendas API. A public REST API, with an official GitHub repository, designed to connect e-commerce: it receives sales orders (individual or in batches of up to 25), allows querying products, prices, price lists, customers and warehouses, and offers webhooks for events such as order processed, order invoiced, price update and stock update. It requires a Tango Tiendas Full license, the treasury module, access-token authentication and TLS 1.2 at minimum.
For a custom AI layer, those webhooks are gold: instead of polling the ERP all the time, your automation reacts when a price or a stock level changes. It is the difference between a bot that "asks every 5 minutes" and one that finds out instantly.
What is left for a custom layer on Tango
Tango AI solves queries and document loading inside Tango. A custom layer appears when the use case crosses systems: when the query combines the ERP with your e-commerce and your CRM, when the alert has to reach the right salesperson on WhatsApp, when the approval flow lives outside the ERP. There the architecture is the usual one: a middleware (we use n8n) that talks to Tango's APIs on one side and to AI agents on the other.
Bejerman ERP: new native AI, external integration to be assessed
Bejerman (now owned by Thomson Reuters) took the opposite path to DUX: lots of native AI, little openness to the outside.
The AI Thomson Reuters added
Since the official October 2024 announcement and according to the Bejerman ERP product page, the system offers five AI features:
AI order manager: centralizes orders from multiple channels by interpreting text, images and audio, including WhatsApp messages.
Smart document loading: automates the capture and registration of purchase documents.
AI-powered Business Intelligence: multi-source management dashboards and periodic reports.
Business intelligence analyst: natural language interaction with the ERP for reports, charts and alerts.
Supplier payment management: a portal for tracking payments and invoices.
If your pain is manual document loading or orders coming in through WhatsApp, try these native features first: you already pay for them with the product or they are contracted on top of it, and they require no integration project.
The blind spot: integrating with Bejerman from the outside
The product page mentions "APIs for other integrations" and ships pre-built connectors with Tiendanube and Mercado Libre, plus cloud access via Bejerman Virtual. But there is no public Bejerman developer portal: no open documentation of endpoints, authentication or conditions. In practice, any external integration starts with an assessment with the vendor or the partner maintaining your installation.
Our concrete experience: for an industrial company running Bejerman on-premise on SQL Server, we evaluated the possible paths and the chosen route was read-only database access, with a user restricted to reads and a layer of versioned custom views on top, so automations and AI agents do not get coupled to the ERP's internal schema. It is a pattern we repeat across closed systems: we do not buy the vendor's SDK when all we need is to read data, and we leave writes where the vendor officially supports them. With that read access solved, natural language queries, collection alerts or automated invoice loading are built on top without touching the ERP's core.
DUX Software: the Argentine ERP with a truly public API
DUX is an Argentine cloud ERP aimed at SMBs, and on integration it is the most transparent of the three: the API is publicly documented, with a complete technical reference any developer can read before signing anything.
What the DUX API allows
Reads: invoices, orders, items, categories and subcategories, price lists, stock, warehouses, companies and branches, withholdings and taxes.
Writes: creating invoices, orders and products (v1) and recording collections, purchases, expenses and supplier payments (v2).
Conditions: the API is available on the PRO and FULL plans, the access token is generated by the client from their own account, and the documentation declares a limit of one request every 5 seconds. DUX says it plainly on its official page: “Dux provides the documentation and the access, but does not perform the integration”. The integration is done by your team or a third party like us.
The limits that matter (and the brochure does not mention)
We assessed this API endpoint by endpoint for an auto parts distributor running on DUX, and these are the findings that change the design of any integration:
Two API generations (v1 and v2) coexist with different authentication: v1 expects the raw token in the header and v2 expects Bearer format. A build using both has to handle the two schemes. It is in the official reference, but easy to miss.
There are no webhooks: it is pull-only. DUX does not push events; to find out about a change you have to poll periodically, respecting the rate limit. For a volume of around 300 documents per month, the one-request-every-5-seconds limit is more than enough; for real-time synchronization, you have to design with that constraint.
DUX's own page declares what the API does not do: it does not allow creating customers independently, transferring stock between warehouses, or managing accounting entries. Add to that the fact that documents loaded via API reference internal IDs (for example, the supplier goes by its DUX ID, not by the tax ID on the invoice), so automatic invoice loading needs a layer that resolves that mapping.
None of this invalidates the API: it is among the best documented in the local market. The point is that "it has an API" is not the same as "the API does everything your project needs". The assessment against the real documentation, before budgeting, is what separates a serious estimate from a blind number.
What if my ERP is not here, or is a custom system?
A good portion of Argentine companies runs on vertical ERPs, custom management systems or desktop software with 15 years on its back. For those cases we always use the same ladder, from the cleanest path to the last resort:
Read-only database access: a user restricted to reads on the system's SQL, with a layer of custom views on top. Cheap and powerful, if whoever administers the installation enables it.
A backup restored in parallel: if there is a daily backup, it is restored into a database of your own and queried there. Zero impact on the productive system; the data is as fresh as the backup.
Scheduled exports: almost every Argentine legacy system exports to Excel or CSV. A watched folder plus an automatic processor turn that export into a living data source.
Document reading with AI: when neither the database nor the exports are accessible, the AI reads what the system prints (PDFs, documents, reports) and structures it. It is the basis of invoice automation with AI.
Interface automation (RPA): the last resort. Fragile against any screen change; only when there is no other way.
Two rules that apply across the whole ladder. First: the custom abstraction layer is not optional. Automations never couple to the internal schema of a system you do not control; they couple to your views or your intermediate model, and if the vendor changes something, you touch a single piece.
Second: the blocker is almost never technical, it is access. Who administers the server, the vendor that enables the database or not, the partner that answers the email or not. Validate access in week one, not in week eight.
Vendor's native AI or custom layer: how to decide
It is not an ideological decision, it is a per-use-case decision:
| Choose the vendor's native AI when… | Choose a custom AI layer when… |
|---|---|
| The use case lives 100% inside the ERP (querying data, loading documents) | The case crosses systems: ERP + e-commerce + CRM + WhatsApp |
| Your version and license already include it or the upgrade is reasonable | You are on a version that lacks it and the upgrade does not add up in cost or timing |
| What the vendor decided to build is enough for you | You need something not on the vendor's roadmap (approval flows, custom alerts, the company's own knowledge) |
| You prefer support from a single provider | You want to choose and switch the AI model, and own the logic |
And they are not mutually exclusive: the typical combination we see in Argentine companies is native AI for what is internal to the ERP plus a custom layer for everything around it.
What to confirm with your provider before starting
The short version of the checklist (the full version, with the questions ready to forward to the vendor, is in the general AI + ERP integration guide):
What official integration path exists for my specific version and license (API, web service, other)? Is there documentation?
What cost and requirements does enabling it have (plan, modules, tokens, version upgrade)?
If there is no API: do you enable read-only database access, or scheduled exports?
With those three answers on the table, only then is an integration budget serious.
Frequently Asked Questions
Does Tango Gestión have an API?+
Can AI be connected to Bejerman?+
Does the DUX API have an additional cost?+
Can AI be integrated with an Argentine ERP without an API?+
Should I use the ERP's AI or build a custom layer?+
Does your company run on Tango, Bejerman or DUX?
How we do it at Duotach
We assess your ERP's real integration path against the official documentation before budgeting, and build the AI layer with n8n middleware and Claude agents: automatic document loading, natural language queries over your data, alerts and cross-system synchronization. We work with Argentine ERPs and custom systems on real projects, alongside the client's own IT teams.
Artículos Relacionados
Integrating AI with your ERP: the complete guide
What integrating AI with an ERP means, the concrete use cases and how it connects for each system.
Automating invoices with AI
How a flow that receives, extracts, validates and loads invoices into the ERP works, leaving only exceptions.
AI Agents with Claude Code: the Complete Guide
What an agent is, how to build one with Claude Code and what it can automate in your company.