| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Expenses (hr_expense)
• Invoicing (account) • Discuss (mail) • Employees (hr) |
| Community Apps Dependencies | Show |
| Lines of code | 600 |
| Technical Name |
l10n_latam_expense_invoice |
| License | OPL-1 |
| Website | https://www.ganemo.co |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Expenses (hr_expense)
• Invoicing (account) • Discuss (mail) • Employees (hr) |
| Community Apps Dependencies | Show |
| Lines of code | 600 |
| Technical Name |
l10n_latam_expense_invoice |
| License | OPL-1 |
| Website | https://www.ganemo.co |
LatAm Expense Automation
Native Integration & Automated Vendor Bills
Bridge module to reliably map Latin American document layouts & types across HR Expenses and vendor bills instantly. Make tax reports a breeze.
What We're Solving
----------------
LatAm Document Types on Expenses
Easily assign legal document types and reference numbers directly when creating an employee expense. Supports filtering the exact allowed documents your workers can submit.
Automated Vendor Bill Propagation
When the expense is reconciled or approved, the document type and legal code are automatically transferred to the newly generated vendor bill, making fiscal reporting accurate instantly.
Setup & User Manual
Step-by-Step implementation
1. Configuration
Prepare the system for tracking LatAm taxes with these detailed steps. Proper configuration ensures your company complies with local tax authority requirements.
-
Step 1 Access Settings
Navigate to Accounting > Configuration > Settings. Scroll down until you find the Expenses section. Ensure your user has 'Billing Administrator' or 'Advisor' access rights.
-
Step 2 Define Allowed Document Types
Locate the field Allowed Document Types. Select the specific legal document types (e.g., Factura, Boleta, Ticket de Gasto) that your employees are allowed to submit. This filters the selection list in the expense form to prevent errors.
-
Step 3 Enforce Strict Compliance
Enable the Force LatAm Document Type checkbox. When this is active, the system will block any expense submission that is missing a document type or document number, guaranteeing 100% fiscal compliance before the expense even reaches accounting.
2. Operating Manual (Workflow)
Experience a seamless end-to-end process from the employee's mobile to the accountant's ledger.
Phase 1: Employee Submission
When an employee records an expense (e.g., a taxi receipt or a lunch bill), they navigate to the Expenses app and create a new record. A new section appears in the form for LatAm Document. The employee must select the `Document Type` (filtered by the accounting rules) and type the official `Document Number` as printed on the physical or electronic receipt. If the company enforces strict compliance, attempting to save without these fields will trigger a friendly validation error.
Phase 2: Manager & HR Approval
The employee submits the expense in an Expense Report. The manager reviews the amounts and business justification. The HR or Accounting team can inspect the `Document Type` and `Document Number` columns within the report lines directly, ensuring the digital entry matches the attached receipt image before clicking Approve.
Phase 3: Automated Vendor Bill Mapping
Upon clicking Post Journal Entries (or when the system automatically books the expense), Odoo core generates a Vendor Bill in Accounting. Our automation intervenes invisibly at this exact moment:
It reads the LatAm Document Type and Document Number from each expense line and injects them natively into the Vendor Bill's standard LatAm fields. The accountant receives a fully compliant Vendor Bill ready for tax reporting, without ever doing double data-entry.
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: LatAm Document Propagated Correctly
- Enable Force Document Type constraint in Settings.
- Create an expense and deliberately fill no Document Type nor Number. Saving gives a clean validation alert ensuring compliance.
- Fill with a valid LatAm Document Type and a Document Number, then post the expense.
- Result: Navigate to the associated Vendor Bill — it seamlessly possesses exactly the Document Type and Number matching your LatAm inputs from context.
Scenario 2: Strict Compliance Enforcement
- In Accounting Settings, enable the "Force LatAm Document Type" option.
- Create a new Employee Expense.
- Fill out all standard fields (product, amount, date) but leave the "LatAm Document Type" and "LatAm Document Number" fields deliberately empty.
- Attempt to save the record.
- Result: A validation error explicitly blocks the save, prompting the user to complete the mandatory fiscal document information.
Scenario 3: Multi-Company Independent Configuration
- Log in to an environment with at least two companies (Company A and Company B).
- In Company A Settings, set the Allowed Document Types to [Factura, Boleta] and enable Force Document Type.
- Switch to Company B, set the Allowed Document Types to [Ticket] only, and disable Force Document Type.
- Create an expense under Company A; verify that only Factura and Boleta can be selected and the fields are mandatory.
- Create an expense under Company B; verify that only Ticket can be selected and the fields are optional.
- Result: The module correctly honors the multi-company context without cross-contamination.
FAQ & Troubleshooting
Common Resolutions
Missing available Document Types?
Reason: Allowed list relies on what types you manually select from settings.
Fix: Contact the admin to allow more types for your company via Accounting > Configuration > Settings.
Is this compatible with Multi-company?
Answer: Yes!
Detail: Configuration dictates allowed types context-effectively for each independent setup.
Can I change the LatAm Document Type after posting?
Answer: No, for accounting compliance reasons.
Detail: Once an expense generates a vendor bill, the accounting record must not be tampered with. To fix mistakes, cancel the entry and recreate.
Does it affect previously created expenses?
Answer: No, historical expenses remain unchanged.
Detail: The module's mapping logic exclusively triggers on newly generated vendor bills.
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.
Help Desk
Exclusive channel for technical assistance and bug reports.
Replies within 48h for active subscriptions.
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