Electronic invoicing 4.4 in Costa Rica: what changes and how to prepare

Version 4.4 of the electronic receipt schema published by Costa Rica’s Ministry of Finance (Hacienda) is the most significant change to electronic invoicing since it was introduced. If your company issues electronic invoices, electronic tickets or credit and debit notes, this change directly affects the XML structure you submit.

What changes in version 4.4

The new schema introduces mandatory fields that were previously optional or did not exist:

• Discount detail: every discount applied to a line item requires a code and a nature.
• Expanded payment methods: payment types that used to be grouped generically are now explicit.
• Stricter recipient data: the recipient identification is validated against the taxpayer registry.
• New receipt types: including the electronic payment receipt.
• Additional sale conditions: for specific tax regime operations.

Deadlines and transition

Hacienda defines a coexistence period during which both versions are accepted. Migrating in stages during that window works best: start with cash invoices, then credit invoices and notes. Once the period closes, receipts using the previous schema are rejected automatically.

How to prepare

1. Audit your catalogs. The CABYS codes for your products and services must be complete and current. An incorrect CABYS code is the most frequent cause of rejection.
2. Validate your customer registry. Incomplete identifications or the wrong identification type cause recipient acceptance errors.
3. Check your digital signature. The certificate must be valid and the cryptographic key reachable from the issuing system.
4. Test against Hacienda’s staging environment before issuing in production.
5. Confirm contingency handling. If Hacienda does not respond, your system must queue and retry without losing receipts.

Common migration mistakes

The most common failure is not technical but data related: outdated catalogs, units of measure that do not match the declared CABYS code, and expired exemptions that are still being applied. Fixing these before migrating prevents most rejections.

The second frequent mistake is failing to retain signed XML files and Hacienda’s responses. Regulation requires five years of custody, and that evidence is the only defense during an audit.

Conclusion

Migrating to 4.4 is primarily a data and validation effort, not just a software change. Companies that audit their catalogs early complete the transition without interrupting invoicing.

At DYR Systems we build an electronic invoicing system that stays current with Hacienda’s active schemas, including digital signature, submission, status queries and receipt custody.