QuickBooks Online integration

Sellergoo connects a seller's marketplaces (Amazon, eBay, Shopify, Walmart, OTTO and Kaufland) and works out what every sale actually earned, after marketplace fees, refunds, cost of goods, advertising and the seller's own expenses. The QuickBooks Online integration posts that month's profit and loss to the seller's QuickBooks company as one journal entry, so the books match the marketplace numbers without anyone typing them in.

Nothing is posted automatically. An entry is created only when the seller picks a month and presses Sync to QuickBooks.

1. Connect. On the QuickBooks page in Sellergoo, the seller signs in with Intuit and chooses the company to connect. One QuickBooks Online company is connected per Sellergoo workspace.
2. Map. Each profit-and-loss category (sales, refunds, marketplace fees, cost of goods, advertising, the expense groups and VAT) is mapped to an account in the company's chart of accounts, by name. The seller also names a balancing account and, optionally, a prefix for the entry numbers.
3. Preview. For a completed month, Sellergoo shows every journal line (account, debit or credit, amount) before anything is sent, computed from the same numbers as the seller's dashboard. Categories without a mapping are listed and left out of the entry.
4. Sync. Sync to QuickBooks creates the journal entry. The export history records the month, its status, the number of lines, the net amount and the QuickBooks journal entry id.
5. Receives a notification from Intuit when a journal entry Sellergoo created is deleted in QuickBooks, so the export history says so. Every notification's signature is verified before it is read, and notifications about anything else are ignored.

• It is dated the last day of the month it covers.
• Its number is the prefix followed by the month, for example SG-2026-06.
• One line per mapped category. A negative amount, such as a refund, posts on the opposite side, so every line carries a positive amount.
• The month's net result closes the entry on the balancing account, the account the marketplace payout is reconciled against.
• A private note on the entry states the period, the currency the amounts are in and, when amounts were converted between currencies, the exchange rates used. The entry can be audited from inside QuickBooks without Sellergoo.

Sellergoo requests one scope: com.intuit.quickbooks.accounting. It requests no payments scope and no sign-in or profile scope. Within that scope it makes only these calls:

• Reads the chart of accounts (id, name, full name, type, active flag) when an export runs, to find the accounts the mappings name. It is used for that export and not stored.
• Reads the company's currency settings (home currency, and whether multicurrency is on), to check that the month's currency is the one the company keeps its books in.
• Looks up an earlier Sellergoo entry by its id or its entry number, and reads only its id and number, to stop the same month being posted twice.
• Creates one journal entry per export.

• We never edit or delete an existing transaction, including entries Sellergoo created.
• We do not read customers, vendors, invoices, bills, payments, bank transactions or payroll.
• We do not post anything the seller has not asked for; there is no automatic sync.
• We do not convert amounts inside QuickBooks or rely on its multicurrency feature; a month whose currency differs from the company's home currency is refused instead.
• We do not sell, share or aggregate company data. Nothing from one company is shown to another customer, and no third party receives it for its own purposes.

• Currency. If QuickBooks reports that the company keeps its books in a different currency from the month being exported, the export is refused with both currencies named, rather than recording one currency's amounts as another's.
• Missing exchange rates. If a month combines currencies and a rate is missing for a day, the export stops and names the currency and the dates, rather than posting a total that leaves money out.
• Accounts. If a mapped account or the balancing account does not exist or is inactive, the export is refused and the accounts are listed.
• No duplicates. A month that is already in QuickBooks is refused and the existing entry is named; to post it again, the seller deletes that entry in QuickBooks first. An export still in progress blocks a second click. If QuickBooks cannot be reached to check, nothing is sent. Each export also carries its own request id, so a network retry cannot book it twice.
• Rate limits. If QuickBooks is rate-limiting the company, the export stops and says to try again, instead of retrying blindly.

• The connection uses Intuit's OAuth 2.0 sign-in. The seller signs in with Intuit; Sellergoo never sees or stores their Intuit password.
• Access tokens are renewed automatically when needed, and the long-lived authorisation is renewed in the background before it can expire, even when no export runs for months. The connection stays until the seller disconnects it. If a renewal is ever refused, or the authorisation is within 21 days of expiring, the QuickBooks page says so.
• If access is revoked on the QuickBooks side, Sellergoo notices on its next call to QuickBooks, and the QuickBooks page then shows that the connection needs to be reconnected.
• Disconnect in Sellergoo revokes Sellergoo's access at Intuit and deletes the stored authorisation. If Intuit cannot confirm the revocation, the page says so, and the seller can also remove the app from the Apps section in QuickBooks.
• Signing out of Sellergoo does not disconnect QuickBooks Online; the connection stays until the seller disconnects it. A seller who disconnects from inside QuickBooks lands on a page that explains how to reconnect.

• The connected company's id, and the OAuth tokens with their expiry times. The tokens are encrypted at rest with AES-256-GCM; the key lives in the server environment, never in the database or the source code.
• The seller's account mappings, balancing account and entry-number prefix.
• The export history: month, status, number of lines, net amount and the QuickBooks journal entry id.

We do not store QuickBooks transactions, customers or the chart of accounts. The authorisation is deleted on disconnect. The rest is deleted with the workspace, or on request, as set out in the privacy policy.

• Stored and processed on our own server in a Hostinger data center in Frankfurt, Germany, with traffic routed through Cloudflare. No customer data is stored outside the European Union.
• Every customer has a physically separate database, so one customer's data cannot be reached from another customer's workspace.
• Details, including backups and how administrative access is controlled, are in the privacy policy and the security policy.

• QuickBooks Online. QuickBooks Desktop is not supported.
• The company's home currency must match the currency of the month being exported. A workspace's currency is set in Sellergoo under Settings › Account.
• The mapped accounts and the balancing account must exist in the chart of accounts.
• The QuickBooks Online integration is included in every Sellergoo plan, each with a 14-day free trial (pricing).

Support and integration questions: [email protected] · support page. See also the privacy policy, terms of service and Impressum (the operator's full legal identity under German law).

Intuit and QuickBooks are registered trademarks of Intuit Inc. Used with permission. Sellergoo is an independent product and is not made or endorsed by Intuit.