Account Funding & Cash Sweep Planner: The Day's Transfers, Computed and Approved

The problem this kills

Every morning, someone on the treasury team stares at a wall of bank balances and plays a high-stakes guessing game: which account is short for today's payroll, which one is sitting on idle cash, and exactly how much to shuffle between them so nothing bounces and nothing sits dead. They do it in a spreadsheet, by hand, against a clock — because the wire cutoff is at 2pm and a missed funding means a returned payment, an angry vendor, or a payroll that doesn't clear.

The math itself isn't hard, but doing it by hand under time pressure is where the mistakes live. You forget a $40k draft that clears tomorrow and sweep an account too thin. You move money in six separate transfers when three would have done it. You fund the AP account but forget it has a minimum balance the bank requires. And there's no record of why you moved what you moved — so when the controller asks, you're reconstructing it from memory and a screenshot.

This is a job that should be computed, checked by a human, and logged — not improvised every morning. A cash sweep planner turns "what do I move today?" into a proposed list the manager approves in thirty seconds, with a clean audit trail and bank-ready instructions on the other side.

What you'll build

A simple internal web app for your treasury team. Each morning you import (or paste) every account's current balance, its target and minimum balance, and the known upcoming outflows hitting it — today's payroll, tomorrow's AP run, the tax draft that clears Thursday. You tell the tool which account is your concentration account (the hub that excess cash sweeps into and funding flows out of).

The tool computes, per account, how much it needs to be funded to hit its target after covering upcoming obligations, and how much excess can be swept out — then nets those moves into the fewest transfers, routing through the concentration account so you're not making more wire transfers than you have to. It proposes the day's transfer list: from-account, to-account, amount, reason. The treasury manager reviews it — checking nothing breaks a minimum balance or strands cash an obligation needs — and approves. Only then can you export bank-ready transfer instructions and the resulting end-of-day positions for every account. Nothing moves money on its own; the tool drafts, a person signs off.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — how many accounts you manage and at which banks, how you name and number them, where targets and minimums come from, how far ahead you look for upcoming outflows, your bank's wire cutoff, and the messy exceptions (a target that's really a range, an account that can't go below a bank-required floor, a sweep that needs two hops between banks). It reflects a short tailored spec back to you and gets your thumbs-up before it builds anything, so the planner matches your account structure and rules — not a generic template.

From there it walks the agent through the data model, the import, the funding-and-sweep computation, the netting logic that minimizes the number of transfers, the proposed transfer list, the manager approval gate, the per-day duplicate guard, and the export of both the transfer instructions and the resulting positions. Every step ends with a ready-to-copy prompt. There's a full "No API yet?" path that uses a Google Sheet / CSV of balances as the data source and produces clean CSV transfer instructions in the exact columns your bank or treasury workstation expects — so you can build and run the whole thing this weekend regardless of whether you have a bank API.

The governance it includes (this is the point)

Moving money is the most consequential thing a treasury tool does, so the controls aren't optional. The plan builds in login so only your treasury team can use it, row-level security so you only ever see your own organization's accounts, a complete audit trail of who imported what and who approved which transfer set, a hard human-approval gate so no transfer instructions can be exported until the manager signs off on the proposed list, and a per-day duplicate guard so the same day's sweep can't be approved or exported twice and accidentally double-moved. The tool proposes; a person approves; only then is anything committed.

Who it's for

Treasury analysts and managers, controllers, and finance-owning founders who run more than one bank account with minimum balances to protect and obligations to fund — anyone doing the morning "what do I move today?" shuffle by hand against a wire cutoff. If you can explain how your accounts are structured and what each one needs to keep on hand, you can build this.

You've got this — start with the plan, paste the first prompt, and answer the interview. You'll have your first proposed transfer list on screen before the weekend's out.