Qolca Team · 2026-05-28 · 9 min read
Manual electronic invoicing wastes hours and hides real compliance risk. Here's how Peruvian SMBs can connect billing directly to SUNAT — and the real gotchas to watch out for first.
If you run a small business in Peru, you already know that emitting a factura electrónica or boleta electrónica is not optional — SUNAT has been rolling out mandatory electronic billing (comprobantes de pago electrónicos) across virtually every business category for years. What many owners haven't solved yet is the difference between complying and automating. Complying means logging into a portal, filling in fields, and clicking "emitir" every time a sale happens. Automating means your system does that work the moment a sale is recorded, the XML is signed, the comprobante reaches SUNAT (or your OSE), and the PDF lands in your customer's WhatsApp or inbox — without you touching it. This post is about making that second scenario real.
The SUNAT portal (Facturador SOL or the free Facturador SUNAT) works fine when you emit ten comprobantes a day. Past that volume — or once you have multiple sellers, multiple sales channels, or recurring billing — the manual portal becomes a daily bottleneck. Someone has to enter the client's RUC or DNI, line items, IGV, the payment reference, and then hit send. One typo in the RUC and the comprobante is rejected. One forgotten sale and your monthly libro de ventas is wrong. The real cost is not just the person-hours: it's the errors, the reconciliation time at month-end, and the stress of knowing that a rejected comprobante means you haven't legally issued it — even if your customer has the PDF.
Before you can automate anything, you need to understand the three legal paths for electronic invoicing in Peru — because they have very different integration implications.
For most Peruvian SMBs automating for the first time, a PSE is the right starting point. They maintain the SUNAT connectivity, handle certificate management, and offer REST or SOAP APIs that are reasonably well documented. You connect your own system to the PSE, not directly to SUNAT. This distinction matters a lot when you're building or buying the integration.
When a sale is recorded in your system — whether that's a custom internal tool, a POS, a WooCommerce store, or even a Google Form — the automated invoicing flow looks roughly like this: your system collects the required data (RUC/DNI, items, amounts, payment method), formats it into a UBL 2.1-compliant XML, signs it with your digital certificate (certificado digital), sends it to the PSE or OSE endpoint, receives a CDR (Constancia de Recepción) back, and stores the result. If SUNAT accepts the comprobante, the CDR has a status of "0" — accepted. Your system then generates or retrieves the PDF representation and sends it to the customer. The whole round trip, when everything works, takes under two seconds.
SUNAT's systems go down. Your PSE's API can have outages. Your internet can drop. Peruvian invoicing regulations account for this with "modo contingencia" — a fallback mechanism that lets you keep operating offline and report later. But contingency mode has its own rules: comprobantes issued in contingency must be declared within a defined window (currently 7 calendar days for most document types), and they must be numbered in a separate series. If your automation doesn't handle contingency properly, you will either stop selling during outages or emit comprobantes that never get properly declared to SUNAT. Neither is acceptable. Any serious invoicing automation — whether custom-built or via a PSE with contingency support — needs to handle queuing, retry logic, and contingency series automatically.
SUNAT's UBL 2.1 validation is strict. The most common rejection reasons in practice are not exotic edge cases — they're predictable, and a well-built system eliminates most of them upstream:
One of the most valuable parts of automating invoicing for a Peruvian SMB is triggering the comprobante from a payment confirmation — not from a manual click. When a customer pays via Izipay's POS terminal, or confirms a Yape/Plin transfer, that payment event can kick off the invoicing flow automatically: look up the sale, fill in the buyer's data, emit the comprobante, and send the PDF to WhatsApp. This closes the loop between payment and legal compliance without any staff action. Izipay, for example, has a merchant API that fires a webhook on successful payment. Yape for business (Yape Biz) provides payment confirmation hooks as well. These integrations are not always perfectly documented, but they're buildable and, once running, they eliminate the most common source of missing comprobantes: sales that got paid but never got invoiced.
Here's the sequence that avoids the most common mistakes when automating SUNAT invoicing for a small business:
Automation is not always the right move at this moment. If your sales data lives entirely in handwritten notebooks or an unstructured WhatsApp chat, the invoicing problem is actually a data-capture problem — and you need to solve that upstream layer first. Similarly, if you emit fewer than 20 comprobantes per month and your business is stable, the manual portal may genuinely be the most cost-effective option right now. Automation has a build and maintenance cost; it pays off as volume and complexity increase. The right question is not "should I automate?" but "at what point does the manual friction cost more than the automation investment?" For most growing businesses, that threshold arrives earlier than owners expect — usually around the time a second employee is spending meaningful hours on billing.
"The real cost of manual invoicing isn't the time to type the comprobante. It's the month-end reconciliation, the rejected XMLs you didn't notice, and the customer who never got their boleta and disputes the charge."
At Qolca, we build custom invoicing automation for Peruvian SMBs — typically as part of a broader internal tool or operations system, not as a standalone invoicing SaaS. That means we connect your existing sales flow (whether it's a custom CRM, a POS, an e-commerce store, or a WhatsApp order intake) to a PSE of your choice, handle the UBL 2.1 generation, certificate management, contingency queuing, and PDF delivery to WhatsApp or email. We don't replace your accounting software; we make sure the comprobante data feeds into it cleanly. The systems we deliver are yours — no per-seat licensing, no vendor lock-in on the integration layer.
If you're spending real hours each week on manual invoicing, or if billing errors are creating reconciliation headaches, it's worth spending 30 minutes mapping out what an automated flow would look like for your specific setup. You can book a free initial consultation at https://calendly.com/qolca-info/consultoria-inicial-gratuita, or just send a message on WhatsApp at https://wa.me/51991376769 — we're happy to take a look at your current process and tell you honestly whether automation makes sense right now.