Argentina ARCA Supplier Invoice Validation: does it fit your Odoo? A case to help you decide

What you are really deciding

When you choose this module you are deciding two things at once: the module itself, bought for each Odoo version, and the FlexigoTech Cloud local service that comes with it. Without a subscription, or with the service suspended, whatever the subscription provides stops; your data stays in your Odoo. That is why it pays to look at both parts before installing anything.

The module is published on Odoo Apps for versions 17, 18, 19 and 20, and costs €9 excluding VAT, a one-off payment per Odoo version, on all four; the local service costs €29/month or €290/year excluding VAT (Pro: €58/month or €580/year).

A case from start to finish

Example Illustrative case: the company and its figures are made up to explain the flow.

Talleres del Paraná is a made-up Argentine SME that already uses Odoo 18 for purchasing and accounting. An external consultant runs the implementation. The head of administration wants to handle supplier invoice validation and withholdings inside Odoo, and before buying the module she goes through the listing with the consultant. These are the steps they follow.

First, the Odoo version

Odoo 18 is among the published versions, so they can buy the module for their version. The consultant raises a question: if they move to Odoo 19 next year, what happens to the module? The listing answers it from two angles. With the subscription, the module for new Odoo versions is included if it was bought on flexigotech.com; if it was bought on the Odoo App Store, each version is bought there. And migrating the database to the new version is not something FlexigoTech does: it is down to the company or its consultant.

What the subscription includes

The listing sets out what the service includes:

• Monitoring of the module's sources, with their alerts and the calendar of their deadlines.
• Monitoring of the module's health in your database, with alerts.
• Support with response times: the first response within 1 working day.
• The service on the staging and test copies of your database.

What is left out

And it sets out what is not included:

• Customising the module or custom development.
• Migrating your database to a new Odoo version.
• Configuring the module for you (the setup).
• Importing historical data.
• Support for modules that are not FlexigoTech's.
• Third-party costs: you contract and pay for your account on each platform, Odoo and your hosting yourself.

For Talleres del Paraná this has a practical consequence: their consultant will do the configuration, and if they want to load old invoices they will have to arrange it themselves. The setup steps are in the getting started guide.

What data leaves their database

The head of administration asks what the database sends to the service. According to the listing:

• The database identifier (uuid), its address (URL) and the Odoo version.
• The FlexigoTech modules installed, with their version, and whether the database is a neutralised copy (staging or test).
• The company name and the email of the person who accepts, with the date and version of the text accepted.
• A public code to check that requests come from that database, and a proof that it is that database, computed on your server without sending its secret.
• A request for its service permit every 6 hours and the module's health: counters and errors (type and code), without the content of your records.
• Its requests for the module's alerts and calendar, with the date of the last alert received: the database identifies itself and sends nothing else.

On top of that come payment from Odoo and a notice when you uninstall the module. Connections to FlexigoTech's servers are encrypted (HTTPS), the servers are in Germany, and the customer area has its own database, backed up daily.

Trying it on a copy

As the service covers staging and test copies, the consultant first installs the module on a staging copy of their Odoo 18. There they review the lists the module adds before touching the production database.

If you want to understand what each of those screens does, we explain it in how the module works under the bonnet.

Criteria to decide

• If your Odoo is on 17, 18, 19 or 20, the module is published for your version; on any other version, it is not.
• If you expect to upgrade, it makes sense to buy it on flexigotech.com with the subscription, as the module for new versions is then included; bear in mind that migrating the database is not covered.
• If nobody on your side can configure the module, you need a consultant or a separate implementation: setup is not part of the subscription.
• If you want to import old invoices or suppliers, plan it yourself: importing historical data is left out.
• If your internal policy requires knowing what leaves the database, the data list in the listing lets you review it with whoever runs your systems.
• If you want to test without risk, the service covers staging and test copies.

What to take from the case

The case leaves three questions worth answering before you buy: which version you are on and whether you will change soon, who configures the module and who loads the old data, and whether you accept the data exchange with the local service. Once those answers are clear, the decision comes down to checking it on a staging copy. The full listing is on Odoo Apps and the purchase with subscription is on the module page.

How FlexigoTech can help

FlexigoTech implements Odoo 17, 18, 19 and 20 and builds custom connectors and integrations. If you need someone to do the setup, adapt the module or connect it to other processes in your business, that is contracted as a project separate from the subscription.

Keep reading