Pass-Through Collections & FX Differences: Bookkeeping That Automates

Most bookkeeping headaches do not come from complicated transactions. They come from routine transactions that are just slightly awkward — the kind that fall outside a clean debit-credit pair and require a judgment call every single time they appear. Pass-through collections and foreign exchange differences sit firmly in that category. Get the structure right once, and automation handles them reliably for months. Get it wrong, and you spend hours each month manually correcting entries that your software confidently got wrong.
The Scenario That Makes This Click
Imagine a London-based digital agency that manages paid media budgets for clients across Europe. Each month the agency collects ad spend from its clients in euros, holds that money briefly, then pays Google and Meta on their behalf before issuing an invoice for its own management fee separately. The money coming in for ad spend is not revenue. It belongs to the client, passes through the agency's bank account, and leaves again quickly. Meanwhile, because payments to the ad platforms happen a few days after the client pays in, the euro exchange rate shifts. The agency banks in sterling. Suddenly you have a timing difference, a currency difference, and a classification question all bundled into one ordinary monthly cycle.
Why Classification Is the Entire Game
The first decision, and the one that determines whether automation will work, is how to classify the pass-through funds. Many bookkeepers instinctively record the client payment as income and the platform payment as a cost. That produces inflated revenue figures, distorts gross margin, and makes the FX difference almost impossible to isolate cleanly. The correct treatment in most jurisdictions is to record the incoming funds as a liability — something like a client funds held account — and to record the outgoing payment as a reduction of that liability. The management fee is the only line that touches the income statement. Once that structure is in place, your automation rules have a clear, consistent pattern to follow: client payment in goes to the liability account, platform payment out reduces it, and anything left over is the FX difference.
How FX Differences Actually Arise in This Setup
When the client pays in euros and the agency records that in sterling at the day's rate, the liability sits on the balance sheet at a specific sterling value. When the agency pays the platform a few days later, it uses sterling from its bank account converted at that day's rate. If the pound has strengthened in those few days, the sterling cost of settling the liability is lower than the sterling value originally recorded, and you have a small gain. If the pound has weakened, you have a small loss. Neither of these is revenue or a cost of service. They belong in an FX gains and losses account, which is typically shown below operating profit. The discipline here is not to absorb those differences into the liability account or leave them as unexplained rounding. Name them correctly and put them in the right place every single time.
Building Automation Rules Around This Structure
Accounting platforms like Xero, QuickBooks Online, and Freeagent all allow you to create bank rules that recognise transaction descriptions, amounts, or counterparties and apply a specific coding automatically. The agency in our example can build a rule that says any incoming payment from client X above a certain threshold, referenced with a specific invoice prefix, posts to the client funds held liability account rather than a revenue account. A second rule handles the outgoing platform payments. The FX difference, however, is trickier because it does not arrive as a transaction — it is the residual after settlement. The cleanest way to handle this is to reconcile the liability account at the end of each period and post the balance as an FX gain or loss with a single journal. Some platforms with multi-currency modules will calculate and suggest this journal automatically if your accounts are set up correctly. That is worth checking before you build a manual workaround.
The Chart of Accounts Setup That Makes It Stick
None of this automation holds together without a deliberate chart of accounts. You need a dedicated current liability account for pass-through funds, ideally one per client if volumes justify it, so that balances are visible and reconciliation is fast. You need a separate bank account or sub-account if your platform supports it for the currency in which pass-through funds are held, because mixing pass-through euros with your operating euros creates a reconciliation nightmare. And you need a clearly labelled FX gains and losses account in the correct section of your profit and loss, below operating profit, so that it never gets mistaken for revenue by anyone reading your management accounts. Spending an afternoon setting these up correctly saves several afternoons per year trying to untangle entries that almost made sense.
The Month-End Routine That Keeps Everything Clean
Even with solid automation in place, pass-through collections and FX differences benefit from a defined month-end routine. The steps do not need to be complicated. First, confirm that all client payments have posted to the liability account and not to revenue. Second, confirm that all platform payments have reduced the liability and not been expensed. Third, check the closing balance on the liability account — in most months it should be close to zero once all payments have cleared, because pass-through funds should not be sitting in your accounts at period end. Fourth, calculate the FX difference between what was received and what was paid out in the base currency, post it to the FX account, and clear the liability to zero. Fifth, review the FX account balance for the period and satisfy yourself it is in the right direction given rate movements. That five-step routine takes under thirty minutes when the structure underneath it is solid. It can take an entire afternoon when it is not.
What Goes Wrong Without This Structure
The most common failure mode is treating pass-through collections as revenue simply because they arrive in the bank account and look like income. This overstates revenue significantly, makes the business look more profitable than it is, and creates tax exposure if the error is not caught before filing. A secondary failure is posting FX differences to sundry income or rounding without investigation. Over time this obscures a real signal about whether your payment timing is costing or benefiting the business. Some agencies with large pass-through volumes find that consistently unfavourable timing on currency settlement is quietly eroding thousands of pounds per year. The bookkeeping structure described here makes that visible. That visibility is itself a reason to get the setup right, quite apart from the automation benefits.
One platform runs an accounting practice
From invoice OCR to filed Thai tax returns — the platform behind these articles runs real operations in Thailand every day.
Explore the platform →