| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4437 |
| Technical Name |
l10n_cr_hacienda_rep |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
| Versions | 18.0 19.0 |
Costa Rica REP v4.4
Recibo Electronico de Pago for collected credit invoices — Clave, MedioPago allocation, InformacionReferencia, QR and BYOK clearance to Hacienda
Under the Ministerio de Hacienda de Costa Rica v4.4 schema (mandatory since 1 September 2025, feeding the TRIBU-CR platform), when a credit comprobante is collected the seller must issue a Recibo Electronico de Pago (REP, tipoDoc 08) that evidences the collection and declares the means of payment actually received. This module automates that obligation directly from Odoo's payment register, building on the Costa Rica Hacienda v4.4 connector and the shared e-Invoice Core Engine. Compatible with Odoo 18 and Odoo 19.
REP on Every Collection
Each reconciled payment against a posted credit customer invoice produces its own Recibo Electronico de Pago (tipoDoc 08) in the exact element order of the Hacienda v4.4 XSD sequence, referencing the original FE/TE document.
Real MedioPago Allocation
The Odoo payment journal and method — cash, card, cheque, bank transfer, SINPE Movil, digital platform — are mapped to the Hacienda MedioPago code and the collected amount is split across the declared means so the REP totals reconcile to the cash actually received.
InformacionReferencia
Every REP references the original invoice Clave, emission date and a collection reason, exactly as mandated for tipoDoc 08, so Hacienda can link the payment receipt to the credit comprobante.
Independent Numbering
A dedicated tipoDoc-08 running number feeds the 20-digit consecutivo and the 50-digit Clave, kept separate from the invoice numbering and reusing the proven Clave generator.
Pre-flight Validation
A REP rule set — Clave, consecutivo (tipoDoc 08), reference presence, valid means of payment, payment coherence and collected-amount coherence — is checked on the shared engine validation framework before any document is built or transmitted.
Verification QR
Each REP carries a QR linking to the Hacienda comprobante consultation page keyed by the 50-digit Clave, rendered through the shared QR engine.
BYOK Clearance
The signed REP is transmitted through the same Hacienda recepcion API client and credentials the v4.4 connector configures. Your certificate, private key and Hacienda password never leave your database, and the official sandbox / production endpoints ship as editable defaults.
Automatic or Manual
Enable automatic REP issuance on collection, optionally auto-submitting to Hacienda, or use the manual registration wizard for mixed and out-of-band collections. A status-polling cron tracks the clearance response.
Requirements
Requires the Costa Rica Hacienda 4.4 connector
(l10n_cr_hacienda_v44_einvoice) and the
e-Invoice Core Engine, which provide the company
identification, the cedula matrix, the v4.4 XML generator and the
Hacienda API configuration this module builds upon.
Disclosure: this module transmits REP data only to the Hacienda recepcion endpoint you configure. No data is sent anywhere else, and your credentials and certificate / private key never leave your database.
Screenshots
Generated Rep Tipodoc 08 For
Source Credit Factura Electr
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4437 |
| Technical Name |
l10n_cr_hacienda_rep |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
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