Split payment is triggered by the electronic invoice, not by the card machine. A point-of-sale terminal only executes: the NF-e stamps IBS and CBS per item, a transaction identifier ties that invoice to the payment, and the government's public platform returns the amount to withhold at settlement.
Split payment: the invoice decides, the terminal obeys
Split payment is a settlement step driven by the electronic invoice, not by the card machine, in Brazil's consumption tax model under LC 214/2025. The NF-e declares IBS and CBS per item, a transaction identifier ties that invoice to the payment, and the acquirer consults the public platform to learn how much to withhold.
The chain runs in four steps, and the terminal appears only at the end.
How does the NF-e hold IBS and CBS for each item?
Each NF-e line now carries its own IBS and CBS fields, so the tax amount comes from the invoice rather than from a calculation at the checkout. The specification is the NF-e Technical Note 2025.002, published by the tax administration, which adds IBS and CBS groups computed per item per invoice.
A useful consequence follows: an invoice carries a 44-character access key, a unique identifier for that document. If there is no invoice, there is no key, no lookup and no split.
The transcript's author points readers to Nota Técnica NF-e 2025.002 as the primary document. The legal basis for the consumption taxes themselves is Lei Complementar nº 214/2025, which sets out the IBS and CBS framework.
Treat the invoice as the system of record for tax. Any split implementation that recomputes tax somewhere else will drift from the declared value.
How are the invoice and the payment linked?
The link between invoice and payment is a transaction identifier: a txId for Pix, a control number for cards, and a document key that can travel inside a boleto or a Pix QR code. Whoever issues the invoice performs the linking, not the buyer and not the acquirer.
Two paths exist. You embed the invoice key in the charge itself, so the association exists at authorization. Or you associate it later by registering an event that points the payment at the correct invoice identifier.
The transcript cites event 110300 as the reconciliation hook documented for this purpose. A developer in the comments, identified only as John Kennedy, reported homologating that flow against a bank API, which is a first-hand claim from the video rather than published evidence.
For anyone building this, the practical test is simple: can your system produce the invoice key and the payment identifier within the same reconciliation window, or does it need a manual step?
What does the public split platform do at settlement?
The Plataforma Pública de Split Payment receives the payment identifier at financial settlement and answers with the IBS and CBS amounts to retain. It is the meeting point when the invoicing system and the acquirer belong to different vendors.
The platform is documented at consumo.tributos.gov.br, the address the transcript names as the government hub. Per the LC 214/2025 framework, IBS goes to the state-municipal managing committee and CBS goes to the federal revenue service, with the remainder settling to the seller.
Two modes show up in the material: an online mode that queries in real time for the exact amount, and a simplified mode aimed at retail that withholds an estimated percentage and settles the difference later. The card route is described as a later phase, starting with Pix and boleto.
The acquirer's role reduces to a query and a transfer. If the invoice never existed, there is nothing for the platform to answer.
Settlement timing and the 2027 deadline
The split mechanism is scheduled around the transition to the new consumption tax model in 2027, which is the deadline the transcript repeats for integration work. The public platform's testing and rollout have drawn political attention well before that date.
In October 2026, Capital Aberto reported that a presidential candidate had proposed removing the mechanism from the reform, a proposal that would require legislative approval. Treat that as a political proposal reported in 2026, not as a current change to the documented architecture.
Consultancy guidance published in 2025 already described a gradual implementation and warned that the withheld tax should not be modeled as working capital available for stock or expenses, as Parcon Consultoria notes.
The planning implication is unchanged for now: build against the published specification and track the political track separately.
What happens when a sale is cancelled or refunded?
A cancelled or refunded sale is supposed to return the withheld amount to the supplier under LC 214/2025 and LC 227/2026, and the transcript puts the outer limit at three business days counted in turns. That means a Friday-afternoon cancellation can land on Wednesday.
The trigger is the cancellation or return invoice. Registering it inverts the debit, and the platform reconciles the amount back to the seller without a separate request, according to the transcript's description.
The timing edge cases matter for cash flow modelling: a Monday holiday pushes the return to Thursday, and two consecutive holidays push it to Friday. Those are operational hours, not a guarantee of same-day recovery.
Program against the worst case in the statute and you will not be surprised by a long weekend.
Who actually has to build this?
Developers who already emit invoices are the group most exposed to split payment, because the mechanism only reaches sellers with a fiscal document. Informal vendors selling without an invoice sit outside the chain for now.
The work is architecture, not just configuration. It touches how the invoice is generated, how the payment identifier is captured and stored, and how reconciliation events are emitted when the two arrive separately.
| Situation | Who carries the work | Why |
|---|---|---|
| Invoicing and payment in one integrated stack | The product's own engineering team | The link happens at charge creation |
| Invoice in one system, card terminal from another | Both vendors plus an integration owner | Reconciliation relies on the government platform and event 110300 |
| Seller who issues no invoice | No split at settlement | No invoice means no key and no lookup |
The transcript's broader point about ecosystem change is scoped to formal sellers with invoicing obligations. Anecdotes about local merchants pricing cash discounts ahead of a change that may not affect them are the author's own observation, not adoption data.
FAQ
- Does split payment happen inside the card machine? No. The terminal executes a query at settlement. The tax amount comes from the NF-e's per-item IBS and CBS fields and is returned by the public split platform, not calculated by the acquirer.
- What ties a payment to the right invoice? A transaction identifier: txId for Pix and a control number for cards. The invoice key travels with the charge when possible, or an event such as 110300 links the payment to the invoice afterward.
- How long does a refund take after the tax was withheld? The transcript describes a limit of three business days counted in turns under LC 214/2025 and LC 227/2026. Weekends and holidays extend the calendar date on which the money returns.
- Is the split mechanism certain to launch as documented? As of October 2026 the architecture is documented and a political proposal to remove it has been reported, but any change would need legislative approval. Build against the specification and monitor the political track.
- Do sellers without invoices get split? They sit outside the chain as it is currently documented, because no invoice means no access key and no lookup. That exclusion is a description of the current design, not a permanent rule.
Turning a technical walkthrough into a written reference
A twelve-minute explanation of invoice keys, txIds and reconciliation events is hard to search six months later, and the details that matter to a developer are the ones a transcript skips past.
If that kind of explanation already exists in one of your videos, Skala Blog turns the YouTube URL into a transcription and then into an article you can review and edit.
Skala Blog is the publishing step, not a substitute for the documentation itself.