SunatResumenBoletas

Description

Sends the daily boletas summary to SUNAT: builds the SummaryDocuments (RC) with the day’s list of boletas, signs it, packages it into a ZIP file and sends it via the sendSummary operation. SUNAT does not return the CDR immediately: it returns a ticket that must be queried later with the SunatConsultarTicket node.

Meant to run on a schedule (for example, once a day), grouping the boletas issued outside this flow.

Configuration

Field	Type	Required	Description
credentials_id	credentials	Yes	SUNAT credential
resumen	json	No	Summary in JSON: fechaReferencia (boletas day), correlativo, boletas (list with id B001-1, total, gravado, igv, estado 1/2/3). If left empty, the input data is used.

Credentials

This module requires a sunat credential type with the following fields:

• Certificate (.p12): the issuer’s digital certificate
• Certificate password
• Issuer RUC (11 digits)
• SOL user and SOL password: SUNAT Clave SOL credentials
• Mode: direct (to SUNAT) or OSE (Electronic Services Operator)
• OSE URL, if mode is OSE
• Environment: beta (testing) or production

Output

{
  "ticket": "1234567890",
  "resumenId": "RC-20260101-1",
  "cantidad": 25,
  "estado": "sent"
}

Usage Example

{
  "credentials_id": "cred-sunat-prod",
  "resumen": {
    "fechaReferencia": "2026-08-04",
    "correlativo": 1,
    "boletas": [
      { "id": "B001-1", "total": 118, "gravado": 100, "igv": 18, "estado": 1 },
      { "id": "B001-2", "total": 59, "gravado": 50, "igv": 9, "estado": 1 }
    ]
  }
}

Notes

• Status “sent” does not mean accepted: query the ticket with SunatConsultarTicket to get the actual CDR.
• Each boleta’s estado uses SUNAT’s catalog: 1 = add, 2 = void, 3 = discard.
• Meant to run once a day, not per issued boleta.

Related Nodes

• SunatConsultarTicket - Query the summary result
• SunatEmitirCPE - Issue an individual invoice or boleta