Receiving Client Payments as a Remote Agency: Account Structure

A remote agency usually starts with one account. One person, one client, one invoice, one payment arriving in one place. It works until it does not. The second client arrives, then a contractor who needs paying in a different currency, and suddenly the single account that felt simple has become a knot nobody can untangle without a spreadsheet and a long evening.

The problem is rarely the money itself. It is that one account is being asked to do several different jobs at once: receive client payments, hold funds for subcontractors, pay for tools and subscriptions, and serve as the record of what the agency earned. When those jobs share one balance, every question becomes harder to answer. Which client paid late? Which payment belongs to which project? How much of the balance is actually yours to spend?

Account structure is the quiet answer to those questions. It is the decision, made deliberately and early, about how many accounts the agency runs, what each one is for, and who can touch it. This guide walks through how remote agencies usually structure their accounts for receiving client payments, what to separate and what to keep together, and how to keep the whole arrangement understandable to the people who rely on it: your clients, your team, and your accountant.

The first sign is usually a small embarrassment rather than a disaster. A client asks for a copy of their payment history and you have to scroll through months of mixed transactions to find theirs. A contractor asks when they will be paid and you cannot say, because the money for their work sits in the same balance as three client deposits and a software renewal. Nothing is lost, but nothing is clear either, and clarity is what clients pay an agency for.

The second sign is risk. When client funds, operating money and your own drawings all move through one account, a single problem touches everything at once: a payment hold freezes the balance you need for payroll, a disputed chargeback pulls money earmarked for a contractor, a platform review locks the account while a client waits for confirmation. Separation does not prevent these events, but it limits how far each one spreads.

The third sign is growth. An agency with one client can remember everything; an agency with eight clients, three contractors and two currencies cannot, and should not try. Structure replaces memory: when each account has one job and one name, anyone on the team can look at a balance and understand what it is for.

Before opening anything new, sketch the flow of money through the agency as it actually happens. A client pays an invoice, and that payment may need to cover contractor fees, platform costs, taxes, and the agency's own margin. Some clients pay monthly retainers, others pay per project, and some pay in a different currency. Write down each step and the accounts you already have, and the gaps will show themselves.

Most agencies find they need at least three functions, even if those functions live in fewer than three accounts at first. There is a receiving function, where client payments land. There is an operating function, where the agency pays its own costs. And there is a holding function, where money waits before it is paid onward, whether that is a tax reserve, a contractor payout, or a project budget. Naming the functions first keeps the structure honest: you are solving for jobs, not collecting accounts.

Resist the temptation to open an account for every client. That looks organised and becomes a burden within weeks, because every account needs its own login, two-factor setup, statement review and recovery plan. Group by function, not by client, and use your invoicing and your account register to tell clients apart. The guide at /blog/building-a-simple-account-register-your-future-self-will-thank-you-for explains a register that does exactly that job.

The single most useful separation an agency can make is between money that belongs to clients and money that belongs to the agency. Client money includes deposits held for work not yet delivered, funds passed through to a subcontractor or a media platform, and retainers paid in advance. Agency money is what remains after those obligations are met. When the two share a balance, it is easy to spend money that was never really yours.

A practical pattern is a receiving account that only receives. Client payments land there and nothing else is paid from it directly. On a regular schedule, perhaps weekly, the agency moves money out into the accounts where it belongs: contractor payouts to the operating account, tax reserves to the holding account, and the agency's margin to its own account. The receiving balance then tells a simple story: this is what has arrived and has not yet been allocated.

This pattern also makes reconciliation a short job instead of a long one. Each transfer out of the receiving account is tied to an invoice or a project, so the trail from a client's payment to its final destination is a short chain of named transfers rather than a long list of mixed spending. If a client ever asks where their payment went, the answer is in the register, not in your memory. The same discipline applies to the boundary between business and personal money, which is covered in /blog/keeping-business-and-personal-finances-separate-from-day-one.

Remote agencies rarely have the luxury of one currency. A client in one country pays in their currency, a contractor in another expects theirs, and the agency's own costs may sit in a third. Every conversion is a cost, and every cost is a decision: who pays it, when it happens, and whether it is visible to the client or absorbed into the price.

One approach is to keep a receiving account in each currency you regularly invoice in, and convert only when you need to move money onward. This keeps the exchange rate question separate from the payment question, and it means a client always pays in the currency on their invoice, which is how most clients expect it to work. The trade-off is more accounts to maintain, so this only earns its keep when a currency is genuinely regular rather than occasional.

Another approach is to receive in one currency and let the platform convert on arrival. That is simpler, but the rate and the fee are decided for you, and they vary. Whichever approach you choose, write it down and tell clients before they pay, not after. A client who knows the currency, the timing and any fee in advance has nothing to dispute; a client who discovers a conversion after the fact has a reason to ask questions. Freelancers face the same choices on a smaller scale, and the thinking in /blog/verified-accounts-for-freelancers-getting-paid-across-borders applies here too.

An account structure is only as good as its access rules. The founder who holds every login becomes a bottleneck the day they are ill, travelling, or asleep in another time zone while a payment needs confirming. The opposite extreme is worse: with everyone holding full access to everything, nobody can say who moved what, and one compromised login reaches every balance at once.

A workable middle is to give each person the smallest access they need. The person who raises invoices needs to see the receiving account, not move money from it; the person who pays contractors needs to move money from the operating account, not see client payment details. The founder keeps full access, and a second trusted person holds recovery access for emergencies. Write these permissions down next to the account list, so they are a policy rather than a habit.

Two-factor authentication belongs on every account in the structure, without exception, and the recovery methods belong in the agency's recovery plan rather than in one person's head. Shared logins sent over chat are the weakest link in most small agencies: a password in a message thread lives forever in that thread. Use a password manager with shared vaults, rotate credentials when someone leaves, and review access at least once a quarter.

Clients do not care about your internal structure, but they do care about what it produces: a clear invoice, a payment route they recognise, and a receipt that matches what they sent. Before a first payment, a careful client will ask who they are paying, what name will appear on their statement, and what happens if something goes wrong. Having those answers ready, in writing, is part of the service.

Verification status matters here in a practical way. A verified account with a consistent business name, a matching email domain and a complete profile gives a finance team something they can approve without escalating, while an account that looks improvised, with mismatched names and a personal email address, gives them a reason to pause. None of this is about impressing anyone; it is about removing friction from the moment a client decides to pay.

It also helps to tell clients how long payment takes to clear before they send it. Different routes clear at different speeds, and a client who expects same-day confirmation on a route that takes three days will worry on day two. A short note on the invoice, stating the expected timing and who to contact if the payment has not appeared, prevents most anxious follow-ups.

Good structure produces good records almost by itself, but only if the records are kept where the money is. Each account should have a monthly statement saved, each transfer should carry a reference naming the invoice or project, and each client payment should be matched to its invoice within days, not at year end. The register is the spine: one place where every account, every login holder, and every regular transfer is listed.

The most common record-keeping failure in small agencies is the undocumented transfer. Money moves between accounts for a good reason, and nobody writes the reason down, so six months later the transfer looks like income, an expense, or a mystery, depending on who is looking. A one-line note at the time of the transfer, naming the invoice and the purpose, costs seconds and saves hours.

Keep the records separate from the accounts themselves. Statements and the register should live in a place that survives losing access to any single account, because the day you need them most is often the day an account is under review. A shared drive folder or a simple bookkeeping tool both work, as long as someone other than the founder can find them. The test is simple: if you were unavailable for a month, could someone else reconstruct the agency's money from your records alone?

No structure lasts forever. A new service line, a new currency, a contractor becoming an employee, or a platform changing its rules can all make yesterday's arrangement the wrong one. Review the structure twice a year, and ask three questions: does every account still have one clear job, is any account doing two jobs badly, and can a new team member understand the system from the register alone?

Change slowly and one account at a time. Move one function, let it settle for a month, and check that the records still reconcile before moving the next. Notify clients before their payment route changes, never after, and keep the old route open until the first payment has cleared on the new one. The goal is a structure that grows with the agency, quietly, so receiving client payments stays the boring, reliable part of the business.

This article is educational information about organising verified accounts for receiving client payments. It is not financial, legal or tax advice, and it is not a recommendation to buy or sell any account. Platform features, limits, fees and verification requirements differ and change over time, so check the current settings and rules of each platform you use, and speak to a qualified adviser about tax and accounting questions for your own business.