Skip to content

Automation Agency Invoicing: Retainers, Usage Costs and Auto-Pay

Automation agency invoicing explained: retainers, usage pass-through, multi-currency, auto-pay, dunning reminders and payment providers by region.

By , Founder & CEO

Updated · Published · 9 min read

Stacked invoices with a recurring arrow and a card for automation agency invoicing

Short answer

Invoice automation clients with a fixed monthly retainer charged automatically, plus a separate usage line for pass-through costs such as voice minutes, LLM tokens and platform fees. Bill in the client's currency through a payment provider that works in their region, turn on auto-pay where the provider supports it, and send reminders at set intervals when a payment fails.

Key takeaways

  • Split invoices into a fixed retainer and a usage line so clients see what is service and what is cost.
  • Track usage costs per client from the platform APIs; do not estimate them at month end.
  • Choose payment providers by client region: card-first globally, UPI in India, SEPA and iDEAL in Europe, mobile money in Africa, Pix in Brazil.
  • Auto-pay removes most late payments; Stripe, Razorpay, PayPal, Paddle, Mollie and Paystack all support recurring charges.
  • Have a written dunning policy: reminder days, retry rules and what happens to service when an invoice stays unpaid.

Most automation and AI agencies start by sending a PDF invoice at the end of the month and waiting. That works for three clients. At fifteen, with voice minutes, LLM tokens and platform fees that change every month, it becomes a part-time job and a steady source of late payments.

This guide covers how to structure invoices for automation work, how to pass usage costs through without disputes, how to handle currencies and regions, and how to set up auto-pay and reminders so you are not chasing payments by email.

How should an automation agency structure its invoices?

Separate what you charge for your service from what you pass through at cost. Clients accept variable bills much more easily when they can see which part is fixed.

Common invoice line types for automation and AI agencies
LineBilling patternTypical contentsHow to charge
Setup or build feeOne-timeDiscovery, workflow build, agent prompt and testingUpfront or 50/50 at start and launch
Monthly retainerFixed, recurringMonitoring, fixes, small changes, reportingAuto-pay on a set day each month
Usage pass-throughVariable, in arrearsVoice minutes, telephony, LLM tokens, platform task or operation feesAdded to the next invoice at cost or with a stated markup
Change requestsAd hocNew workflows or agents outside the retainerQuoted and invoiced separately

If you have not settled your pricing yet, our guide to automation agency pricing covers retainer levels and value-based models. This post assumes you know what to charge and focuses on how to bill it.

How do you pass usage costs through to clients?

Voice AI and LLM work has real per-unit costs. A voice agent bills by the minute; Vapi, for example, lists a $0.05 per minute hosting fee before model and voice costs, and Retell quotes $0.07 to $0.31 per minute (both as of November 2026). If one client's call volume doubles, your costs double, and a flat retainer quietly turns into a loss.

Three rules keep usage billing clean:

  1. Record cost per client from the source. Vapi and Retell return a cost for each call through their APIs. Assign each agent or workflow to a client and sum the actual costs, rather than estimating from minutes.
  2. State the markup in the contract. Either pass costs through at cost and earn on the retainer, or add a fixed markup (for example 20%) and say so. Hidden markups cause disputes when clients compare with the platform's public pricing.
  3. Bill usage in arrears. Invoice last month's usage with this month's retainer, so the number is final when the client sees it.

If you sell a usage-heavy product at scale, Stripe has usage-based billing built in. Its docs now point new integrations to Metronome, which became part of Stripe, while the older Meters API remains supported for existing setups. For most agencies, a usage line added to a monthly invoice is enough.

What does a combined invoice look like? (worked example)

This is an illustrative example for a client with an AI receptionist and a few n8n workflows. The numbers are invented to show the structure.

Worked example: one month's invoice (illustrative numbers)
LineQuantityRateAmount
Monthly retainer: monitoring, fixes, reporting1$1,200.00$1,200.00
Voice agent usage (October, at cost)2,850 minActual platform cost$342.00
LLM usage for workflows (October, at cost)Actual API cost$58.40
Change request: new lead-routing workflow1$450.00$450.00
Total$2,050.40

Put the usage detail (calls, minutes, cost per call) in the client's monthly report so the usage lines match something they have already seen. Our post on voice AI agent reporting covers what to include.

How do you invoice clients in different currencies?

Invoice each client in their own currency when you can. Clients pay faster when they do not have to think about conversion, and some cannot pay in a foreign currency at all without extra steps from their bank.

  • Set a billing currency per client, not one for the whole agency.
  • Keep your costs in their original currency (often USD for platform fees) and convert at invoice time, so you can see margin per client.
  • Match the payment provider to the currency. A provider that only settles INR cannot collect a EUR invoice, and some local methods only work in one currency.
  • Show a fixed price, not a live conversion, on retainers. Review the rate once or twice a year instead of letting the amount move every month.

Which payment provider fits each region?

Clients pay with what they already use. A US company expects a card or ACH; an Indian business expects UPI; a Dutch client expects iDEAL; a Nigerian or Kenyan client may prefer bank transfer or mobile money. Picking the provider by region matters more than picking the cheapest fee.

Payment providers by client region
RegionProviders to considerMethods clients expectRecurring auto-pay
Global / USStripe, PayPal, Square, PaddleCards, Apple Pay, Google Pay, bank debits, PayPalStripe, PayPal, Paddle
IndiaRazorpay, CashfreeUPI, cards, netbanking, walletsRazorpay (cards, UPI AutoPay, eMandate)
Europe and UKMollie, StripeCards, iDEAL, Bancontact, SEPA Direct DebitMollie (mandates), Stripe
AfricaPaystack, FlutterwaveCards, bank transfer, USSD, mobile moneyPaystack
Latin AmericaMercado PagoCards, Pix, boleto, OXXONot covered here
Anywhere, B2BBank transferWire, local bank transfer, UPINo (manual)

Merchant-of-record providers such as Paddle and Dodo Payments act as the seller and handle sales tax and VAT for you, which some agencies prefer when selling into many countries. The trade-off is less control over the checkout.

How do you set up auto-pay for retainers?

Auto-pay is the single biggest fix for late payments. The client authorises once, and each renewal is charged without an invoice sitting in their inbox. How it works depends on the provider:

  • Stripe, PayPal, Razorpay and Paddle run the schedule themselves. You create a subscription and they charge on each renewal date. Razorpay Subscriptions supports cards, UPI AutoPay and eMandate for Indian clients.
  • Mollie and Paystack use a first payment to create a mandate or authorization, and then you charge it on your own schedule. Mollie calls these first and recurring payments; its docs note that the customer goes through the payment steps only once.
  1. Agree auto-pay in the contract, with the charge day and what happens if a charge fails.
  2. Send the client a payment link for the first charge. This creates the subscription or mandate.
  3. Generate a paid invoice for each renewal so the client's finance team has a document for every charge.
  4. Bill usage separately on a normal invoice, or add it to the next renewal if your provider supports variable amounts.

What should happen when a payment fails?

This process is called dunning. You need two parts: automatic retries by the payment provider, and reminders from you.

Providers retry on their own. Stripe's Smart Retries is on by default for new accounts and is set to up to 8 retries within 2 weeks, with options from 1 week to 2 months. Stripe does not retry hard declines such as a lost or stolen card until the customer adds a new payment method. Mollie retries a failed subscription payment up to 5 times, roughly once a day, and cancels immediately for some reasons such as an invalid or closed bank account.

Your reminders cover what retries cannot: expired cards, manual invoices and bank transfers. A simple schedule works:

A simple reminder schedule for overdue invoices
WhenActionTone
Due dateInvoice marked due, payment link includedNeutral
+1 dayFirst reminder with the same payment linkFriendly
+3 daysSecond reminder, ask if the card or details changedDirect
+7 daysFinal reminder, state the service policy from the contractFirm
After final reminderRestrict portal access or pause non-critical work, per contractPer contract

Be careful with pausing automations. Switching off a client's live receptionist can hurt their customers, not just them. Restricting dashboard access or pausing new work is usually a better lever than stopping production workflows.

What should your contract say about billing?

Most invoicing disputes come from terms that were never written down. Put these points in every client agreement before the first invoice goes out:

  • Billing currency and amount of the retainer, and when it can change (for example, once a year with 30 days' notice).
  • Usage rules: which costs are passed through, whether at cost or with a markup, and how they are measured.
  • Payment method and auto-pay consent, including the charge day each month.
  • Payment terms for manual invoices, such as due on receipt or net 7.
  • What happens when payment fails: reminder days, when portal access is restricted, and which systems keep running.
  • Who pays platform accounts directly. Some clients prefer to own their Vapi, Retell or OpenAI accounts and pay those providers themselves, which removes the usage line from your invoice entirely.

Which tools handle automation agency invoicing?

Accounting tools such as QuickBooks or Xero handle invoices and bookkeeping well but know nothing about your workflows or call minutes. Payment providers handle subscriptions but not per-client usage. Most agencies glue the two together with a spreadsheet.

GetFlowBiz combines the pieces for automation and AI agencies. It tracks costs per client (provider, API, LLM and telephony), creates subscription invoices automatically, and lets clients pay in a white-label client portal through 12 payment methods including Stripe, Razorpay, PayPal, Mollie, Paystack, Mercado Pago and bank transfer or UPI, with a 0% platform fee. Auto-pay works on Stripe, Razorpay, PayPal, Paddle, Mollie and Paystack. Overdue invoices get reminders at 1, 3 and 7 days, and you can optionally lock the portal while an invoice is overdue. Each payment is verified with the provider and matched on amount and currency before the invoice is marked paid.

Get paid on time without chasing

Write the billing terms into the contract, split retainer from usage, put every retainer on auto-pay and let reminders run on a schedule. GetFlowBiz is free right now: the first 100 Founding Member accounts stay free forever. You can sign up free or check pricing.

Frequently asked questions

Should I charge clients for voice minutes and LLM tokens separately?

Yes, for most agencies. A separate usage line at cost, or with a stated markup, protects your margin when a client's volume grows and makes the invoice easy to check against your monthly report. Fold usage into the retainer only if volume is small and stable.

What is the best way to collect recurring retainers from clients?

Use auto-pay through a provider that supports recurring charges in the client's region, such as Stripe or PayPal globally, Razorpay in India, Mollie in Europe or Paystack in Africa. The client authorises once and each renewal is charged automatically with a paid invoice.

How many times does Stripe retry a failed subscription payment?

For new Stripe accounts, Smart Retries is on by default and set to up to 8 retries within 2 weeks. You can change the window from 1 week up to 2 months or use a custom schedule of up to three retries. Hard declines are not retried until a new payment method is added.

Can I invoice clients in their own currency?

Yes. Set a billing currency per client and use a payment provider that supports that currency. Stripe, Razorpay and Dodo accept many currencies; others such as Cashfree (INR) or Mercado Pago (Latin American currencies) are tied to specific markets.

Should I switch off a client's automations if they don't pay?

Only if your contract says so, and be careful with customer-facing systems like AI receptionists. Restricting the client's portal access or pausing new work is usually safer than stopping live workflows that their own customers rely on.

Sources

  1. Stripe docs: Smart Retries
  2. Stripe docs: Usage-based billing
  3. Razorpay docs: Subscriptions
  4. Mollie docs: Recurring payments
  5. Vapi pricing
  6. Retell AI pricing

Kishan Makani

Founder & CEO, GetFlowBiz

Kishan builds GetFlowBiz, the client portal and operations platform for automation and AI agencies. He writes about running, pricing and reporting on automation work. More from Kishan

Keep reading

Lock in GetFlowBiz free, forever

Founding Members keep every feature free for life. Only 27 of 100 spots are left.

73/100 founding spots claimed27 left