Find unpaid Stripe invoices going to email addresses that bounce.
Match open Stripe invoices with Postmark bounces, then decide which customers need a new billing contact, which bounces were temporary, and which ones are not a delivery problem at all.
Invoices Jul 22–Nov 18, 2026 · Bounces Oct 5–Nov 18 · Read Nov 18
Thirty-one Stripe invoices are open with 48,320 USD still to collect. Nine go to an address that bounced in Postmark in the last 45 days. Five of them, 7,580 USD from 4 customers, go to an address Postmark has deactivated after a hard bounce or an invalid address, and 4 of those are already overdue or have failed payments. Two had temporary bounces, one customer complained about the newsletter, and one bounce was only an out-of-office reply.
WHERE THE RESULT GOES
Google Sheets
Export each data source report to Google Sheets, then add your analysis or checklist to the review Sheet.
Example use case
Ask. Follow up. Take the next step.
✦ AI assistantSample use case
YOU
Which unpaid invoices go to a bouncing address?
✦
Thirty-one Stripe invoices are open with 48,320 USD still to collect. Nine go to an address that bounced in Postmark in the last 45 days. Five of them, 7,580 USD from 4 customers, go to an address Postmark has deactivated after a hard bounce or an invalid address, and 4 of those are already overdue or have failed payments. Two had temporary bounces, one customer complained about the newsletter, and one bounce was only an out-of-office reply.
01
Address no longer works · 5 invoices4 customers · 7,580 USD · 4 overdue or failed (5,180 USD)Get a new billing contact
Harbor Analytics, Pinewood Clinics, Brightline Freight and Copperleaf Studio each have an open invoice whose customer email hard bounced or was rejected as invalid, and Postmark marked the address inactive. Pinewood’s card has failed 3 times and Brightline’s twice, with retries on Nov 21 and Nov 20. Copperleaf’s invoice was due Oct 30, and its invoice email bounced the day it was created. Harbor’s Nov 13 invoice shows no bounce at all, because its billing notices stopped going out after the Oct 21 bounce suppressed the address on that stream.
NextThe account owner for each customer asks their contact for the right billing email this week. Finance updates the customer in Stripe, resends the open invoices from the Stripe Dashboard and checks that the next payment retry has a working card behind it. Reactivate the old address in Postmark only if the customer says it works again.
02
Temporary bounces · 2 invoicesOakridge Dental · Quarry Labs · 3,150 USDWatch the next send
Oakridge Dental’s mailbox soft bounced twice, on Nov 12 and Nov 15, and its invoice is not due until Nov 25. Quarry Labs had one transient delay on Nov 6, but its card has failed twice and Stripe retries on Nov 19. Neither address is inactive, so Postmark will keep sending to them.
NextFinance checks the customer’s email log in Stripe before chasing. If Quarry Labs’ retry on Nov 19 fails, the account owner calls instead of emailing. If Oakridge bounces again after Nov 25, it moves to the first group.
03
Spam complaint on the newsletter · 1 invoiceMesa Realty · 310 USD · 1 failed paymentAccount owner checks in
The person behind Mesa Realty’s billing address marked the November product newsletter as spam. Postmark suppresses addresses per message stream, so the complaint stops broadcast email but not the billing notices on the transactional stream. Their card failed once, with a retry on Nov 22.
NextNo address change is needed. The account owner mentions the failed payment when they next speak, and marketing leaves the address off broadcasts. Spam complaints cannot be reactivated without Postmark support, so do not move billing email to the broadcast stream.
04
Not a delivery problem · 2 invoices1 out-of-office reply · 1 invoice with no customer emailNormal collection, one fix
Fernhill Bakery Supply’s only bounce was an automatic out-of-office reply, which Postmark records as a bounce type even though the message was delivered. Delta Row Fitness has no customer email on its invoice, so there is nothing to match, and its card has failed once.
NextFernhill stays in normal collection. Finance adds a billing email to Delta Row Fitness in Stripe before the Nov 21 retry. Separately, 6 of the 21 open invoices with no bounce are overdue or have failed payments; Postmark keeps bounce details only for its retention period, so check those addresses on each stream’s Suppressions page in Postmark.
Invoices Jul 22–Nov 18, 2026 · Bounces Oct 5–Nov 18 · Read Nov 18
01 · CONNECT YOUR DATA
Your tools. One place to ask.
2 of 3 Free data sources No credit card · Daily refresh
DatapipeYour project
✦Your AI assistantor a report in Sheets / Data Studio
Create your free workspace
Sign up with your company email. Your first project opens on Data sources.
Add the data sources
Choose the accounts for this use case. Authorize access and select the property or site.
Bring your question
Connect your project to a supported AI assistant, or build your source reports.
Email/password signups confirm their email first. Use Google signup with a company account if you prefer.
Stripe: Authorize the intended Stripe account using its supported sign-in or dedicated read-key setup. Setup guide ↗
Postmark: Paste the Server API token from your Postmark server’s API Tokens tab, then click Save and check. Each Postmark server is added on its own, and Datapipe only reads its bounces, message streams and delivery stats. Setup guide ↗
Free includes 3 data sources across the workspace. One account/property added to one project counts as one. Extra properties or the same account in another project use another slot.
02 · ASK A USEFUL QUESTION
Start with a prompt. Follow the evidence.
Copy these in order into your connected assistant. Each builds on the answer before it.
01
Find the open invoices and where they were sent
Read the full prompt
Use only this Datapipe project’s authorized data. Discover the connected accounts, datasets and compatible fields first. Confirm dates, timezones, currencies and data coverage. Keep missing or unmatched rows visible; never substitute sample data. Compare the sources explicitly and explain every match. Do not change source records or send messages.
From the connected Stripe account, read the invoice resource only, for a 120-day creation window ending today in UTC, and show the window boundaries. Return invoice.id, invoice.number, invoice.customer, invoice.customer_name, invoice.customer_email, invoice.created, invoice.status, invoice.collection_method, invoice.currency, invoice.amount_remaining, invoice.due_date, invoice.attempt_count and invoice.next_payment_attempt. Keep invoices with status open and amount remaining above zero, convert amounts from the smallest currency unit, and total them per currency. For each one, say whether it is past invoice.due_date or has a failed automatic payment (charge_automatically with at least one attempt), and list open invoices with no customer email separately.
02
Read the Postmark bounces for those addresses
Read the full prompt
From the connected Postmark server, read Message streams with Stream ID, Stream name and Stream type, then Bounces with Bounce ID, Message stream, Bounce type, Recipient email, Subject, Inactive and Bounced at for the last 45 days. Tell me how many bounces and distinct addresses there are, and which streams are transactional or broadcast. Match each open invoice’s customer email to Recipient email after trimming spaces and lowering case, and list every matching bounce with its type, stream, Inactive and date. Bounced at is a date as Postmark reports it, so do not infer the time of day. Do not treat a bounce for a colleague at the same company domain as the invoice contact’s own.
03
Prepare the billing contact review
Read the full prompt
Put every open invoice in exactly one group. Address no longer works: a HardBounce, BadEmailAddress or ManuallyDeactivated bounce marked inactive. Spam complaint: a SpamComplaint, with the stream it came from. Temporary: SoftBounce, Transient or DnsError only. Out-of-office only: AutoResponder and nothing else. No customer email. No bounce. Build one table with invoice number, customer, email, amount remaining, due date or next payment attempt, whether it is behind, bounce types, streams, last bounce date and a suggested owner, and total each group per currency. Separately list open invoices with no bounce that are overdue or have failed payments, so someone can check Postmark’s Suppressions page for older bounces. Draft everything here; do not change Stripe customers, resend invoices or reactivate addresses.
Match each open invoice to its bounces and decide who acts.
01
Read the open invoices and the email they were sent to.
02
Read Postmark bounces from every stream.
03
Match each open invoice to its bounces and decide who acts.
↗
Check the result at your next review.
At next week’s finance review, read both sources again. The 5 invoices in the first group should either be paid or have a customer with a new email in Stripe, and no new bounce for the new addresses. Pinewood Clinics and Brightline Freight should have a working card before their retries. Count how many of the 4 overdue or failed invoices in that group, 5,180 USD, were collected. If the same customers still have no reply after a corrected email, the delay is not about the mailbox, and the account owner takes it from there.
Implementation tips for this use case
Match invoice.customer_email to Recipient email after trimming and lowercasing. Put each open invoice in one group: address no longer works (a hard bounce, invalid address or manual deactivation marked inactive), spam complaint, temporary bounce (soft bounce, transient or DNS error), out-of-office only, no customer email, or no bounce. Within each group, mark invoices that are past their due date or have a failed automatic payment. Take the list to the weekly finance review: account owners ask customers for a working billing contact, and finance updates Stripe and resends. The assistant prepares the list; it does not change Stripe or Postmark.
WHEN YOU NEED MORE CONTEXT
Go a little deeper.
The method and reporting checks behind this example.
How to find unpaid Stripe invoices sent to email addresses that bounce in Postmark
Read the open invoices and the email they were sent to.
Add the Stripe account you bill from and the Postmark server that sends your product and billing email to one project. Read the invoice resource with invoice.id, invoice.number, invoice.customer, invoice.customer_name, invoice.customer_email, invoice.created, invoice.status, invoice.collection_method, invoice.currency, invoice.amount_remaining, invoice.due_date, invoice.attempt_count and invoice.next_payment_attempt for a 120-day creation window in UTC, and keep invoices with status open and an amount remaining. Amounts are in the smallest currency unit, so divide USD by 100. invoice.customer_email is frozen when the invoice is finalized, so it shows the address the invoice went to, even if someone has since changed the customer.
Read Postmark bounces from every stream.
In Postmark, read Message streams with Stream ID, Stream name and Stream type, then read Bounces with Bounce ID, Message stream, Bounce type, Recipient email, Subject, Inactive and Bounced at for the last 45 days. Datapipe reads every stream, not only the default transactional one. Postmark keeps bounce details for your retention period, 45 days unless you changed it, and applies the date window in US Eastern time, so compare dates rather than times. Inactive means Postmark stopped sending to that address on that stream; suppressions are kept per stream, and Postmark sends nothing to a suppressed address, so it produces no new bounces.
Match each open invoice to its bounces and decide who acts.
Match invoice.customer_email to Recipient email after trimming and lowercasing. Put each open invoice in one group: address no longer works (a hard bounce, invalid address or manual deactivation marked inactive), spam complaint, temporary bounce (soft bounce, transient or DNS error), out-of-office only, no customer email, or no bounce. Within each group, mark invoices that are past their due date or have a failed automatic payment. Take the list to the weekly finance review: account owners ask customers for a working billing contact, and finance updates Stripe and resends. The assistant prepares the list; it does not change Stripe or Postmark.
See the complete example report
EXAMPLE REPORT
Which unpaid invoices go to a bouncing address?
Invoices Jul 22–Nov 18, 2026 · Bounces Oct 5–Nov 18 · Read Nov 18
Which unpaid invoices go to a bouncing address?
Bounce evidence
Open invoices · USD
Who acts
Dead address
5 · 7,580
Owner, then finance
Temporary bounce
2 · 3,150
Finance watches
Newsletter complaint
1 · 310
Account owner
WHAT TO LOOK ATThirty-one Stripe invoices are open with 48,320 USD still to collect. Nine go to an address that bounced in Postmark in the last 45 days. Five of them, 7,580 USD from 4 customers, go to an address Postmark has deactivated after a hard bounce or an invalid address, and 4 of those are already overdue or have failed payments. Two had temporary bounces, one customer complained about the newsletter, and one bounce was only an out-of-office reply.
Match each open invoice to its bounces and decide who acts.
Harbor Analytics, Pinewood Clinics, Brightline Freight and Copperleaf Studio each have an open invoice whose customer email hard bounced or was rejected as invalid, and Postmark marked the address inactive. Pinewood’s card has failed 3 times and Brightline’s twice, with retries on Nov 21 and Nov 20. Copperleaf’s invoice was due Oct 30, and its invoice email bounced the day it was created. Harbor’s Nov 13 invoice shows no bounce at all, because its billing notices stopped going out after the Oct 21 bounce suppressed the address on that stream. Oakridge Dental’s mailbox soft bounced twice, on Nov 12 and Nov 15, and its invoice is not due until Nov 25. Quarry Labs had one transient delay on Nov 6, but its card has failed twice and Stripe retries on Nov 19. Neither address is inactive, so Postmark will keep sending to them. The person behind Mesa Realty’s billing address marked the November product newsletter as spam. Postmark suppresses addresses per message stream, so the complaint stops broadcast email but not the billing notices on the transactional stream. Their card failed once, with a retry on Nov 22. Fernhill Bakery Supply’s only bounce was an automatic out-of-office reply, which Postmark records as a bounce type even though the message was delivered. Delta Row Fitness has no customer email on its invoice, so there is nothing to match, and its card has failed once.
Try the example with sample CSVs
Fictional rows matching the example above. Attach these files to your assistant for a sample analysis.
Data method, reporting checks & sources
Add the Stripe account you bill from and the Postmark server that sends your product and billing email to one project. Read the invoice resource with invoice.id, invoice.number, invoice.customer, invoice.customer_name, invoice.customer_email, invoice.created, invoice.status, invoice.collection_method, invoice.currency, invoice.amount_remaining, invoice.due_date, invoice.attempt_count and invoice.next_payment_attempt for a 120-day creation window in UTC, and keep invoices with status open and an amount remaining. Amounts are in the smallest currency unit, so divide USD by 100. invoice.customer_email is frozen when the invoice is finalized, so it shows the address the invoice went to, even if someone has since changed the customer. In Postmark, read Message streams with Stream ID, Stream name and Stream type, then read Bounces with Bounce ID, Message stream, Bounce type, Recipient email, Subject, Inactive and Bounced at for the last 45 days. Datapipe reads every stream, not only the default transactional one. Postmark keeps bounce details for your retention period, 45 days unless you changed it, and applies the date window in US Eastern time, so compare dates rather than times. Inactive means Postmark stopped sending to that address on that stream; suppressions are kept per stream, and Postmark sends nothing to a suppressed address, so it produces no new bounces. Match invoice.customer_email to Recipient email after trimming and lowercasing. Put each open invoice in one group: address no longer works (a hard bounce, invalid address or manual deactivation marked inactive), spam complaint, temporary bounce (soft bounce, transient or DNS error), out-of-office only, no customer email, or no bounce. Within each group, mark invoices that are past their due date or have a failed automatic payment. Take the list to the weekly finance review: account owners ask customers for a working billing contact, and finance updates Stripe and resends. The assistant prepares the list; it does not change Stripe or Postmark.
Only open invoices with an amount remaining are reviewed, and amounts are converted from the smallest currency unit and totaled per currency. invoice.customer_email is the address the invoice was finalized with; it is matched to Postmark’s Recipient email after trimming and lowercasing. Out-of-office replies are left off the problem list, and a spam complaint on a broadcast stream is not treated as a dead address. Postmark only returns bounces inside its retention period, so overdue invoices with no bounce are listed for a manual Suppressions check.
Only open invoices with an amount remaining are reviewed, and amounts are converted from the smallest currency unit and totaled per currency.
invoice.customer_email is the address the invoice was finalized with; it is matched to Postmark’s Recipient email after trimming and lowercasing.
Out-of-office replies are left off the problem list, and a spam complaint on a broadcast stream is not treated as a dead address.
Postmark only returns bounces inside its retention period, so overdue invoices with no bounce are listed for a manual Suppressions check.
Access to the intended Stripe account or property.
Access to the intended Postmark account or property.
Only open invoices with an amount remaining are reviewed, and amounts are converted from the smallest currency unit and totaled per currency.
For blended reports, align dates, normalized URLs, and reporting grain. Query-level search rows must not duplicate page-level sessions.
Stripe shows what is unpaid, how late it is and which email address the invoice was sent to. Postmark shows whether mail to that address actually arrives. An overdue invoice with a dead mailbox needs a new contact, not another reminder, and neither tool shows both.
Stripe sends its own invoice emails. Why look at Postmark?
Many teams turn off Stripe’s invoice emails and send their own billing notices from the app through Postmark. Even if Stripe sends the invoice, a mailbox that hard bounces your other email is almost certainly rejecting Stripe’s too. Stripe’s own delivery is not in this read; check the customer’s email log in the Stripe Dashboard before acting.
Why did one invoice have no bounce even though the address is dead?
Once Postmark marks an address inactive on a stream, it stops sending to it there, so later messages create no new bounce. In the example, Harbor Analytics’ second invoice shows nothing because the first bounce already suppressed the address on the billing stream.
Why only 45 days of bounces?
Postmark keeps bounce details for your message retention period, 45 days by default. Older hard bounces and spam complaints stay on each stream’s Suppressions page in Postmark, which this read does not include, so the review lists overdue invoices with no bounce for a manual check there.
Is a spam complaint the same as a dead address?
No. The person received the email and marked it as spam. Postmark suppresses the address only on the stream where the complaint happened, so a complaint about a newsletter does not stop billing notices on a transactional stream.
Does the assistant update customers or resend invoices?
No. It prepares the grouped list in your conversation. Account owners contact customers, finance updates the billing email and resends from Stripe, and whoever runs Postmark decides whether to reactivate an address.
YOUR NEXT STEP
Try it with your own data.
Start free with up to 3 data sources. No credit card.