Tax issuance by CNPJ
Each CNPJ operates under its own tax regime, integrated into the sale, with no separate tax system.
Platform · Management layer
Tax by CNPJ and finance tied to the sale, in the same place.
A chain is many CNPJs, each with its own tax regime, and a register that needs to balance at the end of the day at every location. When tax runs on one system and sales on another, reconciliation becomes manual work that piles up and delays closing.
A tax error is risk and a fine; manual reconciliation is a discrepancy no one audits. And the group's closing waits for each location to close its own, added up in a spreadsheet — late again, and again with no confidence the number is right.
Layer 02
It's the management layer closing the cycle: the sale in the operation generates the tax document and the financial entry, and the result consolidates by CNPJ and by group in the data.
Each CNPJ operates under its own tax regime, integrated into the sale, with no separate tax system.
Each payment received is matched to the order and the capture that generated it.
What the acquirer settles is checked against the sale, transaction by transaction.
The operation's financial routine in the same place the sale happens.
Each location closes its own register; the group reads the consolidated total on the same basis.
Tax and financial data is sent, already structured, to the customer's corporate ERP.
Yes. The chain's hierarchy provides for a tax regime by CNPJ, and issuance follows each one, integrated into the point-of-sale transaction.
No. It covers the tax and financial side of the operation and delivers structured data to accounting and to the corporate ERP, instead of competing for their place.
The acquirer's receivable is checked against the sale that generated it, which makes reconciliation verifiable instead of a manual cross-check of reports.
Talk to a specialist
How many locations, what stack is already running, what needs to be integrated, and what the rollout would look like.