How to Budget on a 20th-to-20th Pay Cycle
If you're paid on the 20th but every budgeting app assumes the 1st, your numbers never quite add up. Here's how to budget around your real pay cycle instead of the calendar — with a worked example you can copy in five minutes.
Why the calendar month works against you
Most budgets run from the 1st to the end of the month. But if you're paid on the 20th, your income lands right in the middle of that window. The result:
- Rent or a big debit order due on the 1st looks unfunded, because this month's pay hasn't arrived yet.
- Money left over after payday rolls into "next month" in the app, but not in your head.
- Your running balance never matches your actual bank balance, so you stop trusting it.
The fix is simple: make your budget period match your pay period. If you're paid on the 20th, your financial month runs 20th → 19th.
What a 20th-to-20th cycle actually means
A 20th-to-20th cycle (more precisely, 20th-to-19th) starts on payday and ends the day before your next payday. So your "June" might be 20 Jun – 19 Jul. Every bill you pay out of that paycheck belongs to that period — even the ones that hit in early July.
Step-by-step: set up your first cycle
- Set your start day to 20. Your month now runs 20th to 19th and labels itself as a date range.
- Enter your opening balance — what's actually in the account on the 20th, right after you're paid.
- List income for the cycle (salary, side income), each tagged with the day it arrives.
- List expenses — rent, debit orders, subscriptions, groceries — each tagged with the day it's debited.
- Put a budget amount next to each line. This is your plan for the cycle.
- Fill in actuals as the month happens. The variance (actual − budget) is calculated for you.
A worked example
Here's a simple 20 Jun – 19 Jul cycle, sorted by the day each item actually occurs:
| Day | Item | Budget | Actual |
|---|---|---|---|
| 20 Jun | Salary | 3,200 | 3,200 |
| 21 Jun | Rent | 1,150 | 1,150 |
| 25 Jun | Car payment | 340 | 340 |
| 1 Jul | Insurance | 95 | 95 |
| 3 Jul | Subscriptions | 45 | 52 |
| — | Groceries & fuel | 600 | 648 |
| — | Everything else | 400 | 381 |
| Net for the cycle | +570 | +534 | |
Because the salary and the bills it pays for sit in the same period, the running balance after each row reflects what's genuinely in your account on that day — including the insurance and subscriptions that fall in early July. You planned a +570 surplus and landed at +534; the −36 variance is overspend on subscriptions and groceries, partly offset elsewhere.
Why tagging the day matters
A budget that balances overall can still leave you short on the 25th if three debit orders land before more income arrives. Tagging each item with its day — and sorting in true chronological order within the cycle — shows you the timing, not just the total. That's the difference between "the month works out" and "I never go into overdraft."
Track your real pay cycle, free
Cash Flow Tracker is built for exactly this: set any start day, tag items by day, and watch budget vs actual with a running balance for every cycle.
Create your first cycleFrequently asked questions
What if I'm paid on the 25th or the last Friday?
Same idea — set your start day to match your pay date. A 25th payer runs 25th → 24th. If your payday floats (e.g. last Friday), pick the earliest day it lands so no bill is ever stranded before income.
What about bills that fall outside the cycle?
They don't — every day of the month belongs to exactly one cycle. A bill on the 5th simply falls in the cycle that started on the 20th of the previous month.
Do I need a spreadsheet for this?
You can start in a spreadsheet, but the day-sorting, running balance, and budget-vs-actual variance get tedious fast. That's the whole reason we built Cash Flow Tracker.