Cesibilidad (Ley 19.983)

An electronic factura (Chile's electronic invoice) can be ceded — its credit handed to a factoring company, with mérito ejecutivo, meaning it is directly enforceable in court. Ley 19.983 says when:

• when the receptor gives an acuse de recibo, a formal acknowledgement of receipt (art. 3), or
• when eight calendar days pass without them disputing it (art. 4 inc. 4).

It also says when never: if the emisor declared the payment as al contado — cash, with no outstanding balance — the document is not cedible. Circular N°35 of 23.06.2017 leaves no room: "these documents may not be ceded".

Ask

curl -X POST https://api.facturia.cl/v1/documents/doc_01K2R7.../cesion \
  -H "Authorization: Bearer $FACTURIA_KEY" -H "Facturia-Empresa: $EMPRESA"

202 if this call queued the question, 200 if an identical one is already in flight. The answer lands on the document; there is no webhook, so you read it with GET /v1/documents/doc_01K2R7...:

{
  "id": "doc_01K2R7...",
  "tipo_dte": 33,
  "status": "accepted",
  "cesion": {
    "cedible": true,
    "sii_status_code": 25,
    "checked_at": "2026-08-23T09:12:40Z"
  }
}

cedible and sii_status_code travel together on purpose. If the SII answers with a code we have not mapped, cedible stays null and the code is stored whole: we would rather tell you "the SII answered 9" than invent a boolean. An invented false would tell a factoring company that a perfectly cedible factura is not.

The two rejections

This is read-only

POST .../cesion cedes nothing. It builds no AEC, signs nothing, writes nothing to the SII's Registro de Cesión de Créditos, the credit assignment registry. The operation it calls (consultarDocDteCedible) is the only one in that service that carries no action code, and it cannot change any state over there.

That is exactly why it accepts a key with the documents:read scope: whoever needs this is usually a factoring system, and it has no business carrying a key that can issue facturas.

Do not confuse it with the cedible copy

Two different things whose names look very much alike:

• GET /v1/documents/doc_01K2R7.../pdf?copy=cedible gives you the third printed copy, the one carrying the CEDIBLE legend and the acuse de recibo box. It exists per type: every 33 and every 34 has one, even an al contado factura whose copy cedes nothing to anyone. See Artifacts.
• cesion tells you whether the credit can move now.

Holding the copy does not mean you can cede.

In test mode

In sandbox none of this touches the network: the answer is simulated in process, applying the same legal rule against the empresa's simulated clock. It returns 24 until eight days have passed since acceptance and 25 from then on, so both branches are testable:

# Recién emitida: todavía no
curl -X POST https://api.facturia.cl/v1/documents/doc_01K2R7.../cesion \
  -H "Authorization: Bearer $FACTURIA_TEST_KEY" -H "Facturia-Empresa: $EMPRESA"
# → "cesion": { "cedible": false, "sii_status_code": 24, ... }

# Adelanta el reloj de la empresa nueve días
curl -X POST https://api.facturia.cl/v1/test_helpers/clock \
  -H "Authorization: Bearer $FACTURIA_TEST_KEY" -H "Facturia-Empresa: $EMPRESA" \
  -H "Content-Type: application/json" -d '{"advance_days":9}'

curl -X POST https://api.facturia.cl/v1/documents/doc_01K2R7.../cesion \
  -H "Authorization: Bearer $FACTURIA_TEST_KEY" -H "Facturia-Empresa: $EMPRESA"
# → "cesion": { "cedible": true, "sii_status_code": 25, ... }

The simulated code for the cedible case is 25 and not 23 on purpose: in sandbox there is no receptor to acknowledge anything, so silence is the only way a simulated factura ever becomes cedible.

Ceding for real — POST .../cede (ticket #60)

Everything above is a read: POST .../cesion only asks. POST .../cede actually cedes — it assembles an Archivo Electrónico de Cesión (AEC) — the emisor's original signed DTE plus the terms of the transfer, signed by the cedente — and uploads it to the SII's Registro Electrónico de Transferencia de Crédito. It is a real and irreversible act, and it works the same regardless of which channel emitted the document — the AEC carries the original signed envelope verbatim, so it no longer distinguishes emission_channel=sfg from emission_channel=mercado (ticket #60, ruled 2026-09-06).

curl -X POST https://api.facturia.cl/v1/documents/doc_01K2R7.../cede \
  -H "Authorization: Bearer $FACTURIA_KEY" -H "Facturia-Empresa: $EMPRESA" \
  -H "Idempotency-Key: $(uuidgen)" -H "Content-Type: application/json" \
  -d '{
    "cesionario": {
      "rut": "76000000-0",
      "razon_social": "Factoring Ejemplo SpA",
      "direccion": "Av. Ejemplo 1234, Santiago",
      "email": "[email protected]"
    },
    "ultimo_vencimiento": "2026-10-15"
  }'

202 with a job if this call queued a NEW attempt; 200 with the SAME job if there is already one in queued/submitted/aec_generated for this document — one attempt at a time. The result lands on the document, under cesion.status:

"cesion": {
  "cedible": true,
  "sii_status_code": 25,
  "checked_at": "2026-08-23T09:12:40Z",
  "status": "confirmed"
}

status runs queued → one of:

An attempt whose envelope never settles within the poll budget keeps submitted (the AEC really was received) and its job ends failed with cesion_registration_unconfirmed: someone has to open the Registro de Cesión de Créditos and look.

Rejections before anything gets written, on top of the usual 404/permission ones:

In test mode this resolves within the same request, just like the sandbox branch of POST .../cesion: no socket is opened, the attempt ends simulated, and both webhooks fire — document.cesion_submitted and then document.cesion_confirmed — so the event you get paid against in production is exercisable in tests too.

Also