Right now, some of your cash is sitting in the wrong account earning nothing. Maybe it is a payroll account you padded "just in case," a disbursement account holding a cushion against checks that have not cleared yet, or a collections account where customer payments pile up until someone remembers to move them. Every idle dollar is a dollar that is not paying down your line of credit, not earning interest, and not available where you actually need it. A zero-balance account, or ZBA, fixes that by keeping subsidiary accounts at exactly zero and holding all of your cash in one master account — automatically, every night.
How a Zero-Balance Account Actually Works
A ZBA is a business checking account that is designed to end every business day at a zero balance. It never holds money overnight. Instead, it is linked to a master account (sometimes called a concentration account) that holds all of your funds, and the bank moves money between the two automatically.
The daily cycle works in both directions:
- When money goes out. Each morning, checks are presented, ACH debits hit, and card charges post against the ZBA. The bank totals the day's presentments and pulls exactly that amount from the master account into the ZBA to cover them. If Tuesday's cleared payroll checks total $18,432.17, the bank moves precisely $18,432.17 — no cushion, no estimate.
- When money comes in. For a ZBA used on the collections side, customer deposits land in the subsidiary account during the day and are swept up into the master account at the end of the day, returning the ZBA to zero.
- Overnight. The ZBA sits at zero. One hundred percent of your cash rests in the master account, where it can earn interest, offset borrowing, or simply be counted in one place.
Nobody initiates these transfers. Once the structure is set up with your bank's treasury department, the sweeps run on their own. That automation is the whole point: the alternative is a bookkeeper manually shuffling money between accounts every day, which is slow, error-prone, and usually means every account carries a lazy buffer "to be safe."
The Three Jobs ZBAs Do
Most businesses that adopt ZBAs start with one use case and add more. The three classic ones map to the three directions cash moves.
Disbursement ZBAs: paying vendors without parking cash
A disbursement ZBA is the account your vendor payments draw on. You issue checks or ACH payments from it, and the bank funds each day's presentments from the master account. Because funding happens only when items actually clear — not when you cut the check — your cash stays in the master account earning its keep until the last possible moment.
This also gives you a clean separation: one account number that only ever pays vendors, with its own statement and its own audit trail, while the economics all live in the master account.
Payroll ZBAs: isolating your biggest single outflow
Payroll is often a company's largest recurring disbursement, and it deserves its own lane. A payroll ZBA receives exactly the net pay, tax deposits, and benefit contributions for each cycle, funded from the master account on payday. Between paydays it holds nothing.
The isolation matters for control. If a payroll account number is ever compromised, the exposure is limited to whatever is mid-flight on that day's cycle — there is no standing balance to drain. And when auditors or lenders ask for payroll records, everything sits in one dedicated statement instead of scattered through your operating account.
Collection ZBAs: concentrating what comes in
On the receipts side, ZBAs work in reverse. A business with multiple locations, lockboxes, or payment channels can give each one its own collection ZBA. Customer payments land locally during the day, then sweep up to the master account each night. A retailer with five stores sees five clean deposit streams for reconciliation purposes, while the cash itself consolidates into one balance it can actually deploy.
ZBA vs. Sweep Account vs. Target-Balance Account
The terminology overlaps, and bankers do not always use it consistently, so here is the map:
- Sweep account is the umbrella term. Any arrangement where the bank automatically moves money between accounts on a schedule is a sweep. A ZBA is one type of sweep account.
- Zero-balance account sweeps to exactly zero. The subsidiary holds nothing overnight, ever.
- Target-balance account sweeps to a fixed floor instead of zero — say, $25,000 stays in the account and only the excess moves. Businesses use targets when an account needs an intraday buffer for same-day wires or unpredictable presentments.
A related but distinct product is the investment sweep, which moves excess master-account cash into an overnight money market fund or similar vehicle and brings it back each morning. Many companies stack the two: ZBAs concentrate cash into the master account, and an investment sweep puts the master balance to work overnight. Ask your banker about both in the same conversation.
Why Businesses Bother: The Real Benefits
Idle cash stops idling. This is the headline benefit. Five accounts each carrying a $10,000 "just in case" buffer is $50,000 earning checking-account interest (usually near zero) while you pay 8 percent on your credit line. Concentrate it and that same $50,000 pays down borrowing or earns yield every single night.
Interest and borrowing math improves. Banks typically pay interest only on the master balance, and many will let a strong master balance offset fees or reduce the drawn amount on a revolving line. Every dollar concentrated is a dollar working at your best available rate instead of your worst.
Fraud exposure shrinks. A compromised account number with a zero balance is a much smaller problem than one holding a month of operating cash. Disbursement ZBAs also pair naturally with positive-pay services, where the bank matches every presented check against an issued-check list you provide — an empty account plus presentment matching is a genuinely hard target.
Spending control tightens. Because a ZBA only receives funding to cover approved, presented items, unauthorized transactions have nowhere to draw from. Companies that issue debit cards against a ZBA structure find that every card transaction must effectively be pre-funded, which enforces approval discipline without anyone playing gatekeeper.
Reconciliation gets simpler — mostly. Each ZBA statement shows only one kind of activity: payroll, vendor payments, or one location's deposits. Your bookkeeper reconciles narrow, single-purpose statements instead of one giant operating account where everything mingles. The master account statement is mostly a record of internal sweeps plus interest and fees, which is easy to verify in bulk.
The Costs and Trade-Offs Nobody Puts in the Brochure
ZBAs are a genuine cash-management upgrade, but they are not free and not foolproof.
Fees are real. Banks charge for ZBA structures: monthly maintenance per subsidiary account, per-transfer sweep fees, and sometimes setup charges. For a company concentrating hundreds of thousands of dollars, the interest pickup dwarfs the fees. For a small business moving a few thousand dollars a month, the monthly service charges can easily exceed the benefit. Run the math with your banker's actual fee schedule before you sign.
The master account can still overdraw. Automation moves the overdraft risk; it does not remove it. If a big batch of checks presents and the master account is short — because a large customer payment has not landed, or because someone forgot a scheduled transfer — the bank still charges overdraft or daylight-overdraft fees, and items can still bounce. ZBAs demand accurate cash forecasting, not less of it.
Reconciliation is still required. Narrower statements are easier to reconcile, but "easier" is not "optional." Every ZBA transaction still needs to be matched to your books, and the nightly sweeps themselves create a high volume of inter-account transfers that your accounting system must record. If your bookkeeping is already behind, a ZBA structure adds moving parts to a mess.
Complexity has a floor. Each ZBA is another account number to secure, another statement to review, another signer list to maintain. Most banks aim the product at mid-size and larger businesses; a freelancer or a two-person shop with one checking account gains nothing from this architecture.
You depend on the bank's cutoff times. Sweeps run on the bank's schedule. Same-day wires, late deposits, and holiday calendars can all create one-day mismatches between your books and the bank's zero. Understand the cutoff times in writing before you promise anyone "the money is there."
How to Keep the Books on a ZBA Structure
ZBAs change where cash sits, not what it is. From an accounting standpoint, the master account plus all linked ZBAs are simply your cash — but sloppy recording turns the nightly sweeps into reconciliation noise. Three practices keep it clean:
- Mirror the structure in your chart of accounts. Create one cash account per bank account: the master plus each ZBA. Recording every account separately preserves the audit trail that makes ZBAs valuable — the payroll ZBA ledger should show only payroll, exactly like its statement.
- Book the sweeps as transfers, not income or expense. A nightly sweep from the master to a disbursement ZBA is a debit to the ZBA cash account and a credit to the master cash account. It changes no balances in total. The most common ZBA bookkeeping error is letting imported bank feeds double-count: the vendor payment posts once, and the funding sweep must post as a transfer, never as a second payment.
- Reconcile each ZBA to zero, then reconcile the master. Each subsidiary statement should end at zero (or show only timing items like deposits in transit on the collection side). Confirm that first — a nonzero ZBA balance is your early warning that a sweep failed or a rogue transaction posted. Then reconcile the master account, where the sum of all sweeps should net against the subsidiary activity.
If you use plain-text accounting, this structure maps beautifully: one Assets:Cash subaccount per bank account, with the nightly sweeps as balanced transfer transactions you can generate mechanically. See the Beancount documentation for how multi-account cash structures translate into ledger entries.
Is a ZBA Structure Right for Your Business?
ZBAs pay off when three things are true at once: you run multiple bank accounts (or need to), meaningful cash sits idle across them, and your bookkeeping is current enough to absorb daily sweep activity. That profile usually starts around the lower middle market — multi-location retailers, property managers with per-building accounts, professional firms separating payroll and operations, any business writing enough checks or ACH payments to justify a disbursement lane.
If that is not you yet, the underlying principle still applies: idle cash scattered across accounts is a silent cost. Even without a formal ZBA structure, you can consolidate accounts, sweep excess balances manually on a schedule, and keep dedicated accounts genuinely lean. When the balances grow large enough that a banker's fee schedule looks cheap next to the interest you are leaving on the table, you will know it is time to make the sweeps automatic.
Simplify Your Financial Management
Whether you run one checking account or a master account with a fleet of ZBAs, the discipline is the same: every dollar accounted for, every transfer recorded, every statement reconciled. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data — no black boxes, no vendor lock-in. Get started for free and see why developers and finance professionals are switching to plain-text accounting.
