Import Koinly, Summ or a generic CSV. Classify, map, reconcile and export balanced Xero and QuickBooks journals — with every line traceable to the source file.
The method, enforced
This posting pattern applies whether it's a $12 swap or a six-figure OTC settlement. The engine doesn't choose when the rule applies — it always does.
Dr Expense fair value Dr/Cr Gain/(loss) tax-software G/L Cr Digital assets cost basis
How it runs
Koinly, Summ or a generic CSV. Exceptions, duplicates and missing cost surface before a single journal is marked ready.
Hash rules for confirmed payroll. Counterparty maps for named vendors. Unmapped stays in suspense — never a guessed expense.
G/L bridge, running balances, and platform validation. Xero and QuickBooks files that a reviewer can tie.
"Unexplained G/L is treated as a defect —
not a footnote."
Core principle, enforced in code, not just policy
What to upload
Koinly
Transactions + capital gains
Reports → Transactions CSV, then Reports → Capital gains CSV — one file per tax year. Cost basis is not on the transactions file.
Summ
Report ZIP or transactions CSV
Generate the tax report, then download the ZIP (or the transactions CSV). A separate gains file is optional when cost and gain already sit on each row.
Generic CSV
Template or any compatible sheet
Date, type, amounts, assets. Cost, proceeds and hash when the tax file has them. Do not invent numbers. Awaken stays parked until certified.
The posting rules come from real Summ-to-Xero workpapers: confirmed payroll hashes, a repayment that contradicted its own comment, and a Xero import that collapsed a hundred journals into one dated year-end. The blank-continuation CSV and the control totals are the fix. Client names stay off the product.
FAQ
Your data is stored securely in an isolated, encrypted database on our servers under your firm's private workspace. All journal construction, rule matching, and gain reconciliations are computed and verified server-side. Only authorized team members assigned to your company have access, and your workpaper automatically persists so you can review and collaborate across sessions.
Use the generic CSV template — date, type, amounts, assets, plus cost and hash when you have them. Awaken support is built but not yet certified, so it stays parked until it is.
They land in Suspense, not a guessed expense account. Coding only applies where a client comment, a confirmed hash, or a clear repeating pattern supports it — everything else waits for you.
Yes. Import a Xero or QuickBooks CoA CSV, or start from the built-in crypto template and add accounts as you go. New accounts export as their own CoA import file.
No. It produces the workpaper and exception queue a reviewer needs to sign off faster — every figure traces back to the source file, and an unexplained G/L is treated as a defect, not a footnote.
Drop in a source pack and see exactly where the books stand before anything touches Xero or QuickBooks.
