> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents/costa-rica.md). # Costa Rica The older documentation names Costa Rica, but no matching classification or configuration entry was found in the inspected development catalogue. Use this guide to identify the configured family and version scope before testing a source file. [All countries and support scope](/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents.md) ## Country explainer Localized narration and WebVTT captions explain format selection, configuration and acceptance checks. This read-only walkthrough shows the country’s existing DocBits configuration. Check the effective source and active version, then validate representative invoices, credit notes and exports in your own organisation. {% embed url="" %} [Costa Rica — Country explainer](https://docbits-videos.fra1.cdn.digitaloceanspaces.com/settings-assistant/edocs_country_costa_rica/v2/en.mp4) [WebVTT](https://docbits-videos.fra1.cdn.digitaloceanspaces.com/settings-assistant/edocs_country_costa_rica/v2/en.vtt) ## Variants and version limits The older documentation names Costa Rica, but no matching classification or configuration entry was found in the inspected development catalogue. **Syntax:** Not confirmed Current built-in processing is not confirmed by this check. Ask support to verify the deployed mapping and test a representative source file before rollout. The tables record a development-catalogue check on 17 October 2026 and the corresponding processing code. They describe available rules and configuration components, not a certification of every file, legal requirement or production rollout. Your organization can override the defaults. ## Inspected rule and component matrix No matching classification or configuration entry was found. Current built-in support is not confirmed by this check. ## Find the mapping in DocBits
Costa Rica: Not confirmed

Real development UI: searching this country name returned no matching configuration entry in the inspected catalogue.

## Acceptance checks A component check confirms configuration presence. It is not an end-to-end processing test for every version. Test the exact payload and the invoice or credit-note path required by your integration. ## Check a format in your organization 1. Keep the original XML or the PDF with its embedded XML. Read the namespace, schema or customization identifier and the declared version/profile. 2. Open Settings → Document Types → E-Doc for the applicable business document. Search for the exact electronic-document format shown in the guide. 3. Check the effective Default or Custom source and its active configuration version. Inspect Transformation, Preview and Extraction Paths. Saving a draft does not activate it. 4. Test representative source files for each syntax, version and business document you need. Verify key fields, amounts, tax, invoice/credit-note classification and the ERP export. 5. Confirm validation policy and transport separately. Preserve custom mappings and check approvals and export history before restarting existing documents. ## Related format reference * [🇨🇷 COSTA RICA](/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents/costa-rica-1.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents/costa-rica.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.