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

Version 4.4 of the electronic receipt schema from Costa Rica’s Ministry of Finance (Hacienda) changed the XML structure your company submits. It is not a cosmetic tweak: it adds mandatory fields, validates data that used to pass unchecked and returns whatever fails. If you issue invoices, tickets or credit and debit notes, the new schema affects you from the first line.

What changes in version 4.4

The changes that affect daily work the most:

• Discount detail. Every discount applied to a line item requires a code and a nature.
• Expanded payment methods. They are no longer grouped generically; the schema has explicit types.
• 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. Finish the migration inside that window: once it closes, receipts on the old schema are rejected automatically.

Migrating in stages reduces risk. Start with cash invoices, then credit invoices, then notes. If something goes wrong, the problem stays limited to one document type.

How to prepare

1. Audit your catalogs. The CABYS codes for your products and services must be complete and current. If you sell consulting, the code for a service cannot be a product code. 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

What usually fails is old data, not the code: 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. If a receipt is already being rejected, why Hacienda rejects an invoice walks through the most common causes and how to correct them.

The other 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 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.