Stripe BECS Direct Debit in QuickBooks (Australia)

A Melbourne co-working operator bills its members by Stripe BECS Direct Debit on Thursday, 29 October. There are 180 dedicated-desk members at A$420 a month and 260 flex members at A$89. The money leaves most of their bank accounts that same Thursday. Stripe does not call any of the payments successful until Monday, 2 November, mid-morning Melbourne time.

So the October run is cash the members have already paid and sales the operator has not yet confirmed. Then comes the part that makes BECS unlike almost anything else Stripe supports: any of those members can go to their bank and reverse the debit, no questions asked, for up to seven years. October 2026's billing stays open until October 2033, and the operator cannot win any of those disputes.

This guide covers how Stripe BECS Direct Debit moves Australian dollars, what it costs, and what reaches QuickBooks at each stage: the two-day wait, the failures and retries, the seven-year dispute tail, and the refund that can cost you the payment twice.

Acodei syncs your Stripe activity into QuickBooks Online, including the failures and disputes that arrive long after the sale. Start a free trial.

What is Stripe BECS Direct Debit?

Stripe BECS Direct Debit is a bank debit that pulls Australian dollars from a customer's Australian bank account, using the account's BSB and account number, under a mandate the customer accepts at checkout. It is only available to Stripe accounts based in Australia, and Stripe confirms each payment about two business days after it is submitted.

BECS stands for the Bulk Electronic Clearing System, the Australian clearing system that carries the debits. In the Stripe API the payment method is called au_becs_debit, and that is the name you will see in exports, reports and webhooks. Stripe's BECS Direct Debit documentation lists the rules this guide relies on.

Four setup details matter later for your books:

• AUD only. The presentment currency is AUD and the customer must be in Australia. There is no second currency to reconcile, unlike Canadian pre-authorized debit, which can run in CAD or USD.
• The Direct Debit Request. In BECS, a mandate is called a Direct Debit Request, or DDR. The customer gives the account holder's name, BSB and account number and accepts the DDR Service Agreement. Stripe can generate the mandate for you.
• Default limits. New users start at 10,000 AUD per transaction and 10,000 AUD per week. Larger annual plans or B2B invoices may need a limit increase from Stripe support before they can go through BECS at all.
• Extra verification. Stripe asks for additional identity verification after you request BECS in your payment method settings, so request it well before your first billing run.

BECS works with Stripe Checkout, Elements, Invoicing, Payment Links and Subscriptions. For a subscription business, the saved mandate covers every future billing period.

How long does a BECS Direct Debit take on Stripe?

Stripe marks a standard BECS payment successful at T+2, at 00:00 UTC, two business days after submission. The funds become available in your Stripe balance at the same moment. A payment created before 18:30 Melbourne time on a business day is submitted that day. Otherwise it goes the next business day.

The detail that surprises bookkeepers is in Stripe's own timeline: the funds are debited from the customer's account at T+0, the day the payment is submitted. The customer sees the money leave two business days before Stripe tells you the payment worked.

For the co-working run, that gives this timeline:

Step	Date (Melbourne)
Debits created and submitted, before 18:30	Thursday, 29 October
Money leaves members' bank accounts (T+0)	Thursday, 29 October
Payments marked successful and funds available (T+2, 00:00 UTC)	Monday, 2 November, 11:00

Midnight UTC is 11:00 in Melbourne during daylight saving, and 10:00 the rest of the year. Either way, the October run succeeds in November. A member who rings on Friday asking why the debit has not been "confirmed" yet is right: their bank has paid and Stripe is still waiting for the scheme to say so.

Stripe also exposes an expected_debit_date on each charge, an estimate of when the customer's account is debited. It is an estimate, and Stripe says the actual date can vary. Use it to answer customer questions, not to date entries in QuickBooks.

BECS also has a notification rule worth knowing before your first run. The scheme advises notifying the customer when the mandate is set up and each time you debit them, and Stripe sends those emails by default, with the pre-debit email going out the day before the debit. The BECS guidelines suggest notifying 14 calendar days ahead, but Stripe notes that this is not mandatory. A clear pre-debit email is the cheapest dispute prevention you have, for reasons the dispute section makes obvious.

How BECS compares with SEPA, Bacs and Canadian PAD

If you also collect in euros, pounds or Canadian dollars, our guide to SEPA Direct Debit failures and disputes covers the euro side. All four schemes share a shape: a mandate, a short wait, and disputes you cannot win. The numbers that decide when a payment is really finished are very different.

	BECS Direct Debit	SEPA Direct Debit	Bacs Direct Debit	Canadian PAD
Currency	AUD	EUR	GBP	CAD or USD
Marked successful	T+2	T+6	T+3	T+4
Dispute window	Up to 7 years	8 weeks, or 13 months if unauthorized	No time limit	90 days personal, 10 business days business
Automatic retries (insufficient funds)	Up to 4, within 30 days	Up to 2, within 30 days	Up to 2, within 30 days	1, within 30 days
Appeal	None	None	None	None

Two rows stand out for an Australian business.

BECS is the fastest of the four to settle. Two business days keeps the month-end overhang small.

The dispute window runs the other way. Seven years is longer than any of the others except Bacs, which has no limit at all. It is longer than most businesses keep a customer relationship active, and it outlasts most annual plans by a factor of seven. Unlike SEPA, there is no shorter "no questions asked" period followed by a stricter unauthorized-only period: Stripe states the full seven years are no questions asked.

What BECS costs on Stripe in Australia

Stripe's Australian pricing for local payment methods lists BECS Direct Debit at:

• 1% + A$0.30 per successful payment, capped at A$3.50
• A$2.50 for each failed payment
• A$2.50 for each disputed payment

The cap starts at A$320, because 1% of A$320 plus A$0.30 is exactly A$3.50. Every payment above that costs the same A$3.50. A A$420 dedicated-desk membership costs A$3.50 to collect, against A$7.23 at Stripe's domestic card rate of 1.65% + A$0.30. On an A$89 flex membership the BECS fee is A$1.19.

Here is the co-working October run. Two dedicated-desk members fail: one for insufficient funds, and one whose account has been closed. Four flex members fail too, three of them for insufficient funds.

Line	Count	Amount
Dedicated desks successful (A$420)	178	A$74,760.00
Flex memberships successful (A$89)	256	A$22,784.00
Processing fees, desks (178 × A$3.50)		−A$623.00
Processing fees, flex (256 × A$1.19)		−A$304.64
Failed-payment fees (6 × A$2.50)		−A$15.00
Net from the run		A$96,601.36

The A$15.00 is the line ledgers lose. Failure fees are costs with no sale attached, so a QuickBooks file that tracks only sales and processing fees drifts from the Stripe balance by A$2.50 every time a debit bounces. The same goes for the A$2.50 on every dispute, years after the sale.

Recording Stripe BECS Direct Debit payments in QuickBooks while they settle

A BECS payment spends two business days in processing. You can record the sale when the debit is created and reverse it if it fails, or wait until Stripe marks it successful. Recording early keeps sales in line with what you billed and with what the customer's bank statement shows. Waiting means every sale is backed by settled cash, but the last two business days of each month slide into the next.

Acodei records early. When its daily scan finds a pending charge, such as a bank debit that has not settled, it creates an individual transaction for it and sends it through the same real-time path as any other sale, rather than putting an unsettled amount into a daily summary. The charge is marked succeeded when Stripe's webhook confirms settlement. If the payment fails instead, the entry is reversed on the failure date and included as a line item on the daily balance summary.

For the co-working run, that has a month-end consequence. Stripe says a BECS success or failure can take up to three business days to be notified, and in this example the six failures are reported on Monday, 2 November. If your books carry the October run's sales in October, the six reversals still land in November, because the reversal is dated when the failure happens. October's BECS revenue is then overstated by A$1,196 (2 × A$420 plus 4 × A$89) and November's understated by the same amount. Over a year it washes out. If you bill on the last business days of the month and report monthly, it is worth knowing which month each reversal lands in before someone asks why November's membership revenue dipped.

Failed BECS payments, retries and mandates

A BECS payment fails when the customer's bank refuses the debit, most often for insufficient funds. Stripe charges A$2.50 for each failure and records a failure code on the payment.

Stripe Billing can retry the insufficient-funds failures for you. With Direct Debit retries switched on, Stripe retries each failed BECS payment up to 4 times, no more than 30 days after the original attempt, and it does not charge failure fees for those automatic retries. Retries can be switched on for subscription invoices, one-off invoices, or both.

Each retry is a new charge with its own two-day cycle, and the failed attempt stays in Stripe as a separate failed charge. So one member's October bill can produce a sale, a reversal on the failure date, and a separate record for the retry that finally succeeds. Each of those is correct, and together they are where most "duplicate" questions come from at month end.

Not every failure is worth retrying. Stripe's BECS testing guide shows which failure codes end the mandate:

• account_closed, no_account and debit_not_authorized move the mandate to inactive. You need a new mandate before you can debit that customer again.
• refer_to_customer leaves the mandate active. The bank wants the customer to sort something out, and a later debit can succeed.

Stripe sends mandate.updated when a mandate goes inactive, whether the customer cancelled it or a permanent failure ended it. Customers can cancel a DDR at any time, through you or through their bank, and that invalidates every future debit. Our Stripe mandate glossary entry covers the object Stripe uses to track this. For the bookkeeper, an inactive mandate means the customer's next invoice will not collect on its own, so it belongs on the close checklist rather than in the failed-payments pile.

Seven years of BECS disputes in QuickBooks

BECS disputes are where this payment method earns its own guide. Stripe's rules:

• Seven years, no questions asked. For up to 7 years, a customer can dispute a payment through their bank, and the bank honors every dispute within that period.
• Immediate deduction. If the bank accepts the request, Stripe removes the funds from your balance straight away and deducts the A$2.50 dispute fee.
• No appeal. All BECS disputes are final. You cannot submit evidence. If you reach an agreement with the customer, they make a new payment.

Back in Melbourne, a dedicated-desk member who left in December disputes the October debit on Monday, 15 March 2027, after a disagreement about the notice period: −A$420.00 and −A$2.50. That one lands inside the same Australian financial year as the sale. The harder case is the flex member who disputes an October 2026 debit in 2029, after you have lodged two more years of returns. Seven years means every BECS debit you take stays a potential liability long after the books for its year are closed.

In Stripe's balance-transaction model, a dispute is an adjustment. In Acodei you map adjustments once, under Balance Transaction Mapping on the Account Mapping page, to a product that points at either your refunds account or a separate expense account for disputes. Acodei then processes the dispute in the daily balance summary or with the payout, depending on your settings. If Adjustments are not mapped yet, the payout that contains the dispute does not sync, and the Data Feed tells you to turn the type on. Once it is mapped, you resync the deposit from the Payouts tab. Our guide to Stripe balance transaction mapping walks through the setup.

Which account should BECS disputes go to? Because no BECS dispute can be won, there is nothing to park while you wait for an outcome, so a "pending disputes" clearing account adds work for no benefit. A dedicated "Direct debit disputes" expense account keeps these losses out of your refunds line and gives you one number to compare with Stripe's dispute total each month. Our guide to Stripe chargeback accounting in QuickBooks covers the wider choices.

The seven-year tail also makes a QuickBooks closing date worth setting if you have not already. A closing date, with a password, stops entries dated in a closed period from being added or changed without someone deciding to do it. Agree with your accountant how a dispute on a debit from a closed year should be booked, then check each late dispute against that rule when it arrives.

Refunds and the double credit

Stripe's BECS page warns that if you refund a customer while their bank also processes a dispute, the customer can receive two credits for the same payment. Stripe also states plainly that issuing a refund does not prevent a dispute from being processed.

BECS refunds make the overlap easy to trigger:

• They are slow. BECS refunds typically take 3 to 5 business days to process. A customer who does not see the money can call their bank in the meantime.
• They are unlabelled. The refund arrives as a credit carrying a reference to the original payment's statement descriptor, not the word "refund".
• The descriptor is short. In the lodgement reference, your statement descriptor is cut to its first 9 alphanumeric characters plus a unique ID, so "ROCKETRIDES" appears as "ROCKETRID" followed by the ID. A customer may not recognize it.

Picture a flex member who cancelled in September and was billed for October anyway. You refund the A$89 on Tuesday, 3 November. Before the credit arrives, they dispute the October debit with their bank, well inside seven years. You have now paid back A$178 and A$2.50 in dispute fees for one A$89 payment.

In QuickBooks, that shows up as two reversals of the same sale:

• A refund dated 3 November. Acodei records Stripe refunds to the Stripe refunds account you chose at setup, or to the matching product's account if you use multiple product mapping.
• A dispute adjustment, wherever you mapped Adjustments, plus the A$2.50 fee.

Both entries are true, so both belong in your books. What closes the gap is a receivable and a conversation. Stripe's advice for avoiding it:

1. Tell the customer you are refunding, so they do not also go to their bank.
2. Tell them a BECS refund takes several business days to arrive.
3. Issue the refund only after the original payment has fully settled.

Two more refund rules. BECS refunds must be issued within 90 days of the original payment, which is short next to a seven-year dispute window, so an old billing error may have to be repaid outside Stripe. And a refund on a payment that has not completed waits until the charge succeeds, and is cancelled if the charge fails, so a failed debit never leaves a refund for you to account for. For refunds after the money has been paid out, see refunding a Stripe payment after payout.

A BECS month-end close in QuickBooks

Card-first close checklists miss the BECS timings. These steps cover them:

1. List the BECS payments still processing on the last day of the month. Anything submitted in the last two business days will be marked successful in the next month, and any failure among them will be reported there too.
2. Clear the failures. Match each reversal to a next step: retry pending, customer contacted, or new mandate needed. Pull every account_closed, no_account and debit_not_authorized failure into the new-mandate list.
3. Count the failure fees. Stripe's failure fees for the month should match a line in QuickBooks. Six failures at A$2.50 is A$15.00 you will not find on any sale.
4. Reconcile disputes. Your dispute account should equal Stripe's dispute total for the month, fees included. A gap usually means a payout that did not sync because Adjustments were not mapped.
5. Look for refund-and-dispute pairs. Any customer with both a refund and a dispute on the same payment needs a receivable and a call.
6. Check inactive mandates. Customers whose mandate went inactive this month will not be collected next month unless someone acts.

If your QuickBooks home currency is AUD, BECS adds no currency work: payments, fees and disputes are all in AUD. If it is not, for example a United States parent company that books an Australian subsidiary's Stripe account in one file, every BECS payment is a foreign-currency transaction. Multicurrency Support in Acodei is turned on by the Acodei team rather than in your own settings. Once it is on, QuickBooks keeps a separate customer record for each currency, such as "Acme - AUD", by design. Our guide to Stripe multicurrency in QuickBooks has the details.

Frequently asked questions

How long does a Stripe BECS Direct Debit take?

Stripe marks a standard BECS Direct Debit payment successful two business days after submission (T+2, at 00:00 UTC), and the funds are available in your Stripe balance at the same time. Payments created before 18:30 Melbourne time on a business day are submitted that day. The customer's account is usually debited on the day of submission.

How long can a customer dispute a BECS Direct Debit?

Up to seven years. Stripe states that a customer can dispute a BECS Direct Debit payment through their bank on a no-questions-asked basis for up to 7 years, and the bank honors every dispute in that period. Disputes are final, you cannot submit evidence, and Stripe deducts the amount plus a A$2.50 dispute fee.

Can I win a BECS Direct Debit dispute on Stripe?

No. Stripe states that all BECS Direct Debit disputes are final and cannot be appealed. If you and the customer agree that they owe the money after all, they need to make a new payment, which you record as a new sale. Map Stripe adjustments to the account where you want these losses to appear.

How much does Stripe charge for BECS Direct Debit in Australia?

Stripe's Australian pricing lists BECS Direct Debit at 1% plus A$0.30 per payment, capped at A$3.50, plus A$2.50 for each failed payment and A$2.50 for each disputed payment. The cap applies from A$320, so every larger payment costs A$3.50 to collect. Automatic Billing retries are not charged a failure fee.

Does Stripe retry failed BECS payments?

Yes, if you switch on Direct Debit retries in Stripe Billing. Stripe retries each BECS payment that failed for insufficient funds up to 4 times, within 30 days of the original attempt, and does not charge failure fees for those retries. Each retry is a new charge, so the failed attempt and the retry are separate events in your books.

BECS Direct Debit is the cheapest and fastest way to collect from Australian bank accounts on Stripe, and the slowest to become final. Acodei records each payment, reverses the failures on the dates they happen, and posts disputes through your Balance Transaction Mapping, so the late ones show up where your close can find them. Start a free trial.