Example scenario: a client’s finance team asks for proof that the $12,000 they approved for Q3 paid ads went only to their campaigns. Your agency paid every client’s Meta, Google and TikTok accounts from two company cards. To answer, an account manager spends two days exporting platform invoices, matching them against card statements and explaining why some charges do not line up with calendar months.
That request is becoming normal. Clients with procurement teams want to see that their budget stayed separate, that spend matched the plan, and that the agency can show its working. Good agency ad budget management is less about software and more about structure: separate money per client, a pacing sheet everyone trusts, and a monthly close that produces the same evidence every time.
What “audit-ready” means for an agency
An audit-ready client file answers four questions without extra work:
- What did the client approve, per platform and per period?
- What did each platform report as spend?
- What was charged to the payment method, and when?
- Who approved changes to the budget, and why?
If any of those answers lives only in someone’s head or in a shared card statement, the file is not ready.
Why platform billing makes this harder
Charges do not follow calendar months
Most ad platforms charge when spend reaches a billing threshold or on a bill date, whichever comes first. A client’s April spend can appear as three charges in April and one in early May. Your sheet needs to separate “spend in period” from “charged in period”.
Daily spend varies by design
Google Ads can spend up to two times a campaign’s average daily budget on a given day, while keeping monthly spend within 30.4 times that daily budget for most campaigns, as Google’s explanation of average daily budgets sets out. That is normal behavior, but a client who sees a heavy day without context may think the budget was broken.
Shared cards blend clients together
When several clients share one card, a charge of a few hundred dollars from one platform could belong to any of them. Matching becomes guesswork based on dates and amounts.
Template: the client pacing sheet
Use one tab per month and one row per client per platform. These columns cover most agencies:
| Column | Example entry | Purpose |
|---|---|---|
| Client | Client B | Groups rows for reporting |
| Platform and account ID | Google Ads, 123-456-7890 | Ties the row to one ad account |
| Approved budget | $4,000 for the month | The number you report against |
| Spend to date (platform) | From the platform dashboard | What the platform says was used |
| Projected month-end spend | Spend to date plus average daily spend times days left | Shows if you will land over or under |
| Pace status | On track, over, under | Prompts action mid-month |
| Payment card | Last four digits | Links charges to this client only |
| Charges this month | Sum of card charges | What was billed to the card |
| Variance note | “Late March spend billed 2 April” | Explains timing gaps |
| Budget change log | Date, who approved, new amount | Evidence for the client |
The monthly close in seven steps
- Export platform invoices or billing summaries for every client account on the first working day of the month.
- Export card transactions for each client’s card for the same period.
- Match charges to invoices. With one card per client, this is a filter on four digits, not a search.
- Record timing differences in the variance column so the next month starts clean.
- Compare platform spend with the approved budget and write one line explaining any gap.
- Save the evidence pack (invoices, card export, pacing row) in the client’s folder.
- Send the client summary with budget, spend, charges and notes in the same order every month.
Comparing ways to pay for client ad spend
| Model | Separation | Agency cash risk | Audit effort |
|---|---|---|---|
| Client adds their own card to the account | Complete | None | Low for the agency, but the client must manage declines |
| Agency card shared across clients | None | Agency floats all spend | High: manual matching |
| Agency card per client | Strong | Agency floats spend per client | Low: one card equals one client |
| Prepaid card per client, loaded after client pays | Strong | Limited to what is loaded | Low, and spend cannot exceed the loaded amount |
Many agencies mix models: large clients add their own cards, while smaller clients are billed by the agency and paid through a dedicated card each.
Decision guide: when to give a client their own card
- The client asks for budget evidence or has a procurement team: always.
- The client runs on more than one platform: one card per client per platform if each platform is a separate invoice line.
- You prepay ad budget after the client pays your invoice: a prepaid card loaded with that amount keeps the agency from floating extra spend.
- A test budget under a few hundred dollars: a shared test card is fine until the account graduates to a real budget.
A worked example with Vizovcc
Vizovcc fits the prepaid-card-per-client model. You fund one account balance with crypto (USDT, USDC, Bitcoin, ETH and other coins), then buy as many prepaid virtual cards as you need from that balance. Each card has its own loaded balance, which cannot be overspent, and you can freeze or unfreeze any card from the dashboard. The site’s own advice is one card per ad account, and it names Google Ads, Meta ads and TikTok Ads among common uses.
In practice, an agency could hold one Vizovcc card per client, label it in the pacing sheet by its last four digits, and load it with the approved budget once the client has paid. When a client pauses, freezing their card stops new charges while the account stays intact. Card pages show each card’s price and how it splits between the issue charge and the spendable balance, so you can choose a card that matches the client’s budget size.
A few limits matter for agencies. Vizovcc has no team roles or sub-accounts, so anyone who signs in sees every client’s card. Keep the login with one finance person and give account managers access through each ad platform’s own user settings. Budgets and caps are set inside Meta, Google and TikTok, not in the card dashboard, and card purchases are final, so match the card to the budget before buying. Each platform decides which cards it accepts, so run a small first charge on a new account. For more detail on platform setup, see how one card per ad account is set up.
Separate cards are a bookkeeping and budgeting tool. Every client account still has to follow each platform’s advertising and payment policies.
Frequently asked questions
Should the agency or the client own the payment method?
It depends on your contract. If the client owns it, you avoid cash risk but lose control over declines. If the agency owns it, you need clear separation per client and a written agreement on who pays what and when.
How do we handle spend that crosses months?
Report platform spend by the period it occurred, and record card charges separately with a variance note. Clients accept timing differences when they are explained the same way every month.
How long should we keep the evidence packs?
Follow your accountant’s guidance and your client contracts. Store packs per client and per month so you can hand over any period on request.
Key takeaways
- Audit-ready means approved budget, platform spend, card charges and change approvals all on file per client.
- Platforms bill on thresholds and bill dates, so separate “spent” from “charged” in your sheet.
- One card per client turns reconciliation into a filter instead of a puzzle.
- Prepaid cards loaded after the client pays limit how much the agency can float.
- Platform budgets and ad policies still apply: cards only handle the payment side.
Pick your client with the most complex billing and run next month’s close using the pacing sheet above. If separate prepaid cards per client would make that close easier, look at Vizovcc and compare its card pages with your client budgets.

Leave a Reply