Chile — Brinta API → XML Field Mapping

Summary

This page maps each field of the Brinta POST /invoices request to the element it produces in
the XML submitted to Chile's tax authority (SII), across every document type Brinta issues in
Chile:

document_typeinvoice_typeSII codeName
invoicedebit33Factura Electrónica
invoice exemptdebit34Factura Exenta
ticketdebit39Boleta Electrónica
ticket exemptdebit41Boleta Exenta
debit note / debit note ticketdebit56Nota de Débito
credit note / credit note ticketcredit61Nota de Crédito
exportdebit110Factura de Exportación
debit note exportsdebit111Nota Débito Exportación
credit note exportsdebit112Nota Crédito Exportación
purchase invoicepurchase46Factura de Compra

Purchase Invoice — roles don't swap. supplier_company_id always identifies your company
(the Brinta client), and buyer always represents the other party in the transaction — this
stays true for Purchase Invoice too. Since a Purchase Invoice records something your company
bought, the real-world roles are reversed from every other document type here — your company
is financially the buyer, and the party in the buyer fields is actually your real-world
supplier/vendor. The API fields keep their usual meaning regardless: don't swap
supplier_company_id and buyer when building a Purchase Invoice request.

The starting point is always Brinta's side: what field you send and whether it's required.
Required? reflects Brinta's requirement level for the field — not necessarily the SII's
requirement level for the XML element (a field can be required for Brinta to accept the request
even where the XML element it produces is optional, and some XML elements are populated
automatically with no direct API input at all).

SII's e-invoice XML schema is shared across document types by family, not by individual code —
so the same field maps to the same XML element across every document type in that family:

  • Standard DTE schema — Invoice, Invoice Exempt, Debit Note (both variants), Credit Note
    (both variants), Export, Debit Note Export, Credit Note Export, Purchase Invoice (33, 34, 56,
    61, 110, 111, 112, 46).
  • Boleta schema — Ticket, Ticket Exempt (39, 41). A handful of element names differ here
    (called out per row below).

Legend

TagMeaning
RequiredBrinta rejects the request without it.
ConditionalRequired only for specific document types or when another field/condition applies — see Notes.
OptionalCan be omitted.

General Information

Brinta API FieldRequired?Generated XML ElementApplies toNotes
document_typeRequiredTipoDTEAllDrives the SII code (33/34/39/41/56/61/110/111/112/46).
invoice_typeRequired(not mapped — Brinta-only)Alldebit, credit, or purchase — see table above. Doesn't produce an XML element on its own, but Brinta requires it on every request.
invoice_dateRequiredFchEmisAllFormat YYYY-MM-DD.
invoice_due_dateOptionalFmaPagoStandard DTE schema only"1" (Cash) if empty or equal to invoice_date; "2" (Credit) otherwise.
(fixed value)—IndServicioBoleta schema only

Issuer

Resolved from supplier_company_id — Brinta resolves the whole block from the company record.
This is always your company, on every document type including Purchase Invoice.

Brinta API FieldRequired?Generated XML ElementApplies toNotes
supplier_company_idRequired(resolves Emisor block)AllOne id populates the whole issuer block.
company.tax_registrations[type="RUT"].numberRequiredRUTEmisorAllWith hyphen.
company.legal_nameOptionalRznSoc (Standard) / RznSocEmisor (Boleta)All
company.category_codeOptionalGiroEmis (Standard) / GiroEmisor (Boleta)AllBusiness activity (Giro).
company.address.address_line_1 + address_line_2OptionalDirOrigenAllconcat(address_line_1, " ", address_line_2).
company.address.neighborhoodOptionalCmnaOrigenAll
company.address.cityOptionalCiudadOrigenAll
company.emailOptionalCorreoEmisorStandard DTE schema only
company.phoneOptionalTelefonoStandard DTE schema only

Buyer

The other party in the transaction on every document type — including Purchase Invoice, where
this is your real-world supplier/vendor (see the note above).

Brinta API FieldRequired?Generated XML ElementApplies toNotes
buyer.company.legal_nameRequiredRznSocRecepAll
buyer.company.tax_registrations[type="RUT"].numberConditionalRUTRecepAllWith hyphen. Required when the buyer is a business; defaults to a generic RUT otherwise.
buyer.company.category_codeOptionalGiroRecepStandard DTE schema onlyBusiness activity (Giro).
buyer.company.address.address_line_1 + address_line_2OptionalDirRecepAllconcat(address_line_1, " ", address_line_2).
buyer.company.address.neighborhoodOptionalCmnaRecepAll
buyer.company.address.cityOptionalCiudadRecepAll

Line Items

Brinta API FieldRequired?Generated XML ElementApplies toNotes
items[].nameRequiredNmbItemAll
items[].descriptionOptionalDscItemAll
items[].quantityRequiredQtyItemAll
items[].amountRequiredPrcItem (via unit_amount)AllLine amount. Used directly when unit_amount isn't sent — see next row.
items[].unit_amountConditionalPrcItemAllSend this when quantity > 1; if quantity is 1 (or not sent), Brinta uses items[].amount instead.
items[].categories[list="unit"].codeOptionalUnmdItemAll
items[].external_idOptionalCdgItem/VlrCodigoAll
items[].discountOptionalDescuentoPct + DescuentoMontoAll
items[].taxes[type="VAT"].rateOptionalTasaIVAStandard DTE schema only
items[].taxes[type="VAT"].amountOptionalIVAAll

References

Only applies to Debit Note and Credit Note (both variants) — not used on Invoice, Ticket,
Export, or Purchase Invoice.

Brinta API FieldRequired?Generated XML ElementApplies toNotes
original_invoice_idRequiredTpoDocRef + FolioRef + FchRefDebit Note / Credit Note (both variants)
original_invoice_id.reasonRequiredRazonRefDebit Note / Credit Note (both variants)

Vertex API · api.brinta.com


Did this page help you?