OSE validation · PSE signing · Peru

Signs and validates with SUNAT with no certificates of your own.

You 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.

1.6s
From sending to CDR
0
Certificates you buy
8.4M
Documents processed
Document traceability F001-00045
Your systemPOST /comprobante · JSON 0.0s
PSE signingA signed UBL 2.1 XML 0.4s
OSE validationSUNAT rules and catalogues 1.1s
SUNATCDR 0 · Accepted 1.6s

Returned to your system .xml.pdf.cdr
The full route JSON → XML → CDR
your system PSE signing · OSE validation SUNAT accepted · CDR 1.6s
With no certificates to buy REST API or XML file No annual renewals CDR accepted in1.6s
Operating since 2012 The PSE signs, the OSE validates Zero certificates to buy JSON in, CDR in 1.6s A volume price, not a list price

The two concepts

The PSE signs. The OSE validates. SUNAT receives.

They are named together because they are bought together, but each does something different along the document's path.

Electronic Services Operator

The OSE validates and issues the CDR

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.

  • What it is: the validator authorised by SUNAT
  • Who needs it: whoever issues in volume and does not want to depend on SUNAT's queue
  • What it saves you: long waits and cryptic rejection messages
  • A response with the reason spelled out when something is wrong
In practice: the PSE signs, the OSE validates and SUNAT receives it. You only send the document's data and get the XML, the PDF and the CDR back.
Why it makes sense

30 issuing tax IDs, zero certificates to renew.

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.

1.6sto CDR It is the time measured in production between the POST from your system and the accepted receipt coming back.
  • You do not buy a digital certificate per tax ID
  • There are no expiry dates to watch and no renewals to schedule
  • You handle no files .pfx and no signing passwords
  • You maintain no XML signing libraries in your code
  • You do not chase SUNAT catalogue changes: we apply them
  • If you issue for several companies, the saving multiplies per tax ID
Two routes to signing
With your own certificate
Buying the certificate for each tax ID Validating the legal representative's identity Installing it in your invoicing system Renew before expiry
4 recurring tasks per tax ID
vs
With PSE signing
You authorise the PSE in your SOL credentials You connect your system to the API You issue
1 initial set-up
Zero .pfx files
Both routes

Fewer steps and less waiting before the first document.

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.

Tasks before you can issue

The traditional route 7 tasks
With Búho validation 3 tasks
  • Traditional: buy the certificate, validate identity, install it, build the XML signing, certify, go live and renew at every expiry
  • With us: authorise the provider in your SOL credentials, connect your system and go live

Days to the first accepted CDR

The traditional route 10 – 15 d
With Búho validation 2 – 3 d
  • The bulk of the traditional route goes on issuing the certificate and validating the legal representative's identity
  • Here the clock starts when you authorise us: the sandbox is ready the same day

The traditional route depends on the body issuing the certificate and on your technical team. Ours depends on how fast you connect your system.

Who it's for

For whoever issues in volume or on behalf of others.

The more documents you issue and the more tax IDs you manage, the heavier the cost of maintaining certificates one by one.

High-volume companies

Retail and distributors that cannot afford a signature going down on a closing Monday.

Queue and automatic retries

Software and marketplaces

You 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 point

Accounting firms

Instead of 30 certificates with 30 expiry dates, one integration.

No expiry dates to chase
What's included

Signing, validation, archiving and response.

The service covers the document's whole cycle, from leaving your system to being stored and downloadable.

UBL 2.1 XML PSE signing OSE validation PDF with a QR Archive
current rules and catalogues

Building the XML

You send JSON and we build the UBL 2.1 XML with the structure, the catalogues and the taxes SUNAT requires.

PSE digital signing

It signs with the authorised provider's certificate. You buy nothing.

OSE validation

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.

PDF and printed representation

The PDF with its QR code and hash, ready to print or send by email.

Document archive

SUNAT requires the XML, PDF and CDR to be kept. They are stored and downloadable.

Webhooks and retries

If SUNAT does not respond, the document queues and retries itself. Your system is notified as soon as the status changes.

Getting started

Three steps and you are issuing.

You authorise the provider

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.

You connect your system

We give you sandbox credentials, the documentation and examples. You can send JSON through the API or hand over your XML already built.

You move to production

We validate together the document types you issue and switch production on. The first accepted CDR comes out the same day.

An engineer walks you through the integration on WhatsApp until the first accepted document. Message on WhatsApp
Price

This service is quoted individually.

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.

Monthly volume

How many documents go through a month. The price falls in tiers.

Integration type

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.

REST API + JSON The XML already built Status webhooks Sandbox Multi-issuer A tailored SLA
Volume rangeTypical profileModelPrice
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
The proposal always arrives with the same things: sandbox, credentials, the API documentation, an engineer walking you through the integration on WhatsApp, and the detail of which documents we cover in your case.
The ranges above are there to place you before we talk. Today this service has no published plans in the shop: the proposal is built case by case and includes a sandbox, guidance through the integration, and support.

Tell us how much you issue and we will give you the number.

With your monthly volume, your document types and how you want to connect, we put the proposal together. No commitment.

A reply the same business day Sandbox included No certificates to buy
Which one fits me

Your own certificate or PSE signing?

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 certificateOSE validation / PSE signing
Certificate purchaseOne per issuing tax IDNone
Periodic renewalEvery 1 to 3 yearsNot applicable
Identity validationYes, the legal representative'sAuthorisation from your SOL credentials
You handle .pfx files
You maintain signing libraries
SUNAT catalogue changesYou apply themWe apply them
Ideal forA business issuing steadilyHigh volume or many issuers
CostFrom On request
  See SUNAT certificate → You are here
Results

Infrastructure proven in production.

8.4M
Documents processed
99.97% accepted
1.6s
From sending to CDR
Measured in production
99.97%
Service uptime
Last 12 months
14 years
Operating from Peru
Certification up to date
Clients

What people who have already integrated say.

4.9/5 across 824 verified reviews

A notary going through documents at his desk 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'.
Rodrigo AlcántaraNotary and accounting firm · Lima · 30 issuing tax IDs

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.

Fernando GálvezDistributor · Chiclayo

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.

Paola NietoMarketplace · Lima
Questions

What people ask us before integrating.

Is Búho the PSE or the OSE?
No, and it is worth saying plainly. The PSE and the OSE are bodies authorised by SUNAT, and we are neither of them. We have arrangements with authorised providers and buy capacity from them in volume, so the price we give you is lower than the one you would get contracting them yourself. We provide the integration, the support and the account; they provide the signing and the validation. We buy and renew that capacity all year, along with the tax-ID, national-ID, licence and number-plate lookups, because our own systems need them daily.
Why do I not see published prices?
Because this service is not sold off the shelf. The rate depends on monthly document volume and on the type of integration, so we build it case by case. We buy capacity in volume from the authorised providers, and that discount is passed on to your rate. Write to us with your approximate volume and we will give you the figure the same business day.
Is it legal to issue without a certificate of your own?
Yes. SUNAT provides for the PSE precisely for this: an authorised third party carries out the issuing activities on your behalf, signing included. You authorise the provider from your SOL credentials and the document remains yours.
What is the difference between an OSE and going direct to SUNAT?
With direct filing, your document goes to SUNAT's service and you wait for its response. With an OSE, the validation is done by the authorised operator and it informs SUNAT. In practice, the OSE usually responds faster and with clearer error messages.
Which documents does it cover?
Invoice, receipt, credit note, debit note, electronic dispatch note, daily receipts summary and void notice. If you need a specific document, say so in the quote and we will confirm it.
How do I connect?
Through the REST API by sending the document as JSON, or by handing us the XML already built if your system generates it. In both cases you get back the signed XML, the PDF and the CDR, plus webhooks for status changes.
What happens if SUNAT is down?
The document queues and retries automatically. Your sale does not stop: you hand over the printed representation and the CDR arrives when the service is back. You are notified by webhook.
Is it any use if I already use Fastura?
Yes. It can be combined with the Fastura panel or with an installation of the source code so that signing and validation go through the OSE/PSE scheme rather than through your own certificate.
And if I would rather buy my own certificate?
It is a perfectly valid route, especially if you have a single tax ID and steady volume. We arrange it with 100% remote validation and terms of 1, 2 or 3 years. See SUNAT digital certificate →
When does this suit me and when does my own certificate?
With one tax ID and steady issuing, your own certificate usually works out cheaper. From several tax IDs or thousands of documents a month, what weighs is no longer the certificate's price but chasing expiry dates and catalogues. That is where the PSE scheme suits.

You issue. The signing and the validation are we provide.

Tell us how many documents you issue a month and how you want to connect. We put together the proposal and the sandbox.

No certificates to buy Sandbox included Support through the integration