Building a Tax-Loss Harvesting Log from Your Wallet Export

Crypto investors across Sydney, Melbourne, and Brisbane have learned that the run-up to 30 June is rarely a quiet stretch. Every arvo spent watching the market turns into a scramble once July arrives and the ATO's tax time countdown begins. For anyone holding digital assets, the question of which positions to crystallise before the end of the financial year has become part of the routine. A neat tax-loss harvesting log is one of the cleanest ways to keep the ATO happy, and the browser-based SAWANVEGAS Wallet includes an export function that gives you most of what you need without leaving the tab you already have open.

What follows is a practical walk-through of how to take a raw export from SAWANVEGAS, shape it into a harvestable record, and align each line with the way the Australian Taxation Office expects capital gains to be reported. The process is not glamorous, but the difference between a quick lodgement and an awkward audit follow-up usually comes down to how disciplined your log is on the night you actually build it.

Understanding Tax-Loss Harvesting Under Australian Rules

Tax-loss harvesting in Australia is the deliberate sale of a digital asset at a loss in order to offset a capital gain elsewhere in your portfolio. Once realised, that loss reduces your net capital gain for the income year, which in Australia runs from 1 July to 30 June. If your realised losses exceed your realised gains, the net capital loss can be carried forward indefinitely and applied against future gains, which makes the discipline worth maintaining year after year.

The ATO treats crypto assets as property, meaning each disposal is a CGT event. Holding an asset for more than twelve months unlocks the 50 per cent CGT discount on any resulting gain, but losses do not receive the same treatment. A loss is recorded at full value, and only the gain side is halved. That asymmetry is precisely why end-of-year planning matters; the discount does not save you on the loss, but a well-timed harvest can still drag your taxable position down considerably.

A small but important detail is that the ATO expects the cost base to include brokerage, gas fees, and the fair market value of any tokens paid as transaction costs. Skipping those numbers is a common reason a neatly built log later proves too optimistic once a tax agent reviews the working papers. ASIC has repeatedly warned that data matching programs now scrutinise exchange records against what taxpayers declare, so a log that reflects on-chain reality tends to age well.

Preparing Your SAWANVEGAS Wallet Data

Before touching the export button, it pays to tidy up the wallet itself. The SAWANVEGAS interface keeps transactions in chronological order inside a single browser session, so any in-flight swaps or pending transfers should either be settled or noted for later. A pending swap is, for tax purposes, unsettled business. Recording it would lock in a price that may not be the one that ultimately settles, which complicates the log.

The wallet's black, gold, and white layout is designed to keep the eye on the running total, but the numbers that matter for harvesting live in the detailed transaction view. Open each significant trade and confirm the date, the quantity, the unit price, and any fee component. If the wallet is connected to a network where the fee was paid in a separate token, make a note of the spot value at the time. These line items become the raw material for the cost base calculation once the export is downloaded.

Tagging transactions while you are still inside the wallet saves a great deal of cleaning later. Many Australian investors using the platform find it useful to mark entries as "long-term", "short-term", "transfer between own wallets", or "fee only" before exporting. That habit turns a flat ledger into something closer to a working paper, and it makes the harvest easier to defend if the ATO ever asks how a particular loss was calculated.

Generating the Export File

The export function is reached through the wallet's settings panel, which is rendered in the same high-contrast palette as the rest of the application. The button is small and sits below the balance display, so first-time users sometimes miss it. Once selected, you are offered a CSV or JSON file, and for the purpose of building a harvest log, CSV is usually the friendlier format. The file downloads straight to your default browser folder without the need for any separate software installation.

After the file lands on your machine, open it in a spreadsheet program rather than a text editor. Spreadsheets allow you to sort by date, filter by asset, and apply formulas to totals, all of which will be needed in the next stage. Resist the urge to edit the raw file in place; keep an untouched copy as a record of what the wallet produced on that day. Australian tax agents often ask for a snapshot of the source data, and a clean original makes that conversation shorter.

The wallet's export includes a timestamp field, a transaction hash field, and a fee field. Confirm that none of these are truncated by the spreadsheet's default formatting. A transaction hash can look like a number to a careless spreadsheet, which then rounds it to a meaningless string. Forcing the column to plain text before doing anything else prevents that quiet corruption.

Organising Transactions for the ATO

With the export safely copied, the next move is to group transactions by asset. A loss only makes sense within a single CGT event stream, so mixing Ethereum trades with stablecoin transfers in a single column is a fast way to confuse yourself. Build a separate sheet per asset, or at the very least, a separate coloured band, so each line can be read in isolation.

Sort the entries by disposal date, then by acquisition date, and apply the ATO's standard method for matching. Most retail investors use the "same-day" rule first, then the "30-day buy-back" rule, before falling back on the diminishing balance method for everything else. The same-day rule matches a sale with any purchase of the same asset on the same day. The 30-day rule is the section that makes tax-loss harvesting interesting in the first place, because it prevents you from repurchasing the same asset within thirty days and still claiming the loss.

For Australians running multiple wallets, the ATO's "change of ownership" rules can interfere if a transfer between your own wallets is recorded as a disposal. Most practitioners treat a transfer between wallets you control as a non-taxable event, provided the cost base and acquisition date are carried across. The export from SAWANVEGAS will show the transfer; the log simply needs to flag it so the spreadsheet does not interpret it as a sale.

Calculating Realised Losses

Realised losses are the difference between the cost base and the proceeds of a sale that has actually settled. Within the spreadsheet, create a column for proceeds, a column for cost base, and a column for the difference. The harvest log is essentially a running total of that difference across the financial year, separated into short-term and long-term rows so the 50 per cent CGT discount can be applied correctly to the long-term side.

Pay attention to the fee columns on both ends of the trade. A swap that returns slightly less than the quoted amount because of network costs still counts as a disposal at the actual received amount, and the fee paid in a separate token is part of the cost base of whatever was received. These small numbers are easy to miss on a tired evening, but they are also the first place an ATO review tends to look when checking whether a loss is fully documented.

A useful audit trail is to add a column that records where each cost base figure came from. A simple code such as "EX" for exchange-derived, "WC" for wallet-confirmed, or "ES" for estimated is enough. Australian investors who go through a registered tax agent will often be asked to defend a handful of entries, and that one-character code turns a long explanation into a quick reference.

Carrying the Log Through to Financial Year Reporting

Once 30 June passes, the log freezes for the year. Save a dated copy, lock the spreadsheet, and begin the next year's file from a clean sheet. Carrying a rolling workbook across years is tempting, but a single edit in retrospect can undermine the whole document. The ATO does not require continuous records, but a tidy year-end snapshot makes the myTax or agent-prepared return far less stressful during the July to October lodgement window.

When the time comes to lodge, the harvest log feeds directly into the CGT worksheet within myTax or the equivalent schedule in commercial tax software. The realised losses are entered as net capital losses for the year, and any excess is shown as a carry-forward figure. Most Australian investors who take harvesting seriously will show a loss in one year and a smaller gain in the next, which is exactly the pattern the ATO expects to see when the strategy has been applied consistently.

Common Pitfalls and How to Dodge Them

The following items tend to derail an otherwise solid log once the lodgement window opens:

• Recording a transfer between your own wallets as a disposal and a fresh acquisition, which can artificially inflate both losses and gains.
• Forgetting to include gas and network fees paid in a token rather than in the unit being sold.
• Buying back the same asset within thirty days of a loss-realising sale and then trying to claim the harvest.
• Treating the wallet export as the only source of truth when some early trades were completed on an external venue.
• Quoting values in a foreign currency without converting to AUD at the ATO's published exchange rate for the transaction date.
• Leaving the spreadsheet in a shared folder without a dated version, which makes year-end reconciliation harder than it needs to be.

Keeping a short companion file alongside the harvest log usually helps in the long run. The following records are worth holding for at least five years after lodgement, which matches the ATO's standard record-keeping window:

• The original unmodified export from SAWANVEGAS on the day it was generated.
• Screenshots of the wallet balance on 30 June for each asset held.
• A copy of the acquisition record for every long-term position.
• A list of any tokens received through airdrops, forks, or staking rewards, with the value at receipt.
• Notes explaining any unusual entries, including transfers, gifts, or lost keys.
• The tax agent's engagement letter or confirmation that the figures were reviewed before submission.

The discipline of building the log once a year, rather than reconstructing it from memory in October, is what separates a calm tax time from a frantic one. A clean export from the wallet, a tidy spreadsheet, and a habit of marking transactions while the detail is still on screen are usually enough to keep the ATO satisfied and the harvest strategy working year after year.