| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 185 |
| Technical Name |
invoice_type_document |
| License | OPL-1 |
| Website | https://www.ganemo.co |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 185 |
| Technical Name |
invoice_type_document |
| License | OPL-1 |
| Website | https://www.ganemo.co |
Document Types
Automatic Series & Number Propagation
Automatically copy the Official Document Type and Number (Serie-Correlativo) from Invoices to their Journal Entries and Payments. Essential for LATAM accounting compliance and traceability.
What We're Solving
----------------
Reconciliation Traceability
When you pay an invoice (e.g., F001-123), the payment entry usually lacks this reference in its accounting lines. This module automatically fills the document type and series columns in the payment journal entry, keeping perfect traceability.
Automatic Propagation
No manual input required. The system detects the reconciliation link between Payments and Invoices and instantly updates the accounting moves with the correct LATAM Document Number.
Setup & User Manual
Step-by-Step implementation
1. Configuration Guide
Follow these steps to ensure correct operation. The module relies on standard Odoo Localization configurations.
Step 1: Check Dependencies
Ensure that l10n_latam_invoice_document is installed.
This module is usually installed automatically when you select a LATAM country
package (e.g., Peru, Argentina, Chile, Colombia).
Step 2: Configure Journals
The propagation logic only activates for Journals where "Use Documents" is enabled. This is critical for determining if a transaction is an official document.
- Go to Accounting > Configuration > Journals.
- Open your Sales or Purchase journal.
- Click on the Advanced Settings tab.
- Ensure Use Documents is checked.
2. Operating Manual (Workflow)
How to verify the automatic data propagation in your daily operations.
1. Issue/Receive Invoice
Create an Invoice or Vendor Bill. It is mandatory to set the Document Type (e.g., "Factura Electrónica") and the Document Number (e.g., "F001-000045"). Post the document.
2. Register Payment
Use the standard "Register Payment" wizard or reconcile via Bank Statement. The method does not matter; as long as a reconciliation is created, the data will flow.
3. Verification (Result)
Navigate to the Journal Entry generated by the payment. In the Journal Items tab, verify the columns:
- Document Type: Matches the invoice type.
- Series-Correlative: Matches the invoice number (spaces removed).
This ensures that your General Ledger and auxiliary reports show the official document reference instead of just the internal system payment ID.
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: Customer Invoice Workflow
- Pre-condition: Ensure Sales Journal has "Use Documents" active.
- Create a Customer Invoice. Set Type to "Factura" and Number to "F001-001". Post it.
- Register a full payment using Bank Journal.
- Validation: Open the Payment's Journal Entry. Check the Journal
Items.
- Expected: "Document Type" = Factura.
- Expected: "Serie-Correlativo" = F001-001.
Scenario 2: Vendor Bill Logic (Space Sanitization)
- Create a Vendor Bill.
- Manually type " F001 - 12345 " (with spaces) in the Document Number field.
- Post and Pay the Bill.
- Validation: Check the Payment Entry lines.
- Expected: "Serie-Correlativo" must be "F001-12345" (Spaces removed automatically).
Scenario 3: Credit Notes / Refunds
Goal: Verify that refunds also carry the document reference.
- Create a Customer Invoice "F001-500". Post it.
- Click "Add Credit Note". Post the Credit Note "NC01-20".
- The system automatically reconciles them.
- Validation: Check the "Reversal Entry" or the reconciliation lines. The Credit Note lines should ultimately reference the document they belong to (or their own document number depending on localization rules). This module ensures the propagated field exists on the move lines.
Scenario 4: Partial Payments
- Create Invoice "F001-999" for $1000.
- Register a specific payment of $400 (Partial).
- Validation: The Journal Entry for the $400 payment MUST have "F001-999" in its lines.
- Register the remaining $600.
- Validation: The second payment entry MUST also have "F001-999".
FAQ & Troubleshooting
Common Resolutions
Data is missing in Payment Entry?
Check 1: Does the paid Invoice have a Document Type and Number set?
Check 2: Is "Use Documents" enabled on the Journal used for the invoice?
Does it work with Historical Data?
The module acts on the reconciliation event. If you have old open invoices and you pay them now after installing the module, the data WILL be propagated correctly. It does not retroactively update payments made before installation.
Does it support POS?
This module is designed for Accounting Invoices/Bills. Point of Sale (POS) transactions often follow a different flow (Session Closing entries). While POS Invoices are supported if they go through the standard Account Move model, aggregate session entries are not the primary target.
Why are spaces removed?
To ensure data consistency and matching. "F001 - 123" and "F001-123" might look similar but are different strings to a computer. We sanitize inputs to avoid matching errors in external systems or reports.
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