In this article

Accounting for Stripe Credit Risk and Collections under ASC 606 and ASC 326

September 15, 2026
4
min read
Insights
Monk and HubiFi webinar promo: Accounting for Stripe Credit Risk and Collections under ASC 606 and 326, September 29 at 1pm ET, with Cody Leach and George Kurdin

On Tuesday, September 29, Monk is co-hosting a webinar with HubiFi on how to account for Stripe credit risk and collections under ASC 606 and ASC 326. The session runs at 1pm ET / 10am PT, it is CPE accredited, and accountants who attend earn 1.0 CPE credit in Accounting.

Cody Leach, CPA, Head of Product Experience at HubiFi, is joined by our co-founder George Kurdin from Monk. The session is built for accounting and finance leaders who are closing books on revenue that runs through Stripe and who need a defensible position on credit losses before an auditor asks for one.

What the session covers

The hour is split between accounting treatment and operations.

On the accounting side, Cody walks through how to account for credit risk and bad debt under the applicable standards. ASC 606 governs how you recognize revenue and how collectibility factors into that judgment. ASC 326, the current expected credit loss model, governs how you reserve against receivables you may not collect. The two interact, and the session covers where.

On the operations side, the conversation moves to where credit risk shows up in a Stripe-based revenue stack, and what a finance team can do about it before it becomes a write-off.

The session opens with the four ways revenue leakage shows up in a subscription or usage-based business, then works through the accounting considerations for each.

Why Stripe changes the credit risk picture

A Stripe-based revenue stack produces failure modes that a traditional invoice-and-check business does not.

Cards decline. Limits get hit. A customer stays on the books as current while their payment method quietly stops working. Subscription revenue keeps recognizing while the cash behind it does not arrive. Finance teams often find out at close, or later.

Under ASC 326 those patterns are supposed to inform your expected credit loss estimate. Most teams build that estimate from an aging report, which is a lagging view. Payment behavior is available earlier than aging, and the session covers how to use it.

Where this meets accounts receivable in practice

The accounting question and the collections question are the same question asked at different times.

If you can see which accounts are drifting before they age, you can set a credit limit or adjust terms rather than book a reserve later. Monk manages more than $2B in receivables and the credit tooling we have shipped this year is built around that: a credit management workspace that holds limits and terms in one place, and dynamic credit management that reads payment behavior rather than a bureau score alone.

Monk is in the Stripe App Marketplace, so the payment history behind those decisions is the same data your revenue runs on. More on that in Monk's Stripe app.

One boundary worth naming. Monk follows up on invoices and manages collections. It does not run card-decline retries. Recovering a failed card charge is a separate job from collecting an overdue invoice, and the session treats them separately.

How to earn the CPE credit

HubiFi is the CPE sponsor for this session, Sponsor ID 169732, Field of Study: Accounting. Participants earn 1.0 CPE credit.

To receive the full credit you must attend live, answer at least three poll questions during the session, and stay on for the full duration. Recordings do not qualify.

How to register

Registration is open at hubifi.com/resources-webinars.

Tuesday, September 29, 2026. 1pm ET / 10am PT.

If you cannot attend live, register anyway and HubiFi will send the recording. You will not earn CPE credit for watching it later, but the material stands on its own.

Frequently asked questions

Who should attend this webinar?

Controllers, accounting managers, CPAs, and finance leaders who recognize revenue that flows through Stripe. It assumes working familiarity with revenue recognition rather than a specialist background in credit modeling.

What is the difference between ASC 606 and ASC 326 here?

ASC 606 governs revenue recognition, including whether collection is probable at the point you recognize. ASC 326 governs the allowance you carry against receivables you expect not to collect, under the current expected credit loss model. One decides what goes on the books, the other decides what you reserve against it.

Do I earn CPE credit for watching the recording?

No. CPE credit requires live attendance, participation in at least three polls, and staying for the full session.

How many CPE credits is this worth?

1.0 credit in Accounting. HubiFi is the sponsor, Sponsor ID 169732.

Does Monk handle failed card payments?

No. Monk follows up on invoices and manages collections through to cash. Retrying a declined card is a different job handled by card recovery tools.

How does Monk use payment behavior for credit decisions?

Monk reads payment history and how an account has responded over time, and surfaces accounts that are drifting before they show up in an aging bucket. You can read more in how to assess customer credit risk.

Is there a cost to attend?

No. The session is free. Registration is required for CPE tracking.

Automate Accounts Receivable with Monk
Monk brings together collections, cash application, and forecasting. 40% DSO reduction. $2B+ in receivables managed. 26 hours a month back to your team.
Book a demo

Manual AR is death by a thousand cuts

Deploy the Monk platform on your toughest AR problems.