Accounting extensions for Paraguay localization
Project description
Paraguay - Accounting Extensions
Paraguay - Accounting Extensions
This module extends the base Paraguayan accounting localization with specific functionality required for Paraguayan fiscal compliance.
Features
Journal Extensions: Enhanced journal configuration with Paraguayan-specific fields
Establishment (punto de expedición)
Point of Sale (punto de emisión)
Timbrado (tax stamp authorization)
Authorization Management: Complete timbrado lifecycle management
Authorization number tracking
Validity period control
Document number range management
Automatic sequence generation
Account Move Extensions: Enhanced invoice/bill features
Automatic timbrado assignment
Document number formatting
Fiscal validations
Fiscal Validations:
Valid timbrado verification
Document number range validation
Expiration date checking
Purpose
This module bridges the gap between Odoo’s standard accounting and Paraguayan fiscal requirements, particularly focusing on timbrado management which is mandatory for all fiscal documents in Paraguay.
Dependencies
account: Odoo core accounting
l10n_py_base: Base Paraguayan localization
Table of contents
Installation
Installation
Prerequisites
Odoo 16.0
account module (core Odoo)
l10n_py_base module installed
Valid timbrado from SET (for production use)
Installation Steps
Install Base Module: Ensure l10n_py_base is installed first
Install Module:
Go to Apps
Click Update Apps List
Search for “Paraguay - Accounting Extensions”
Click Install
Verify Installation: Check that new menus appear:
Accounting > Configuration > Timbrados
Enhanced journal configuration options
Post-Installation Setup
Step 1: Configure Company
Ensure company fiscal data is complete in l10n_py_base
Step 2: Create First Timbrado
Go to Accounting > Configuration > Timbrados
Click Create
Enter your SET-provided authorization:
Authorization number
Validity dates
Document number range
Establishment and point of sale codes
Step 3: Configure Sales Journal
Go to Accounting > Configuration > Journals
Edit your sales journal
Set:
Establishment code
Point of sale code
Link to timbrado
Save
Step 4: Test Invoice Creation
Create a test invoice
Verify document number format: XXX-XXX-NNNNNNN
Check timbrado information appears correctly
Cancel test invoice if in production
Demo Data
The module includes demo data:
Sample timbrados
Configured journals
Note: Delete demo data before using in production:
Go to Settings > Technical > Database Structure > Demo Data
Remove demo timbrados and journal configurations
Configuration Checklist
Before going live:
☐ Company fiscal data complete
☐ Valid timbrado from SET
☐ Timbrado record created in system
☐ Sales journals configured
☐ Purchase journals configured (if needed)
☐ Document number sequences tested
☐ User permissions configured
Required Information from SET
Before you can use this module in production, obtain from SET:
Timbrado Number: Authorization number
Validity Period: Start and end dates
Document Range: From/to numbers authorized
Establishment Code: Your establishment code
Point of Sale Code: Your point of emission code
Dependencies
This module requires:
account: Core accounting functionality
l10n_py_base: Paraguayan base localization
Optional Modules
For complete functionality, consider:
l10n_py: Paraguayan chart of accounts
l10n_py_edi_base: Electronic invoicing
Troubleshooting Installation
Timbrado Fields Not in Journal
If timbrado fields don’t appear in journals:
Update module
Restart Odoo server
Clear browser cache
Configuration
Configuration
Journal Configuration
Configure journals for Paraguayan fiscal documents:
Navigate to Accounting > Configuration > Journals
Select or create a sales/purchase journal
Configure Paraguayan fields:
Establishment (Punto de Expedición): e.g., “001”
Point of Sale (Punto de Emisión): e.g., “001”
Link to active Timbrado
Document Number Sequences
The module automatically manages sequences:
Sequences are created based on timbrado configuration
Format: XXX-XXX-NNNNNNN (Establishment-Point of Sale-Number)
Numbers increment automatically
System warns when approaching limit
Automatic Validations
The system validates:
Timbrado is active and not expired
Document numbers are within authorized range
Establishment and point of sale match
Date is within authorization period
Multiple Timbrados
You can have multiple timbrados:
Different establishments
Different points of sale
Overlapping periods (for transition)
Best practice:
Create new timbrado before current one expires
Activate new timbrado when ready
Old timbrado becomes inactive automatically
Usage
Usage
Creating Invoices with Timbrado
Standard Invoice Flow
Go to Accounting > Customers > Invoices
Click Create
Select customer and add invoice lines
The system automatically:
Assigns the active timbrado from the journal
Generates the next document number
Validates timbrado status
Click Confirm
Invoice Number Format
Invoices will have the format:
XXX-XXX-NNNNNNN
XXX: Establishment (e.g., 001)
XXX: Point of Sale (e.g., 001)
NNNNNNN: Sequential number (e.g., 0000001)
Example: 001-001-0000123
Managing Timbrados
Checking Timbrado Status
Go to Accounting > Configuration > Timbrados
View list of all timbrados
Status indicators show:
Active: Green (currently valid and in range)
Expired: Red (past end date)
Exhausted: Orange (all numbers used)
When Timbrado is Expiring
The system will warn you when:
End date is approaching (configurable threshold)
Document numbers are running low (e.g., <100 remaining)
Action required:
Request new timbrado from SET
Create new timbrado record in system
Update journal to use new timbrado when ready
Switching Between Timbrados
To change timbrado on a journal:
Go to Accounting > Configuration > Journals
Edit the journal
Change the Timbrado field
Save
New documents will use the new timbrado
Vendor Bills
For vendor bills:
Create bill as usual
Enter vendor’s timbrado information if required
System validates format and structure
Reports and Monitoring
Timbrado Usage Report
Monitor timbrado usage:
Go to Accounting > Reporting > Timbrado Report
View:
Numbers used
Numbers remaining
Expiration status
Document count
Fiscal Period Closing
When closing fiscal periods:
Verify all timbrados for the period are valid
Check document number sequences are complete
Generate required fiscal reports
Common Scenarios
Scenario 1: Starting a New Establishment
Create new timbrado with new establishment code
Create or update journal with new establishment
Link timbrado to journal
Start issuing documents
Scenario 2: Renewing Expired Timbrado
Obtain new authorization from SET
Create new timbrado record
Set start date (can overlap with old one)
Switch journal to new timbrado
Old timbrado remains for historical reference
Scenario 3: Multiple Points of Sale
Create timbrado for each point of sale
Create separate journal for each
Each journal uses its own timbrado
Users select appropriate journal when creating documents
Troubleshooting
Error: “Timbrado Expired”
Solution:
Create new timbrado
Update journal configuration
Try creating document again
Error: “Document Number Out of Range”
Solution:
Request new timbrado from SET with higher range
Create new timbrado record
Switch journal to new timbrado
Warning: “Timbrado Expiring Soon”
Action:
Request renewal from SET
Create new timbrado in system
Plan transition date
Update journal when ready
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
This module is part of the OCA/l10n-paraguay project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distributions
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file odoo_addon_l10n_py_account-16.0.2.0.0-py3-none-any.whl.
File metadata
- Download URL: odoo_addon_l10n_py_account-16.0.2.0.0-py3-none-any.whl
- Upload date:
- Size: 52.5 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.12.3
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
ef3229fa9f3b2c8c6d0f967863f93b9a0babfee457bb41d308f07f49445e84ca
|
|
| MD5 |
eff629d9dab7bfc3e729060253c9a886
|
|
| BLAKE2b-256 |
b7071931c2ab7ef6fac2e13fad182ffc3602331cbadc1c57077d9778ee4bd771
|