Electronic invoicing · Peru
Issue today.Have SUNAT accept it today.
Electronic receipts with signed XML, submitted to SUNAT and with their CDR stored. Whatever can be validated before burning a sequence number is validated before.
How it works
A receipt is not issued until the CDR comes back.
That is the order the engine keeps: validate first, then reserve the number, then sign, and only then send.
A rejected sequence number is burned.
It is never reused: the gap stays in the series. That is why the engine validates everything it can before reserving the number.
You load your credentials
Your digital certificate and your Clave SOL, per RUC and per environment: beta to test, production to issue.
You build the receipt
Customer, lines, VAT treatment, unit of measure and currency. If something does not add up, it stops you before the sequence number is taken.
It is signed and sent
The engine serialises UBL 2.1, signs the XML and sends it to SUNAT.
The CDR comes back and is stored
SUNAT’s reply is filed next to the XML and the PDF. The history keeps the trail of every attempt.
The screens
This is what you will use.
Three views of the engine: the history with the status SUNAT returned, the dashboard with your active series, and the pending-send tab on a phone.
Illustrations, not screenshots: the labels, columns and statuses are the ones from the real screens, which ship in Spanish for the Peruvian market; the RUCs, customers, series and amounts are made up and belong to no taxpayer.
| Documento | Cliente | Fecha | Monto | Estado |
|---|---|---|---|---|
| F001-00000241BETA01 — Factura | Comercial Ejemplo S.A.C.20000000019 | 2026-09-01 10:32:00 | S/ 1200.00 | Aceptado |
| B001-00001180BETA03 — Boleta | Cliente de Muestra00000000 | 2026-09-01 11:04:00 | S/ 120.00 | Aceptado con obs. |
| FC01-00000018BETA07 — Nota de Crédito | Comercial Ejemplo S.A.C.20000000019 | 2026-09-01 12:15:00 | S/ 350.00 | Aceptado |
| F001-00000242BETA01 — Factura | Servicios Demo E.I.R.L.20000000029 | 2026-09-02 09:20:00 | US$ 500.00 | Por enviar |
| F001-00000239BETA01 — Factura | Tienda Ficticia S.A.C.20000000039 | 2026-08-31 16:48:00 | S/ 890.00 | Rechazado |
| Serie | Type | Env | Last Used | Next |
|---|---|---|---|---|
| F001 | Factura | BETA | 00000241 | 00000242 |
| B001 | Boleta | BETA | 00001180 | 00001181 |
| FC01 | Nota de Crédito | BETA | 00000018 | 00000019 |
Invoice, boleta and the receipts almost nobody gets right.
Twelve document types in a single flow, each with its own series and format.
Signed XML, not exported
The engine serialises UBL 2.1 and signs the XML before sending it to SUNAT.
The CDR is stored
SUNAT’s reply is filed with the receipt; the history keeps every attempt.
Taxes from the catalogue
Taxed, exempt, unaffected, free of charge and export; VAT at 18% or 10.5%, plus excise tax where it applies.
Credit sales with instalments
The payment schedule RS 000193-2020 requires: amount and date of each instalment, inside the XML.
«Whatever can be validated before reserving the number is validated before.»Sequence-number rule
You correct with a note, not by deleting.
Every note points at the receipt it corrects, with its type, its series and a catalogue reason.
Catalogue reason, not free text
Reasons come from SUNAT catalogues 09 and 10, verified against the official source.
Mandatory reference
A note does not stand alone: it carries the type, series and number of the receipt it corrects.
Its own series
FC and BC for credit notes, FD and BD for debit notes.
In step with the rules
The changes in RS 000048-2026 start on 2027-01-01, not before: the engine follows that date, not the announcement.
«A wrong reason declares to SUNAT an operation other than the real one.»Credit/debit note audit
If the goods move, the guide moves with them.
Sender guide and carrier guide, with their origin and destination points.
Both types
The sender guide when you move the goods; the carrier guide when a third party does.
Its own series
T for the sender guide, V for the carrier guide.
Field by field
The implementation is written against SUNAT’s GRE services manual, which lives in the repo.
Same flow
Built, signed, sent, CDR back — just like an invoice.
«SUNAT’s manual outranks any summary of it, ours included.»Source-of-truth rule
Boletas travel together; so do voids.
Daily summary, void communication, reversal summary and batch submission.
Daily summary (RC)
The day’s boletas are reported together, in a single submission.
Void communication (RA)
Voids an invoice already issued, inside the window SUNAT allows.
Reversal (RR)
Reverses the receipts that are not voided but reversed.
Batch (LT)
Several receipts in one submission, with its own ticket.
«An acknowledgement is not an outcome: until the cycle closes, the receipt is still alive.»Void incident, 2026-09
Your numbering, sorted by type.
Every document type with its prefix, and your credentials stored per RUC and per environment.
A prefix per type
F for invoices, B for boletas, FC and BC for credit notes, FD and BD for debit notes, R and P for withholding and perception, T and V for guides.
A number that never repeats
The number is reserved once; if SUNAT rejects it, the gap stays.
Certificate and Clave SOL
Your digital certificate and your SOL credentials, per RUC, stored out of the browser’s reach.
Beta before production
You test against SUNAT’s test environment and only then issue for real.
«A series with gaps is not a bug: it is the footprint of a rejection.»Sequence-number rule
The receipt belongs to SUNAT; the print is yours.
Logo, colours per document type and the QR code where it has to be.
Your logo
Upload it or pick it from your asset library; it is stored as a reference, not glued into the document.
One colour per type
Invoice, boleta, note, guide, withholding and perception can each carry their own accent.
SUNAT’s QR code
With the data the printed representation requires.
PDF, XML and CDR
All three download from the history whenever you need them.
«The tax document is not negotiable; its presentation is.»Invoicer principle
Plans
Three ways to use it. We set the price with you.
The structure is here; the amount is not published yet.
The amounts in this section are placeholders: a published price is a commercial commitment and a person sets it, not this page. When they are published, every amount carries its currency (PEN or USD).
Issuing
For whoever is just starting to issue electronically.
- Invoices and boletas
- Credit and debit notes
- Series and sequence numbers
- PDF with your logo
- History with XML and CDR
Operation
For whoever moves goods and issues every day.
- Everything in Issuing
- Electronic despatch guides
- Daily summaries and voids
- Withholding and perception receipts
- Credit sales with instalments
Tailored
For whoever issues from their own system.
- Everything in Operation
- Several RUCs in one account
- Colours per document type
- Hands-on help going live
Contact
Tell us what you issue.
We show you Invoicer issuing against SUNAT’s test environment, with your own data.
- A demo with your document types
- We review your current series and numbering
- Setting up the certificate and Clave SOL
- Beta first, production after