Skip to Content

DUA in Invoice

by
Odoo

$ 30.01

v 19.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Invoicing (account)
• Discuss (mail)
Community Apps Dependencies
Lines of code 376
Technical Name dua_in_invoice
LicenseOPL-1
Websitehttps://www.ganemo.co
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Invoicing (account)
• Discuss (mail)
Community Apps Dependencies
Lines of code 376
Technical Name dua_in_invoice
LicenseOPL-1
Websitehttps://www.ganemo.co
Enterprise (Odoo.SH, Ganemo Online, Ganemo.SH)

DUA IN INVOICE

------

Streamline your Import Accounting in Peru

Automatically handle DUA (SAD) requirements in Purchase Invoices. Ensure 100% compliance with SUNAT PLE books without manual data entry errors.

What We're Solving

----------------

Importing goods into Peru requires distinct accounting declarations. Recording the Declaration of Customs (DUA/SAD) is mandatory for tax compliance. Standard Odoo lacks the specific fields for "Year of Emission" and "Customs Dependency" tied to the official SUNAT tables. Incorrect entries here lead to rejected Electronic Books (PLE) and potential fines. This module solves that gap instantly.

Overview

----------------

This module integrates seamlessly into your Bill processing workflow:

  • Smart Activation: Fields appear ONLY when you select Import Document types (50, 52, 53).
  • Official Data: Pre-loaded with all valid Peruvian Customs Dependency Codes (Code 118, 235, etc.).
  • Validation: Ensures data integrity before you post the entry.

Easy Setup

----------------


Plug & Play.
Install the module, and it works immediately. No complex configuration menus. It simply enhances your existing Document Types functionality.

Workflow Guide

----------------

  1. Open a Vendor Bill.
  2. Set the Document Type to "50 - Declaración Única de Aduanas".
  3. Notice the new fields "Year of Emission" and "Customs Dependency" appear automatically.
  4. Select the correct Customs Code from the dropdown list.
  5. Confirm and Post. Your data is now ready for PLE reports.

Supported Languages

----------------

This module is fully translated and supported in:

English (EN) Español (ES)

User Manual & Configuration

----------------

Installation:
This module depends on localization_menu. Ensure the Peruvian Localization is installed. Upon installation, the module automatically loads the catalog of Customs Dependency Codes (Catalog No. 11 of SUNAT PLE).

Configuration:
No manual configuration is required. The logic is hardcoded to respond to specific L10N Latam Document Types that correspond to Importations (Codes 50, 52, 53). Ensure your Document Types are correctly set up in Accounting > Configuration > Document Types.
Note: If you add custom Document Types for imports, you may need to extend the module or contact support to include them in the visibility logic.

QA / User Testing Scenarios

----------------

Use these scenarios to validate the module functionality in your environment:

Test Case 1: Standard Import Invoice (Happy Path)
  1. Create a Vendor Bill.
  2. Select Document Type: 50 - Declaración Única de Aduanas - Importación definitiva.
  3. Verify: The fields "Year of Emission" and "Customs Dependency" become visible and mandatory (visual indicator).
  4. Select "2024" and "118 - MARÍTIMA DEL CALLAO".
  5. Post the invoice.
  6. Result: Invoice posts successfully. Data is saved.
Test Case 2: Switching Document Types (Dynamic Visibility)
  1. Create a Vendor Bill with Doc Type 50. Fill in the DUA fields.
  2. Change Document Type to 01 - Factura.
  3. Verify: The DUA fields disappear instantly.
  4. Verify: The internal values for Year and Customs Dependency are cleared (to prevent pollution of database).
Test Case 3: Validation Constraints
  1. Create a Vendor Bill with Doc Type 50.
  2. Leave "Year of Emission" empty.
  3. Try to Post.
  4. Result: Odoo should raise a validation error or the field should be marked required (red underline), preventing posting.

FAQ & Troubleshooting

----------------

These fields only appear for specific Document Types (Codes 50, 52, 53). Check that you have selected one of these types in the "Document Type" (Tipo de Comprobante) field.
The module loads the standard list from SUNAT. If a new code has been created by the government recently, you can manually add it in the code.aduana model if you have permissions, or contact us to update the module.
Yes, the data structure is designed to be compatible with the standard Peruvian Localization PLE reports.

Why Choose Ganemo?

----------------

Ganemo is the #1 Odoo Partner for Localization in Latin America. With over 5 years of experience and recognition as the Best Partner in Peru, USA, Mexico, Chile, Spain, Colombia, and Ecuador, we deliver apps that are robust, compliant, and continuously updated. Trust the experts who define the standard for Odoo localization.

Support & Contact

We are here to help you succeed.

WhatsApp

Instant support

Chat with Us

Email

Detailed inquiries

Email Us

Meeting

Schedule a Demo

Book Now 
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

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.