How a 10-person agency maps freelancer payouts to retainer receipts

Your retainer is due on the 1st. Your freelancer invoices land on the 28th. In between, you're floating €14,000 in payroll from your operating account. That gap is not a cash flow problem. It is a scheduling problem, and scheduling problems have solutions.

Why the gap exists in the first place

Most agencies invoice retainer clients at the start of a month and offer Net 30 terms as a courtesy. That means cash arrives around the 30th, if you're lucky. Freelancers, meanwhile, deliver work mid-project and invoice when delivery happens, usually late in the month. The result is a recurring 10–25 day float that compounds every single month.

A 10-person studio billing €60k a month across four retainer clients and three active projects can sit on €18k–€22k of outstanding receivables at any given moment. That's not a sign of a struggling agency. It's the default state of project-based billing. The fix is not "invoice faster" in a vague sense. It is building a timing map that makes the float predictable and, where possible, eliminates it entirely.

Build your cash flow timing map

A timing map is a simple spreadsheet with two columns: money in and money out, laid out by calendar day across a rolling 45-day window. That's it.

Step 1: Anchor your retainer invoice send dates

Pick a fixed send date for every retainer client. The 1st or the 25th of the prior month both work. The goal is that payment arrives before your freelancer invoices are due. If your retainer clients are on Net 30 from the 1st, send invoices on the 25th of the prior month. That shifts receipt to the 25th, giving you a 3–5 day buffer before month-end freelancer payments.

Use ZenPay's recurring invoice feature to auto-send each retainer invoice at a set time (say, 8am client-local time) on the 25th. You set it once, and it sends itself every month. No manual trigger, no forgotten draft.

Step 2: Map your freelancer payment obligations

List every active freelancer, their typical invoice date, and your agreed payment terms. Most agencies pay freelancers on Net 7 or Net 14 terms. If you don't have written terms, now is the time to set them. A freelancer who invoices on the 28th on Net 7 expects payment by the 4th. That's after your retainer receipt. Good.

Group freelancers by payment week, not by project. If you have six freelancers and they all invoice in the last week of the month, stagger delivery milestones so two invoice in week 3, two in week 4, and two on project completion. This smooths the outflow curve.

Step 3: Identify the float windows

Once your map is built, the float windows become obvious. For a typical 10-person studio:

• Days 1–10: Retainer invoices sent, no receipts yet, payroll running
• Days 11–20: Freelancer invoices arriving, retainer cash still outstanding
• Days 21–28: Retainer receipts start landing, freelancer payments going out
• Days 29–31: Project invoice receipts, next retainer cycle prep

The danger zone is days 1–20. Any client who pays late in that window forces you to float payroll from reserves. The solution is two-part: tighten receipt timing and trigger reminders before the due date, not after.

Use auto-reminders to close the receipt gap

A Net 30 retainer client who pays on day 38 costs you 8 days of float. Over 12 months with four clients, that's 384 client-days of unpaid receivables. The fix is not chasing after the due date. It's a reminder 5 days before, so a slow-moving accounts payable team has time to process.

ZenPay's auto-reminders fire N days before (or after) the due date, in your name, using your editable template. Set a "5 days to go" reminder for every retainer client. The email comes from you, references the invoice, and includes the shareable payment link. Clients with a payment link pay an average of 6–8 days faster than those who have to log into a portal.

Handle multi-currency retainers without guessing your position

A 10-person studio with international clients often runs EUR retainers alongside GBP or USD project invoices. The mistake is converting everything to one currency in a spreadsheet and treating exchange rate estimates as real numbers.

ZenPay captures the exchange rate at payment time for reporting purposes and keeps multi-currency wallets separate, so your EUR retainer receipts sit in an EUR wallet and your GBP project receipts sit in a GBP wallet. When you pay a UK-based freelancer from GBP receipts, you're not touching your EUR operating buffer. That separation alone can prevent a perceived cash shortfall that isn't real.

Protect your map when projects overrun

Retainer clients who ask for extra work mid-cycle are the most common cause of timing map breakdowns. The work gets done, the freelancer gets paid, and the extra invoice sits in draft because nobody wants to "make it awkward."

Send the overrun invoice the same week the extra work is delivered. Frame it as a natural project update, not a surprise. Use a separate line item structure (creative direction, production, revisions) so the client sees exactly what they're paying for. With ZenPay, you can duplicate the retainer invoice, adjust line items, and send it as a standalone invoice in the client's currency without touching your recurring schedule.

The one rule that holds the whole system together

Every freelancer payment date must be at least 7 days after the expected receipt date of the retainer it's funded by. Build that buffer into your freelancer contracts as a payment terms clause. If a client slips past their due date, your auto-reminder fires. If they slip further, you have 7 days of buffer before the freelancer payment is due. That window is enough to make one direct call, offer a payment link, and close the gap.

The timing map does not eliminate late payments. It turns an unpredictable crisis into a known event with a pre-planned response.