Accounting
QuickBooks
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 4 dimensions proven
by Intuit Inc. · quickbooks.intuit.com
Compare with Xero → Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
QuickBooks is Intuit's accounting product, but the captured public pages are a privacy statement, so the bench verified almost nothing about the books. Scores sit at 0-0 on bookkeeping core, GoBD compliance, tax and filings, documents and banking, adviser handoff and pricing transparency, sovereignty alone spans 0-1, and the flagged splits report none. The judges found no public information on double-entry bookkeeping, SKR03/SKR04 charts of accounts, a period close, GoBD conformity or a Verfahrensdokumentation, on VAT logic, UStVA, ELSTER or EÜR, on bank feeds or receipt capture, or on a DATEV export or adviser login; the sole bookkeeping mention is "bookkeeping details from QuickBooks" powering other Intuit products. On sovereignty, Intuit Inc. is the named controller, US tax return information is "processed and stored in the United States", other data may sit in "any other country" where Intuit or its providers operate facilities, transfers rest on standard contractual clauses and the EU-U.S. Data Privacy Framework, and we found no published subprocessor list; the third parties named are YouTube, Twilio, the credit bureaus, FullStory and Medallia. No prices appear in the captures.
Speaks for it
- Intuit self-certifies under the EU-U.S. Data Privacy Framework, its UK Extension and the Swiss-U.S. DPF, with TRUSTe handling disputes at no cost to the individual
- Cross-border transfers are papered with the European Commission's Standard Contractual Clauses of 4 June 2021, plus the UK Addendum and Swiss Modifications
- Biometric information is collected only after notice and consent, with a separate Biometric Notice published
- Data obtained through Google Workspace APIs is not used to develop, improve or train generalized AI or ML models
Held against it
- Bookkeeping core scores 0-0, with no public information on double-entry bookkeeping, SKR03/SKR04 charts, journals, opening balances or a period close
- GoBD compliance scores 0-0, with no GoBD claim, audit trail or Verfahrensdokumentation found in the captured pages
- Tax and filings scores 0-0, with no VAT logic, UStVA, ELSTER or EÜR found; the only tax statement captured concerns US tax return information stored in the United States
- Adviser handoff scores 0-0, with no DATEV export, other named export format or adviser login found
- Sovereignty scores 0-1, with no EU hosting option named and US tax return information stated to be stored in the United States
Best for
- Your business files US taxes and wants its US tax return information processed and stored in the United States, as the pages state
- You procure from vendors certified under the EU-U.S. Data Privacy Framework and papering transfers with standard contractual clauses — both confirmed in the captured pages
- You are consolidating on the Intuit platform and accept bookkeeping details being used to power experiences across QuickBooks, Mailchimp, TurboTax and Credit Karma
Avoid if
- Your books must remain under EU hosting — the pages name no EU hosting option and reserve storage in "any other country" where Intuit or its providers operate facilities
- You cannot accept session-replay recording of your team's user sessions by providers such as FullStory and Medallia
- You will not accept your bookkeeping details being shared across the Intuit Platform to power other products
- You must see the ledger, German filings and a DATEV handoff documented before signing — the captured public pages are a privacy statement and nothing else
The scores
Bookkeeping core
Show reasoningHide reasoning
How this is scored
Double-entry, the chart of accounts (SKR03/SKR04), postings, journals, opening balances and period closing — the ledger underneath the pretty screens.
0 — Income-and-expense lists only; no double-entry, no chart of accounts, no journal.
3 — Simplified bookkeeping suitable for EÜR with a fixed account list; no free posting, no period close.
5 — Double-entry with SKR03/SKR04, manual postings, journals, opening balances and a month-end close.
8 — Full ledger with cost centres, recurring and reversing entries, accruals, multi-year comparatives, and a documented close checklist with locking.
10 — An accountant's ledger: configurable charts including customised accounts, period locking with audit, foreign currency with documented valuation, group or multi-entity handling, and reporting that reconciles to the trial balance.
The Bookkeeper
What was captured is a privacy statement and nothing else: we found no public information on double-entry bookkeeping, a German chart of accounts, journals, opening balances or a month-end close that locks. A ledger with no documented close is unproven as far as I am concerned, so this sits at the bottom. 1 1
The Tax Adviser
Forty year-ends a year and the captured pages say nothing about the ledger: we found no public information on double-entry bookkeeping, SKR03/SKR04 or any other chart of accounts, journals, opening balances or a period close. The only bookkeeping mention is that QuickBooks details feed the wider Intuit platform, which tells me nothing about postings. 1 1
The Auditor
The captured pages are a privacy statement and nothing else; we found no public information on double-entry, a chart of accounts such as SKR03 or SKR04, journals, opening balances or a period close. Without a ledger description I cannot begin to examine the books underneath the screens. 1 1
The Founder
The ledger underneath the screens is the first thing I check, and I found no public information on double-entry, a chart of accounts, journals, opening balances, or a period close — the only captured material is a privacy statement. A bookkeeping core this unevidenced lands at the bottom of the scale. 1
The Integrator
The captured pages are a privacy statement, and the only ledger-related detail anywhere is that Intuit may use "your bookkeeping details from QuickBooks" to power other products. We found no public information on double-entry bookkeeping, an SKR03/SKR04 chart of accounts, manual postings, journals, opening balances or a period close — the ledger underneath the screens is undocumented here. 1 1
The Skeptic
The captured pages are a privacy statement, and I found no public information on the ledger underneath the product — nothing on double-entry, SKR03/SKR04 charts, journals, opening balances or a period close. A product name in an accounting category is not evidence of a posting engine, so this sits at the lowest step. 1 1
GoBD, immutability & audit
Show reasoningHide reasoning
How this is scored
Whether the record survives a tax audit: unalterable postings, complete change history, retention across the statutory period, and a Verfahrensdokumentation the vendor actually supplies.
0 — Postings can be edited or deleted without trace; no retention statement, no GoBD claim, no documentation.
3 — GoBD asserted on the marketing page with nothing behind it — no described audit trail, no documentation offered, no statement on retention.
5 — Postings become unalterable after close with corrections booked as reversals, a change log exists, and the statutory retention period is stated.
8 — Documented GoBD conformity with a supplied Verfahrensdokumentation template, complete and exportable audit trail, receipts linked to postings, and a GoBD-compliant data export (GDPdU/Z3) for the auditor.
10 — Audit-ready as a product feature: an independent GoBD certification or attestation published, Verfahrensdokumentation maintained per release, tamper-evident journals, retention executed across the full statutory period, and an export the Betriebsprüfer accepts without argument.
The Bookkeeper
We found no public information on GoBD conformity, unalterable postings, a change log or a Verfahrensdokumentation. The only retention language is personal information kept "as long as it is necessary to comply with our data retention requirements" — a privacy commitment, not a statement that postings survive a German tax audit. 1
The Tax Adviser
We found no GoBD statement, no audit-trail description and no Verfahrensdokumentation in the captured pages. The only retention language concerns personal information kept "as long as it is necessary" — nothing on unalterable postings surviving a Betriebsprüfung, so this sits at the floor. 1 1
The Auditor
I ask for the Verfahrensdokumentation and an export the Betriebsprüfer accepts, and we found no public information on either — no GoBD claim, no posting immutability, no change history, no audit trail, no data export for the auditor. The only retention statement in the record covers personal information kept as long as business and legal needs require, which says nothing about posting records surviving the statutory period. 1
The Founder
Whether my postings would survive a Betriebsprüfung is unaddressed: I found no public information on a GoBD claim, an audit trail, unalterable postings, or accounting-record retention, and the one retention statement concerns personal information kept as long as business needs require. Nothing on a Verfahrensdokumentation either. 1
The Integrator
The captures show no GoBD claim, no described audit trail, no Verfahrensdokumentation and no auditor export, and the only retention language keeps personal information "as long as it is necessary" for legal compliance and running the business — nothing about accounting records or the statutory period. Whether postings can be changed without trace, and whether corrections are booked as reversals after close, is something we found no public information on. 1 1
The Skeptic
I found no public information on GoBD conformity, unalterable postings, an audit trail or a Verfahrensdokumentation — not even the bare "GoBD-konform" line that would lift it one step. The only retention wording captured concerns personal information kept "as long as necessary", which says nothing about statutory retention of accounting records. 1
Tax handling & filings
Show reasoningHide reasoning
How this is scored
VAT logic and the filings that follow: UStVA, ELSTER submission, EÜR or Bilanz, OSS for cross-border sales, and reverse-charge handling.
0 — No VAT logic beyond a rate field; no filings, no ELSTER.
3 — VAT rates and a UStVA figure to copy out by hand; no electronic submission, no special cases.
5 — UStVA prepared and submitted electronically via ELSTER, EÜR or a simple balance sheet produced, and reverse-charge and intra-community supply handled.
8 — The above plus OSS handling for cross-border B2C, Zusammenfassende Meldung, small-business (§19) and Ist/Soll taxation, permanent extension (Dauerfristverlängerung), and E-Bilanz where relevant.
10 — The filing year is handled end to end: every routine German filing generated and submitted electronically with validation before sending, cross-border VAT determined from the transaction rather than by hand, and correction filings supported.
The Bookkeeper
We found no public information on VAT rates, UStVA, ELSTER submission, EÜR, OSS or reverse-charge handling. The one filing-adjacent statement in the captures is that US tax return information is processed and stored in the United States, which describes a US tax arrangement rather than German filings. 1
The Tax Adviser
We found no public information on VAT logic, UStVA, ELSTER submission, EÜR or OSS; the only filing-related statement is that US tax return information is processed and stored in the United States. For my German clients these captures are silent on every filing I prepare. 1
The Auditor
We found no public information on VAT rates or logic, UStVA preparation, ELSTER submission, EÜR or balance sheet output, OSS or reverse-charge handling. The one statement on tax storage concerns US Tax Return Information processed and stored in the United States — American filings, not the German filing year. 1
The Founder
I pay for the hour saved on VAT, and I found no public information on VAT logic, UStVA, ELSTER submission, EÜR, or reverse-charge handling. The only tax statement captured is that US tax return information is processed and stored in the United States. 1
The Integrator
The only tax facts captured concern United States tax-return information stored in the US and TurboTax data being shared across the Intuit platform. We found no public information on VAT logic, UStVA preparation, ELSTER submission, EÜR or a balance sheet, OSS, or reverse-charge handling — there is nothing here from which to run a German filing year. 1 1
The Skeptic
I found no public information on VAT logic, UStVA, ELSTER or any German filing; the captured pages are silent on the entire filing year. The single tax-adjacent statement is that US tax return information is processed and stored in the United States — a different jurisdiction's story. 1
Receipts, banking & matching
Show reasoningHide reasoning
How this is scored
How evidence and money get into the ledger: bank feeds, receipt capture, OCR, matching rules, and whether the digital receipt is legally sufficient on its own.
0 — Manual entry only; no bank connection, no receipt storage.
3 — Bank statement import by file and receipt upload as plain attachments; matching is entirely manual.
5 — Automatic bank feeds for the major German banks, receipt upload with OCR, suggested matches, and receipts linked to their postings.
8 — PSD2 feeds across many institutions, rule-based automatic matching with learning, e-invoice handling (ZUGFeRD/XRechnung) both directions, and replacement scanning (ersetzendes Scannen) documented so paper can be destroyed.
10 — The evidence chain is closed: every posting reaches its receipt in one click, e-invoicing inbound and outbound as standard, documented compliant archiving of the digital original, and matching accurate enough that exceptions rather than transactions are the work.
The Bookkeeper
We found no public information on bank connections, receipt capture, OCR or matching rules — nothing on how money and its evidence reach the ledger. The only automation described in any detail is session-replay recording by third-party providers, which belongs to support tooling, not bookkeeping. 1
The Tax Adviser
We found no public information on bank feeds, statement import, receipt capture, OCR or matching rules, and nothing on e-invoicing or compliant archiving. Without an evidenced link between a receipt and its posting I cannot even begin to close a year on this. 1 1
The Auditor
We found no public information on bank feeds or statement import, receipt capture or OCR, matching rules, or e-invoice handling in either direction. The captured pages name session-replay and credit-bureau partners, but nothing on how evidence and money reach the ledger. 1
The Founder
Sunday bookkeeping lives or dies on bank feeds that match themselves, and I found no public information on bank connections, receipt capture, OCR, matching rules, or e-invoice handling in the captured pages. How evidence and money reach the ledger is entirely unevidenced. 1
The Integrator
The third-party services these pages do name — YouTube, Twilio, credit bureaus, FullStory and Medallia — serve video, messaging, credit scores and session replay, and not one of them connects the books to a bank, a payment provider or payroll. We found no public information on bank feeds, statement import, receipt capture or OCR, matching rules, or ZUGFeRD/XRechnung e-invoicing in either direction. 1 1
The Skeptic
I found no public information on bank feeds, receipt capture, OCR or matching rules — the banking and receipt side of the product does not appear in what was captured at all. What the pages do discuss is biometric information and session replay, which is privacy plumbing, not a receipt chain. 1 1
Tax adviser handoff
Show reasoningHide reasoning
How this is scored
How the books reach the Steuerberater — DATEV above all — and whether the adviser can work in the system rather than around it.
0 — No adviser access and no accounting export; the year-end is a pile of PDFs.
3 — Generic CSV or Excel export described as "suitable for your tax adviser", with no named format.
5 — A documented DATEV export (postings and, ideally, receipts) plus a read-only login for the adviser.
8 — DATEV export including receipt images with correct linking, or a maintained DATEV interface; the adviser gets their own scoped access with an audit of what they changed.
10 — The adviser is a first-class user: bidirectional DATEV exchange including corrections coming back, or a certified interface; period handover with locking, and a workflow where adviser queries are resolved inside the system.
The Bookkeeper
We found no public information on a DATEV export, any other named adviser format, or an adviser login. From what was captured, a Steuerberater would receive nothing structured at year-end. 1 1
The Tax Adviser
We found no public information on a DATEV export, any other named accounting export format, or a scoped adviser login. A clean period handover to the Steuerberater is not something the captured pages evidence — as the receiving adviser I would be rebuilding the books from PDFs. 1 1
The Auditor
We found no public information on a DATEV export, any accounting export in a named format, or an adviser login of any kind. From this record the year-end handover to the Steuerberater cannot be evidenced at all. 1
The Founder
My Steuerberater asks for DATEV by name; I found no public information on a DATEV export, any other accounting export, or an adviser login in the captured pages. The year-end handoff is a blank from the buyer's side. 1
The Integrator
We found no public information on a DATEV export, any other named export format for the Steuerberater, or an adviser login of any kind. How the year-end reaches the tax office's desk is entirely undocumented in these captures. 1 1
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where the books live and who could be compelled to produce them — plus, uniquely here, whether statutory retention survives leaving the vendor. Independently sourced by the sovereignty pipeline.
0 — Non-EU vendor and contracting entity, hosting unstated or non-EU, subprocessors unnamed — with a ten-year retention obligation attached to data held abroad.
3 — EU hosting offered while the contracting entity is non-EU, or the subprocessor list is absent.
5 — EU hosting as standard and an EU contracting entity, but parts of the chain — OCR, AI categorisation, support tooling — are non-EU without an explained safeguard.
8 — EU or German hosting on named infrastructure, EU contracting entity, full subprocessor list published, and a stated export that satisfies retention if the contract ends.
10 — Sovereign and durable: German or EU hosting throughout, every subprocessor European, certification published, and a documented archive export that keeps the customer compliant for the full retention period after they leave.
The Bookkeeper
The controller is Intuit Inc. in the United States, US tax return information is processed and stored in the United States, and data may be held in any country where Intuit or its providers operate facilities; the named third parties — TransUnion, Experian, Equifax, FullStory, Medallia, YouTube, Twilio — are US services. We found no public information on EU hosting, a European subprocessor commitment, or an export that would satisfy statutory retention after leaving the vendor; cross-border transfers rest on Standard Contractual Clauses and the Data Privacy Framework. 1
The Tax Adviser
The contracting entity is Intuit Inc., a US controller; the captures state US tax return information is stored in the United States and other personal information may be kept in "any other country" where Intuit or its providers operate facilities, with no EU hosting option named. The only processors named are US services such as Twilio, TransUnion and FullStory, and cross-border transfers rest on the EU-U.S. Data Privacy Framework rather than EU hosting. German books under statutory retention held abroad by default is precisely the exposure I cannot sign off. 1
The Auditor
The contracting controller is Intuit Inc. of the United States, the captured pages name no EU hosting option while reserving storage in any other country where Intuit or its providers operate facilities, and no subprocessor list was confirmed. Certification under the EU-U.S. Data Privacy Framework presumes transfers to the United States rather than EU residency, and we found no public information on an archive export that would keep statutory retention alive after the contract ends. 1
The Founder
The contracting entity is Intuit Inc. of Mountain View and I found no public information on an EU hosting option — US tax return information is even stated to be processed and stored in the United States, while credit bureaus and session-replay providers appear in passing as US services. Transfers rest on standard contractual clauses and the Data Privacy Framework rather than EU storage, and I found no public information on an export that would keep my German retention obligation alive if I left. 1
The Integrator
Intuit Inc. and its group companies act as controller, self-certify under the EU-U.S. Data Privacy Framework, and state that United States tax-return information is "processed and stored in the United States", with international transfers papered by standard contractual clauses rather than EU hosting. No EU hosting option is named in the captures and no subprocessor list is published — only incidental names like Twilio, FullStory and Medallia — and we found no public information on an archive export that would keep statutory retention intact if the customer leaves. 1
The Skeptic
The named controller is Intuit Inc. and its group companies, a US contracting entity, with US tax return information processed and stored in the United States and personal information possibly held in "any other country" where Intuit or its providers operate facilities; no EU hosting option is named. Third parties like YouTube, Twilio, the credit bureaus, FullStory and Medallia appear scattered through the privacy statement, but that is not a published subprocessor list, and I found no public information on an export that would satisfy statutory retention after the contract ends. 1
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a business can compute the real annual invoice — including the bookings, users, bank accounts and adviser access they actually need — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A headline monthly price exists, but booking or document limits, extra users or the tier where DATEV export begins are unstated.
5 — Tier prices public with billing period stated and the main limits given, but at least one commonly needed piece (DATEV export, extra bank accounts, adviser seat) sits in an unpriced tier.
8 — Every tier and add-on priced publicly with limits, overage, minimum term and VAT treatment stated; adviser access priced or explicitly free.
10 — Complete price computability: annual invoice derivable for a given transaction volume, user count and feature set, including overage and the year-end extras.
The Bookkeeper
We found no public information on tier prices, billing period, booking or document limits, extra users, bank accounts or adviser access. A business cannot compute any part of its annual invoice from what was captured. 1 1
The Tax Adviser
We found no public prices at all in the captured pages — no tiers, no booking or document limits, no billing period, no statement of VAT treatment. A client cannot compute even a rough annual invoice from what was captured. 1 1
The Auditor
We found no public information on tier prices, billing periods, booking or document limits, charges for extra users or bank accounts, or the price of adviser access. No business can compute an annual invoice from this record. 1 1
The Founder
I notice when the headline price was not the invoice, but here I found no public price at all: no tiers, no limits, no add-ons, no billing period. From the captured pages, every figure would have to come out of a sales conversation. 1
The Integrator
The captures contain no prices of any kind — no tiers, no booking or document limits, no per-user, bank-account or adviser-access pricing, and no statement of VAT treatment. We found no public information from which a business could begin to compute its annual invoice. 1 1
European sovereignty — proven facts
1 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined ⚠ unverified | — | uncited Report an error |
| Data residency | US by default ⚠ unverified | 0/3 pts | 1 Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 11 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Ownership, Legal entity, Subprocessors. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Data residency. The excerpt names no EU hosting option and promises no region choice, but storage is not guaranteed to be the US either — "any other country" where Intuit or its providers operate facilities may also be used.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- We found no public information on pricing on the pages we read (intuit.com/privacy/statement). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 7 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (1)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Privacy policy www.intuit.com Checked 15 Sep 2026 +1 earlier capture: 11 Sep 2026 Details →