Make Scenario: Payment to Spreadsheet Automation for 2026

Manually logging payments into a spreadsheet is exactly the kind of work Make was built to remove. You do not need a huge accounting project to get value here. One scenario that writes each payment to a single sheet can give you real visibility into revenue, fast.

Some links in this guide are affiliate links. I only recommend tools I actually use or would use in my own business.

This scenario takes payments from your main processor and logs them into a Google Sheet. It follows the same logic you mapped in your payment-to-bookkeeping article, but keeps the implementation simple and visual.

What this scenario does

• Trigger: A new paid order or charge in Shopify, Stripe, SumUp, or another processor.
• Action: Add a row in a “Revenue” Google Sheet with date, customer, description, gross, fees, net, and source.

Step 1: Create your revenue sheet

In Google Sheets, create a sheet called “Revenue, 2026.” Add columns: Date, Customer, Description, Gross, Fees, Net, Source, Payment ID, Notes. This is where all payments will land.

Step 2: Choose your first payment source

Pick the processor you want to wire up first (for example, Stripe). You can add more processors later by repeating the pattern with a different trigger and a different “Source” value.

Step 3: Build the scenario in Make

1. Create a new scenario in Make.
2. Add your payment app as the first module (“Watch Events,” “Watch Charges,” or similar).
3. Configure it to trigger on successful payments only.
4. Run “Run once” and create a small test payment so Make can see sample data.

Step 4: Add the Google Sheets row creation

1. Add “Google Sheets, Add a Row” as the next module.
2. Connect to your “Revenue, 2026” sheet and select the correct tab.
3. Map fields:
   • Date = payment created date.
   • Customer = billing name or email.
   • Description = product name or internal label.
   • Gross = total amount.
   • Fees = fee amount if available, or 0.
   • Net = gross minus fees.
   • Source = hardcoded (for example, “Stripe”).
   • Payment ID = the processor’s unique ID.

Step 5: Test and turn on

• Run the scenario once and trigger 1, 2 small test payments.
• Check your sheet to make sure rows appear as expected.
• Fix any mapping mistakes (wrong columns, wrong formats).
• Turn scheduling on so it runs automatically.

Over time you can extend this with filters, categories, or connections into your accounting tool, but this single sheet will already give you a clean, trustworthy view of what actually came in this week.