# Invoicer — Issue today. Have SUNAT accept it today. > Electronic invoicing · Peru 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. Invoicer · Electronic invoicing for Peru. Receipts with signed XML, submission to SUNAT and stored CDR; credit and debit notes with official catalogue reasons; electronic despatch guides; withholding and perception receipts; daily summaries, voids and reversals; series and sequence numbers; digital certificate and Clave SOL; branded PDF; credit sales with instalments. ## Numbers - **12** document types - **4** main ones: invoice, boleta, CN and DN - **3** issuable currencies - **17** units of measure ## 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. 1. **You load your credentials.** Your digital certificate and your Clave SOL, per RUC and per environment: beta to test, production to issue. 2. **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. 3. **It is signed and sent.** The engine serialises UBL 2.1, signs the XML and sends it to SUNAT. 4. **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. **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. ## 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. - **Extract of the receipt history.** Five of the eight columns of the real screen; every row carries the status SUNAT returned: accepted, accepted with observations, rejected or still to send. - **Dashboard and active series.** How many receipts you have issued, how many need action, and where each series stands. - **Pending send on a phone.** The ones already signed that have not gone out yet, as cards, each with its button to resend it to SUNAT. > 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. ## Electronic receipts Invoice, boleta **and the receipts almost nobody gets right**. Twelve document types in a single flow, each with its own series and format. ### Module menu - Invoicer dashboard (`/invoicer`) - Issue a receipt (`/invoicer/submit`) - History (`/invoicer/history`) - Withholding and perception (`/invoicer/submit?documentType=20`) - Download XML and CDR (`/invoicer/history`) Formats and views: 01 Invoice · 03 Boleta · 20 Withholding · 40 Perception · PEN · USD · EUR · PDF · XML · CDR ### Capabilities - **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 ## Credit and debit notes 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. ### Module menu - Credit note (`/invoicer/submit?documentType=07`) - Debit note (`/invoicer/submit?documentType=08`) - Catalogue reasons (`/invoicer/submit`) - History (`/invoicer/history`) Formats and views: 07 Credit note · 08 Debit note · Catalogue 09 · Catalogue 10 · Series FC · BC · FD · BD ### Capabilities - **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 ## Electronic despatch guides If the goods move, **the guide moves with them**. Sender guide and carrier guide, with their origin and destination points. ### Module menu - Despatch guides (`/invoicer/guides`) - Sender guide (`/invoicer/submit?documentType=09`) - Carrier guide (`/invoicer/submit?documentType=31`) - History (`/invoicer/history`) Formats and views: 09 Sender · 31 Carrier · Series T · V · Transfer · PDF · XML ### Capabilities - **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 ## Summaries, voids and batches Boletas travel together; **so do voids**. Daily summary, void communication, reversal summary and batch submission. ### Module menu - Summaries and voids (`/invoicer/summary`) - Void communication (`/invoicer/summary`) - Reversal summary (`/invoicer/summary`) - History (`/invoicer/history`) Formats and views: RC Daily summary · RA Void communication · RR Reversal summary · LT Batch ### Capabilities - **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 ## Series, sequence numbers and credentials Your numbering, **sorted by type**. Every document type with its prefix, and your credentials stored per RUC and per environment. ### Module menu - Series and numbering (`/invoicer/numbering`) - Certificate and Clave SOL (`/invoicer/credentials`) - Settings (`/invoicer/settings`) - History (`/invoicer/history`) Formats and views: F · B · FC · BC · FD · BD · R · P · T · V · Beta · Production ### Capabilities - **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 PDF your customer sees The receipt belongs to SUNAT; **the print is yours**. Logo, colours per document type and the QR code where it has to be. ### Module menu - PDF customization (`/invoicer/customization`) - Company logo (`/invoicer/customization`) - Colours per type (`/invoicer/customization`) - History (`/invoicer/history`) Formats and views: Logo · Colours · QR · Invoice · Boleta · Note · Guide · Withholding ### Capabilities - **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** (Plan 01) — For whoever is just starting to issue electronically. · Price: Price to be defined ([PENDING] a person sets it · it will carry its currency). Invoices and boletas · Credit and debit notes · Series and sequence numbers · PDF with your logo · History with XML and CDR. - **Operation** (Plan 02) — For whoever moves goods and issues every day. · Price: Price to be defined ([PENDING] a person sets it · it will carry its currency). Everything in Issuing · Electronic despatch guides · Daily summaries and voids · Withholding and perception receipts · Credit sales with instalments. - **Tailored** (Plan 03) — For whoever issues from their own system. · Price: Let’s talk ([PENDING] scope and price are defined case by case). Everything in Operation · Several RUCs in one account · Colours per document type · Hands-on help going live. ## Contact 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 Form: https://invoicer-site.pages.dev/#contact · Dishub Technologies: https://dishub.city --- Invoicer is the e-invoicing engine by [Dishub Technologies](https://dishub.city).