A fair number of companies in Vietnam keep their books in QuickBooks Online or Xero — usually foreign-owned subsidiaries whose parent standardised on one of them, or service businesses invoicing overseas clients.

The question worth asking is not whether these are good products. They are. It is narrower and more practical: how far do they get you in Vietnam, and what do you have to bolt on?

The short answer

You can run QuickBooks or Xero in Vietnam. You cannot run only QuickBooks or Xero.

There are three obligations under Vietnamese rules that neither product performs, and none of them can be worked around with configuration.

1. They cannot issue Vietnamese e-invoices

Vietnam's e-invoice regime is centralised. Since 1 July 2026 it has operated under Decree 254/2026/ND-CP and Circular 91/2026/TT-BTC, replacing Decree 123/2020 and Decree 70/2025.

Under that regime, only an organisation that has contracted with the tax authority to receive, transmit and store e-invoice data may provide the service. That is a licensed, listed role — and a foreign SaaS accounting product is not on the list.

So when you sell something in Vietnam, the invoice does not come out of QuickBooks. It comes out of a Vietnamese e-invoice solution, and then somebody records it in QuickBooks. That is your first duplication.

2. They cannot pull your input invoices from the tax portal

This is the one that eats the most time, and it is invisible until you are living it.

Your suppliers issue e-invoices, which are filed with the tax authority. Your copy of those invoices lives on the national portal at hoadondientu.gdt.gov.vn. To get them into your books, someone has to log in, filter by period, download the XML files, and enter them.

Neither QuickBooks nor Xero connects to that portal. There is no integration to enable, because the connection is Vietnam-specific and the portal is not something a foreign vendor builds for.

For a company with a couple of hundred purchase invoices a month, this is where the bookkeeping hours actually go. Not to judgement — to retrieval and typing.

3. They cannot produce Vietnamese statutory output

You can edit the chart of accounts in either product and map balances onto Circular 99/2025 or Circular 133 account numbers. That part is genuinely solvable.

What is not solvable inside the product is the output. Vietnamese statutory financial statements and tax returns follow prescribed forms. Getting from a QuickBooks trial balance to a filed Vietnamese return means someone re-entering the numbers into Vietnamese software or the tax authority's own tool.

And underneath all of it sits the language and currency requirement. The Accounting Law 88/2015/QH13 provides that the written language used in accounting is Vietnamese — where a foreign language is used on vouchers, books and financial statements used in Vietnam, both must appear — and that the accounting currency is the Vietnamese dong. An English-only ledger is a management record, not the statutory one.

What the two-system setup really costs

Companies usually budget one line for this and get surprised by three:

Cost line Typically budgeted?
QuickBooks or Xero subscription Yes
Vietnamese e-invoice solution Sometimes
Monthly labour re-keying between systems Almost never

The third line is the one that grows. It scales with transaction volume, it does not go away as the team gets more experienced, and it is the line where errors originate — because a number typed twice is a number that can disagree with itself.

There is also a quieter cost: when the Vietnamese ledger is assembled from the foreign one rather than kept in parallel, it tends to be assembled late. That is fine until the annual audit, when the auditor works from the Vietnamese books and the tax authority's invoice records, and any gap between them becomes a finding.

When keeping QuickBooks or Xero is still the right call

Not every company should drop them. Keep the foreign system when:

  • Your parent consolidates in it and reporting into the group is a genuine requirement, not a habit.
  • Most of your revenue is invoiced overseas, so the Vietnamese e-invoice volume is small and the duplication is minor.
  • You have a real management-reporting need in English that the group already understands.

In those cases the sensible architecture is: foreign system for group reporting, Vietnamese system for the statutory set, and as little manual movement between them as you can arrange.

Drop the foreign system when it is there by inertia — when nobody upstream actually reads its output, and you are paying a subscription plus a monthly re-keying tax for reports no one opens.

The version of this that does not hurt

If the statutory side is going to exist anyway, the thing to optimise is how much typing it demands. That is the design brief Vietbooks was built to:

  • Input invoices arrive on their own. Vietbooks fetches them from the tax authority nightly and backfills the year, so nobody logs into the portal to download XML files.
  • Bank statements become journal entries. Upload the statement and the AI proposes the postings; your accountant reviews instead of keying.
  • The statutory set stays native — Vietnamese, VND, under Circular 99/2025 or Circular 133 — and e-invoices are issued through approved providers, so there is no separate invoicing tool to reconcile against.

What that leaves is a much smaller bridge to your group system: a trial balance, once a month, instead of a second full bookkeeping operation.

Free for 30 days, no card required. Start a trial.

Read next

This article is general guidance, not legal or tax advice, and reflects the position as at August 2026. It refers to the Accounting Law 88/2015/QH13, Decree 254/2026/ND-CP and Circular 91/2026/TT-BTC on electronic invoices, and Circulars 99/2025/TT-BTC and 133/2016/TT-BTC on accounting regimes. Product capabilities and the list of licensed e-invoice service providers change over time; verify the current position with the vendor and with the tax authority that administers your company.