The situation
It's the first week of the month. Your bookkeeper asks: "What did you convert last month, at what amounts, with what fees, and when did the money hit the bank?" If you've been converting by hand, the answer sits in your exchange history, a spreadsheet you half-maintained, and your memory.
Automating the cash-out doesn't remove the need for records. But it can make them more consistent, as long as you know where to look and what each page means.
The problem and the decisions
Coinomatic shows two kinds of history, and they serve different purposes:
- Transactions: "Conversion and withdrawal history." According to the app, "COMPLETED rows reflect finalized accounting-relevant executed financial actions," while "PENDING and FAILED rows reflect exchange-action attempts and are not completed accounting records."
- Logs: "System activity and event history." The page states clearly: "Operational explanations only; not accounting records."
So the first decision is simple: for the books, start from Transactions (COMPLETED rows). Use Logs to explain why something did or didn't happen.
Other decisions:
- How do you structure automations? One automation per purpose (e.g., "Client income – weekly," "Operating cash – 50% weekly") makes every Transactions row easier to categorize, because each row references the automation that triggered it.
- When do you export? Pick a fixed day each month.
- What's the source of truth for the bank side? Your bank statement. A withdrawal request on the exchange is not the same as money received.
Illustrative example
Illustrative example – made-up business, not a real customer.
A two-person design studio uses two automations:
- "Client income – weekly fixed": a fixed amount in BTC every Monday, USD withdrawn immediately (strategy: fixed amount on a schedule).
- "Operating cash – 50% weekly": 50% of the available BTC balance on Thursdays, with a minimum balance to keep (strategy: percent of balance).
On the 2nd of each month, one partner opens Transactions, filters to last month, exports the list, and sends it to the bookkeeper together with the bank statement. If a row is missing or a week looks odd, they open Logs to see whether a run was skipped (for example, insufficient balance or an amount below the exchange minimum).
How Coinomatic helps
- Transactions: each row shows from/to amounts (e.g., BTC → USD), the fee, the automation reference, a status (COMPLETED / PENDING / FAILED), and a timestamp. Filters are available for type, status, and more.
- Export: according to the Knowledge Base guide Review transactions, the list can be exported as CSV or XLSX. The Export button is visible in the app. We haven't tested an export ourselves yet. Timestamps in the export follow the time zone chosen in the app settings.
- Logs: entries such as "Rule evaluation," "Conversion completed," and "Skipped execution," each with a short reason, plus filters by Automation ID, Execution ID, Correlation ID and date range.
- The Transactions page also states: "Coinomatic executes user pre-defined instructions using the connected exchange account. Financial transactions are executed by the exchange." Your exchange account remains the underlying record.
What it looks like
[IMAGE TO ADD: L10_transactions.png - Live test screenshot, Oct 10, 2026, anonymized. Transactions show status, amounts, fee and automation reference.]
Live test, Oct 10, 2026, anonymized. Test amounts only.
[IMAGE TO ADD: L11_logs.png - Live test screenshot, Oct 10, 2026, anonymized. Logs carry the note "Operational explanations only; not accounting records."]
Live test, Oct 10, 2026, anonymized.
[IMAGE TO ADD: D02_transactions-demo.png - Demo data – illustrative. Transactions with conversion and withdrawal rows in different statuses.]
Demo data – illustrative. Amounts, dates and the withdrawal rows are made up. Our live test showed conversion rows only.
Time check: the monthly review is part of the cost
Model example, your numbers will differ.
In our model, a manual cash-out includes ≈4 minutes of record-keeping per run (part of ≈17 minutes total). With automation, we still budget ≈10 minutes a month for review and export, plus ≈2 minutes per run to glance at Logs/Transactions, and 20 minutes of setup spread over 12 months.
For the studio above (2 weekly automations ≈ 8.6 runs/month):
8.6 × (17 − 2) − 10 − 1.7 ≈ 117 minutes a month, modeled.
The record-keeping minutes don't disappear. They shrink into one predictable monthly session instead of a little bit of work after every sale.
Limits and how to check the result
- Logs are not accounting records. The app says so explicitly.
- PENDING and FAILED rows are not completed records. Only COMPLETED rows count as finalized.
- Tax export: the export in Transactions includes all your conversions, which gives your accountant the data. Coinomatic doesn't give tax advice, and your accountant or tax professional decides how conversions are treated.
- Timestamps: times follow the time zone chosen in the app settings, including in exports. Tell your bookkeeper which zone you're using.
- Date formats varied between screens in our test (e.g., "Oct 10, 12:48" vs. "Oct 10, 2026 12:48").
- Check against the source: compare a sample of rows with your Kraken history and your bank statement.
Next step
Read the Knowledge Base guide Review transactions. Then name your automations by purpose and put a monthly export reminder in your calendar.
Coinomatic is software that triggers actions on your connected exchange account (today: Kraken) based on rules you set. It is not a financial advisor, broker, or money transmitter, and it does not take custody of your funds. Nothing in this article is financial, tax, or legal advice.