A regional rollout reaches Peru
One client, several countries, one Odoo database. Every country follows the same template until Peru, where the tax authority requires document types, books and withholding regimes that no generic localization covers.
For partners and integrators
Peru localization support for Odoo partners
You already own the project. We cover the country that does not fit the template: SUNAT electronic invoicing, the Peruvian chart of accounts, PLE and SIRE, detracciones and percepciones — configured under your lead, not ours.
Why partners call us
A subsidiary has to report upward
The parent company consolidates inventory or accounting in its own system. The Peruvian entity still has to issue valid electronic documents and keep its books in the format SUNAT accepts.
A developer is stuck on l10n_pe
The Peruvian localization modules work, but the configuration decisions behind them are accounting decisions. Reading the code does not tell you which document type a credit note needs, or how a detraction is posted.
What Peru actually requires
| Requirement | What it means in Odoo |
|---|---|
| Chart of accounts (PCGE) | The official Peruvian chart is not a naming convention. Account structure drives the statutory reports, so it is decided before any journal is configured. |
| Electronic invoicing (CPE) | Document types, series, the sending service and SUNAT acceptance. Part is localization configuration, part is integration with a provider. |
| Electronic books (PLE and SIRE) | Book formats the accountant has to file. What Odoo exports and what still needs formatting work are two different questions. |
| Detracciones | A withholding on specific services, paid into a separate account. It changes the payment flow, not just a tax rate. |
| Percepciones and retenciones | Regimes that depend on the counterparty's status, so they belong in master data rules rather than in the invoice. |
| Exchange rate | Official published rates, and which rate applies to which document date. Getting this wrong shows up at the first month-end close. |
None of these are difficult once decided. They are difficult to decide from outside the country, because the answer comes from Peruvian accounting practice rather than from documentation.
How we work inside your project
- You keep the client. We work as your Peru workstream, under your project lead and your methodology.
- Scoped as a workstream. A defined Peru deliverable inside your plan, with its own acceptance criteria.
- White label if you prefer. We can stay behind your team, or join client calls as your local specialist.
- Accounting on the call. Configuration decisions get made with an accountant present, which is the part most partners cannot staff locally.
- Confidentiality first. NDA before any access to your client's data or your repository.
Where we came from
We implemented Odoo for the first time in 2022 from inside an accounting firm, for clients whose books we closed ourselves. More than 40 companies later, Tech Jungle works as an official Odoo partner in Peru. The Peruvian tax detail is not research for us; it is what we used to be responsible for.
What you get back
A Peru scope document
Written decisions on chart of accounts, document types, tax regimes and books, in a form your client can approve and your team can build against.
Configured localization
Peruvian localization set up in your database, with the reasoning recorded so your team can maintain it after handover.
A document test set
Invoices, credit notes, withholdings and guides run end to end, through SUNAT acceptance and down to the journal entry.
Accounting validation
An accountant confirms that the entries the configuration produces are the entries a Peruvian close requires.
First close support
The month-end that follows go-live is where localization errors surface. We stay for it.
Handover notes
What was decided, what was left open, and what changes if the client adds a company or a line of business.
FAQ
Questions partners ask
Will you approach our client directly?
No. The engagement is with you, and the commercial relationship stays yours. If it helps the project, we join calls introduced as your local specialist.
Can you work in our repository and our branch strategy?
Yes. We work on Odoo.sh, on self-hosted environments and on Odoo Online within the limits of each. We follow your branching and review process rather than imposing one.
Do you cover only accounting, or the whole Peruvian scope?
Whatever the project needs: tax configuration alone, electronic invoicing end to end, or the full Peruvian scope inside a multi-country rollout. Smaller engagements are common and welcome.
What do you need to quote?
The Odoo version and hosting, which localization modules are already installed, the client's lines of business, and whether the Peruvian entity reports into a parent system. That is usually enough for a scoped estimate.
Which languages do you work in?
Spanish and English. Documentation and handover notes are delivered in whichever language your team works in.
Tell us which country broke the template
Send the Odoo version, the modules installed and the client's lines of business. We come back with a scoped Peru workstream.