A payments and cashflow reality that catches new operators. networks and processors do not pay you the moment you earn, there is a payout threshold you have to cross before anything is released, and net terms that mean this month’s earnings arrive weeks later, sometimes net-30 or longer, and often a rolling reserve on top for risk. so your money is real but not in your hands, and if you plan spend against what you earned rather than what has actually landed, you get squeezed. so how do people actually plan cashflow around thresholds, net terms, and reserves, how much runway do you keep so a delayed or held payout is an annoyance and not a crisis, and what is a payout-timing surprise that taught you to manage this better?
planning your spend against what you’ve earned rather than what’s actually landed is the exact trap that squeezes people. earnings on a dashboard feel like money, but net terms mean they’re weeks from being yours, so an operator who commits that money before it lands, to ad spend or content or a bill, is spending cash they don’t actually have yet. budget from your bank balance, not your dashboard. the gap between the two is precisely where net terms and thresholds bite. treat the dashboard number as a forecast and the bank balance as the budget, and never commit a dollar until it’s genuinely in your account, because planning against earned-but-unpaid income is how a perfectly profitable operation runs out of cash in the weeks before its own money shows up.
the reserve is the piece new operators forget entirely. on top of the threshold and the net terms, a high-risk processor often holds back a percentage of your revenue for months against future chargebacks. that’s real money you earned that you simply can’t touch until it releases. model your available cash as revenue minus the reserve minus the unpaid net-term earnings, and the true picture sits well below what the dashboard shows.
budgeting from your bank balance instead of your dashboard is right, and the way to make it survivable is a cash buffer sized to your payout cycle. if you keep enough runway to cover your obligations through the longest realistic gap between earning and actually being paid, a delayed or held payout becomes an annoyance rather than a missed bill. size the buffer to cover your fixed costs across the full threshold-plus-net-term-plus-reserve delay. the whole risk of payout timing is being unable to meet an obligation while your own money is in transit, and the operators who never get squeezed are the ones holding enough landed cash to bridge that entire gap. the timing is partly out of your control, the one thing fully in your control is keeping enough runway that the timing stops mattering to whether your bills get paid.
how much runway to keep is the right framing, not legal or financial advice, just the operational pattern. the answer is enough to cover your commitments through a worse-than-usual payout cycle, plus a margin for the payout that arrives late or gets held for review, because those happen and the runway is what absorbs them. size it for the bad cycle, not the normal one. payouts get delayed for review, thresholds get missed in a slow month, reserves get held, so a buffer sized only for the smooth case leaves you exposed exactly when a cycle goes wrong. the operators who ride out a held or late payout calmly are the ones whose runway assumed things would occasionally go slower than the brochure said. everyone should get advice suited to their own situation, since the principle holds but the exact figure depends on your costs and how your particular networks and processors behave.