Dividend Vouchers and QuickBooks Online: A Complete Integration Guide (UK)

This guide explains a typical QuickBooks Online → dividend voucher workflow at a practical level. It is not legal or tax advice. Confirm compliance requirements for your company's circumstances with an accountant. If you run your books in Xero, read the Xero integration guide instead.

Why integrate dividend vouchers with QuickBooks Online?

For most UK limited companies on QuickBooks Online, the dividend itself is already recorded — a payment leaves the bank, it is coded to a dividend account, and the books balance. What is usually missing is the paperwork around it: the dividend voucher for each shareholder, the board minutes that approved the payment, and the resolution that declared it.

Producing those separately — in Word, in a spreadsheet, in an email thread — creates the same friction every time:

• shareholder names, amounts and dates are re-keyed,
• per-share figures drift from what was actually paid,
• the voucher PDF ends up in a downloads folder rather than against the transaction,
• year-end and Self Assessment questions mean hunting through old files.

An integration approach treats QuickBooks as the source of accounting context, generates the voucher and its companion documents from the same figures, and files the PDF back against the transaction so the audit trail stays in the books.

What data you typically need from QuickBooks Online

A dividend voucher workflow draws on a narrow slice of your QuickBooks company:

• the company you connect (one QuickBooks company per Dividendly company),
• your chart of accounts — specifically the bank account the dividend is paid from and the dividend equity account it is coded to,
• vendors, because QuickBooks has no "shareholder" record — each shareholder is mapped to a vendor so the Purchase has a payee,
• past purchases on the dividend account, if you want to back-fill vouchers for dividends already paid.

Registered office details do not come from QuickBooks. Dividendly fetches them live from Companies House, so the address on the voucher always matches the official record.

One point worth knowing before you connect: QuickBooks only stores the month your financial year starts. It does not store the year-end date. You confirm the financial-year end once, during connect, and every voucher uses it from then on.

A typical end-to-end workflow (at a high level)

Here's the common "happy path" for UK QuickBooks Online users who want a repeatable voucher workflow:

1. Connect your QuickBooks company

   • Authorise the connection through Intuit's OAuth screen. Dividendly requests a single scope, com.intuit.quickbooks.accounting — it does not read payroll or payments.
   • Confirm your financial-year end when prompted.
   • There is no "Sign in with Intuit". You sign in to Dividendly with a magic link (or Sign in with Xero) and connect QuickBooks from inside the company.

2. Choose the bank account and dividend account

   • Pick the bank account dividends are paid from and the equity account they are coded to. Every posting uses this pair.

3. Map shareholders to vendors

   • Match each shareholder to the existing QuickBooks vendor that represents them. If there isn't one, create it in QuickBooks first (QuickBooks UK may list vendors as suppliers). Each shareholder's shareholding and share class are kept in Dividendly, so per-share amounts are calculated from the shareholdings on file, not typed.

4. Run a dividend

   • Enter the total and the date; Dividendly allocates it across shareholders by shareholding and drafts a voucher for each.
   • For each shareholder it posts a Purchase (an expense, with a No VAT line) to the chosen bank and dividend equity account, and attaches the voucher PDF to that Purchase.
   • Board minutes and a dividend declaration (interim) or shareholder resolution (final) are generated alongside, using the defaults you set for the company.

5. Sign and send

   • Each voucher passes through an e-signature acknowledgement step, then goes to the shareholder by email. A copy stays in voucher history.

6. Keep the audit trail in the books

   • Open the Purchase in QuickBooks and the voucher PDF is there as an attachment. Nothing to file separately.

"Upcoming runs" vs "historical runs"

The workflow above is an upcoming run: Dividendly creates the QuickBooks transaction. There is also a historical run for dividends that were paid and coded in QuickBooks before you connected.

A historical run reads past Purchases on your dividend account within a date window you choose, and drafts a voucher for each one — same document, same fields, no new transaction. It is the quickest way to bring an existing company's paperwork up to date, and it needs a connected provider: it is not available in documents-only mode.

Practical integration tips (to avoid common issues)

• Code dividends consistently. Back-fill finds past dividends by account. If some were coded to directors' loan or a miscellaneous expense account, they will not appear until they are recoded.
• Deleting a voucher from an upcoming run deletes the Purchase. QuickBooks has no "void" for Purchases, so when you delete a voucher whose payment Dividendly posted, the linked Purchase is permanently removed from QuickBooks along with its attachment. (In Xero the equivalent transaction is voided, not deleted.) The in-app dialog says this before you confirm — read it.
• Expect a reconnect prompt roughly every 100 days. Intuit's refresh tokens expire. Dividendly tracks the expiry and shows a reconnect prompt before it lapses; it takes a few seconds and nothing is lost.
• One provider per company. A company can be connected to Xero or QuickBooks, not both. Switching means disconnecting one and connecting the other.
• Check the vendor mapping before the first run. A shareholder mapped to the wrong vendor produces a correct voucher against the wrong payee in QuickBooks.

Where QuickBooks fits into compliance (and where it doesn't)

QuickBooks records the money. It does not know whether the company had distributable reserves, whether the directors met to approve the payment, or whether every shareholder in a share class was paid pro rata. Those are the questions a voucher, minutes and resolution exist to answer — and the questions HMRC or a buyer's due-diligence team will ask.

The integration keeps the records consistent with the books. It does not replace the judgement of an accountant on whether a dividend was lawful in the first place.

Your accounting connection tokens are encrypted at rest and voucher PDFs are stored privately behind expiring links; the full scope list and tenant model are on the security page.

FAQ: QuickBooks dividend voucher integration

Does Dividendly work with QuickBooks Desktop?

No. The integration is with QuickBooks Online only, for UK companies (GBP, UK tax years, Companies House).

Does it cost more to connect QuickBooks?

No. Xero and QuickBooks Online integrations are included on every plan, and so is documents-only mode. Plan limits are the same whichever way you work.

Can I generate vouchers for past dividends?

Yes — run a historical back-fill over the date range you need. It reads past Purchases on your dividend account and drafts a voucher for each. Historical runs are included on Growth, Accountant and Enterprise.

What happens in QuickBooks when I delete a voucher?

If the voucher came from an upcoming run, the Purchase Dividendly posted and its attachment are permanently deleted. QuickBooks does not offer a void for Purchases. A back-filled or manual voucher has no Purchase posted by Dividendly, so only the voucher is removed. A generated voucher can't be edited, so check the figures in the PDF preview before you generate. If a voucher turns out to be wrong, delete it and issue a corrected one.

I don't use QuickBooks or Xero. Can I still use Dividendly?

Yes. Pick Documents only at sign-up: vouchers, board minutes and resolutions are generated, e-signed and emailed without any accounting connection. You can connect QuickBooks later without redoing anything. The step-by-step QuickBooks walkthrough covers the connect flow in more detail.