| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 376 |
| Technical Name |
dua_in_invoice |
| License | OPL-1 |
| Website | https://www.ganemo.co |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 376 |
| Technical Name |
dua_in_invoice |
| License | OPL-1 |
| Website | https://www.ganemo.co |
DUA in Invoice
PLE Compliance for Imports
Complete your Purchase Electronic Record (PLE) in Peru by correctly registering Customs Declarations (DUA/DSI).
What We're Solving
----------------
Missing Legal Fields
Odoo's standard localization often misses the specific fields required for Doc Type 50 (DUA). This module adds "Year of Emission" and "Customs Dependency" to ensure valid tax reporting.
Smart Visibility
The fields only appear when you select Import Document Types (50, 52, 53). For regular local invoices, these fields utilize auto-hide to keep your interface clean.
Setup & User Manual
Step-by-Step implementation
1. Configuration Guide
System readiness in seconds.
System Dependencies
- This module relies on l10n_pe_localization_menu.
- Zero Manual Config: All Customs Codes (Dependencies) are pre-loaded automatically.
Verification
- Go to Accounting / Accounting / Localization / Customs Codes.
- Verify that the list is populated (e.g., 118, 235).
- If empty, upgrade the `l10n_pe_localization_menu` module.
2. Operating Manual (Workflow)
Correctly registering an Import (DUA/DSI) for PLE:
1. Create the Vendor Bill
Navigate to Accounting / Vendors / Bills and click New. Select your international vendor.
2. Select Document Type
In the "Document Type" field, select 50 - Declaracion Aduanera de Mercancias - Importacion Definitiva (or 52/53). This action triggers the fields to appear.
3. Set Emission Year
Locate the new Year of Emission field (usually below the Date). Select the year corresponding to the DUA issuance (e.g., 2024).
4. Set Customs Dependency
In the Customs Dependency field, search for the Customs Office code/name (e.g., "118 - MARITIMA DEL CALLAO").
Result: PLE Compliance
When you generate the PLE 8.1 (Purchase Register), the system will concatenate these fields into the Series/Number formats required by SUNAT (e.g., `118-2024-001234`).
Global Ready | Multi-Language Support
This module is fully translated into English and Spanish (en_US, es_ES, es_PE, es_MX), ensuring a professional experience for international organizations.
Why Choose Ganemo?
----------------
Ganemo is the world's leading Odoo App developer and a multi-award-winning Gold Partner. For over 5 years, we have been recognized as the #1 seller of high-quality apps on the Odoo App Store. Trusted as the "Best Partner" in USA, Mexico, Chile, Spain, Colombia, Ecuador, and Peru, we deliver robust, secure, and localization-compliant solutions for global businesses.
Get a Quote & Resolve Commercial Doubts
Join thousands of satisfied clients on Odoo. Contact our sales team directly.
Official WhatsApp
Fastest response time.
LINK
+1 (828) 672-6150
Book a Demo
Let's explore your needs.
LINK
Schedule Meeting
Need More? We Do It All
Professional Odoo Services
ERP Implementation
Transform your business with a full Odoo implementation. We analyze, configure, and train your team to maximize productivity. From Accounting to Inventory, we handle the complexity so you can focus on growth.
Module Dev & Migration
Need a custom feature? Or stuck on an older version? We develop high-performance custom modules and migrate your existing code to Odoo 19 with zero data loss. Expert developers at your service.
QA / User Testing Scenarios
Enterprise Validation Plan
Scenario 1: Field Visibility & Logic
- Create a Vendor Bill.
- Select Doc Type 50 (Declaracion Aduanera).
- Check: "Year of Emission" and "Customs Dependency" fields MUST appear.
- Change Doc Type to 01 (Factura).
- Check: The fields MUST disappear instantly.
- Change Doc Type back to 52 (Simplificada).
- Check: The fields MUST reappear.
Scenario 2: Validation Enforced
- Set Doc Type to 50.
- Fill in the Invoice Number and Date.
- Leave "Year of Emission" empty.
- Click Save.
- Result: Odoo MUST block the save and show a validation error for the missing required field.
Scenario 3: Data Persistence
- Create and Save a DUA (Doc 50) with Year "2024" and Code "118".
- Navigate back to the Tree View (List).
- Re-open the record.
- Result: The fields must retain the values "2024" and "118". They should not be lost.
Scenario 4: Credit Note Warning
Goal: Ensure logic holds for Refunds.
- Create a Credit Note (Refund).
- Select Doc Type 50 (Unlikely, but testing edge case) or related correction type.
- Result: If the Doc Type involves Customs, the fields should behave identically to the Invoice.
FAQ & Troubleshooting
Common Resolutions
Where do I find the Customs Code?
Answer: The codes (e.g., 118, 235) are pre-loaded based on the official SUNAT catalog via the dependency module.
Tip: If the
list is empty, ensure l10n_pe_localization_menu is installed and updated.
Why can't I see the fields?
Answer: The fields are dynamically hidden. They only activate for Import Document Types.
Fix: Ensure the L10N LATAM Document Type is set to 50, 52, or 53.
Does this affect PLE Reports?
Answer: Yes. The data entered here is what fuels columns 11, 12, and 13 of the PLE 8.1 Register.
Note: Without these fields, your PLE 8.1 will likely be rejected by SUNAT for imports.
I made a mistake in the Year, can I fix it?
Answer: Yes, as long as the invoice is in Draft state.
Fix: Reset to Draft, correct the Year/Code, and Post again.
Commercial & Sales
For inquiries about licenses, demos, or partnerships.
Official WhatsApp
Fastest response time.
LINK
+1 (828) 672-6150
Book a Demo
Let's explore your needs.
LINK
Technical Support
Existing customers regarding module functionality.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module