Purchases API

The /purchase-invoices resource issues E41 documents for informal suppliers (not registered with the DGII). The API requires the supplier to exist and be active in your catalog; the document is recorded as E41 in your purchase reports.

E41 covers purchases from informal suppliers: you issue the e-CF on behalf of the supplier because the supplier is not a registered DGII taxpayer and cannot issue E31. If the supplier is registered, use the E31 they issue themselves. The body reuses the same line, tax and withholding shape as sales invoices.

Overview

Before saving, the API validates that supplierId references an active supplier in your catalog and that the supplier is not marked as registered with the DGII (isRegisteredInDGII = false). If the sum of payments does not match the document total, the API also responds 400.

Available operations

• GET /api/v1/purchase-invoices — Devuelve un PagedResult con los gastos, compras y pagos al exterior del espacio de trabajo; esta ruta no filtra por tipo de e-CF.
• GET /api/v1/purchase-invoices/{id} — Devuelve el detalle completo de un comprobante de compra (E41).
• POST /api/v1/purchase-invoices — Registra un comprobante de compra (E41) emitido al espacio de trabajo por un proveedor.
• POST /api/v1/purchase-invoices/{id}/void — Anula el comprobante; si la DGII ya lo aceptó, emite una nota de crédito (E34) y devuelve su creditNoteId.
• POST /api/v1/purchase-invoices/{id}/edit-amount — Emite una nota de débito (E33) que corrige los montos de el comprobante y devuelve el documentId de esa nota; el original no se modifica.
• POST /api/v1/purchase-invoices/{id}/edit-text — Emite una nota de débito (E33) que corrige la descripción de las líneas de el comprobante y devuelve el documentId de esa nota; el original no se modifica.

Example: record a purchase document

The body includes supplierId (reference to the contacts catalog), tipoBienServicioComprado (606 classification, 1 to 11), sequence (optional: if omitted, the next E41 NCF from the active sequence is used) and the lines with their taxes and withholdings. Always send tipoBienServicioComprado: the API does not validate it and, if missing, silently stores 0 and the 606 comes out wrong. Also note that the /purchase-invoices list returns expenses, purchases and foreign payments mixed, and that edit-amount and edit-text issue a new debit note (E33) instead of editing the purchase. The immediate response is the same as the rest of the resource: documentId and consultationUrl.

curl -X POST https://tuempresa.factura.com.do/api/v1/purchase-invoices \
  -H "X-Api-Key: $FACTURA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "branchId": "b1a2c3d4-e5f6-4789-abcd-1234567890ab",
    "sequence": "E410000000001",
    "issuedAt": "2026-05-08T10:00:00Z",
    "paymentTermId": 1,
    "limitDate": "2026-05-08T10:00:00Z",
    "supplierId": "8c2e4f1a-6d3b-4a9e-b7c5-1f0d2e3a4b6c",
    "tipoBienServicioComprado": 2,
    "currencyId": 1,
    "currencyRate": 1,
    "lines": [
      {
        "code": "INSUMO-21",
        "order": 1,
        "description": "Insumos de oficina",
        "isService": false,
        "quantity": 5,
        "unitId": 1,
        "unitPrice": 1200.00,
        "taxes": [{ "taxId": "3a5e98e0-33ff-44be-bd37-e3f9b35a25e2", "rate": 18.0, "taxTypeId": 1 }],
        "withholdings": [{ "withholdingId": "0b6d81a6-083c-449e-8791-770ff5b3379d", "rate": 5.0 }]
      }
    ],
    "payments": [
      { "reference": "TR-2026-05-001", "amount": 6720.00 }
    ]
  }'

const res = await fetch(
  "https://tuempresa.factura.com.do/api/v1/purchase-invoices",
  {
    method: "POST",
    headers: {
      "X-Api-Key": process.env.FACTURA_API_KEY!,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      branchId,
      sequence: "E410000000001",
      issuedAt: new Date().toISOString(),
      paymentTermId: 1,
      limitDate: new Date().toISOString(),
      supplierId,
      tipoBienServicioComprado: 2, // clasificación 606 (1 a 11); si falta, se guarda 0
      currencyId: 1,
      currencyRate: 1,
      lines,
      payments,
    }),
  },
);
if (!res.ok) throw new Error(`factura.com.do: ${res.status}`);
const { documentId, consultationUrl } = await res.json();

{
  "documentId": "c1d2e3f4-a5b6-4c7d-8e9f-0a1b2c3d4e5f",
  "consultationUrl": "https://ecf.dgii.gov.do/ecf/ConsultaTimbre?RNCEmisor=131000001&ENCF=E410000000001&…"
}

Example: 400 when the supplier is registered with the DGII

{
  "success": false,
  "message": "No se puede crear un Comprobante de Compras (E41) para un proveedor registrado en la DGII."
}

Supplier validation

E41 is reserved for informal suppliers. Before accepting the POST the API checks two conditions against the workspace catalog: the supplier must be active and must not be marked as registered with the DGII. If either fails, it responds 400 with { success: false, message }.

Next steps