[CL] Related Documents (relations)

Overview

A Chilean DTE can carry references to other documents (SII Referencias). Large buyers often match each invoice against their purchase order (OC) or service entry sheet (HES), and an invoice without the reference they expect can be held at payment.

In Brinta you send these references in the root-level relations[] array. Each entry produces one reference in the XML:

Brinta fieldRequired?SII XML elementNotes
relations[].document_typeRequiredTpoDocRefSee the table below.
relations[].invoice_typeRequired(Brinta-only)See the table below.
relations[].invoice_numberRequiredFolioRefNumber of the referenced document.
relations[].invoice_dateRequiredFchRefFormat YYYY-MM-DD.
relations[].relation_reasonOptionalRazonRefFree text.

You can send several relations in the same document, for example an OC and an HES.

Credit and debit notes keep the reference to the original invoice (original_invoice_id / original_invoice_external_id); any relations[] you send are added to it.


Document types

document_typeinvoice_typeSII codeName shown on the document
purchase orderdebit801Orden de Compra
service entry sheetdebitHESHoja de Entrada Servicio
order notedebit802Nota de pedido
contractsupport_document803Contrato
resolutionsupport_document804Resolución
chile compra processsupport_document805Proceso Chile Compra
chile compra recordsupport_document806Ficha Chile Compra
export customs declarationtransport807DUS
bill of lading seatransport808B/L (Conocimiento de embarque)
bill of lading airtransport809AWB (Air Waybill)
export transporttransport810MIC/DTA
bill of lading roadtransport811Carta de Porte
customs export resolutiontransport812Resolución del SNA donde califica Servicios de Exportación
exchange deposit certificatesupport_document814Certificado de Depósito Bolsa Prod. Chile
exchange pledge vouchersupport_document815Vale de Prenda Bolsa Prod. Chile
exceptional payment term agreementsupport_document820Código de Inscripción en el Registro de Acuerdos con Plazo de Pago Excepcional
transporttransport52Guía de Despacho Electrónica

To reference a DTE already issued through Brinta (for example, an invoice from a previous month), send only invoice_id or invoice_external_id plus relation_reason: Brinta takes the SII code, folio and date from that document.


Example — Invoice referencing an OC and an HES

{
  "e_invoice": true,
  "currency": "CLP",
  "supplier_company_id": "{{supplier_company_id}}",
  "invoice_date": "2026-10-21",
  "document_type": "invoice",
  "invoice_type": "debit",
  "invoice_external_id": "{{invoice_external_id}}",
  "buyer": {
    "company": {
      "legal_name": "Buyer Company SpA",
      "type": "business",
      "address": {
        "address_line_1": "Av. Apoquindo 1234",
        "neighborhood": "Las Condes",
        "city": "Santiago",
        "country": "CL"
      },
      "tax_registrations": [
        {
          "number": "77000000-0",
          "type": "RUT",
          "level": "country",
          "location": "CL"
        }
      ]
    }
  },
  "items": [
    {
      "name": "Maintenance service",
      "quantity": 1,
      "amount": 100000,
      "taxes": [
        {
          "name": "IVA",
          "type": "VAT",
          "rate": 0.19,
          "rate_type": "percentage",
          "amount": 19000
        }
      ]
    }
  ],
  "relations": [
    {
      "document_type": "purchase order",
      "invoice_type": "debit",
      "invoice_number": "4500265361",
      "invoice_date": "2026-09-15"
    },
    {
      "document_type": "service entry sheet",
      "invoice_type": "debit",
      "invoice_number": "{{hes_number}}",
      "invoice_date": "{{hes_date}}",
      "relation_reason": "HES {{hes_number}}"
    }
  ]
}

Resulting SII references:

TpoDocRefFolioRefFchRefRazonRef
80145002653612026-09-15
HES{{hes_number}}{{hes_date}}HES {{hes_number}}

Check with your buyer which reference they expect. Most buyers ask for the OC (801), and some also ask for the HES. Use the number exactly as it appears in the buyer's system.


Did this page help you?