High-volume companies
Retail and distributors that cannot afford a signature going down on a closing Monday.
Queue and automatic retriesYou send us the document's data as JSON. We build the XML, sign it with the PSE's certificate, validate it with the OSE and return the CDR in 1.6s. You buy and renew no certificates.
They are named together because they are bought together, but each does something different along the document's path.
It is the body SUNAT authorises to validate documents in its name. It checks that the XML meets the UBL 2.1 standard, the business rules and the current catalogues, and issues the receipt confirmation. Once the OSE accepts, the document is already valid: informing SUNAT is its job.
It is the third party authorised to carry out the technical issuing tasks: building the XML, sign it digitally, sending it and storing the files. The signing is done with the PSE's certificate, not with one of yours. You authorise it from your SOL credentials and the document stays yours.
Every issuing tax ID buys its tax digital certificate, validates the legal representative's identity, installs it in its invoicing system and renews it before it expires. It is a perfectly valid route and, with a single tax ID and steady volume, usually the simplest and cheapest.
We arrange it with 100% remote validation. See SUNAT digital certificate →
Your system sends the document to SUNAT's service and waits for its response. You need your own certificate, signing libraries and someone to chase every catalogue change. It is what any invoicing system you install does underneath.
If you go this way, Fastura's source code gives you the full issuer with certification kept current.
The traditional route requires every tax ID to buy its certificate, be validated, install it and renew it before it expires. With the PSE scheme that comes off your calendar.
We are not comparing prices here: we are comparing work. How many tasks you have to do in order to issue, and how long each route takes to reach the first accepted CDR.
The traditional route depends on the body issuing the certificate and on your technical team. Ours depends on how fast you connect your system.
The more documents you issue and the more tax IDs you manage, the heavier the cost of maintaining certificates one by one.
Retail and distributors that cannot afford a signature going down on a closing Monday.
Queue and automatic retriesYou issue on behalf of many merchants. Asking every seller for a digital certificate does not scale, and each one that expires takes a shop down.
One single integration pointInstead of 30 certificates with 30 expiry dates, one integration.
No expiry dates to chaseThe service covers the document's whole cycle, from leaving your system to being stored and downloadable.
You send JSON and we build the UBL 2.1 XML with the structure, the catalogues and the taxes SUNAT requires.
It signs with the authorised provider's certificate. You buy nothing.
It is validated against the current rules and the CDR comes out. If something is wrong we return the code and the reason in plain language, not a bare number.
The PDF with its QR code and hash, ready to print or send by email.
SUNAT requires the XML, PDF and CDR to be kept. They are stored and downloadable.
If SUNAT does not respond, the document queues and retries itself. Your system is notified as soon as the status changes.
From your SOL credentials you register the PSE and the OSE that will operate for your tax ID. We guide you screen by screen; it takes minutes.
We give you sandbox credentials, the documentation and examples. You can send JSON through the API or hand over your XML already built.
We validate together the document types you issue and switch production on. The first accepted CDR comes out the same day.
There is no off-the-shelf rate because no two integrations are alike. The price comes from two figures: how many documents you issue a month and how you connect.
How many documents go through a month. The price falls in tiers.
Sending us JSON through the API does not cost the same as handing us the XML already built, nor does connecting one tax ID compare with running a platform of a hundred issuers.
| Volume range | Typical profile | Model | Price |
|---|---|---|---|
| Up to 5,000 documents / month | One tax ID, issuing from a single system | Base pack | Quote this range |
| Up to 50,000 documents / month | Retail, distributors, several points of sale | Tiered by volume | Quote this range |
| More than 50,000 documents / month | Platforms, marketplaces, multi-company | A tailored contract with an SLA | Quote this range |
With your monthly volume, your document types and how you want to connect, we put the proposal together. No commitment.
Both routes are valid with SUNAT. What changes is the fixed cost, the maintenance and who carries the technical side.
Prices already include tax. Those marked with * are charged in US dollars because that product is not sold in soles.
| Your own digital certificate | OSE validation / PSE signing | |
|---|---|---|
| Certificate purchase | One per issuing tax ID | None |
| Periodic renewal | Every 1 to 3 years | Not applicable |
| Identity validation | Yes, the legal representative's | Authorisation from your SOL credentials |
| You handle .pfx files | ||
| You maintain signing libraries | ||
| SUNAT catalogue changes | You apply them | We apply them |
| Ideal for | A business issuing steadily | High volume or many issuers |
| Cost | From | On request |
| See SUNAT certificate → | You are here |
4.9/5 across 824 verified reviews
Compliance
"We had thirty certificates with different expiry dates and a calendar full of reminders. We authorised the provider from our SOL credentials and that was that. These days the only paperwork we chase is our clients'.”
We issue around 60,000 documents a month. The queue with retries has saved us several times when SUNAT slowed down on a closing Monday.
We are a marketplace: asking every seller for a digital certificate was impossible. With the PSE scheme we issue for all of them from a single point.
Tell us how many documents you issue a month and how you want to connect. We put together the proposal and the sandbox.