Juneteenth tested how many calendars a bank really runs

The week

On the evening of Tuesday, June 15, 2021, the Senate passed a bill by unanimous consent to make June 19 a federal holiday. The House passed it the next afternoon, 415 to 14. On Thursday, June 17, President Biden signed it into law. Juneteenth National Independence Day became the first new federal holiday since Martin Luther King Jr. Day was created in 1983.

The day commemorates the end of slavery in the United States. It marks June 19, 1865, when Union troops in Galveston, Texas, announced that enslaved people there were free. Texas had made it a state holiday in 1980, and many other states already recognized it in some form. The federal law did something narrower and more mechanical. It added a line to the list of legal public holidays in Title 5 of the US Code, the list that governs federal employees.

The calendar created an immediate practical puzzle. June 19 fell on a Saturday in 2021. Under federal leave rules, when a holiday falls on a Saturday, federal employees generally observe it on the Friday before. So most of the federal workforce took Friday, June 18 off, the day after the signing. Most changes in banking arrive with months or years of warning. This one arrived overnight.

For most employers, a surprise day off is a scheduling question. For a bank, a holiday is something more. The Federal Reserve runs the core plumbing that moves money between banks, including the systems that settle payroll deposits, bill payments and large wire transfers. When the Fed is closed, much of that money simply does not move. Thousands of computer systems across the industry count “business days” to decide when a payment lands, when a deposit becomes available and when a bill is due. A new holiday on one day’s notice could, in principle, have thrown those counts off.

The Fed chose a calm path. The Board of Governors closed its Washington offices on June 18. Its financial services, the payment and settlement systems run by the regional Reserve Banks, operated normally on June 18 and June 21. The Fed said it would decide later how to adjust its schedule for the new holiday in the years to come. It first observed Juneteenth in 2022, which gave the payments industry a year to adjust.

That choice also matched a long-standing rule. The Fed’s published holiday policy says that when a holiday falls on a Saturday, the Reserve Banks stay open the preceding Friday, while the Board itself closes. A Saturday holiday never closed the payment system on the Friday before. Juneteenth 2021 simply followed that pattern.

Markets made their own calls. SIFMA, the securities industry association that recommends bond market hours, said it would not recommend a fixed-income close because the holiday fell on a Saturday and Fedwire remained open. On July 14, 2021, it revised its 2022 recommendations to include a full close for Juneteenth. The New York Stock Exchange and Nasdaq stayed open that Friday. The NYSE later amended its rules to make Juneteenth a market holiday from 2022. The Securities and Exchange Commission closed its offices.

Elsewhere, the picture was mixed. Many banks and credit unions remained open. Bloomberg reported that some large firms, including JPMorgan Chase and UBS, gave US employees a floating holiday instead. State and local governments and other employers made their own choices about whether to observe the day. So on that first Juneteenth, the federal workforce was off, the payment system was running, the stock market was trading, and banks were deciding branch by branch and team by team what to do.

The paperwork followed within weeks. In early August, the Consumer Financial Protection Bureau issued an interpretive rule on how the new holiday affected the business-day counts in Regulation Z, the federal rule for consumer credit disclosures. Mortgage rescission periods and closing disclosure waiting periods that straddled June 19 needed an answer. The answer turned on whether a period began before or after the signing on June 17.

Nothing dramatic broke, which is what makes the week worth a second look. It posed a question most financial institutions had never had to answer all at once. When the definition of a business day changes, what inside the organization has to change with it, and who makes sure it does?

Most operational change in financial services comes with long notice. New regulations have comment periods, new payment rules have implementation dates, and new products have launch plans. Juneteenth was an exception: a new federal holiday enacted on a Thursday and observed by the federal workforce on the Friday.

The Federal Reserve’s decision to keep its services running in 2021 prevented immediate disruption. It did not spare institutions the question they then faced for 2022: what does adding a holiday touch? The honest answer surprised many leadership teams. A business day is defined in at least three places, each usually owned by a different team: the payment rails, customer commitments and the workforce. Juneteenth showed how rarely the three are managed together.

We start with the mechanism all three share, the holiday table. We then take each calendar in turn. Two issues cut across all three: who owns the calendar, and the calendars hidden inside vendors’ software. We close with the habits that absorbed the change smoothly and a short test for the next surprise.

A day off is a line in a table

To a customer, a holiday means the branch is closed. To a bank’s systems, a holiday is a piece of data. Somewhere inside almost every financial application is a list of dates on which it should not count a day as a “business day.” Engineers call this a holiday table or a business calendar. It is about as glamorous as a wall calendar in a break room, and it is just as easy to forget to update.

Those lists matter because so much of banking is counting. A payroll deposit is due to arrive on a particular day. A check deposit becomes available after a set number of business days. A customer has a set number of business days to dispute an error, and the bank has a set number of business days to respond. A loan payment due on a holiday may roll to the next business day. Each of those rules depends on a computer knowing, correctly, which days count.

A bank may have dozens of these lists, kept by different departments and different vendors. If one is set differently, the handoffs between systems go wrong, even though each system believes it is on time. A new holiday is the moment everyone discovers how many there are.

How the counting works

Most systems answer two questions with the table. The first is “add N business days to this date.” The second is which day to use instead when a date is not a business day. That question has several standard answers. A payment can roll forward to the next business day, roll back to the previous one, or roll forward unless that crosses into a new month. Loan and capital markets contracts name the convention they use, and different products in the same bank often use different ones.

The table itself is usually a list of specific dates, not a rule. Many systems are loaded each autumn with the coming year’s holidays, sometimes by a vendor and sometimes by an operations analyst typing them in. A holiday created in June falls outside that annual routine. It has to be added mid-year, to a list that may already have been loaded for the next year as well.

Not one kind of day, several

The vocabulary matters because the rules use it precisely. A calendar day is any day. A business day is defined differently by different rules, as later sections show. A banking day, in Regulation CC’s terms, is the part of a business day on which a bank office is open for substantially all of its banking functions. A Fed processing day is a day the Reserve Banks run a given service. A market day is a day an exchange trades.

A single holiday can turn some of these off and leave others on. Systems that store only “holiday: yes or no” lose that distinction at the moment it matters. Cutoff times add a further layer. The Fedwire Funds Service’s business day, for example, opens at 9:00 p.m. Eastern time on the previous calendar day and closes at 7:00 p.m. A late-evening wire request can belong to the next business day even when the calendar date has not changed.

Calendars from other countries

Institutions with international business carry still more tables. Correspondent banking, foreign exchange and cross-border wires depend on the holidays of every currency and market involved. A US holiday leaves European and Asian markets running. A bank that settles euro or sterling payments must know both calendars and how they combine. A new US holiday is one more date in a matrix that already has many.

The Fed’s calendar sets the pace for payments

Payment rails are the shared networks that move money between banks, much as railroad tracks carry trains between cities. Two of the most important in the United States are run by the Federal Reserve. Fedwire handles large, urgent, individual transfers, such as the funds for a house closing. FedACH handles the Automated Clearing House, or ACH, which processes huge batches of routine payments: direct-deposit payroll, Social Security payments, utility bills and mortgage autopays. Settlement is the moment money actually changes hands between banks, as opposed to the moment someone presses “send.”

For payment operations, the governing calendar is the Federal Reserve’s. Fedwire and FedACH processing days determine when funds move, when ACH entries settle and when returns are due. When the Fed adds a holiday, every system that calculates settlement dates must know. That includes the core banking platform, which is the central system of record that keeps every customer’s balance and transaction history, a bank’s master ledger. It also includes ACH origination software, wire systems, card settlement processes, loan servicing engines, and the many vendor systems that compute effective dates.

Holiday tables in those systems are often maintained separately, some by vendors, some by hand. A new holiday reveals how many such tables exist and who updates them. Institutions that found several inconsistent calendars learned something useful about their architecture before it caused a settlement error.

Effective dates and settlement dates

ACH separates two dates that customers tend to treat as one. The Nacha Operating Rules define the effective entry date as the date the originator intends a payment to settle. The settlement date is the date the ACH operator actually settles it. On an ordinary Tuesday they are the same. Around a holiday they can come apart, because the network will not settle on a day it is closed.

The clocks that follow settlement also count in banking days. Under the Nacha rules, deadlines for returning an entry and for notifications of change run a set number of banking days after settlement. A holiday therefore moves more than the payment. It moves the deadline for sending it back. A receiving bank that counts the holiday as a working day can believe it is late when it is not, or on time when it is late.

Suppose a regional bank’s ACH origination platform, the software that builds and sends payment files on behalf of business customers, knows about the new holiday, but its core banking system does not. A business client submits its payroll file. The file carries an effective date, the day the money is meant to land, that the network will not settle because it is now a holiday. The result is confusion at best and late paychecks at worst, plus a stream of calls to the bank’s business banking team.

Who absorbs the shift

Payers move their dates around holidays as a matter of routine. Social Security, for example, pays early when a scheduled payment date falls on a holiday. Many employers and payroll providers move a payday forward when it lands on a bank holiday. Each of those adjustments depends on someone knowing about the holiday in time to pull a file forward. A payroll company that learns of a holiday after its file deadline has fewer good options.

Card settlement follows its own path. Card networks publish their own settlement calendars, and the funds behind card settlement for US banks typically move over Fed services. A card program manager or processor has to reconcile the network’s calendar with the Fed’s. Merchants feel any mismatch as a deposit that arrives a day later than usual.

Why the Fed’s timing mattered, and its limits

The Fed’s choice to defer observance deserves more credit than it got. A closure on June 18 with one day’s notice would have caused real problems. ACH files already sent for that settlement date would have needed holiday handling. Card and payroll processors would have faced shifted settlement, and some workers expecting Friday pay could have waited until Monday. By separating the date the holiday became law from the date the payment system observed it, the Fed gave institutions a year to update calendars, test settlement logic and tell customers.

The strongest counter-argument is that the Fed had little choice to make. Its standing policy already kept the Reserve Banks open on a Friday before a Saturday holiday. In a sense the 2021 outcome was set by the calendar rather than by a decision. The first real test came in 2022, when June 19 fell on a Sunday and the Fed closed on Monday, June 20. That point narrows the credit due to the Fed for 2021. It does not change the outcome for institutions, which still got a year to prepare for the first true closure.

Any operator of shared infrastructure can apply the same rule: set the effective date of a system change by how long participants need to prepare, not by the date of the decision. That principle applies well beyond holidays. A bank that runs a shared platform for its own business lines faces the same choice. So does a state agency that runs a system used by counties, every time it changes something everyone depends on.

Promises to customers run on a different list

The second place a business day is defined is in customer-facing obligations: the promises a bank makes to its customers, many of them written into federal rules.

The best-known example is Regulation CC. It is the federal rule that governs funds availability, meaning how quickly a bank must let a customer use money from a deposited check or other deposit. It applies to depository institutions generally, including banks, savings associations and credit unions. It is the reason a customer can see a deposit on their account but not yet spend all of it. Regulation CC defines a business day with its own list of holidays. As codified in 2024, that list still did not include June 19, even though Federal Reserve Banks close for Juneteenth.

The detail is easy to miss. It means the calendar that governs when money moves between banks and the calendar written into a customer-protection rule are not automatically the same list. They are maintained separately, and they can differ.

Three regulations, three definitions

Regulation CC is one of several rules that count business days, and they do not define the term the same way. Comparing three of them shows why a single “holiday” flag cannot serve them all.

• Regulation CC uses a fixed list of named holidays written into the regulation. A new federal holiday does not join that list until the regulation itself is amended.
• Regulation E, which covers electronic fund transfers and error resolution, defines a business day as any day the consumer’s institution is open to the public for substantially all business functions. That definition follows each institution’s own decision. A bank that stays open on Juneteenth has a business day; a bank that closes does not.
• Regulation Z, for consumer credit, has two definitions. A general one follows the creditor’s own opening days. A more precise one, used for mortgage rescission and certain disclosure waiting periods, excludes the legal public holidays in federal law. That list changed automatically when Juneteenth was signed, which is why the CFPB issued its interpretive rule that August.

So the same Monday could be a business day for one rule, not for another, and dependent on the institution’s own choice for a third. Which rule governs which product is a question for each institution’s counsel. The operational point is simpler. A calendar that cannot tell these apart will get at least one of them wrong.

Other promises with clocks

Regulation CC is not alone. Electronic fund transfer error resolution timelines, loan payment due dates, statement cycles and many account agreements also run on business day counts. So do internal service standards, such as how quickly a dispute is acknowledged. Each of these is a promise with a clock on it, and each clock needs to know which days count.

Under Regulation E, for example, an institution generally has ten business days to investigate a reported error before it must provisionally credit the account to take longer. Whether a holiday counts toward those ten days depends on whether the institution was open. A dispute system configured with the Fed’s calendar, for a bank that stayed open, would give the bank one more day than the rule allows.

These obligations do not automatically move when the Fed’s calendar changes. Systems must calculate availability correctly, disclosures and availability schedules must stay accurate, and service teams must explain why a deposit made on a Friday is available a day later than usual. A customer who deposits a check before a long weekend and finds the money unavailable on Tuesday is not interested in which list of holidays the bank was using. They want the bank to have been right and to have told them in advance.

How it differs by type of institution

The mix of clocks depends on the business. A community bank or credit union lives mainly with funds availability, Regulation E disputes and loan due dates. A mortgage lender, bank or nonbank, lives with Regulation Z rescission and disclosure timing, where a miscounted day can delay a closing. A broker-dealer settles securities on the market calendar, which since May 2024 has meant one business day after the trade for most US securities. A market holiday the broker’s systems miss can push a settlement into a day the market treats as closed.

A fintech that offers accounts through a partner bank inherits several calendars at once. Its customer promises run partly on the bank’s opening days, partly on the processor’s calendar and partly on the card network’s. Each of those may have been updated by a different company on a different day.

Exactly which rules and agreements apply is a question for each institution’s lawyers. Customer commitments run on calendars written into regulations and agreements, and those can drift away from the payment calendar without anyone noticing until a holiday exposes the gap.

A practical control is a dependency list. For each customer-facing commitment that counts business days, record which calendar it uses and which system computes it. That list turns a holiday change from a scramble into a checklist. It also helps when examiners ask how the institution ensures availability is computed correctly. Bank examiners, the regulators who periodically review a bank’s operations, tend to be more reassured by a clear, maintained list than by confident verbal assurances.

Who works on a day the Fed is closed

The third calendar is the institution’s own. Whether branches and call centers open on a holiday, whether staff get the day off, and whether operations teams work to handle exceptions are each institution’s decisions. In 2021, many banks stayed open. From 2022, institutions had to decide whether to close branches when the Fed was closed, how to staff operations for international payments and fraud monitoring, and how to tell customers or members.

The industry already had experience with this split. Some institutions stay open on other Fed holidays, such as Columbus Day or Veterans Day, while others close. Juneteenth added one more day on which each institution had to choose, and on which customers would find different answers at different banks.

The choices behind “open” or “closed”

The decision is rarely binary. An institution can close branches but keep the contact center open. It can open branches with a reduced set of services. It can give staff a floating holiday, as some large firms did in 2021, and keep operations running. Each option has a cost in holiday pay or overtime, and each sends a signal to staff and customers.

These human resources and operations decisions interact with the other two calendars in ways that are easy to overlook. A branch open on a day the Fed is closed takes deposits that will not be credited until the next business day, which customers may not expect. Front-line staff need a simple, accurate explanation ready, or they will improvise one. Under Regulation E’s definition, an institution that opens for substantially all functions on that day also creates a business day for its own dispute clocks.

Coverage the rails still require

Staffing for operations teams has to reflect what the rails will and will not do. International payments may still be arriving from countries that do not observe a US holiday. Fraud teams need coverage on days when card and instant payment activity continues even though settlement does not. Criminals do not take federal holidays off, and a thinly staffed fraud desk on a slow day is an invitation.

Treasury and liquidity teams also need a plan. A bank that knows the Fed is closed on Monday must fund its positions on Friday for three days of card activity and customer withdrawals. Business clients with sweep accounts or daily cash concentration need to know what will and will not run.

The workforce calendar has its own systems. Time-and-attendance and payroll platforms carry holiday tables that set holiday pay and overtime. Scheduling tools for contact centers forecast volume around holidays. These are usually owned by human resources, not by operations, and they are rarely part of the payment calendar’s change process.

Meaning as well as logistics

A new holiday that commemorates the end of slavery carries meaning for employees. How an institution decides to observe it, and how it explains that decision, says something about its culture. The operational and the human decisions are made by different people, but staff experience them as one decision. An institution that closes branches but asks operations staff to work, for good reasons, should say so plainly and explain how those staff will be recognized.

Time is configured data: the ownership question

Behind all three calendars sits an ownership question. Time in financial services is configured data. A holiday is a parameter, a setting, that drives settlement, compliance and staffing logic across dozens of systems.

Institutions that keep one authoritative, version-controlled business calendar, distributed to every system and vendor that needs it, absorb a change like Juneteenth with a routine update. Version-controlled simply means every change to the calendar is recorded: who changed it, when, and why, with the ability to see exactly what it said on any past date. That history is valuable when a customer or examiner asks why a payment was handled the way it was a year ago.

Running one authoritative calendar requires a named owner who knows which systems depend on the calendar and is accountable when a change is announced. In many institutions in 2021, that role did not exist. Payments owned the payment calendar. Compliance owned the regulatory timelines. Human resources owned the staff holiday schedule. Vendors owned whatever was inside their software. Nobody owned the whole.

Take a credit union in the summer of 2021 whose payments manager hears about the new holiday and updates the ACH software. Its human resources team announces a paid holiday for staff in 2022. Its card processor, a vendor, updates its own systems on its own schedule. Its loan servicing platform, from another vendor, is not updated until a member complains that an autopay was drafted on the wrong day. No one did anything wrong individually. The gap was that nobody was responsible for asking, “Which of our systems count business days, and have they all been told?”

What the owner actually does

The role is small but specific. The owner watches the sources that can change a calendar: the Fed’s published holiday schedule, Nacha, SIFMA’s market recommendations, the exchanges, federal and state legislatures, and the institution’s own human resources decisions. When one changes, the owner updates the master calendar and records why. The owner then notifies each consuming system and vendor, collects confirmation that the update was applied, and keeps that evidence.

Where the role sits matters less than that it exists. Operations risk, payments operations and enterprise architecture are all reasonable homes. The owner needs authority to ask a business line or vendor to confirm a change, and a route to escalate when one does not.

The trade-off in centralizing

A single calendar has a cost that its advocates sometimes skip. If every system reads the same table, one wrong entry propagates everywhere at once. A typo in a central calendar can do more damage than a stale local copy. Some institutions also cannot connect older systems to a central service at all.

Two practices reduce the risk. The first is staged rollout: update the master, test with sample transactions across the affected dates, and then release to consuming systems. The second is reconciliation. Where local tables must remain, the owner compares each one against the master at least once a year, and after every change. A federated model with regular reconciliation is a reasonable middle course for institutions with older platforms.

The evidence an examiner would expect

When a holiday changes, the record that shows control is modest. It includes the change request and its source, the date the master calendar was updated, the list of consuming systems and vendors notified, their confirmations, and the test results for transactions spanning the date. An institution that can produce that file in an afternoon has a working control. One that has to reconstruct it from emails does not.

The calendars inside vendors’ software

Much of a modern bank’s technology is not built in-house. Core banking, card processing, online banking, loan servicing and payment software are frequently supplied by outside vendors, and each may carry its own holiday table. That makes the calendar question partly a contract question. When a new holiday is announced, the vendor may update its calendar automatically, wait for the client to request a change or leave the client to configure it. Either way, someone at the institution has to confirm that the update was made.

Leaders sometimes assume that because a function is outsourced, its risk is too. Regulators take the opposite view: the institution remains responsible for the outcomes its vendors produce on its behalf. A short, standing request to each critical vendor, asking how they handle calendar changes and what notice they need, costs little and closes a gap many institutions only discover after an error.

Hosted, licensed and configured

The answer depends on how the software is delivered. A hosted core or card processor usually maintains one calendar for all clients and publishes a holiday processing schedule. A licensed system the institution runs in its own data center usually leaves the table to the institution. Many products sit between the two: the vendor ships a default calendar, and each client can override it. Overrides made years ago, by staff who have since left, are a common source of drift.

Vendor assurance reports can help, within limits. A SOC 1 report describes a service provider’s controls over processing that affects clients’ financial reporting. Whether calendar maintenance is among the controls tested varies by provider. Asking the question, and reading the answer in the report, is cheaper than discovering the gap in production.

What to put in the contract

Useful terms are short. They state which party maintains each calendar and how quickly the vendor will apply a new federal or market holiday. They also say how the vendor will notify the client and what evidence it will provide that the change is live. For a hosted service, the contract can also require advance notice of the vendor’s own holiday processing schedule each year. These terms are not unusual, and most vendors will agree to them if asked.

Five habits that close the gap

The institutions that absorbed the change smoothly tended to share five inexpensive habits:

• One source of truth. A single business calendar, owned by a named person or team, with every change logged.
• A known list of consumers. A maintained inventory of every internal system and vendor that uses business-day logic, and how each receives calendar updates.
• Clear distinctions. The calendar records which kind of day it is, rather than “holiday or not”: Fed closed, markets closed, branches closed, regulatory business day or not. As Juneteenth showed, these are different questions with different answers.
• Testing before the date. When a new holiday is added, payment and availability logic is tested with sample transactions that span the date, well before it arrives.
• A customer script. Front-line and call center staff get a plain explanation of what changes and why, before customers start asking.

What each habit costs

None of the five requires a large project, but each takes some effort. The single calendar needs an owner’s time and, ideally, a simple service or file that systems can read. The inventory takes a few weeks to build the first time, mostly by asking each system owner and vendor one question. Recording kinds of day means changing a yes-or-no field into several fields, which some older systems cannot hold. In that case, the master calendar keeps the detail and each system receives the simplified view it can use.

Testing is the habit most often cut under time pressure. A useful test set is small: an ACH credit, an ACH debit, a wire, a check deposit, a dispute and a loan payment, each dated across the holiday. The expected results are written down in advance by someone who understands each rule. The customer script is the cheapest of all and is often the most visible to customers.

The usual failures are mirror images of those habits:

• assuming the vendor has handled it without confirming;
• treating “holiday” as one switch, when the payment system, the markets, the regulations and the branches may each be on a different schedule;
• updating systems but forgetting the disclosures and availability schedules that customers read;
• planning staff time off without asking how fraud monitoring and exception handling will be covered;
• discovering the full list of affected systems only after something goes wrong.

Avoiding them takes no large project, only someone who owns the question.

Testing for the next calendar surprise

A leader does not need to understand settlement software to test whether the organization is ready for the next one. Five questions reveal a great deal:

1. How many separate holiday or business-day calendars do we and our vendors maintain, and do we know where each one lives?
2. Who is the single owner of our business calendar, and who do they call when a new holiday is announced?
3. When the Federal Reserve, the stock markets and our branches are on different schedules, does our calendar record that difference, or only “open” and “closed”?
4. For each customer promise that counts business days, such as funds availability, dispute timelines and payment due dates, which calendar does it use and which system computes it?
5. If a holiday were announced with one day’s notice tomorrow, what is the plan, and how long would it take to confirm every system knew?

Good answers will be specific and quick. They will name systems, vendors and people, and they will come with dates. A good answer to the last question is measured in hours, with a list of who confirms what. Vague answers, or answers that begin “I think the vendor handles that,” point to where the work is.

A short tabletop exercise turns the questions into evidence. The calendar owner announces a hypothetical closure for a date two weeks out. Each system owner and vendor contact reports how they would apply it and how long it would take. The exercise takes an hour, and the gaps it finds are usually the same ones a real short-notice closure would find.

With hindsight

The Fed and equity markets first closed for the holiday in 2022. June 19 fell on a Sunday that year, so the Fed, the stock exchanges and the bond markets closed on Monday, June 20. Payments ran smoothly. At the system level Juneteenth was a well-handled change, largely because the industry had a year to prepare. The episode prompted many institutions to inventory and consolidate their holiday calendars, a modest but useful cleanup.

That outcome was not inevitable. The difference between a smooth transition and a messy one was a matter of timing. The holiday became law in one year and was observed by the payment system in the next. The industry used that year to find and fix its scattered calendars. Without it, the same discovery would have happened under pressure, with real payments in flight.

Some of the gaps proved durable. As codified in 2024, Regulation CC’s list of holidays still did not include June 19, and the current published text of its business-day definition still lists the older set of holidays. The regulation and the payment system continue to run on lists maintained by different processes. Institutions that built a calendar able to record that difference were not caught out by it.

Short-notice closures did not end there. The national day of mourning for President Carter in January 2025 was announced about ten days ahead. US stock exchanges closed, bond markets closed early, and Federal Reserve payment services operated normally. The calendars had diverged: markets, bond trading and the payment system each made a different choice on the same day. An institution whose systems could only record “open” or “closed” would have struggled to represent that day correctly.

Planned divergence recurs as well. The Fed’s published holiday schedule lists Friday, July 3, 2026, the day before an Independence Day that falls on a Saturday, as a day the Reserve Banks are open and the Board is closed. The stock exchanges closed that Friday. The same schedule lists Friday, June 18, 2027, when Juneteenth again falls on a Saturday. The 2021 pattern, with markets and federal offices on one schedule and the payment system on another, is now a regular feature of the calendar.

Faster payments have made the picture more complex. The Fed’s FedNow service, launched in July 2023, runs around the clock. It lets banks send money between accounts within seconds, at any hour, on any day. The Reserve Banks moved to seven-day accounting that June so that FedNow activity is recorded on weekends and holidays. Their other services, including Fedwire, FedACH and check, continued to run only on standard business days. Institutions now manage always-on rails alongside traditional settlement calendars.

The next shift is already scheduled. In October 2025 the Fed announced that the Fedwire Funds Service and the National Settlement Service would expand to operate Sunday through Friday, including weekday holidays. The Fed said it expected to implement the change in 2028 or 2029, with use of the added days voluntary. A weekday holiday will then be a day the wire system is open even though the Fed observes the holiday.

Industry rule-makers have started to look at the definitions themselves. In May 2026, Nacha issued a request for information on the meaning of “Banking Day” in its operating rules. It noted that Nacha, The Clearing House and the Federal Reserve Banks use varying definitions of the term. The question Juneteenth raised inside individual institutions is now being asked of the ACH network as a whole.

What held up is the central finding: calendars are infrastructure, even though they are rarely treated that way. What did not hold up is the assumption that a holiday means everything stops. A business calendar now has to say which services run on which days, as well as which days are closed. One with a clear owner, a known list of dependent systems and that level of detail is a small investment. It pays off whenever the schedule changes, with little warning or with years of it.