Skip to content
OpeniDevelopers

CasesTax invoices

40,000 tax invoices a month run by API

WAM Group runs 40,000 tax invoices a month on Docs. Issuance is one call, processing is asynchronous and every invoice event arrives by webhook, with single or batch download of the documents.

WAM Group
Request accessDocumentation

From source data to result

  1. 1Invoice data
  2. 2Issuance
  3. 3Webhook
  4. 4Document
tax invoices per month
40K

The challenge. Tax invoices.

In a group with several companies, every sale and every service rendered generates a tax invoice, which has to go out under the right CNPJ and be authorized by Sefaz or by the city government. Authorization is not immediate and can come back rejected. Whoever issues at volume needs to know, without checking invoice by invoice, what was authorized, what was rejected and why.

From issuance to invoice event
Example
Invoice sent (API)Event (webhook)

  • NFS-e · Company 1

    R$ 1,840.00

    Authorized

    Authorized

    Document available

  • NF-e · Company 2

    R$ 12,300.00

    Authorized

    Authorized

    Document available

  • NFS-e · Company 1

    R$ 560.00

    Rejected

    Rejected

    With the reason

  • NF-e · Company 3

    R$ 4,215.90

    processing

    Processing

Sample data, to illustrate the flow.

How it works. In 3 steps.

  1. 01

    The company is registered once

    Each issuer in the group is registered through the API. The same key serves several companies.

  2. 02

    Issuance is one call

    The API validates the data and returns the invoice identifier with status processing. Processing continues asynchronously.

  3. 03

    Every event arrives by webhook

    Authorization, rejection with the reason, cancellation and correction letter reach the client's endpoint. Documents can be downloaded one by one or in batch.

How it runs through the API. In documented calls.

  1. GET /v1/invoices/product/sent/list

    Docs lists the tax invoices sent in the period.

What stays visible. Set apart for the people who operate.

  • Rejected invoice, with the reason
  • Authorized invoice
  • Cancellation and correction letter

Other cases

“We integrated Open Finance in one sprint. The documentation answers before we need to ask.”
Marina DuarteHead of Engineering, credit fintech
“The reconciliation that took the team two days now runs on its own.”
Rafael AntunesCTO, retail chain

Teams from fintechs, retail and accounting already integrate with Openi.

Request access

Build your reconciliation. With the same calls.

The cases use documented endpoints only. Request access and run the flow with your own operation's data.

Request accessDocumentation