Cash Flow Forecasting with Payment Float
- Payment float puts your cash 2-3 business days behind your sales. You can't spend Tuesday's revenue until Thursday or Friday.
- Model three scenarios every week. Normal, refund spike, chargeback hold. The one you skip is the one that hits you.
- Fifteen minutes a week of forecasting saves more businesses than any fraud tool. Cash flow kills more SMBs than fraud does.
- Your formula: expected payout cash = projected sales - new reserve withholding + reserve releases - refunds - chargebacks - fees. Map each movement to its expected posting date
Your money arrives days after you earn it. Forecasting is how you keep that gap from breaking you.
You already know how payouts work. Settlement timing, batch cutoffs, reserves. That page has the mechanics. This one answers the next question. How do you actually plan around it?
Cash flow kills more small businesses than fraud does. The money's coming, it just arrives on the wrong day. You sold $40K last week, and payroll is due today. Your processor hasn't deposited yet. That gap between earning money and having money is where businesses break.
The Cash Flow Gap
Every card sale creates a timing mismatch. You deliver on Day 0. The cash lands Day 2 or 3. Suppliers, payroll and rent don't wait for it.
The core problem: revenue flows in continuously. Obligations hit on fixed dates. A $100K month sounds great. Then $15K is in reserve, $8K in refunds hasn't settled, and payroll lands three days before your biggest weekly payout.
Building Your Forecast Model
Stop guessing. Use this formula:
Expected Payout Cash = Projected Sales - New Reserve Withholding + Reserve Releases
- Refunds - Chargebacks - Fees
Map sales to the expected payout date using your account's delay and bank calendar. Map refunds, disputes, fees and reserve releases to their own posting dates. A T+2 business-day schedule sends Thursday sales to Monday, before bank holidays, not Saturday.
Input Variables
Every number comes from something you already have. Where to find each one:
| Variable | Where to Find It | Update Frequency |
|---|---|---|
| Projected weekly sales | POS/e-commerce dashboard, trailing 4-week average | Weekly |
| Reserve percentage | Processor agreement or merchant portal | Check monthly |
| Refund rate | Processor dashboard, returns report | Weekly |
| Chargeback volume | Processor dashboard, chargeback metrics | Weekly |
| Processing fees | Monthly statement, effective rate | Monthly |
| Payout delay (T+X) | Processor agreement, deposit history | Verify quarterly |
| Batch cutoff time | Processor docs or support | Set once |
| Upcoming fixed costs | Accounting software, bill calendar | Weekly |
Example: $80K/Month E-Commerce Store
Assumed inputs for a four-week planning period, with no reserve releases due this week:
- Weekly sales projection: $20,000
- Rolling reserve: 10% new withholding ($2,000 held)
- Refunds expected to post this week: $600, assumed at 3% of projected sales
- Chargeback principal expected to post: $100, assumed at 0.5% of projected sales value, not a count-based dispute ratio
- Processing fees: assumed blended 2.9% including fixed fees ($580)
- Payout delay: assumed T+2 business days
Expected weekly cash arriving: $20,000 - $2,000 - $600 - $100 - $580 = $16,720
That's 83.6% of gross sales. Plan your expenses around the full $20K and you're short every single week.
Three Scenarios to Model
Run your numbers through three scenarios every week. Five minutes, once you have a template.
Scenario 1: Normal Operations
Use your trailing 4-week averages for sales, refunds and chargebacks. That's your baseline, the week where nothing unusual happens.
Example assumptions for this store: sales within 10% of average, refund rate under 3%, chargebacks under 0.5%. These are forecast inputs, not healthy ranges.
Scenario 2: Refund Spike
A product recall, a viral complaint, a seasonal return wave like January on holiday sales. Model a refund spike using your return history and the orders still eligible for refunds.
Example stress test: swap this store's normal refund rate for an assumed 10%. On the $20K/week store above, $600 in refunds becomes $2,000. Weekly cash drops $1,400.
Why it matters: refunds hit your account as debits. On a thin balance, a spike can overdraft your deposit account before you notice.
Scenario 3: Chargeback Hold
Your chargeback rate breaches your processor's written limit. The processor flags the account. It could raise your reserve or pause payouts for review. Check your limits.
Example stress test: raise the reserve from 10% to 25% and add a 5-day payout delay. On the $20K/week store, $2,000 in reserves becomes $5,000. Every dollar arrives a week later. These are model inputs, not predicted processor terms.
Why it matters: this is the scenario that bankrupts businesses. The money isn't gone, it comes back eventually. Payroll and rent just don't wait for a risk team to finish reviewing. See holds and reserves for how to respond.
| Scenario | Weekly Cash | vs. Normal | Cash Gap Risk |
|---|---|---|---|
| Normal | $16,720 | Baseline | Low |
| Refund spike (10%) | $15,320 | -$1,400 | Medium |
| Reserve increase (25%) | $13,720 | -$3,000 | High |
| Payout pause (7 days) | $0 for first week | -$16,720 | Critical |
Cash Flow by Business Type
The timing mismatch looks different depending on what you sell.
E-Commerce / Inventory Businesses
The gap, as an assumed timeline: you buy inventory on Day 0 and pay the supplier on Day 30. It sells on Day 45-60 and the card revenue lands Day 47-63. That's Day 47-63 minus Day 30 = a 17-33 day hole between cash out and cash in.
What helps: negotiate supplier terms that better match sales. Price purchase order financing before using it. Set an operating-cash buffer from the gap you modeled. Track inventory turnover next to your cash forecast.
SaaS / Subscription Businesses
The gap: small day to day, since recurring revenue is predictable. Annual plan refunds are the hidden risk. One enterprise customer cancelling a $12K annual subscription puts a $12K hole in the month.
What helps: model annual-plan refunds separately. As a starting stress assumption, try three times your largest single-plan refund, then tune it to refund rights, history and cash needs. Watch for friendly fraud on annual renewals.
Service Businesses
The gap: you pay staff on the 1st and 15th. Clients pay net-30, if you're lucky. Cards help, but most service businesses still invoice. So the real delay is 30-45 days, not 2-3.
What helps: move as much billing to card-on-file as you can. Offer invoice clients 2% off for paying inside 10 days. Track card revenue and invoice revenue separately, because one is fast and one is slow.
Seasonal Businesses
The gap: revenue lands in 3-4 months. Expenses spread across 12. Peak season has to fund 6-8 months of little or nothing.
What helps: model off-season expenses and expected cash receipts. Work backward to the peak-season cash you need to set aside in your own reserve account, separate from the processor's.
When Cash Gets Trapped
Sometimes it isn't timing. Sometimes your money is being held. These need action, not planning.
Reserve increases, worked example: assume withholding rises from 5% to 15% on $80K a month. $80,000 × (15% - 5%) = another $8,000 withheld each month, before releases and deductions. The locked balance depends on the release schedule. See holds and reserves.
Payout holds: deposits can stop during a risk review. Get the review status and any stated release condition from your processor, then model a longer pause as a stress assumption. Don't budget around a generic duration.
Chargeback cascades: one product issue triggers 50 chargebacks in a week. Each one comes off your next payout. If the total beats the payout, your processor debits your bank account. See chargeback metrics for thresholds.
Bank debited or sale reversed? Match the entry and ask for the calculation.
Processor account review: they decide to look at your account. Maybe a volume milestone. Maybe your MCC code drew attention. Payouts slow or stop while they look.
Suggested starting buffer: two weeks of fixed operating expenses in a separate bank account. Include payroll, rent and subscriptions you can't lose. Tune it to the payout pause and obligations you modeled.
Simple Weekly Forecast Process
It takes 15 minutes once you've done it twice. Monday morning.
Step 1 - Record last week's actuals (3 minutes) Log actual deposits, refunds, chargebacks and fees. Compare them with your forecast. Suggested starting trigger: investigate an error over 10%, then tune that trigger to your cash buffer and payment deadlines.
Step 2 - Project this week's sales (3 minutes) Use your trailing 4-week average. Adjust for what you know about this week: a promotion, a seasonal shift, a launch. Don't overthink it. The average is usually close enough.
Step 3 - Apply the formula (2 minutes) Projected sales - new reserve withholding + reserve releases - expected refunds - expected chargebacks - fees = expected payout cash. Map each movement to its expected posting date.
Step 4 - Check against obligations (4 minutes) Map daily cash arrivals against what's due. Payroll, suppliers, subscriptions, rent. Flag any day where outflows beat your projected balance.
Step 5 - Run the stress scenario (3 minutes) Pick whichever scenario feels likeliest this week and re-run the numbers. Still solvent under stress? You're fine. If not, move money or delay a payment now. Not Friday.
Tools That Help
You don't need expensive software. Start simple and add a tool when manual tracking breaks down.
| Tool | Cost | Best For | Limitations |
|---|---|---|---|
| Spreadsheet (Google Sheets/Excel) | Free | Everyone starting out | Manual data entry, easy to forget |
| Float | Check the current plan and currency (pricing) | Visual cash flow forecasting | Needs accounting software integration |
| Pulse | Basics $29/month; Small Business $59/month (pricing) | Simple scenario modeling | Check which plan includes your integration |
| Fathom | Check company count, currency and Pro features (pricing) | Reporting and forecasting combined | Portfolio features differ from Pro |
VENDOR Pricing pages checked 22 October 2026. Choose the plan, currency, billing period and company count before budgeting. | Processor dashboard | Free | Real-time deposit tracking | No forecasting, just actuals | | Your accounting software | Varies | Cash flow reports built in | Forecasting features vary widely |
Start with a spreadsheet and update it weekly. Suggested upgrade trigger: two weeks running where forecast error exceeds 20% because you couldn't track the inputs. Tune that trigger to your cash buffer and obligations. Diagnose the missing data before buying software. See scaling milestones.
Next Steps
Your next move depends on where you are:
- Just starting on cash flow planning? Go back to payout strategy. Know your exact payout timing, batch cutoff and reserve terms. You can't forecast what you can't measure.
- Forecasting already, but worried about disruptions? Read holds and reserves. It covers what triggers a hold and how to get money released faster.
- Outgrowing manual processes? Check scaling milestones for the volume thresholds where better tooling pays for itself.
Related Pages
- Payout Strategy - settlement timing, batch cutoffs and reserve structures
- Money Held or Frozen - types of holds, how to respond, how to get funds released
- Settlement Timing - when an authorization becomes settled funds
- Reconciliation - matching expected deposits to actual arrivals
- Accounting Integration - connecting processor data to your books
- Reading Your Processor Statement - fees, and your effective rate
- Scaling Milestones - what to add at each volume tier
- Chargeback Metrics - the thresholds that trigger reserves and holds