Koinly's Xero Integration vs a Reviewer Workpaper: When to Use Which
TL;DR
Use Koinly's native Xero / QuickBooks sync when crypto fits 7 fixed accounts. Use Ledger Bridge — a crypto subledger tool that turns Koinly, Summ or CSV exports into balanced Xero and QuickBooks journals — when you need your full chart of accounts, per-token ledgers, or a signed year-end workpaper with control totals.
How do I sync crypto transactions into Xero?
Direct answer
You have two paths. (1) Koinly's native Xero sync — OAuth, category mapping, journal drafts under 7 fixed accounts. (2) A reviewer workpaper — reviewed CSVs mapped to your custom chart of accounts, then export. Ledger Bridge is that workpaper path: import Koinly, Summ or CSV, sync the chart from Xero, and export balanced, traceable journals by CSV or API.
The deciding question is rarely "do we like Koinly?" — it is "will the journals land on the accounts we actually use?"
How do I sync crypto transactions into QuickBooks?
Direct answer
Same two paths. Koinly's native QuickBooks sync posts to the same 7 fixed, pre-mapped accounts. Ledger Bridge syncs the client's custom chart from QuickBooks, assigns any transaction to any account, can create accounts that sync back, and exports balanced QuickBooks journals by CSV or API — with optional per-token ledgers.
Many practices use both: selective native sync during the year, then a workpaper true-up at close that posts to the real chart.
Why does Koinly's Xero sync only use 7 accounts?
Direct answer
Koinly's native integration to Xero and QuickBooks posts journals into 7 fixed, pre-mapped accounts. That works when the engagement lives in a handful of buckets. It breaks down when the firm already runs a chart of 50–80 accounts or more, or when crypto alone needs more than about ten accounts.
Journals then arrive under the fixed mapping and someone edits them one by one inside Xero or QuickBooks to reclass them. That reclassing pass is the subledger gap between a tax tool like Koinly and the accounting software. A reviewer workpaper that syncs the custom chart of accounts closes that gap before posting, instead of after.
If seven accounts is fine, keep reading the native path with an open mind. If you will reclass half the pack, start with the workpaper path.
Can I sync Koinly to QuickBooks with my own chart of accounts?
Direct answer
Not with the native sync alone — that path is limited to 7 fixed accounts. Yes with Ledger Bridge: sync the custom chart from QuickBooks (or Xero), assign any account, and create new accounts inside Ledger Bridge that sync back.
Setup facts for the native path come from Koinly's help centre ( How to use Xero with Koinly, updated 19 June 2026). Re-check that article before you rely on a sync limit; the 7 fixed accounts posting model is confirmed separately and stated plainly here.
You need a paid plan, a business Koinly account, and matching base currency. Connect via OAuth, create the accounts Koinly should post to within the native model, map every Koinly category, then sync all (Koinly states a maximum of 1,000 per sync in that help article) or send selected transactions. Entries land under Journal Drafts — under the 7 fixed, pre-mapped accounts — until posted. Values under 0.01 of base currency and untagged fiat deposits/withdrawals are not sent. Futures and perpetuals P&L follow Koinly's other gains guidance.
This article does not claim partnership with Koinly or invent native-sync capacity beyond those 7 accounts.
How do I create a ledger per token in Xero or QuickBooks?
Direct answer
With Ledger Bridge, one toggle auto-creates an account per token (USDC, ETH, BTC, …) and syncs them to Xero or QuickBooks. Native sync usually stays pooled unless you build each token mapping yourself.
Choose pooled or per-token before the first year is posted; switching later is a restatement. The tax report still drives cost and gain; the books still carry the client's real chart.
What is a reviewer workpaper for crypto accounting?
Direct answer
A workpaper starts from the reviewed tax-year exports (for Koinly: Transactions CSV plus Capital gains CSV). You attach lots to disposals (hash / ID first); decide exclusions; map accounts against the client's real chart with hash rules and counterparty maps; post multi-trade and liquidity legs as one conversion where that is the economic event; tie control totals (debits = credits; source gain = booked gain + income legs + excluded G/L); then import via Xero's classic manual-journal importer, or export by CSV/API into Xero or QuickBooks.
The goal is a file a second reviewer can tick back to source, and journals that already sit on the accounts the firm uses.
Journals step-by-step: How to turn a Koinly capital gains report into Xero journals. Method: ledgerbridge.si/method.
How do I choose: native sync or Ledger Bridge? (step by step)
Direct answer
Ask six questions. Short chart, drafts, OAuth, live ops → native sync. Real chart, no reclassing, per-token ledgers, firm sign-off, closed year → Ledger Bridge workpaper path.
Count the accounts crypto needs
Ask: roughly seven buckets, or more than about ten on a chart of 50–80+?
Check whether someone will reclass
Will native-sync journals be edited one by one in Xero or QuickBooks after they land?
Decide on per-token ledgers
Do you need USDC, ETH, BTC on separate balance-sheet accounts without building each mapping by hand?
Decide who signs off before journals go live
Draft review in the GL, or a firm reviewer on a workpaper with control totals?
Decide live feed vs closed year
Do you have OAuth and want a live feed, or a closed-year file handoff?
Pick the path (or use both)
Short chart + drafts + OAuth + live ops → native sync. Real chart + no reclassing + per-token + firm sign-off + closed year → workpaper / Ledger Bridge. Many firms run selective native sync in-year, then a year-end workpaper true-up — avoiding double-posting and documenting which months each path covers.
Native sync vs Ledger Bridge
| Native Koinly → Xero / QuickBooks sync | Reviewer workpaper (Ledger Bridge path) | |
|---|---|---|
| Starting point | Live Koinly business account | Reviewed year-end / catch-up CSV (Koinly, Summ, or generic) |
| Account mapping | 7 fixed, pre-mapped accounts | Sync client's full custom chart; assign any transaction to any account |
| Chart size fit | Short chart; handful of buckets | Charts of 50–80+ accounts; crypto needing more than about ten accounts |
| After posting | Firms that need more accounts often reclass journals one by one in Xero / QuickBooks | Journals land on mapped accounts; no chart-fit reclass pass |
| Creating accounts | In Xero / QuickBooks, then remap in Koinly | Create in Ledger Bridge; sync back to Xero / QuickBooks |
| Per-token ledgers | Usually pooled unless you build each token yourself | One toggle auto-creates and syncs a ledger per token (USDC, ETH, BTC, …) |
| Review / audit trail | Journal drafts in the GL; you check after they land | Exception / suspense queue before export; control totals and source trace required |
| Connection | OAuth | CSV or API export |
| Best fit | Short chart, ongoing ops, draft review | Real client charts, per-token ledgers, signed year-end, no reclass after posting |
When is Koinly's native sync enough?
Direct answer
Prefer the native sync when crypto fits a short chart and you are genuinely happy with 7 fixed accounts; you do not need more than about ten accounts across crypto for this client; you will maintain any extra remappings yourself or reclass a small number of drafts; you do not need per-token ledgers (or will build each by hand); you already run a business Koinly account with OAuth; volumes fit the published sync limit; and you do not need a separate year-end workpaper for an external reviewer.
If that is the engagement, use the native path. Do not buy a workpaper tool for a problem you do not have.
When is Ledger Bridge the better fit?
Direct answer
Choose Ledger Bridge when the chart has 50–80 accounts or more, or crypto needs more than about ten accounts; you refuse to reclass journals one by one after they post under a fixed mapping; you want to sync the client's custom chart from Xero or QuickBooks, assign any transaction to any account, and create new accounts that sync back; you want per-token ledgers created with a toggle; year-end or catch-up files must be signed before posting with control totals; or the firm does not hold OAuth and handoff is a file.
Ledger Bridge is a crypto subledger tool that turns Koinly, Summ or CSV exports into balanced, traceable Xero and QuickBooks journals. It imports the file; syncs the custom chart; maps with hash rules and counterparty maps; creates accounts that sync back; turns on the per-token ledger toggle when you want USDC, ETH, BTC and the rest on their own accounts; reconciles so nothing posts to suspense silently and cost or gains are never invented; and exports by CSV or API.
Data is stored on EU servers. Pricing: $490 per company per tax year; packs of 3 at $390 per file; packs of 10 at $290 per file. Review free; export paid.
Not a replacement for every use of Koinly's sync, and not a claim of partnership with Koinly, Xero, or QuickBooks — the path when the native 7-account model would force a reclass pass you do not want.
Worked mini example (illustrative)
Illustrative only — not a client file.
Short chart: 1 ETH cost 1,800, sold for 2,500 USDC. Native sync can be enough if the asset and gain land among the 7 fixed accounts you actually use.
Real chart / per-token: the firm wants ETH, USDC and realised gain on specific codes — not one Digital Assets bucket. A workpaper that synced the custom chart and turned on per-token ledgers posts there once. The native path posts under the fixed mapping; someone then edits the draft in Xero or QuickBooks.
Multi-trade swap: workpaper posts one conversion journal on mapped accounts. Native mapping may send each category line into drafts under the 7 accounts — review as a set, then reclass if needed.
Key takeaways
- Ask the chart-of-accounts question first: will journals land on the accounts you actually use?
- Koinly's native Xero / QuickBooks sync posts to 7 fixed accounts.
- Charts of 50–80+ accounts usually force a reclass pass after native sync.
- Ledger Bridge syncs the custom chart, assigns any account, creates accounts that sync back, and offers a per-token toggle.
- You can use both: selective native sync in-year, workpaper true-up at close — avoid double-posting.
- Review is free at ledgerbridge.si; export is paid.
FAQ
Use Koinly's native Xero sync for short charts under 7 fixed accounts, or use Ledger Bridge to sync your custom chart of accounts from Xero and export balanced, traceable journals by CSV or API from a reviewed Koinly, Summ or CSV file.
Same choice: Koinly's native QuickBooks sync (7 fixed accounts) for short charts, or Ledger Bridge to sync your QuickBooks chart, map any account, optionally create per-token ledgers, and export balanced journals.
After you connect and map, you sync all (within Koinly's published limit) or selected transactions. Entries land as drafts under the 7 fixed, pre-mapped accounts until posted. See Koinly's Xero help article.
The native path posts into just 7 fixed accounts. If the real chart has dozens of accounts — or crypto needs more than about ten — journals arrive under the fixed mapping and get edited one by one. A workpaper that syncs the custom chart maps once and posts correctly.
Yes, on the Ledger Bridge path: sync the custom chart, assign any account, and create new accounts inside Ledger Bridge that sync back.
Yes. One Ledger Bridge toggle auto-creates an account per token (USDC, ETH, BTC, …) and syncs them. Choose pooled or per-token before the first year is posted; switching later is a restatement. Native sync usually stays pooled unless you build each token mapping yourself.
The ledger gain should equal the tax-report gain for the same scope. On a workpaper path, control totals gate export.
For the native Xero / QuickBooks integration, yes — Koinly requires a business account and a paid plan. A CSV workpaper path through Ledger Bridge starts from exports and does not require OAuth.