guide · erp and business software · french polynesia

Which ERP should an SME in French Polynesia choose?

For an SME in Tahiti, choose an ERP that works natively in Pacific francs, applies the territory’s VAT, prepares corporate tax and the DAS2, connects to your local banks and tracks stock from one island to another, with support you can reach on Tahiti time. Vaka, the ERP published by Devlab in French Polynesia, covers these points; an international ERP still makes sense for a group that already runs one.

  • Devlab · tahiti
the essentials
  • An ERP keeps sales, invoicing, inventory, banking and accounting in a single database: a transaction entered once feeds all the others instead of being copied from one tool to the next.

  • The criteria that matter here: amounts in Pacific francs with no conversion, the territory’s VAT rates (5%, 13% and 16% depending on the transaction), corporate tax and DAS2 preparation, local banks, warehouses spread across the islands.

  • Three families of options: all-in-one online business software, international ERPs set up by an integrator, and an ERP published in Tahiti such as Vaka.

  • Vaka is not the right choice for everyone: a sole trader issuing a few invoices a month, or a company already well served by an international ERP connected to its tools, has no reason to switch.

  • Vaka Pro is the edition for businesses; its entry price is published on its page, and anything beyond one module is quoted.

What does an ERP do for an SME in French Polynesia?

An ERP means entering things once. The quote becomes an order, the order leaves the stockroom, the invoice goes to the customer, the payment lands in the bank and the entry is booked in the accounts, without anyone copying amounts between three programs and a spreadsheet.

In a Polynesian SME the question usually comes up when the files stop keeping up: a second warehouse on Raiatea, an accountant chasing documents at month end, VAT rebuilt by hand. That is when a single business system saves hours, provided it knows the local rules.

Which criteria really matter in French Polynesia?

The first filter is local: an ERP that does not handle the territory’s currency, taxes and banks natively will leave you compensating on the side. Check each point below in a demonstration, with your own cases, rather than in a brochure.

  • Native Pacific francs: amounts kept in XPF, rounded to the franc, with no conversion from another currency.

  • Local VAT: one rate per sales or purchase line, and a return prepared from the accounting entries.

  • Corporate tax and DAS2: figures prepared at year end, which the accountant checks before filing.

  • Local banks: statement import, or automatic collection where the bank and the contract allow it, then a reconciliation approved by a person.

  • Stock and warehouses across the islands: quantities per warehouse, tracked transfers, stock counts done on site.

  • Patchy connections: an interface that works on a phone, and a till that keeps selling during an outage.

  • Support on Tahiti time: a team that answers during your working day, not overnight from another time zone.

  • Data migration: customers, items, balances and open items brought over from Excel or your current software.

  • Readable pricing: a published entry price and a written quote for everything beyond it.

All-in-one online business software: who is it for, and where does it stop?

Online business software opens in minutes, is paid monthly and covers what a small business needs most: quotes, invoices, payment follow-up. For a shop or a service firm without much stock, it is often the simplest and cheapest answer.

The limit is context. Many of these tools are built for other markets: check that they keep Pacific francs without conversion, offer the territory’s VAT rates and that a person answers during your hours. Multi-warehouse stock and full accounting are sometimes missing or thin.

An international ERP with an integrator: who is it for, and where does it stop?

An international ERP suits groups, companies operating in several countries and complex industrial or logistics processes. Its range of modules is wide, and an integrator adapts it to your organisation. Devlab does this work too, through Devlab Arpana.

The trade-off is the project: configuration, adaptation to Polynesian rules, training and maintenance depend on the integrator, and every change goes through them. If your international ERP is already well integrated and used, replacing it usually costs more than it returns. Our guide to choosing an integrator lists the questions to ask.

An ERP published in Tahiti: who is it for, and where does it stop?

An ERP designed in French Polynesia starts from local rules instead of bolting them on later: currency, the territory’s VAT, corporate tax and DAS2 preparation, local banking practice. The team that writes it is reachable in the same time zone, which shortens the path from a question to its answer.

Its limits are those of a younger ecosystem: fewer third-party modules and ready-made connectors than an international ERP, and bank connections confirmed one bank at a time. Ask to see each module in a demonstration and have anything that counts as an adaptation written down.

Where does Vaka fit?

Vaka is the ERP published by Devlab in Tahiti. Its business edition, Vaka Pro, brings together sales, invoicing, inventory and warehouses, banking and cash flow, accounting and French Polynesian tax (VAT, corporate tax and DAS2). It is modular: you start with sales, invoicing and accounting, then switch on inventory or cash management on the same data.

Migration from Excel or other software is handled with the Devlab team, which answers in French during Papeete hours. Devlab runs its own company on Vaka. Vaka Expert, the other edition, is for accounting firms. The entry price is published on its page.

Vaka is not the right choice if you are a sole trader issuing a few invoices a month: a simple invoicing tool will do. Nor is it if your international ERP works, is connected to your tools and your teams have adopted it.

How do you compare two ERPs before signing?

Prepare a fictitious scenario and ask each vendor to run it in front of you: a quote with two VAT rates, turned into an invoice with a deposit, paid by transfer, matched to the bank statement, then found in the accounts. Add a transfer of goods between two warehouses and a stock count.

Note what happens without re-entry, what needs a manual step and what would require development. The quote should state the modules, data migration, training and support included.

  • Scenario: quote, invoice, payment, reconciliation, accounting entry.

  • Inventory: transfer between warehouses and a stock count.

  • Tax: VAT amounts per rate, traced back to the entries.

choosing an ERP for an SME in Tahiti