This addon stores the fiscal control number, its assignment date, and the emission medium used for Venezuelan customer documents.
The emission medium is copied from the sales journal when a document is posted, so later journal configuration changes do not alter its fiscal history. Posted customer fiscal identification is immutable; supplier document data remains correctable.
Existing posted or cancelled customer documents are also locked at installation, without attempting to infer missing historical fiscal data.
The addon does not allocate control numbers, manage paper batches, print fiscal documents, or communicate with fiscal machines or digital printers.
The legal basis covered by this addon is:
Table of contents
On each Venezuelan sales journal, select the emission medium used for customer documents: free form, contingency, fiscal machine, or digital billing. Customer documents cannot be posted until this setting is configured.
When the addon is installed, existing posted or cancelled Venezuelan customer documents are locked. Their historical fiscal data is not reconstructed.
Enter the fiscal control number and assignment date on the invoice when they are available. Integrations with fiscal machines or digital printers can write these fields while the document is still in draft.
Trusted in-process connector addons can assign control data returned after posting for digital or fiscal-machine documents with _l10n_ve_assign_control_data(control_number, control_date=None). The method is idempotent and does not expose an RPC context bypass for the fiscal lock. control_date must be a Python date-only value; datetimes, strings, and other types are rejected.
After a Venezuelan customer document is posted, it cannot be reset to draft or deleted and its fiscal identification cannot be changed. Use a credit or debit note to correct the transaction.
A fiscal machine or an authorized digital printing house connector normally only learns the control number after the document is posted and totalled. For that case, call account.move._l10n_ve_set_control_number(control_number, control_date=False) on the posted document: it is the only supported way to assign the control number once posting has locked the fiscal data, refuses to run on a document that is still a draft, and refuses to overwrite a number already assigned.
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.
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.
Current maintainer:
This module is part of the OCA/l10n-venezuela project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.