Automate UK Stripe Payouts: Make.com to Google Sheets Setup

Automate UK Stripe Payouts: Make.com to Google Sheets Setup

Running a small business or working as a freelancer in the UK often means juggling a hundred different hats. Financial administration, while absolutely crucial, can feel like the heaviest one. You're generating income through platforms like Stripe, which is brilliant, but then comes the task of actually tracking that money once it lands in your bank account. Manually downloading CSVs, matching bank statements, and trying to categorise everything for HMRC can be a huge time sink. I know, because I've been there, staring at a spreadsheet late on a Sunday evening, wondering if I've missed anything.

What if you could bypass most of that manual effort? Imagine having your Stripe payout data automatically appear in a dedicated Google Sheet, ready for reconciliation, tax planning, and a clear overview of your UK small business income? That's exactly what we're going to set up today using Make.com (formerly Integromat), a powerful automation platform. This isn't about getting rid of your accountant; it's about providing them (or yourself) with cleaner, more organised data, saving everyone time and stress.

Why Automate Stripe Payout Tracking in the UK?

For UK freelancers and small businesses, staying on top of your financial records isn't just good practice; it's a legal requirement. HMRC expects you to keep accurate records for at least five years after the 31 January submission deadline of the relevant tax year. That includes all your income, and Stripe payouts are a significant part of that for many digital businesses. Manual payout tracking comes with several downsides:

• Time-consuming: Every week or month, you're logging into Stripe, downloading reports, and copying data. It adds up.
• Prone to human error: One wrong copy-paste, a missed row, or an incorrect filter, and your figures are skewed.
• Delayed cash flow visibility: If you only update your records periodically, you don't have a real-time picture of your finances, making forecasting and budgeting harder.
• HMRC headache: When it comes to Self Assessment or year-end accounts, piecing together scattered data can be a nightmare. You want a clear audit trail.

By implementing Stripe automation, you're not just saving minutes; you're gaining accuracy and control. Your Google Sheet becomes a living, breathing record of your income, updated automatically. This is a crucial step towards efficient financial admin automation, helping you understand precisely what income has landed and when, which is vital for Make.com finance scenarios.

Understanding the Core Tools: Make.com, Stripe, and Google Sheets

Before we dive into the setup, let's quickly review the tools we'll be using and why they're such a good combination:

Stripe: This is where your money comes from. Stripe processes credit card payments, handles subscriptions, and then bundles these funds into regular payouts to your connected UK bank account. It's robust and widely used, but its native reporting, while comprehensive, still requires manual downloading for ongoing, granular tracking outside its platform.

Make.com: Think of Make.com as the digital glue. It's a visual automation platform that allows you to connect thousands of apps without writing a single line of code. You build "scenarios" that tell different applications to talk to each other. For example, "When X happens in Stripe, do Y in Google Sheets." It's incredibly flexible and powerful for custom automation flows, much more so than some of its simpler competitors, particularly for financial data.

Google Sheets: This is our destination. Google Sheets is a free, cloud-based spreadsheet application that's accessible from anywhere. It's perfect for this scenario because it's easy to connect to automation tools, highly customisable for your specific data needs, and readily shareable if you work with an accountant or team member. Plus, it plays nicely with other Google services, which can be handy for further automation down the line.

The Anatomy of a Stripe Payout for UK Businesses

When Stripe sends you a payout, it's not just a single number; it's a summary of multiple underlying transactions. For UK tax record-keeping, you might need to understand not just the net amount that arrived in your bank, but also the gross amount of sales, the fees Stripe deducted, and any refunds processed. While a simple payout tracker can just record the net amount, a more comprehensive approach considers these details.

A typical Stripe payout will contain:

• Payout ID: A unique identifier for that specific payout. Crucial for matching and referencing.
• Payout Date: When the payout was initiated or completed.
• Arrival Date: The date the funds actually hit your bank account (this can differ slightly from the payout date).
• Amount: The net amount of money transferred to your bank, after Stripe fees and any refunds.
• Currency: Usually GBP for UK businesses, but you might handle other currencies.
• Status: Whether the payout is 'paid', 'pending', or 'failed'.
• Balance Transactions: This is the really granular stuff – a list of all the individual charges, refunds, adjustments, and Stripe fees that make up that single payout amount. This is where the magic happens for true financial clarity.

For our initial setup, we'll focus on getting the core payout details into your sheet. Then, I'll touch on how you might expand this to capture those individual transaction details, which provides much richer data for your accountant or for deeper AI assistant-driven analysis. If you're looking to categorise individual expenses and income for HMRC, you might find Mastering HMRC-Ready AI Expense Tracking for UK Freelancers a useful read.

Setting Up Your Google Sheet for Success

Before we touch Make.com, we need a place for our data to live. Open Google Sheets and create a new, blank spreadsheet. I'd suggest naming it something clear like "Stripe Payout Tracker (WealthFlow Agents)".

In the first row of your sheet, set up your column headers. These are the fields we'll populate from Stripe. I find these particularly useful for UK businesses:

1. Payout ID: Stripe's unique identifier for the payout.
2. Payout Date: The date Stripe initiated the payout.
3. Arrival Date: The estimated date the funds will reach your bank.
4. Net Payout Amount: The amount that landed in your bank (after fees).
5. Currency: e.g., GBP.
6. Status: 'paid', 'pending', etc.
7. Description: A brief summary from Stripe.
8. Total Fees: The sum of Stripe fees deducted from this payout.
9. Gross Amount: The sum of all charges *before* fees and refunds for this payout. (This one requires a slightly more advanced Make.com setup, but it's good to have the column ready).
10. Number of Transactions: How many individual charges/refunds make up this payout.
11. Make.com Scenario Run Date: When our automation actually processed this entry. Useful for debugging!

Keep your sheet clean. Avoid merging cells in the header row or having empty rows above your headers, as this can confuse Make.com. You can always add more columns later if you discover other data points you want to track.

Building Your Automation Scenario in Make.com

Now for the exciting part! Head over to Make.com and log in. If you don't have an account, sign up for one; they have a generous free tier that's perfect for getting started with something like this.

Here's a step-by-step guide to building your scenario:

Step 1: Create a New Scenario

• From your Make.com dashboard, click the large purple "Create a new scenario" button.

Step 2: Add Your Stripe Trigger Module

• Click the large central circle with a plus sign. Search for "Stripe" and select it.
• From the list of triggers, choose "Watch Payout Events". This listens for specific events related to payouts.
• You'll need to create a "webhook" connection to your Stripe account. Make.com will guide you through connecting your Stripe API keys. This is a secure process where you grant Make.com permission to read specific data from your Stripe account. For this, you'll generally need your Secret key from your Stripe Developer settings.
• Once connected, Make.com will present you with an "Add a webhook" dialogue. Just follow the instructions; it usually involves copying a URL from Make.com and pasting it into your Stripe dashboard's "Webhooks" section (dashboard.stripe.com/webhooks). Make sure the event you're listening for is payout.paid or payout.created. I usually start with payout.paid as it signifies the money is definitely on its way.
• Set "Limit" to 1 for initial testing. This means it'll only process one payout event at a time, making it easier to see if it's working correctly.

Step 3: Add Your Google Sheets Action Module

• Click the "Add another module" circle (the one with the plus sign) next to your Stripe module.
• Search for "Google Sheets" and select it.
• Choose the "Add a Row" action.
• Connect your Google Account. This is usually straightforward, as it just requires you to authorise Make.com to access your Google Sheets.
• Configure the module:
  • Spreadsheet: Select the Google Sheet you created earlier (e.g., "Stripe Payout Tracker (WealthFlow Agents)").
  • Sheet Name: Select the specific sheet within your spreadsheet (usually "Sheet1" by default).
  • Table Contains Headers: Ensure this is set to "Yes", as we've already defined our column headers.

Step 4: Map Stripe Data to Google Sheet Columns

This is where you tell Make.com which piece of data from Stripe should go into which column in your Google Sheet. Make.com will display a list of your Google Sheet headers, and you'll drag and drop or select the corresponding Stripe data elements from the dropdown menu (which will appear once Make.com has received some sample data from your Stripe webhook – you might need to run the Stripe module once manually to get this sample data).

Here’s a common mapping you might use:

• Payout ID: Map to ID from the Stripe module (under 'Payout').
• Payout Date: Map to Date from the Stripe module (under 'Payout'). Make sure to format this to a readable date in Google Sheets if needed.
• Arrival Date: Map to Arrival Date from the Stripe module (under 'Payout').
• Net Payout Amount: Map to Amount from the Stripe module (under 'Payout'). Remember, this is in pence, so you'll usually want to divide by 100 in Make.com using a math function (e.g., {{divide(2.amount; 100)}}).
• Currency: Map to Currency from the Stripe module (under 'Payout').
• Status: Map to Status from the Stripe module (under 'Payout').
• Description: Map to Description from the Stripe module (under 'Payout').
• Total Fees: This is a bit trickier. Stripe payouts are *net* of fees. To get the fees, you'd typically need to look at the 'Balance Transactions' that make up the payout. For a simpler setup, you can leave this blank or, more advanced, use an "Iterator" module on the payout's balance transactions to sum fees. For now, let's keep it simple and focus on the net amount.
• Gross Amount: Similar to fees, this requires iterating through related charges. Leave it blank for now or populate it with Net Payout Amount if you're okay with a simpler view initially.
• Number of Transactions: You can often find a field like transactions_count or similar in the Stripe payout object, or you'd sum them via iteration.
• Make.com Scenario Run Date: Use Make.com's built-in now function (e.g., {{now}}) to timestamp when the entry was made.

Refining Your Automation: Handling Multiple Transactions per Payout

The basic scenario above gets you the payout amount. That's a great start for Make.com finance tracking, especially for bank reconciliation. However, for a truly detailed view – one that helps with granular income categorisation or accurately calculating gross sales versus fees – you need to look at the individual transactions within each payout. This is where you might bring in an AI model like ChatGPT or Claude later to help categorise transaction descriptions.

To get individual transaction details, your Make.com scenario would look a little different:

1. Stripe Trigger: "Watch Payout Events" (as before, looking for payout.paid).
2. Stripe Module: "List All Balance Transactions for a Payout". This action takes the Payout ID from the trigger and fetches all the individual charges, refunds, adjustments, and fees associated with that specific payout. This is critical for UK accounting as it provides the full audit trail.
3. Iterator Module: Make.com has an "Iterator" tool. You'd feed the list of balance transactions from the previous step into this. The iterator will then process each individual transaction one by one.
4. Google Sheets Module: "Add a Row". This time, you'd add a row for *each individual transaction* to a separate Google Sheet (perhaps named "Stripe Transactions"). You could map fields like:
   • Transaction ID
   • Payout ID (to link it back)
   • Type (e.g., 'charge', 'refund', 'Stripe fee')
   • Amount (gross charge, refund amount, fee amount)
   • Net Amount (for charges)
   • Currency
   • Description
   • Customer Email (if available)

This more advanced setup gives you incredible detail. You can then use your Google Sheet's capabilities (or even connect it to an accounting package like Xero or QuickBooks via Make.com) to sum up gross sales, calculate total fees, and get a much clearer picture for your tax returns. For ideas on how to use AI models like Gemini for categorisation, check out Essential AI Prompts for UK Small Business Bookkeeping.

Monitoring and Maintenance

Once your scenario is live, it doesn't mean you can forget about it completely, though it will do the heavy lifting. Make.com provides excellent monitoring tools:

• History: In your scenario's detail page, you'll find a "History" tab. This shows every time your scenario ran, how many operations it performed, and if there were any errors. It's your first port of call if something isn't appearing in your Google Sheet.
• Error Handling: You can configure Make.com to send you email or even Notion notifications if a scenario fails. This is a good idea, especially for critical financial flows.
• Testing: Before turning on your scenario permanently, use the "Run once" button to test it. If you trigger a test payout in Stripe (or use an existing one if you have some), you'll see the data flow through Make.com in real-time.
• Regular Review: I'd recommend a quick glance at your Google Sheet weekly or monthly, just to ensure data is still flowing correctly and that the format is as you expect. You might also want to occasionally compare the totals in your sheet to Stripe's own payout reports for an extra layer of verification, especially when you're first getting started.

You'll need to decide how often you want your scenario to run. For payouts, daily is usually sufficient, as payouts generally don't happen more frequently than that. You can set this in the schedule settings of your Make.com scenario.

Beyond Payouts: Expanding Your Financial Automation Horizons

Once you've got this Stripe automation working, you'll likely start seeing other areas where Make.com could assist. Think about:

• Automating Invoice Reminders: If you issue invoices, you could use Make.com to check due dates in a Google Sheet and automatically send follow-up emails. We've got a great guide on that: How to Automate Invoice Reminders with AI and Google Sheets.
• Integrating with Accounting Software: While Google Sheets is great, you might eventually want to push this data directly into your accounting software like Xero, QuickBooks, or FreeAgent. Make.com has modules for most popular accounting platforms.
• AI for Categorisation: As mentioned, once you have detailed transaction data, you could use an AI assistant to help automatically categorise transactions based on descriptions, saving even more manual effort.
• Reporting & Dashboards: Link your Google Sheet to Google Looker Studio (formerly Google Data Studio) for visual dashboards of your Make.com finance and Stripe automation data.

This initial setup for Stripe payout tracking is a foundational step. By automating these repetitive tasks, you're not just saving time; you're gaining better insights into your finances, reducing errors, and making your life as a UK business owner or freelancer significantly easier. Give it a try, and see how much lighter that financial admin hat feels!