> 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/brazil-cte.md).

# BRAZIL CT-E

BRAZIL CT-E electronic document support in DocBits

{% hint style="info" %}
Check the country guide for version limits, effective configuration and the country explainer. [Brazil](/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents/brazil.md). These are different document families. A configured NFS-e version does not certify every municipal schema or every national service-invoice layout.
{% endhint %}

| Property             | Value                                                     |
| -------------------- | --------------------------------------------------------- |
| **Country / Region** | Brazil                                                    |
| **Document Types**   | Transport Invoice (Conhecimento de Transporte Eletrônico) |
| **Format**           | XML                                                       |
| **Standard**         | CT-e 3.0 (electronic freight/transport bill of lading)    |
| **Locale**           | `pt_BR`                                                   |

CT-e (Conhecimento de Transporte Eletrônico, `<mod>57</mod>`) is the Brazilian electronic transport document issued by logistics and freight companies. It documents the transport service, cargo value, origin and destination municipalities (`cMunIni` / `cMunFim`), and the freight price (`vTPrest`). Unlike NF-e, CT-e uses `cteProc` as root element and references linked NF-e documents.

## Support Status

| Component        | Status      |
| ---------------- | ----------- |
| Preview          | ✅ Supported |
| Field Extraction | ✅ Supported |
| Transformation   | ✅ Supported |

## Default Preview

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-80be78a911c194b95b41fdf9674e453b51077239%2Fbrazil-cte-preview.png?alt=media" alt="Brazil CT-e preview in DocBits"><figcaption><p>Default DocBits preview for a BRAZIL CT-E document</p></figcaption></figure>

## Field Mapping

### Header Fields

| DocBits Field   | Source XPath                                           | Notes                         |
| --------------- | ------------------------------------------------------ | ----------------------------- |
| `invoice_id`    | `//*[local-name()='ide']/*[local-name()='nCT']`        | CT-e number                   |
| `invoice_date`  | `//*[local-name()='ide']/*[local-name()='dhEmi']`      | ISO 8601 with BRT offset      |
| `currency`      | Fixed: `BRL`                                           | Always Brazilian Real         |
| `total_amount`  | `//*[local-name()='vPrest']/*[local-name()='vTPrest']` | Total freight service value   |
| `net_amount`    | `//*[local-name()='vPrest']/*[local-name()='vRec']`    | Amount to be received         |
| `tax_amount`    | `//*[local-name()='ICMS']//*[local-name()='vICMS']`    | ICMS on transport service     |
| `supplier_name` | `//*[local-name()='emit']/*[local-name()='xNome']`     | Carrier (transportadora) name |
| `supplier_id`   | `//*[local-name()='emit']/*[local-name()='CNPJ']`      | Carrier CNPJ                  |
| `buyer_name`    | `//*[local-name()='dest']/*[local-name()='xNome']`     | Consignee (destinatário) name |
| `buyer_id`      | `//*[local-name()='dest']/*[local-name()='CNPJ']`      | Consignee CNPJ                |

> CT-e does not include a line item table — the transport service is a single document-level charge.

## Classification Rule

DocBits detects BRAZIL CT-E documents via:

```
http://www.portalfiscal.inf.br/cte
```

in the XML namespace (root element `<cteProc>`).

## Related

* [BRAZIL NF-E](/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents/brazil-nfe.md)
* [BRAZIL NFC-E](/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents/brazil-nfce.md)
* [BRAZIL NFS-E](/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents/brazil-nfse.md)
* [Supported Electronic Documents](/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents.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/brazil-cte.md?ask=<question>&goal=<user_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.