Why Cash Flow Visibility Software Runs Hours Behind the Bank
Cash flow visibility software can show nothing newer than the bank's last report. How balances age, which status to trust, and what a stale number costs.
Cash flow visibility software shows where a company’s cash is, but every balance on its screen is a report the bank produced earlier, with a particular status. Bank formats and payment rails set that age and status; the dashboard cannot. Judge the software by the oldest balance it relies on, and close the gap with payments already scheduled.
The industry’s own file standard is candid about it. In BAI2, the format banks use to report balances to corporate treasurers, the field for the hour at which a balance was current is marked “For reference only. Optional.” (BAI, 2005). Plaid, an aggregator that links finance apps to bank accounts, checks for new transactions “typically between one and four times per day, depending on the institution” (Plaid). What follows sets out how old a balance can be and which balance it is, then prices a stale one on a single Tuesday.
Cash flow visibility software can show nothing newer than the bank’s last report
Each BAI2 file carries an as-of date and a modifier with four values, interim or final and previous-day or same-day. Final data describe the close of business on that date; interim data “may not reflect all activity” on it.
The other standard, ISO 20022, draws the same line. Its end-of-day statement, camt.053, reports “the entries booked to the account”, while the intraday report, camt.052, can be used to “report pending and booked items” (ISO 20022 definitions).
Finance apps that reach the bank through an aggregator see a third cadence. Plaid’s documentation says data from its free accounts endpoint “is cached, making it unsuitable for situations where you need real-time balance information”, and that cached balances may update “once a day or more”. A live balance costs a separate, billed call, answered in about 3 seconds at the median and 11 seconds at the 95th percentile (Plaid, Balance).
The age of a balance is the time between its as-of time and the decision that relies on it, and it grows hour by hour until the next report arrives. With one aggregator check a day, a balance is on average 12 hours old and at worst 24; with four evenly spaced checks, 3 and 6 (ignoring delivery delays). In cash flow visibility software, a consolidated position is as old as its oldest balance. Reloading a dashboard does not make it younger, and only a new report from the bank does.
hours behind = time of decision − as-of time of the oldest balance in the position
Age has one limit that matters for cash. It says how long the company has been uninformed and nothing about how wrong the number is: a balance nothing has touched since the report is old and still correct. Whether it is wrong depends on which balance was reported and on what settled in between.
A current balance can still be the wrong one to spend
BAI2 defines several balances for one account on one day. There are opening, closing and current ledger balances (type codes 010, 015 and 030), opening, closing and current available balances (040, 045 and 060), and one-day and two-or-more-day float (072 and 074) (BAI, 2005). The ledger balance counts what the bank has posted. The available balance, in Plaid’s words, “represents predicted balance net of any pending transactions”, and it is the one that pays bills. Plaid reports typical fill rates of 99% for the current balance and 91% for the available balance; on its own figures, roughly one balance in eleven arrives without the number a payment depends on.
The law limits the gap between the two. Under Regulation CC, a bank must make an electronic payment available “not later than the business day after the banking day on which the bank received the electronic payment”. It has received the payment only once it holds “actually and finally collected funds” (12 CFR 229.10). Nacha’s rules are tighter for Same Day ACH. Credits must be available by 5:00 p.m. in the receiving bank’s local time, or by the end of its processing day for the third window. Credits from the first window must be available by 1:30 p.m., a rule in force since September 2019 (Nacha). A company that spends its ledger balance is betting that what has posted will also be collected, and when that bet fails the bank settles it with a returned payment or an overdraft.
The payment rails decide when a balance can change
ACH settles in batches at set times. Same Day ACH, launched for credits in September 2016, settles in three windows: files submitted by 10:30 a.m. ET settle at 1:00 p.m., files submitted by 2:45 p.m. settle at 5:00 p.m., and since a third window opened on 19 March 2021, files submitted by 4:45 p.m. settle at 6:00 p.m. (Nacha, 2018; Nacha, 2021). The network carried 1.4 billion same-day payments in 2025, and 403 million worth $1.1 trillion between January and March 2026 (Nacha).
Fedwire, the Federal Reserve’s wire service, keeps business hours. Its funds-transfer business day “begins at 9:00 p.m. ET on the preceding calendar day” and ends at 7:00 p.m., 22 hours in all, and customer transfers stop at 6:45 p.m. (Federal Reserve Financial Services). On Fedwire, Monday begins at 9:00 p.m. on Sunday.
FedNow, the Fed’s instant-payment service, went live on 20 July 2023 with 35 early-adopting banks and credit unions, for transfers “any time of the day, on any day of the year” (Federal Reserve, 2023). Adoption is still small by count. FedNow settled 2.7 million payments in those same three months of 2026, about 148 Same Day ACH payments for every FedNow payment (our arithmetic). By value the ratio is about 4 to 1, because FedNow’s average payment in that quarter was $99,414 against about $2,730 for Same Day ACH (our arithmetic; FedNow statistics).
For a company paid mainly by ACH, the balance therefore moves in steps at a few known times, and wires move it only within Fedwire’s hours. The reads that count come just after each settlement and before each cutoff. Instant payments are the exception, since they can land at any hour, and a company that receives many of them has to look more often.
A stale balance can be wrong in either direction
A hypothetical Series A software company has one operating account. Its bank’s final previous-day report is taken as of 19:00 on Monday, when Fedwire closes, and its finance app last refreshed through an aggregator at 08:00 on Tuesday. At 14:00 the founder must decide whether to wire $210k to a supplier and make a $95k payroll-tax deposit through EFTPS before the 15:00 same-day cutoff: $305k in all. A federal tax deposit made 1 to 5 days late costs 2% of the amount, and 5% at 6 to 15 days (IRS, Publication 15; IRS, failure to deposit penalty).
One Tuesday at a hypothetical startup: two stale views err in opposite directions ($ thousands)
| Time | Event at the bank | Available balance | Prior-day report shows | Aggregator shows |
|---|---|---|---|---|
| Mon 19:00 | Final previous-day close | 480 | 480 | 480 |
| Tue, before 08:00 | Payroll provider’s debit for Wednesday’s payroll posts | 220 | 480 | 480 |
| 08:00 | Aggregator refreshes | 220 | 480 | 220 |
| 09:00 | Card processor’s payout arrives | 255 | 480 | 220 |
| 13:00 | Customer’s Same Day ACH credit settles in the first window | 375 | 480 | 220 |
| 14:00 decision | $305k to pay: what each view says | $70k to spare | $175k to spare | $85k short |
| Age of the balance shown, at 14:00 | Current | 19 hours | 6 hours |
Hypothetical company; balances and ages follow from the events listed. Settlement and cutoff times from Nacha and IRS Publication 15.
The prior-day report approves both payments for the wrong reason, since it has not seen the payroll debit. The aggregator blocks one of them for the wrong reason, since it has seen the debit but not the money that came in afterwards. If the founder trusts the aggregator and holds the tax deposit until Wednesday, the IRS charges 2% of $95k, or $1,900. Had the customer’s payment been sent in the third window instead, settling at 18:00, the account would hold $255k at 14:00. The prior-day view would still show $480k and approve $305k of payments, $50k more than the account holds.
Neither error needed a faster feed to avoid it. The payroll debit, the card payout and the customer’s payment were all known before Tuesday began, each with a rail and a settlement time. Applied to the freshest final balance, that schedule gives $375k at 14:00 and shows that $120k of it depends on the 13:00 settlement having happened. Age tells the company how long it has been uninformed; only the schedule tells it in which direction.
Does a startup with one bank need intraday data at all?
BAI’s own specification makes the case against. It observes that “When a company uses the services of only a few banks, telephone notification usually meets the treasurer’s needs” (BAI, 2005). A seed-stage company with one bank, one entity and two years of runway is that company, and on most of its days the morning report and a list of scheduled payments do meet the need without cash flow visibility software. Continuous feeds would cost money, since every live balance call is billed, for little return.
The days that matter are few and dated: a payroll-tax deadline, a large wire, a customer payment the plan depends on. On those days the question is the age and status of one balance at one hour, which a prior-day report cannot answer. The cheap fix is a habit: read the available balance after the relevant settlement and before the cutoff, and leave it alone for the rest of the day.
Cash flow visibility software is therefore only as fresh as the bank’s last report and only as right as the balance that report gives. A company that records each balance’s as-of time, spends the available balance and keeps a schedule of known flows against its cutoffs sees its cash as well as the rails allow. On the hypothetical Tuesday, that schedule applied to Monday’s final balance gave the true $375k at 14:00, where a 6-hour-old aggregator balance showed $220k and an $85k shortfall.
Sources and notes
- BAI (2005). Cash Management Balance Reporting Specifications Version 2: Technical Reference Manual. Chicago: BAI.
- Board of Governors of the Federal Reserve System (2023). Federal Reserve announces that its new system for instant payments, the FedNow Service, is now live. Press release, 20 July 2023.
- Federal Reserve Financial Services. Fedwire Funds Service operating hours; FedNow Service volume and value statistics, updated 6 July 2026.
- Federal Reserve System. 12 CFR 229.10 (Regulation CC), via eCFR.
- Internal Revenue Service. Publication 15 (2026), Employer’s Tax Guide; Failure to deposit penalty.
- ISO 20022 message definitions for camt.052 and camt.053, as reproduced by iso20022ref.com.
- Nacha. Same Day ACH; Same Day ACH: Moving Payments Faster (Phase 3); Expanding Same Day ACH (effective 19 March 2021).
- Plaid. Transactions and Balance documentation.
Formats, rules, cutoffs and payment volumes come from the standards bodies, regulators, Nacha and the Federal Reserve as listed, and Plaid’s refresh and fill rates are its own documentation. Ratios, ages of balances and totals shown without a citation are derived from the figures above. The company in the Tuesday table is hypothetical, and times are US Eastern unless stated.
More in Cash & Treasury Management
Treasury Management Software: Where a Startup's Cash Is Held
Treasury management software for startups, compared: Mercury, Brex, Rho, Ramp and five TMS vendors, judged as treasurers rank them: safety, liquidity, yield.
How Much to Hold and Where to Park Idle Startup Cash
Where to park idle startup cash: hold runway to the next milestone plus a raise, fence the surplus, then choose each home by its exit on a bad day.
Is Your Cash Position the Number on the Bank Statement?
Your cash position is four balances: book, ledger, available and free. Holds, cut-offs, restricted cash and covenants split them; spend only the smallest.