On 5 December 2025, Brazil’s instant payment system cleared 313.3 million transactions and R$179.9 billion in twenty-four hours — a single-day record, according to Banco Central do Brasil figures. Pix closed the year at 79.8 billion transactions and R$35.4 trillion, roughly three times Brazilian GDP.
That statistic travels well. This one doesn’t: the Sistema de Transferência de Reservas, which settles TED and interbank obligations, was shut on 13 days in 2026 and runs 6h30 to 18h30 Brasília time on the days it opens, with a 17h30 cut-off for anything touching a client account.
Both facts describe the same financial system on the same afternoon. Every platform operating in Brazil is running two clocks at once, and the space between them is where money and compliance quietly break.
Two rails, two calendars
| SPI (Pix) | STR (TED, interbank) | |
| Availability | 24 hours, every day of the year | Business days only |
| Window | Continuous | 6h30–18h30 (Brasília) |
| Client cut-off | None | 17h30 |
| Settlement | RTGS — definitive, irrevocable, unconditional | RTGS |
| Days closed in 2026 | 0 | 13 national banking holidays, plus weekends |
Article 8 of the SPI rulebook puts it plainly: the system is available to participants for settling credit orders twenty-four hours a day, on every day of the year. On the primary channel, a Pix that fails to settle within 40 seconds is rejected.
The STR carries a different sentence: available on days considered business days for national financial system operations.
Boleto and card money moves on the second clock. Boleto credits typically land one to three business days after payment; card receivables land roughly thirty days after the sale, and only on a day the rail is open. A sale on Friday 13 February 2026 was not cash on Carnival Monday, no matter what the merchant dashboard implied.
What Brazil actually closed in 2026
Resolução CMN nº 4.880/2020 sets the definition: Saturdays, Sundays and national holidays are not business days for financial market operations or for reporting to the Central Bank.
FEBRABAN’s 2026 calendar produced 13 national banking holidays: 1 January, 16 and 17 February (Carnaval), 3 April, 21 April, 1 May, 4 June, 7 September, 12 October, 2 November, 15 November, 20 November and 25 December.
Four details in that list break naive implementations.
Three of those dates are computed, not fixed. Good Friday, Corpus Christi and Carnival are all derived from Easter. They move every year. A hardcoded array is correct for twelve months and wrong afterwards, silently.
18 February was a business day with a half schedule. On Ash Wednesday, branches opened at 12h local time. Where branches normally close before 15h, opening was brought forward to guarantee three hours of service. It counts as a business day. It does not behave like one.
31 December was not a holiday and had no public banking service. Only interbank operations and clearing ran. Any system that derives “closed” from a holiday table missed it entirely.
15 November fell on a Sunday. Thirteen holidays cost twelve weekdays that year. Capacity and cash-flow models that subtract 13 were off by one — in the wrong direction, all year.
There is also 9 July, the Revolução Constitucionalista, a São Paulo state holiday. Banks in the state close. B3 trades normally. National and subnational calendars do not agree, and neither one is the calendar.
The field that proves the regulator saw this coming
Pix Automático is now live across Pix participants; institutions had until 1 January 2026 to migrate existing automatic-debit authorizations. Every Pix participant offering transactional accounts must support it on the paying side.
Its authorization message, pain.012, carries a mandatory field called codMunIBGE — the IBGE code for the payer’s municipality.
The Central Bank’s participant FAQ explains the purpose: the code is needed to calculate the payment date in case the original date coincides with local holidays. Where the paying PSP doesn’t hold the information, the field is transmitted as 0000000.
Brazil built a municipality identifier into its instant-payment protocol so that a recurring debit can be moved off a city-level holiday. That is the level of precision the domestic rulebook operates at, and it is roughly six levels below where most cross-border integrations are built.
The rules a recurring debit actually obeys
From the BCB FAQ and Instrução Normativa BCB nº 513/2024:
The receiver decides whether the debit may fall on a non-business day. The receiving PSP may shift it to the next business day, and that adjustment must account for weekends, national holidays and the local holidays of the payer’s banking domicile. If the receiver chooses not to shift, it must be able to show legal grounds for charging on a non-business day.
The date can only move forward. Under art. 5 §§5–6 of IN BCB 513/2024, the settlement date must correspond to the charge’s due date. The single permitted exception is moving to the first following business day. Pulling a due date back to the preceding Friday is not available, however sensible it looks in a product spec.
Instructions ship between 10 and 2 days ahead of the expected settlement date. Nothing earlier, nothing later, outside defined exceptions.
There are two mandatory settlement windows: 00:00–08:00 and 18:00–21:00. A charge that fails the first window gets a compulsory evening retry the same day. Attempts across the following seven days happen only if the authorization provided for them.
A refused authorization cannot be re-offered for 30 dias corridos — calendar days, in the same rulebook that computes payment dates in business days. The two conventions sit in adjacent paragraphs.
The Central Bank names the specific failure mode. If the due date is the last day of the billing cycle and that day is a municipal holiday where the payer banks, the business-day adjustment pushes settlement into the following cycle — and no other charge can settle in that cycle. One city holiday, one skipped month of revenue, no error thrown.
The legal layer: a grace period that isn’t one
Article 1 of Lei nº 7.089/1983 bars banks and financial institutions from charging default interest on instruments maturing on a Saturday, Sunday or holiday, provided the debt is settled on the first following day. Breach triggers the penalties in art. 44 of Lei nº 4.595/1964.
Most collections logic reads that as an unconditional one-day grace. The Third Panel of the Superior Tribunal de Justiça closed that reading in REsp 1.954.924: where payment is not made on the first following business day, the protection falls away and default interest runs from the original due date.
The rollover is conditional on performance. A dunning engine that anchors on the adjusted date over-credits paying customers and understates balances on the ones who didn’t pay — the exact population where the number matters.
Spain runs the same problem in reverse
| Brazil | Spain | |
| Commercial payment terms | Practice varies; settlement on dias úteis | 30 días naturales default, 60 ceiling |
| Governing text | Res. CMN 4.880/2020 | Ley 3/2004, amended by Ley 15/2010 |
| Administrative deadlines | Counted in dias úteis | Días hábiles, Saturdays excluded |
| Settlement system closures, 2026 | 13 | 6 (TARGET) |
Spain fixes B2B payment terms at 30 días naturales from receipt of the invoice or delivery, extendable by agreement to a hard ceiling of 60, and 30 with public administrations. The law defines the payment term by reference to all natural days of the year. Agreements above the ceiling are void and replaced by the statutory term.
Default interest accrues on its own. Article 7 sets it at the ECB main refinancing rate plus eight percentage points, republished in the BOE every six months. For the second half of 2026, the ECB rate stood at 2.40%, putting the statutory rate at 10.40%. No reminder, no formal notice — non-payment alone starts it.
Then the inversion. Article 30.2 of Ley 39/2015 provides that where an administrative deadline is set in days, those days are hábiles, with Saturdays, Sundays and public holidays excluded. The same Spanish company therefore counts its supplier invoice in calendar days and its filing deadline in working days, under two statutes that were never designed to be read together.
Article 30.6 sharpens it further: where a day is hábil in the interested party’s municipality but inhábil at the seat of the administrative body, or the reverse, it is treated as inhábil. The stricter of two local calendars governs.
On the settlement side, the euro area is far calmer. TARGET closed on six days in 2026: 1 January, Good Friday (3 April), Easter Monday (6 April), 1 May, 25 December and 26 December. TIPS, the instant-payment service, keeps running through all of them. Same architectural split as SPI and STR, at less than half the holiday count.
Mexico supplies a third pattern
The CNBV list of non-business days for 2026, published in the Diario Oficial de la Federación and mirrored by the Asociación de Bancos de México: 1 January; the first Monday of February; the third Monday of March; 2 and 3 April; 1 May; 16 September; 2 November and the third Monday of November; 12 and 25 December; plus Saturdays and Sundays.
Note 12 December. It is a banking non-business day and it is not a public holiday under Mexico’s Federal Labour Law. Sourcing your Mexican calendar from labour law gives you the wrong answer once a year.
The rule most cross-border teams never reach sits in article 3 of the same publication: an institution that does open on one of those days must book the operation with value date on the next banking business day whenever settlement runs through the country’s payment system. Opening the doors does not open the rail.
Treat the calendar as a dependency, not a constant
The recurring error in payment systems is architectural rather than arithmetic. Business-day rules get written into application code as constants — a weekday check, a static holiday array, a +30 — when they are volatile third-party data with a legal effect and a per-country release cycle.
What that means in practice:
Store the calendar, don’t compute it. Easter-derived dates, half-days like Ash Wednesday, and non-holiday closures like 31 December cannot be derived from rules a developer can hold in their head.
Split the two questions. “Is the obligation counted in business days or calendar days?” is a legal question. “Can the rail move money today?” is an operational one. Brazilian card receivables answer the first with calendar days and the second with business days on the same transaction.
Carry the payer’s location. Brazil made this a protocol field for a reason. If your recurring-billing schema has no place for the payer’s municipality, you cannot implement the domestic rule correctly, whatever your date library does.
Most teams end up maintaining a small internal calendar service, then checking its output against an independent reference before trusting it in production. Contar Dias works well as that second opinion for these markets: it separates dias úteis from dias corridos and carries national holiday sets for Brazil, Spain, Mexico, Colombia, Argentina and Chile, so you can diff its answer against your own logic when a settlement window lands on Corpus Christi or a due date falls inside Semana Santa.
Log which rule fired. When a customer disputes an interest charge two years later, “the system adjusted it” is not a defence. “Adjusted to the next business day under the local calendar of municipality X, per the authorization terms” is.
Test the ugly weeks. Carnival week in Brazil, Semana Santa across Iberia and Latin America, and the last week of December. Three test fixtures cover most of the annual damage.
Three questions that surface in every integration review
If Pix runs on holidays, why does the calendar still matter?
Because Pix is one rail. Boleto, TED, card settlement, interbank clearing and B3 all run on the FEBRABAN business-day calendar. Instant collection with business-day payout is a treasury problem, not a solved one.
Can we normalise everything to calendar days and simplify?
No. Brazilian financial market operations are legally defined against business days, and Spanish administrative deadlines against días hábiles. Normalising to calendar days doesn’t remove the rule, it just moves the error somewhere it won’t be caught until an audit.
Does a due date on a holiday automatically extend?
In Brazil, under Lei nº 7.089/1983, only if the debt is actually settled on the first following day. The STJ has held that where it isn’t, interest runs from the original due date. The extension is conditional, and billing systems routinely model it as unconditional.
The point
Instant settlement is the part of Brazilian payments that gets written about. Business-day settlement is the part that decides whether Tuesday’s revenue arrives, whether the interest charge holds up, and whether a recurring debit skips a month because of a city holiday nobody put in the database.
Pix runs continuously. Almost nothing around it does.
