Reviewed guide | 2026-09-27
Building a Simple Spot Trade Recordkeeping System for Ukrainian Users
A practical method for Ukrainian crypto users to log spot trades across Binance, OKX, Bybit and Bitget in one consistent file, with clear rules on what to record, when to update, and which official pages to check for fee and export details.
Multiple exchanges | Ukraine | UAH | fees, access and account safety
Trading spot markets on more than one exchange usually creates a recordkeeping problem long before it creates a trading problem. You buy on one platform, sell on another, move coins between them, and after a few weeks the only complete history lives inside four separate account pages that you rarely open. The result is a pile of numbers you cannot reconcile and a vague sense of what you actually did. This guide describes a small, boring system that fixes that: one master file, one fixed set of columns, one weekly session, and a habit of pulling the official export from each exchange before you start editing anything. The goal is not accounting perfection and it is not tax advice. The goal is that any trade you made in the last year can be found, explained and matched to a source record in a couple of minutes. You will still need to check the help centre of each platform for the current export options, the fee page for how fees are displayed, and your account settings for what data is stored where, because those details change and only the official pages are authoritative.
Decide the shape of your record before you touch a spreadsheet
Start with one file and one sheet per year, not one sheet per exchange. The most common failure is building a separate tab for Binance, another for OKX, another for Bybit and another for Bitget, then discovering that transfers between them appear in two places and nowhere at the same time. A single chronological sheet forces you to describe each event once, in one row, with a column that says which platform it happened on.
Agree on the columns now and then never add a column mid-year. A workable minimum is: date and time in your own timezone, exchange name, event type, pair or asset, amount bought or sold, amount received, fee paid and in which asset, the identifier of the source record, and a short free-text note. The event type column should be a closed list you control, for example buy, sell, transfer in, transfer out, fee, and adjustment. Closed lists stop you from inventing new wording every week.
Write down the rule for timezones and stick to it. Exchanges display timestamps in different formats and sometimes in different timezones, so a trade late in the evening can land on a different calendar date depending on where you read it. Pick your local time, convert once when you enter the row, and note the conversion rule in a cell at the top of the sheet so a future you does not have to guess.
Pull the official records first, edit second
Before typing anything, open the transaction or order history section of each account and export or download the period you are about to record. The exact path and the available formats differ per platform and change over time, so treat the help centre of Binance, OKX, Bybit or Bitget as the place to confirm how export works today rather than relying on memory. Save the raw file untouched in a folder named by exchange and month. That raw file is your evidence; the spreadsheet is your interpretation.
When you read those records, note carefully how each platform presents fees. Some show the fee as a separate line, some subtract it from the received amount, and some display a fee percentage that depends on your tier or on whether you used a platform token discount. The fee page of the exchange is the correct place to understand the structure, and your own account history is the correct place to see what was actually charged to you. Record the actual charged amount, not the headline rate.
Keep the source identifier column honest. It should point to something you can reopen later, such as the order number shown in the history, or the file name plus row of the raw export. If you cannot point to a source for a row, mark the row as unverified rather than inventing a number. Unverified rows are useful because they tell you exactly where to look next week.
Run a short weekly session instead of a monthly panic
Set one recurring slot of about twenty minutes per week. In that slot, export the last seven days from each platform you actually used, append the new rows to the master sheet, and reconcile the totals against the account balances shown on each platform. Reconciling means: does the sum of my recorded buys minus sells minus transfers match what the account page says I hold. If it does not, you have found the missing row while you still remember the trade.
Handle transfers immediately, because they are the rows people forget. A transfer out of one exchange and into another should appear as two rows that reference each other, one outgoing and one incoming, with the network fee recorded on the outgoing side. If the incoming row never arrives, the transfer is either still pending or was sent to an address you have not recorded, and both cases deserve a note rather than silence.
Close the session by writing a one-line status note at the top of the sheet: the date, the period covered, and any row still open. That single line is what makes the file usable after a two-month break, because it tells you where the work stopped. Do not leave the session without either resolving an open row or explicitly labelling it as open.
Keep the system small enough to survive a busy month
Resist the urge to build dashboards, pivot tables and automatic price feeds in the first version. A system that requires maintenance during a volatile week will be abandoned during exactly the week you most need records. Plain columns, one sheet per year, and a consistent event list will survive; a fragile formula chain will not. Add complexity only after three consecutive months of clean weekly sessions.
Decide in advance what you will do when a record is genuinely unavailable, for example an old trade from before you started logging. Create a clearly labelled opening-balance row dated at the point where your reliable records begin, and note in the source column that earlier activity is not covered. That is more useful than a year of guessed rows, and it makes the boundary of your data explicit.
Finally, back the file up somewhere you can reach without the exchange. A local copy plus one encrypted cloud copy is enough. The point of the whole exercise is to hold your own history independently of any platform interface, so a file that only exists inside one account page defeats the purpose.
Risk boundary: Ukraine Crypto Guide
Digital assets are volatile and derivatives can amplify losses. This website has no login, wallet connection, deposit form or customer-support chat. A referral link only records attribution; it does not guarantee access, pricing, rewards, approval or investment results. Availability can differ by residence, legal entity and product, so no regional access is assumed from language or branding alone.
Scenario checkpoint
- Create one master file with a single sheet per year and a fixed column set agreed before the first entry.
- Record the timezone rule and the event-type list at the top of the sheet so entries stay consistent.
- Export the raw order and transaction history from each exchange before editing, and store the untouched files by platform and month.
- Check the official fee page of each platform to understand how fees are structured, then record the amount actually charged to your account.
- Reconcile recorded totals against account balances every week and label any unresolved row as open rather than guessing.
- Back up the file locally and in one encrypted cloud location so your history does not depend on any single platform.
Digital assets are volatile and derivatives can amplify losses. This website has no login, wallet connection, deposit form or customer-support chat.