Why don't credit memos appear immediately in QuickBooks?

Zapier checks for new Stripe refunds every 15 minutes on paid plans, 15 minutes on free plans. The credit memo creates within 2-3 minutes after Zapier detects the refund.

What happens if a customer doesn't exist in QuickBooks?

The Zap will fail with a 'Customer not found' error. You'll get an email notification and need to either create the customer in QuickBooks or update the customer email to match an existing record.

Can I automatically apply credit memos to open invoices?

No, Zapier's QuickBooks integration only creates credit memos - it can't automatically apply them to invoices. You'll need to apply credits manually in QuickBooks or use a more advanced integration platform.

Do partial refunds create separate credit memos?

Yes, each Stripe refund event triggers a separate credit memo in QuickBooks. Multiple partial refunds on the same charge create multiple credit memos, which is correct accounting treatment.

How do I handle refunds for deleted Stripe customers?

The Zap will fail if the Stripe customer was deleted but the refund still references them. Add a filter to check if customer data exists, or modify the customer mapping to use a default 'Deleted Customer' record in QuickBooks.

Beginner~8 min setupFinance & FinanceVerified April 2026

How to Record Stripe Refunds in QuickBooks with Zapier

Automatically create credit memos in QuickBooks whenever Stripe processes a refund to keep your accounting accurate.

Steps and UI details are based on platform versions at time of writing — check each platform for the latest interface.

Zapier

Also on:Make N8n Power-automate Pipedream

Best for

Small businesses processing under 200 refunds monthly who want automatic QuickBooks credit memo creation without coding

Not ideal for

High-volume merchants needing real-time sync or complex refund approval workflows before accounting entry

Sync type

polling

Use case type

sync

Real-World Example

💡

A 12-person e-commerce startup uses this to automatically record their 30-40 monthly Stripe refunds as QuickBooks credit memos. Before automation, their bookkeeper manually created credit memos twice weekly, often missing refunds that happened over weekends. This caused month-end reconciliation headaches when Stripe deposits didn't match QuickBooks revenue reports.

What Will This Cost?

Drag the slider to your expected monthly volume.

Monthly workflow runs

/mo

505005K50K

Each platform counts differently — Zapier: 1 task per trigger. Make: 1 operation per module per record. n8n: 1 execution per run.

$30/mo if billed monthly

Pipedream

$29/mo

Basic plan

Prices shown for annual billing. Based on published pricing as of April 2026.

Estimated ROI

1000

min saved/mo

$583

labor value/mo

Free

no platform cost

Based on ~2 min manual effort per operation at $35/hr fully loaded labor cost.

Implementation

Before You Start

Make sure you have everything ready.

Active Stripe account with refund processing enabled

QuickBooks Online subscription (not Desktop version)

Matching customer records between Stripe and QuickBooks

Zapier account with available task credits

Admin access to both Stripe and QuickBooks accounts

Field Mapping

Map these fields between your apps.

Field	API Name	Description
Required
Customer Email	`customer.email`	Maps Stripe customer email to QuickBooks customer lookup for credit memo assignment
Refund Amount	`amount_refunded`	Dollar amount of the refund, converted from Stripe's cents format to QuickBooks currency
Charge Description	`description`	Original charge description to use as the credit memo line item description
Stripe Charge ID	`id`	Unique Stripe charge identifier for the memo field to enable transaction tracing
Refund Date	`created`	Timestamp when refund was processed in Stripe for proper accounting period assignment

1 optional field▸ show

Customer Name customer.name Stripe customer display name as fallback if email lookup fails in QuickBooks

Step-by-Step Setup

Dashboard > Create Zap > Choose App & Event

Create new Zap with Stripe trigger

Start a new Zap and select Stripe as your trigger app. Choose the 'Charge Dispute' or 'Invoice Payment Failed' event since Stripe doesn't have a dedicated refund trigger - you'll filter for refunds in the next step.

1Click 'Create Zap' from your Zapier dashboard
2Search for 'Stripe' in the trigger app selector
3Select 'Charge Dispute' from the trigger event dropdown
4Click 'Continue' to proceed to connection setup

✓ What you should see: You should see the Stripe trigger configured with 'Charge Dispute' selected as the event type.

⚠

Common mistake — Don't select 'New Charge' - that triggers on payments, not refunds, and you'll get flooded with irrelevant data

Zapier

click +

search apps

QuickBooks

Create new Zap with Stripe t…

QuickBooks

module added

Trigger > Stripe > Account Connection

Connect your Stripe account

Authenticate with Stripe using your API keys. Zapier needs read access to pull refund data from your Stripe account.

1Click 'Sign in to Stripe' button
2Enter your Stripe account credentials
3Authorize Zapier to access your Stripe data
4Select your Stripe account from the dropdown if you have multiple

✓ What you should see: Green 'Connected' badge appears next to your Stripe account name in the connection panel.

Zapier settings

Connection

Choose a connection…Add

click Add

QuickBooks

Authorize Zapier

popup window

✓

Connected

green checkmark

Zap Steps > + > Filter by Zapier

Add filter for refund events

Since Stripe's webhook sends all dispute events, add a filter to only proceed when the event type is actually a refund. This prevents credit memos for chargebacks or other disputes.

1Click the '+' button between trigger and action steps
2Select 'Filter by Zapier' from the app list
3Set condition to 'Reason' 'Exactly matches' 'refund_requested'
4Click 'Continue' to save the filter

✓ What you should see: Filter step shows 'Only continue if Reason exactly matches refund_requested' in the step summary.

⚠

Common mistake — Don't use 'Contains' matching - Stripe sends various dispute reasons and you'll catch unrelated events

QuickBooks

trigger

filter

Condition

matches criteria?

yes — passes through

no — skipped

Stripe

notified

Zap Steps > + > QuickBooks Online > Create Credit Memo

Add QuickBooks action step

Set up QuickBooks as your action app to create the credit memo. Choose 'Create Credit Memo' since this matches the accounting treatment for refunds.

1Click '+' to add an action step after your filter
2Search for 'QuickBooks Online' in the app selector
3Select 'Create Credit Memo' from the action event list
4Click 'Continue' to proceed to account connection

✓ What you should see: QuickBooks Online appears as your action step with 'Create Credit Memo' configured.

⚠

Common mistake — Don't confuse 'Create Credit Memo' with 'Create Refund Receipt' - credit memos reduce A/R while refund receipts are for cash transactions

Action > QuickBooks Online > Account Connection

Connect QuickBooks Online

Authenticate with your QuickBooks company file. Zapier needs write permissions to create credit memos in your accounting system.

1Click 'Sign in to QuickBooks Online'
2Choose your company from the QuickBooks login screen
3Grant Zapier permission to access your QuickBooks data
4Verify the correct company appears in the connection dropdown

✓ What you should see: Your QuickBooks company name shows with a green 'Connected' status indicator.

⚠

Common mistake — Make sure you're connecting to your live company file, not a sandbox - Zapier can't sync data between QB environments

Action > QuickBooks Online > Credit Memo Fields > Customer

Map customer information

Link the Stripe customer to the corresponding QuickBooks customer. This ensures the credit memo applies to the right customer account.

1Click in the 'Customer' field in the credit memo form
2Select 'Customer Email' from the Stripe trigger data
3Set 'Customer Display Name' to map to Stripe's customer name field
4Choose 'Find existing customer' for the customer lookup method

✓ What you should see: Customer field shows mapped Stripe data with 'Customer Email' and lookup method configured.

⚠

Common mistake — QuickBooks matches customers by email - if your Stripe customer emails don't match QB exactly, the lookup will fail

QuickBooks fields

DocNumber

CustomerRef.name

TotalAmt

Balance

DueDate

available as variables:

1.props.DocNumber

1.props.CustomerRef.name

1.props.TotalAmt

1.props.Balance

1.props.DueDate

Action > QuickBooks Online > Credit Memo Fields > Line Items

Configure line item details

Set up the credit memo line items to reflect the refunded amount and description. Map the refund amount and original charge description from Stripe.

1Click in the 'Line 1 Description' field
2Map to 'Charge Description' from your Stripe trigger data
3Set 'Line 1 Amount' to the 'Amount Refunded' field from Stripe
4Leave 'Line 1 Item' blank unless you track specific products

✓ What you should see: Line item section shows Stripe charge description and refund amount mapped to the credit memo fields.

⚠

Common mistake — Use 'Amount Refunded' not 'Amount' - Stripe amounts are in cents so partial refunds will show the wrong value if you map the original charge amount

Action > QuickBooks Online > Credit Memo Fields > Accounting

Set accounting categories

Assign the credit memo to the correct income account to properly categorize the refund. This should match the account used for the original sale.

1Click the 'Line 1 Account' dropdown
2Select your main income/revenue account
3Set 'Tax Code' to match your original sales tax treatment
4Leave 'Class' and 'Location' blank unless required

✓ What you should see: Account field shows your selected income account with tax settings configured.

⚠

Common mistake — Don't use an expense account here - credit memos should reduce income, not create expenses, or your P&L will be wrong

Action > QuickBooks Online > Credit Memo Fields > Additional Details

Add reference information

Include the Stripe charge ID in the memo field so you can trace the credit memo back to the original payment. This helps with reconciliation and customer inquiries.

1Click in the 'Memo' field at the bottom of the form
2Type 'Stripe Refund: ' followed by the Charge ID from trigger data
3Set 'Credit Memo Date' to 'Created' timestamp from Stripe
4Leave 'Credit Memo Number' blank to auto-generate

✓ What you should see: Memo field shows 'Stripe Refund: ch_xxxxx' with the actual charge ID mapped from Stripe data.

⚠

Common mistake — Don't use today's date - use Stripe's created timestamp so the credit memo date matches when the refund actually happened

Action > QuickBooks Online > Test & Continue

Test the integration

Run a test to verify the credit memo creates correctly in QuickBooks with all the mapped Stripe data. This catches field mapping issues before you go live.

1Click 'Test & Continue' at the bottom of the action step
2Review the test credit memo data in the results panel
3Open QuickBooks and verify the test credit memo appeared
4Check that customer, amount, and memo details are correct

✓ What you should see: Test results show 'Success' with a QuickBooks credit memo ID, and the actual credit memo appears in your QB company file.

⚠

Common mistake — The test creates a real credit memo in QuickBooks - delete it manually if you don't want test data in your live books

Zapier

▶ Turn on & test

executed

✓

QuickBooks

✓

Stripe

🔔 notification

received

Zap Settings > Error Handling

Configure error handling

Set up error notifications so you know if refunds fail to sync. QuickBooks API errors are common when customer data doesn't match exactly.

1Click 'Settings' in the Zap header menu
2Scroll to 'Error Handling' section
3Select 'Send email notification' for failed Zaps
4Add your email address to receive error alerts

✓ What you should see: Error handling shows 'Email notification enabled' with your email address listed.

⚠

Common mistake — Don't set errors to 'Skip' - failed refund syncs create accounting discrepancies that you need to catch and fix manually

Zap Header > On/Off Toggle

Turn on the Zap

Activate your automation to start syncing Stripe refunds to QuickBooks. The Zap will check for new refunds every 15 minutes on paid plans.

1Click the toggle switch in the top right to 'On' position
2Confirm activation in the popup dialog
3Review the 'Zap History' tab to monitor for successful runs
4Set a calendar reminder to check the integration weekly

✓ What you should see: Zap status shows 'On' with a green indicator, and you should see 'Waiting for data' in the Zap History.

⚠

Common mistake — Zapier's free plan has 15-minute delays - refund credit memos won't appear in QuickBooks immediately after processing in Stripe

Drop this into a Zapier Code step.

Copy this template{{amount_refunded__value}}/100

▸ Show code

{{amount_refunded__value}}/100

... expand to see full code

{{amount_refunded__value}}/100

Scaling Beyond 200+ refunds/month+ Records

If your volume exceeds 200+ refunds/month records, apply these adjustments.

Add rate limit delays

Insert 'Delay by Zapier' steps between QuickBooks actions to avoid hitting the 500 requests/hour API limit. Set 10-15 second delays for volumes over 200 monthly refunds.

Batch process during business hours

Use 'Schedule by Zapier' to queue refunds and process them during 9-5 when QuickBooks API limits reset. This prevents weekend refund backlogs from failing Monday morning.

Consider QuickBooks Advanced

Upgrade to QB Advanced for higher API rate limits (1000/hour vs 500/hour) if you regularly hit timeout errors during high refund periods like Black Friday.

Going live

Production Checklist

Before you turn this on for real, confirm each item.

Test with a real refund, not sample data, to verify customer matching works

Applies when: Always

Set error handling to email notification, not 'Skip' mode

Applies when: Always

Add Formatter step to convert Stripe cents to dollars if amounts look wrong

Applies when: Always

Verify credit memo posts to correct income account, not an expense account

Applies when: Always

Configure 10-second delays between QuickBooks API calls

Applies when: High volume

Set up duplicate detection based on Stripe charge ID in memo field

Applies when: High volume

Troubleshooting

Common errors and how to fix them.

Frequently Asked Questions

Common questions about this workflow.

Analysis

VerdictWhy Zapier for this workflow

Use Zapier for this if you process under 200 refunds per month and your team doesn't want to code custom webhooks. The setup takes 15 minutes and runs automatically after that. Your credit memos appear in QuickBooks within 15 minutes of the Stripe refund. Skip Zapier if you need real-time sync — go direct with Stripe webhooks to a custom endpoint instead.

Cost

This workflow uses 2 tasks per refund: one for the Stripe trigger and one for the QuickBooks credit memo creation. At 50 refunds per month, that's 100 tasks monthly. The Zapier Professional plan at $19.99 covers 750 tasks, so you're well within limits. Make would cost $9/month for the same volume with their Core plan. N8n self-hosted is free but requires server maintenance. Make saves you $11 monthly if cost matters more than convenience.

Tradeoffs

Make handles QuickBooks rate limiting better with built-in delays between API calls — Zapier can hit the 500/hour limit if you process refunds in batches. N8n gives you more control over error handling and retry logic when QuickBooks API calls fail. But Zapier's guided setup means you'll have this running today instead of spending a weekend reading API docs. Most small businesses value the time savings over the extra features.

You'll hit QuickBooks' customer matching quirks fast. If Stripe customer emails have extra spaces or different capitalization than QuickBooks, lookups fail silently. Stripe sends amounts in cents but QuickBooks expects dollars — easy to miss until you see $500 refunds as $5.00 credit memos. The Zapier trigger checks every 15 minutes, so refunds that happen Friday night don't show up in QB until Monday morning. Plan your month-end close accordingly.

Ideas for what to build next

→
Add Slack notifications for large refunds — Create a second Zap that sends Slack alerts when refunds exceed a dollar threshold so your team knows about significant credits immediately.
→
Sync credit memo applications back to Stripe — Build a reverse integration that updates Stripe customer notes when credit memos get applied to invoices in QuickBooks for complete audit trails.
→
Create monthly refund summary reports — Set up a scheduled Zap that pulls monthly credit memo data from QuickBooks and emails a refund summary to your finance team.