Tech Jungle · Peru
Odoo and SUNAT: Peruvian localization implemented correctly
Understand Peruvian electronic invoicing, accounting localization, SUNAT workflows and the implementation decisions foreign companies need to make.
Standard, configuration or development
The most expensive assumption in a Peruvian implementation is that "Odoo is already localized", and then discovering the gaps during the first invoicing run. This is the split we work with.
| Requirement | Where it is solved |
|---|---|
| Chart of accounts and base taxes | Standard localization, with a review of accounts and tax bases |
| Document types and series | Configuration, by establishment and issuing point |
| Electronic document transmission (CPE) | Integration with the issuing service the company uses |
| Electronic dispatch guides (GRE) | Configuration and integration, depending on transport mode |
| Detracciones (SPOT), withholdings, perceptions | Tax and document configuration, with rules per operation type |
| Sales and purchase records for SIRE | Generated from Odoo; format work may require development |
| Company-specific controls | Development, when the control does not exist in the standard |
Decisions before the first document is issued
- Establishments and series: which issuing point each document uses, and how it is numbered.
- Operation types: taxable, exempt, non-taxable, export, non-domiciled.
- Detracciones: which operations trigger the deposit, how it is recorded and reconciled.
- Credit and debit notes: reasons and their accounting effect.
- Dispatch guides: who transports, what data is required, when the document is issued.
- Contingency: what happens when the transmission service is unavailable.
| Document | Amount | SUNAT |
|---|---|---|
| F001-004182Taxable invoice | S/ 14 160.00 | Accepted |
| F001-004183Invoice with detracción | S/ 41 300.00 | Accepted |
| B001-009034Sales receipt | S/ 236.00 | Accepted |
| FC01-000117Credit note | S/ 1 180.00 | In process |
| F001-004184Export | USD 8 400.00 | Rejected |
SIRE and electronic books
SIRE is progressively replacing PLE for sales and purchase records, with SUNAT generating proposals from issued and received documents. In practice the accounting work changes: instead of building the record, the company compares it against what the tax authority already holds and explains the differences.
What we prepare in Odoo is the ability to make that comparison: correctly typed documents, correct dates, a consistent exchange rate, and flagged documents identifiable before filing rather than after.
Rollout schedules and formats are set by SUNAT and updated periodically. Any scope is confirmed against the regulation in force at the time of the project.
FAQ
Odoo and SUNAT: common questions
Does Odoo issue valid Peruvian electronic documents?
Issuing requires a service that transmits documents to SUNAT and manages responses. Odoo produces the document and the integration handles transmission and status. Defining that component is part of scope and is quoted explicitly.
What about electronic dispatch guides?
They are configured according to transport mode and required data. The logistics process should be reviewed first, because the moment of issue differs for own versus third-party transport.
Is SIRE generated from Odoo?
Odoo provides the sales and purchase information that feeds the record. Depending on version and scope, part of the format may need adjustment or development.
How are detracciones handled?
As part of the payment cycle, with the account and document that allow the deposit certificate to be reconciled against the supplier payment and the detracciones account.
Do we have to change our invoicing provider?
Not necessarily. We review the service already in use and assess whether integration is viable before proposing a change.
Let us review your localization before the next close
Series, taxes, detracciones and records reviewed so manual adjustments stop being monthly routine.