The Spanish version is the authoritative reference. View in Spanish
Sending Flows
The Gosocket OSE operates with two sending flows. The choice depends exclusively on the type of document you are sending.
Synchronous or asynchronous?
Use synchronous sending if your document represents an individual operation — a sale, a note, a one-off withholding — and you need to know immediately whether it was accepted or rejected. It applies to invoices, sales tickets, credit/debit notes, withholdings, perceptions and DAE, all sent via sendBill.
Use asynchronous sending if your document groups multiple receipts or is processed in batch by SUNAT — a daily summary, a void, a reversal — and you can wait for the result via subsequent queries. It applies to daily sales-ticket summaries, void communications and reversal summaries, all sent via sendSummary.
Both flows go through the same OSE validations (authentication, schema, signature, content). The difference lies only in how and when you obtain the CDR: immediately in the synchronous flow, deferred via ticket in the asynchronous flow.
Not sure which method to use for your document type? Review the Receipt Types, where each receipt type is associated with its corresponding sending method.