Odoo · ERP · Peru
Common Odoo localization mistakes in Peru
Most localization problems we are asked to fix were created in the first two weeks of configuration, by decisions that looked small at the time. These are the ones that come back.
Last updated: September 2026
Issued per week
By document type
Series defined before the establishments were known
Numbering set up without accounting for branches and issuing points. It works until the second establishment starts invoicing, and by then documents have already been issued under the wrong scheme. Correcting it is possible but never clean.
Duplicate tax configurations
Two or three configurations for the same tax, created by different people at different moments. Each produces a slightly different base, and the reports stop agreeing with each other. The symptom is a monthly argument about which report is right.
Detracciones treated as ordinary payments
The deposit recorded without a link to the certificate or to the supplier payment. The detracciones account balance then cannot be verified, and the reconciliation queue grows every month.
Inconsistent exchange rate
Purchasing using one source, sales another, accounting a third. The differences are small per document and significant at close, and tracing them means revisiting individual transactions.
Credit notes not linked
Notes issued as independent documents rather than linked to what they modify. It passes validation, breaks reporting, and produces differences against the SUNAT proposal.
Inventory accounts left at default
Existence, cost and variance accounts never mapped to the company's own chart. The warehouse valuation and the accounting balance then diverge, and nobody can explain by how much or why.
Localization assumed to be complete
The largest mistake of all: treating "Odoo has a Peruvian localization" as the end of the analysis. The localization is a foundation. Document types, series, special regimes, statutory registers and the transmission service are all decisions on top of it.
Any of these found in a running system is worth fixing before the next close, not before the next audit. They compound.
Frequently asked questions
Can these be corrected on a live system?
Most can, with care and a defined cut-off. Series are the hardest, because issued documents cannot be renumbered. That is why they are worth an hour of discussion before configuration.
How do we know if our localization is incomplete?
Recurring manual adjustments every month, an unverifiable detracciones balance, reports that disagree, or a warehouse valuation that does not match the ledger.
Who should review it?
Someone who understands both the accounting result and the ERP configuration. A purely technical review will not find these.