Costa Rica invoice 4.4 changes from 1 November 2026 explained
The Ministerio de Hacienda's update to the version 4.4 annexes applies from 1 November 2026, so it is already in force as of this page. Electronic documents must now carry new reference codes that say whether a document is annulled (code 13), has its amount corrected (14), or is replaced after a material error (15). Codes 16 and 17 cover replacing a rejected document and applying a payment to a payment receipt. Legal ID fields are also being prepared for alphanumeric company cédulas. For a billing team, the job is to confirm that the billing software sends these codes correctly, to put corrections in the right tax period with the accountant, and to follow each rejection until a valid document is accepted. An AI worker can run the checks and draft the re-issue. A person still approves each corrected document.
In short
- The v4.4 annex update applies from 1 November 2026, and the version number stays at 4.4.
- Codes 13, 14 and 15 handle annulment, amount correction and replacement after a material error; code 13 pairs with code 15 in the reference.
- Codes 13 and 14 book the effect in the period of the original document, so the accountant must review period moves.
- Alphanumeric company IDs depend on a Registro Nacional date that has not been published in the sources found.
- An AI worker can check documents and track rejections, but a person approves every re-issue and the tax decisions stay with the accountant.
What changed on 1 November 2026
The Ministerio de Hacienda and its Dirección General de Tributación announced the update to the Anexos y Estructuras, the technical annex that defines fields and code lists for electronic vouchers, on 22 April 2026. The version number stays at 4.4. What changes is the catalogue of codes that the version uses. The ministry set 1 November 2026 as the date when issuing systems must carry the new codes.
The codes matter because a credit note, a correction or a replacement points back to another document. The reference code tells the tax authority what kind of correction it is. Before this update, a replacement for a document that Hacienda had rejected had no code of its own, according to a 2026 summary published by a Costa Rican billing vendor. The new codes close that gap.
The update adds or changes these codes:
- Code 13 annuls a referenced document because of a material error.
- Code 14 corrects the amount of a referenced document because of a material error.
- Code 15 replaces an electronic document because of a material error.
- Code 16 replaces a document that Hacienda rejected.
- Code 17 applies a payment to an electronic payment receipt, known as REP (Recibo Electrónico de Pago).
- Code 12 is renamed and now applies only to financial credit notes for exemptions granted after the invoice was issued.
- Codes 19 and 20 in the document-type catalogue refer to an export invoice and to a payment receipt.
A note on how to verify these codes. The ministry notice names codes 13, 14 and 15 under the Nota 9 catalogue and says they reflect the accounting effect in the period concerned. Codes 16, 17, 19 and 20 come from summaries that quote the notice. Before you configure them, open the full Anexos y Estructuras v4.4 document on the ministry's website and check the exact names and the notes under each table. Your billing software vendor should be able to show you which version of the annex it has implemented.
One pairing rule needs attention. When code 13 annuls a document and a new document must be issued, the reference section of the new document should use code 15. A KPMG Costa Rica bulletin from May 2026 describes this pairing, and the rule matters because a checker that does not know it will pass a document that the ministry may question.
Timing also matters. Codes 13 and 14 are booked in the period of the document they modify, not in the month the correction is issued. A Costa Rican billing vendor gives the example of a September correction to an August invoice, which changes August's VAT figure and leaves September alone. That is one reading of the rule. Your accountant should confirm how it applies to your returns.
Alphanumeric company IDs
The notice also changes the description of identification fields so that companies can use alphanumeric cédulas jurídicas, but only once the Registro Nacional has said so. The Registro Nacional has reported that the six-digit numeric sequence will run out, and that new companies will receive a six-character code that mixes letters and numbers. The target it has given is the fourth quarter of 2026. It has said it will announce the exact date at least two months ahead.
No exact start date appeared in the sources found for this page. The Registro Nacional has said that companies that already hold a six-digit number keep it and do not need to take any step. Practically, this means two things. First, your customer and supplier records need a field that accepts letters, and your software must be able to store and print them. Second, do not change an existing customer's ID to a letter format before the date is announced and your software vendor confirms support.
Why this problem costs money
A rejected document does not work as a tax document on its own. Costa Rican rules require an acceptance message from the ministry for an electronic document to support an IVA credit or a deductible expense. A rejected invoice that is not re-issued therefore leaves a gap in your records and in the support your accountant can use.
The main cost is staff time. Someone has to notice the rejection, read the cause, correct the data, issue a new document, tell the customer and record the outcome. If the error reached an accepted document, a correction is needed too, and that correction can move tax between periods. Each of those steps takes a person away from other work, and the work often lands at month end, when the accountant is already busy.
This guide does not give a cost range. The public sources found for this page do not publish a figure for the cost of rejections, and any percentage or amount here would be invented. The number that matters is your own. Count the rejections in a normal month, estimate the minutes each one takes from first notice to accepted re-issue, and multiply by the loaded hourly cost of the person who handles them. The free audit measures these figures from your own records.
Manual way and automated way
| Task | Manual way | Automated way with an AI worker and tools |
|---|---|---|
| Choosing the right code | Staff remember the codes or ask the accountant case by case. | A code map approved by the accountant is stored once. The worker suggests a code for each correction, and a person confirms it. |
| Checking outgoing data | Someone reads the invoice by eye, often after it has been sent. | The worker checks ID format, required fields, reference codes and amounts before signing. Anything that fails goes to a review queue. |
| Reading rejections | The portal or inbox is checked when someone remembers. | The worker collects the ministry's response for each document, sorts rejections by cause and opens a task for each one. |
| Re-issuing | The document is retyped from memory or from a PDF. | The worker drafts the corrected document from the original record. A person approves it before it goes out. |
| Telling the customer | A phone call or an email, sometimes missed. | A draft message goes by email or WhatsApp after approval, with the new document attached. |
| Keeping a record | Folders of PDFs and XML files. | A log in a spreadsheet or ERP shows status, date, code and original period for each document. |
| Period corrections | Found at month end or later. | The log flags the original period, so the accountant sees it before the return is prepared. |
The automated column describes what the system is built to do. How much of the work it removes depends on your volume and on how clean your data is, which the free audit measures.
How to automate it, step by step
Step 1: Get the code map signed off
Ask your accountant to write a short table that links each document type you issue to the codes it may need. Include the rule that code 13 pairs with code 15, and the rule for which period a correction belongs to. Keep the table in a shared spreadsheet. The worker reads from this table, so it should be short and agreed before any software is changed.
Step 2: Confirm the software version and test it
Ask your billing software vendor, in writing, which version of the annex it has implemented and whether it covers the November 2026 update, not only the base version 4.4. The ministry notice says the changes are already available in the test environment called STAG as well as in production. Send a set of test documents covering each code, and keep the accepted responses as evidence.
Step 3: Connect the data sources
Invoice data usually sits in one of three places: the billing software, an ERP such as Odoo, or spreadsheets kept by the sales or accounts team. Customer purchase orders often arrive by email as PDFs. For Odoo, a community localisation module for Costa Rica has a public pull request that adds the new reference codes, so ask your Odoo partner whether that work is in your version. Where documents are scanned, optical character recognition (OCR) can read the text, but a person should check any amount it extracts.
Step 4: Run checks before anything is signed
Start with plain rules that a person can read: the ID has the right length and format for the customer type, the reference code is allowed for that document type, the amount matches the original document, and the product codes are present. These checks should be deterministic, meaning the same input always gives the same result. A large language model can help read a free-text email and suggest which fields it contains. It should not decide whether a document is valid. The ministry's own validation decides that.
Step 5: Track every rejection
When the ministry rejects a document, its response explains the error in the XML. The worker collects these responses, groups them by cause, such as a wrong reference code or a field that does not match the schema, and opens a task with the document number and the customer. A weekly summary shows which cause appears most often, so the fix can go into the software or the code map instead of being repeated by hand.
Step 6: Prepare the re-issue and the customer message
The worker drafts the corrected document from the original record and a message to the customer that says what changed. A person checks the draft and approves it. The message can go by email or through the WhatsApp Business Platform for customers who prefer chat. Check the platform's current rules for automated messages before you set this up, because they can restrict which message types may be sent without prior customer contact.
Step 7: Track the documents you receive
Costa Rican taxpayers who receive electronic documents must also send their own acceptance or rejection message to the ministry. The deadline is set in the Dirección General de Tributación's resolution, and the sources found for this page do not agree on how it applies in every case. Check the current rule on the ministry's website. The worker can list incoming documents that still need a response and send a reminder to the person responsible.
Step 8: Reconcile with the accountant every month
At month end, export the log for accepted, rejected and re-issued documents, with the codes and the original period for each correction. The accountant uses this to prepare the return. This step is where most errors are caught, and it is also where the business keeps its evidence.
What breaks and how to prevent it
The most common failure is a mismatch between the annex and the technical schema. A developer's public report from late September 2026 said that the published schema did not yet list codes 13 to 17 in the same way as the annex. A Spanish-language technical note from earlier in the update cycle also found that the annex and the schema disagreed on the digit length of one amount field. Validators built to the old rule can reject documents that the new schema accepts. Prevention: test on STAG, keep copies of both the annex and the schema version you tested, and ask the vendor to show an accepted test document for each code.
The second failure is a wrong code pairing, for example code 13 used with no new document, or code 14 used to cancel a whole invoice. Prevention: write the pairing rules into the checker and have the accountant test each one once.
The third failure is a period error. A correction booked in the month it was issued, rather than the month of the original document, changes the wrong return. Prevention: the log must show the original period, and the accountant reviews each period move before filing.
The fourth failure is an early change to company IDs. Once the Registro Nacional announces the date, the update still needs to reach your software. Prevention: hold changes to customer records until both the date and the software update are confirmed.
The fifth failure is trust in the wrong layer. A language model may say that a document looks correct when the rules say it is not. Prevention: deterministic rules make the decision, the model only drafts, and a person approves anything that leaves the business.
When not to automate
If you issue only a few documents a month and your accountant already reviews every one, a checklist in a spreadsheet may be enough. If your billing software already applies the new codes and shows rejections on one screen, adding another layer may only add a place where data can go wrong. If nobody in the business has the time to approve corrections, do not automate the sending. Keep a person in that step.
Some questions are not technical. Whether an exemption applies, which rate is correct, or which period a correction belongs to are tax questions. The worker can point to the case and prepare the paperwork, but the accountant decides.
What automation cannot do here is also clear. It cannot make the ministry accept a document, change the rules, or tell you which period a correction belongs to without your accountant's rule. Results depend on your own volumes and data, which the free audit measures.
What it typically takes
The cost to the business is mostly time from three people: someone in billing who owns the documents, someone in accounting who owns the code map, and whoever manages the software vendor. The code map is usually a short series of working sessions. The software check and the test run depend on the vendor's response and on how many document types you issue. Connecting the data sources takes longer where invoices live in several systems, and the alphanumeric ID step waits for the Registro Nacional's date.
Plan for a period of parallel checking. In that period the worker runs alongside the current process, and a person compares the two before the worker takes over the drafting and tracking. The length depends on your volume and on how many rejections your current process already produces. Start with the rejection log, because it shows the cost of the problem before any automation is built.
This explains the rule in general terms; it is not legal or tax advice for your case.
How AiStaffo would automate this
AiStaffo would connect your billing software or ERP export, a code map that your accountant approves, and the mailbox or WhatsApp number where customers reply. The AI worker checks each outgoing document against those rules before signing, flags anything that fails and groups every ministry rejection by cause. It drafts the corrected document and the customer message from the original record. Your billing lead approves each re-issue, and your accountant reviews period moves at month end. Book a free automation audit.
Questions people ask
Is the Costa Rica electronic invoice 4.4 update already mandatory?
Which code should I use to cancel an invoice I issued by mistake?
What happens to an invoice that Hacienda rejected?
Can my company use letters in its cédula jurídica now?
Can an AI tool send my invoices to Hacienda by itself?
Do I have to respond to invoices my suppliers send me?
Book a free automation audit
Thirty minutes. We look at one process you run every week and tell you exactly what an AI worker would take off your desk, and what it would not.
