A business issuing electronic documents in Costa Rica during 2026 should already be using version 4.4. Hacienda made that version mandatory on September 1, 2025, after a transition period in which version 4.3 was also accepted. The migration deadline has passed. The useful question now is whether the company's data, catalogs and daily procedures were adjusted properly.
A document accepted by Hacienda's validation platform can still expose an operating problem later. The payment method may be wrong, a CABYS code may be outdated, a foreign-currency invoice may carry the wrong exchange rate, or a credit note may lack a clear reference. A sound review follows the complete path from the item catalog to the files delivered to the customer. Merely checking that an XML was transmitted is not enough.
What version 4.4 introduced
The update was more than a new version number. Materials published by Costa Rica's tax authority describe changes to header data, product and service details, taxes, exemptions, payment methods, currency and reference information. They also include fields for specific situations involving non-domiciled parties, non-nationalized goods, medicines, vehicles and certain taxes assumed by the issuer. Most businesses will use only a portion of those fields. The work lies in identifying the ones that actually describe their transactions.
- Payment methods include specific options for SINPE Móvil and digital platforms.
- A document can show the amount paid through each method when the customer combines methods.
- Currency and exchange-rate rules are explicit; US dollar documents use the BCCR selling rate as their reference.
- Credit and debit notes require reference information when they modify an electronic document.
- Transactions that are exempt, not subject to IVA or covered by an exemption need more precise codes than a generic label.
Start the review in the catalog
The worst time to discover bad setup data is while a customer waits for an invoice. Review the products and services that appear most often: commercial description, unit of measure, CABYS code, IVA rate, price and currency. If an item receives different treatment for a certain customer or exemption, decide who confirms that condition and which document supports it. Software can validate a format. It cannot infer the tax facts behind a sale.
Test the less routine cases as well. Create a controlled example for a credit sale, a payment split between card and SINPE, a US dollar invoice, a discount and a partial credit note. Those scenarios tend to reveal incomplete settings. A short test before the next busy billing day is much cheaper than correcting a chain of documents that customers have already received.
A practical 2026 checklist
- Confirm that your provider generates XML documents using the 4.4 structure.
- Review whether each product or service uses a current CABYS code that describes the actual sale.
- Test invoices in colones and dollars, including the currency code and exchange rate.
- Check the payment methods your business uses, especially combined payments and SINPE Móvil.
- Generate a test credit note and verify that it points to the original document.
- Download the XML, PDF representation and Hacienda response, then keep them with the transaction.
- Review which team members can issue or change documents.
Where Tario fits
Tario connects an invoice to the customer, line items, taxes, payments and accounting records. The practical benefit appears after issuance. The balance remains visible in accounts receivable, partial payments reduce the amount outstanding, and approved documents feed reports and IVA working data. The electronic invoice does not have to sit alone in a folder while someone types its information into another spreadsheet.
Initial setup still deserves care. Economic activities, numbering, certificates, currencies, catalog items and tax treatment should be reviewed before automation becomes routine. If a rate or exemption depends on facts unique to a transaction, confirm it with a Costa Rican accountant or tax adviser before turning it into a permanent system rule.