Sending email from QuickBooks Desktop after the password sign-in cut-off

QuickBooks Desktop webmail stops sending once Gmail and Microsoft reject plain passwords; an older install can still email invoices reliably.

Webmail inside QuickBooks Desktop asks for a username and a password. Gmail and Microsoft no longer accept that kind of sign-in from mail-sending programs, so invoices that used to leave the building now sit with an authentication error. You have two ways forward: move to a release that signs in the modern way, or teach an older install to hand its mail to desktop Outlook, which handles the modern sign-in on its own.

The password door is closed

Google retired password sign-in for third-party mail programs in 2022. Microsoft completed the same withdrawal across its personal and business mailboxes in the years that followed. Both providers now expect an OAuth sign-in: the program opens the provider's own page, you approve access, and the program keeps a token instead of a password.

QuickBooks webmail was built around the older method. It stores your username and password and presents them to the mail server each time a form goes out. The password is still correct. The server simply refuses it, because plain passwords are no longer an accepted credential on that door. The result looks exactly like a broken password: the setup screen accepts it, the test message fails, and sent forms come back with an authentication error. Nothing is wrong with your account. The login method itself has been retired.

Which releases can sign in the modern way?

Press F2 inside QuickBooks to open the Product Information window and note the year and release. Intuit introduced sign-in through the provider's own web page, which it calls secure webmail, across the 2021 line and later. From 2022 onward it is the normal path. You can confirm your build at a glance: if the webmail setup opens a browser window asking you to sign in to Google or Microsoft, your release has the capability. If it still shows two text fields, it does not.

A copy on an active subscription can be brought current through Help, then Update QuickBooks Desktop, then Update Now. Install the newest maintenance release and press F2 again. Secure webmail stores a token rather than a password, so after the first sign-in you should not be asked for either again. Keep Windows current as well, because the sign-in handshake depends on modern encryption that very old systems handle badly.

A perpetual 2020 or older install no longer receives maintenance releases, so the modern code path cannot be added to it. For those machines, the Outlook route below is the durable answer. It also suits anyone who has finished moving the file onto a perpetual licence of its own and intends to stay there.

A Google app password buys time

If your account is Google and 2-Step Verification is switched on, you can generate a 16-character app password in your Google Account settings and paste it into the webmail password field. Google still honours these for legacy mail programs. Treat it as a stopgap rather than a fix: the credential is an exception Google grants, not a method it promises to keep. Microsoft has withdrawn the equivalent for its personal accounts, so this path does not exist there at all. Plan the Outlook switch regardless.

Send through desktop Outlook instead

Desktop Outlook, from Microsoft 365 or Office 2016 onward, signs in to Gmail and Microsoft mailboxes with the modern method and keeps its own session alive. QuickBooks can hand each form to Outlook and let Outlook deal with the provider. Setup takes a few minutes:

1. Add the sending account to Outlook itself and complete its sign-in once. From then on, Outlook refreshes its access without your help.
2. In QuickBooks, open Edit, then Preferences, then Send Forms. On the My Preferences tab, set Send email using to Outlook and confirm.
3. In Windows Settings, under Default apps, make Outlook the default program for email. QuickBooks passes mail through the Windows mail interface.
4. Send any invoice as a test. Approve the first prompt Outlook shows; later sends run without one.

Because authentication now lives in Outlook, provider changes land on Outlook, which is built for them, rather than on an ageing QuickBooks email module. If the internet drops mid-day, forms wait in the Outlook Outbox and leave on the next send and receive.

Why does sending still fail after the switch?

Three causes cover most failures our engineers see. The first is bitness: QuickBooks Desktop is a 32-bit program, and older releases only cooperate with 32-bit Office, while newer releases work with either. If QuickBooks cannot see Outlook at all, or it hangs the moment a form is sent, check which Office build is installed.

The second is elevation. When one program runs as administrator and the other does not, Windows blocks the handoff between them. Run both the same way.

The third is the default mail setting. An Office update can reset it, and the Send Forms preference is stored per Windows user, so every user on every workstation needs the same setup. Work through the four steps again on the machine that fails and the link usually comes back.

Keeping the setup working

Keep Outlook updated, because it is now the piece that talks to the provider. Keep Windows current, since both the OAuth handshake and the Outlook link depend on system components. Note that Intuit's own email service is not an alternative here: it rides on a supported subscription, so a perpetual install cannot rely on it either. The Outlook path is the one that does not care how old your QuickBooks is, and that is precisely what makes it the right one for the long term.