<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Reconciliation Archives - LadyChain</title>
	<atom:link href="https://www.ladyww.net/tag/reconciliation/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.ladyww.net/tag/reconciliation/</link>
	<description>Crypto fees, wallets and offers — checked against the terms page</description>
	<lastBuildDate>Tue, 27 Oct 2026 12:02:14 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1</generator>

<image>
	<url>https://www.ladyww.net/wp-content/uploads/2026/10/mark-512-150x150.png</url>
	<title>Reconciliation Archives - LadyChain</title>
	<link>https://www.ladyww.net/tag/reconciliation/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Reading Your Exchange Statement</title>
		<link>https://www.ladyww.net/exchange-statement/</link>
					<comments>https://www.ladyww.net/exchange-statement/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Tue, 27 Oct 2026 12:02:14 +0000</pubDate>
				<category><![CDATA[Exchanges]]></category>
		<category><![CDATA[Cost Basis]]></category>
		<category><![CDATA[Data Export]]></category>
		<category><![CDATA[Exchange Statement]]></category>
		<category><![CDATA[Fee Reporting]]></category>
		<category><![CDATA[Portfolio Accounting]]></category>
		<category><![CDATA[Reconciliation]]></category>
		<category><![CDATA[Record Keeping]]></category>
		<category><![CDATA[Tax Records]]></category>
		<category><![CDATA[Transaction History]]></category>
		<category><![CDATA[Withdrawal Log]]></category>
		<guid isPermaLink="false">https://www.ladyww.net/exchange-statement/</guid>

					<description><![CDATA[<p>An exchange statement is a record of what the venue did with your money, not a record of what your money is worth. Those two things diverge constantly, and most [&#8230;]</p>
<p>The post <a href="https://www.ladyww.net/exchange-statement/">Reading Your Exchange Statement</a> appeared first on <a href="https://www.ladyww.net">LadyChain</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>An exchange statement is a record of what the venue did with your money, not a record of what your money is worth. Those two things diverge constantly, and most of the confusion around statements comes from reading the second meaning into the first.</p>
<p>A good exchange statement answers three questions: what moved, when it moved, and what was charged for moving it. It does not answer whether you made money, because it does not know your cost basis on assets you transferred in, and it does not know what you did elsewhere. Read it as a record of events, and it becomes useful.</p>
<ul>
<li><strong>Statements describe flows, not performance.</strong> Deposits, withdrawals, trades and fees are events. Profit and loss is a derived figure that depends on assumptions the statement does not contain.</li>
<li><strong>Timestamps are usually in one timezone.</strong> Most venues record in UTC. A trade at 23:40 UTC lands on a different calendar day in many local timezones, which matters at period boundaries.</li>
<li><strong>Fees appear in two currencies.</strong> Some are charged in the asset bought, some in the quote currency. Summing a column without checking the unit produces nonsense.</li>
<li><strong>Reconciliation is the test.</strong> Opening balance plus inflows minus outflows should equal closing balance. If it does not, something in the statement is missing or misread.</li>
</ul>
<h2>What an exchange statement is built from</h2>
<p>A statement is a rendering of the venue&#8217;s internal records over a period. Each line corresponds to a booked event, and the same event can appear more than once in different sections — once as a trade, once as a fee, once as a balance change.</p>
<p>Double counting is therefore easy. Knowing which section is authoritative for which question is most of the skill.</p>
<h3>The four sections you will find</h3>
<p>Most exports contain a transaction history, a fee summary, a deposit and withdrawal log, and an opening and closing balance. The first is the detail, the second is a subtotal of the first, and the third records movements that never touched the order book.</p>
<p>For activity, use the transaction history. For charges, check the fee summary against the detail. For anything leaving without your knowledge, use the withdrawal log — the shortest and most important section.</p>
<h3>Why the statement will not match your screen</h3>
<p>Your portfolio view marks holdings to current prices. The statement records historical events at their historical prices. Between the two sits every price change since the event, which the statement has no reason to know about.</p>
<p>Recent activity commonly lags by a day or more, and pending withdrawals can appear in one section before another. Neither is an error; both make same-day comparison misleading.</p>
<h2>The numbers people misread on an exchange statement</h2>
<p>Three line items cause most of the arguments, and each has a specific reading error behind it.</p>
<h3>Realised versus unrealised</h3>
<p>Realised amounts come from closed positions and are fixed at the moment of the closing trade. Unrealised amounts move with price and are an estimate at the timestamp on the report. A statement that shows a large unrealised figure is describing a moment, not a result.</p>
<p>A statement run at a different hour of the same day can show a materially different total with no trade in between. Note the generation time when comparing periods.</p>
<h3>Fees quoted in the asset, not the currency</h3>
<p>Many venues charge a fee in the asset you receive. Buy a small amount of a token and the fee arrives as a slightly smaller amount of that token, not as a separate currency charge. On the statement it may appear as a reduced quantity rather than an explicit cost.</p>
<p>This is the most common source of &#8220;where did my fee go&#8221; questions. The cost is real, just denominated in what you bought; its currency value at the time of the trade is the figure you need.</p>
<h3>Transfers in versus trades</h3>
<p>An asset arriving from an external wallet is not a purchase. It has no price on the statement, because the venue never saw the price you paid. Treating an inbound transfer as a buy at the day&#8217;s market price will overstate or understate your position by however far your original entry price sits from today.</p>
<h2>Reconciling an exchange statement</h2>
<p>Reconciliation means proving the closing balance from the opening balance and the events in between. Worked through on a small illustrative account, the method is straightforward.</p>
<p>Start with 10,000 USDC and no other holdings. During the period you buy 2 units at 2,500 each with a 5 USDC fee, sell 1 unit at 3,000 with a 3 USDC fee, and withdraw 500 USDC. Every figure is illustrative.</p>
<ol>
<li>Opening balance: 10,000.00 USDC, 0 units.</li>
<li>Buy: −5,000.00 for the two units, −5.00 fee. Cash is now 4,995.00, holdings are 2 units.</li>
<li>Sell: +3,000.00 for one unit, −3.00 fee. Cash is now 7,992.00, holdings are 1 unit.</li>
<li>Withdraw: −500.00. Cash closes at 7,492.00.</li>
<li>Closing balance should be 1 unit and 7,492.00 USDC. If the statement says otherwise, find the discrepancy before drawing any conclusion from the period.</li>
<li>Total fees for the period are 5.00 + 3.00 = 8.00, or about 16 basis points on the 5,000.00 of buying and 3,000.00 of selling combined.</li>
<li>Repeat the check against the venue&#8217;s own closing balance field; a mismatch there usually means a pending item or a timezone boundary, not a missing trade.</li>
</ol>
<blockquote><p>A statement you cannot reconcile is not evidence of a problem, but it is a reason to stop reading the summary and start reading the detail.</p></blockquote>
<div class="slv-table not-prose my-6 overflow-x-auto rounded-2xl border border-ink-800/70 bg-ink-900" data-slv-table><table>
<thead>
<tr>
<th>Line item</th>
<th>What it records</th>
<th>What people assume it records</th>
</tr>
</thead>
<tbody>
<tr>
<td>Trade history</td>
<td>Fills with price, size and time</td>
<td>Their profit on the position</td>
</tr>
<tr>
<td>Fee summary</td>
<td>Charges, sometimes in mixed units</td>
<td>A single currency total</td>
</tr>
<tr>
<td>Deposit log</td>
<td>Assets arriving from outside</td>
<td>A purchase at market price</td>
</tr>
<tr>
<td>Withdrawal log</td>
<td>Assets leaving, with destination</td>
<td>Only the amounts they remember sending</td>
</tr>
<tr>
<td>Closing balance</td>
<td>Holdings at the cut-off timestamp</td>
<td>Value at today&#8217;s prices</td>
</tr>
</tbody>
</table></div>
<h2>Using an exchange statement beyond bookkeeping</h2>
<p>The statement is also the input to any tax or audit process, and that is where its limits bite hardest. Cost basis methods differ — some jurisdictions use first-in-first-out, others allow average cost, and the treatment of transfers between your own accounts varies.</p>
<p>A venue only sees its own side, so one statement cannot describe assets held elsewhere. Consolidating across accounts is your job, and it is easier monthly than annually.</p>
<h3>What to keep and for how long</h3>
<p>Keep the full transaction-level export, not the PDF summary. Summaries drop the identifiers you need to match trades across accounts, and retention periods differ by jurisdiction. Check local rules for how long records must be kept; the safe habit is to keep everything and archive it offline.</p>
<p>Name exports with their generation date and keep a copy that does not depend on continued access to the venue. If an account is closed or restricted, the export is all you will have.</p>
<p>The post <a href="https://www.ladyww.net/exchange-statement/">Reading Your Exchange Statement</a> appeared first on <a href="https://www.ladyww.net">LadyChain</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.ladyww.net/exchange-statement/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>What Exchanges Report About You</title>
		<link>https://www.ladyww.net/exchange-reporting/</link>
					<comments>https://www.ladyww.net/exchange-reporting/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Tue, 27 Oct 2026 10:02:31 +0000</pubDate>
				<category><![CDATA[Regulation]]></category>
		<category><![CDATA[Audit Trail]]></category>
		<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Crypto Tax]]></category>
		<category><![CDATA[Exchange Reporting]]></category>
		<category><![CDATA[Identity Checks]]></category>
		<category><![CDATA[Information Returns]]></category>
		<category><![CDATA[Jurisdiction]]></category>
		<category><![CDATA[Reconciliation]]></category>
		<category><![CDATA[Records]]></category>
		<category><![CDATA[Tax Reporting]]></category>
		<guid isPermaLink="false">https://www.ladyww.net/exchange-reporting/</guid>

					<description><![CDATA[<p>Exchange tax reporting is the flow of account data from a trading venue to a tax authority, and it is narrower than most people assume. A venue generally reports what [&#8230;]</p>
<p>The post <a href="https://www.ladyww.net/exchange-reporting/">What Exchanges Report About You</a> appeared first on <a href="https://www.ladyww.net">LadyChain</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Exchange tax reporting is the flow of account data from a trading venue to a tax authority, and it is narrower than most people assume. A venue generally reports what it can see: the trades on its own order books, the fiat that moved through its banking rails, and the identity attached to the account. It does not report your wallet balances, your positions elsewhere, or what you originally paid for the coins you deposited.</p>
<p>That gap is the whole story. Exchange tax reporting is an information stream, not an assessment. It tells an authority that something happened; it rarely tells them whether the result was a gain, a loss, or neither — and that determination depends on records the venue has never held.</p>
<ul>
<li><strong>Reporting is usually about gross amounts, not net results.</strong> Proceeds without cost basis look like income to anyone reading a summary.</li>
<li><strong>Coverage is venue-by-venue.</strong> Accounts on different platforms produce separate streams that may never be joined up.</li>
<li><strong>Deposits are the weak point.</strong> A coin bought elsewhere and sold here arrives with no price history attached.</li>
<li><strong>Your own records remain the primary source.</strong> Reporting is cross-checked against them, not a replacement for them.</li>
</ul>
<h2>What exchange tax reporting usually contains</h2>
<p>Reporting scope depends on the jurisdiction, the venue, and the type of account, but the underlying data set is fairly consistent because it comes from the same order management systems that produce your statements.</p>
<h3>Proceeds rather than profit</h3>
<p>Most regimes built for securities reporting were designed around gross proceeds, because the broker knows the sale price and does not know the customer&#8217;s basis. Crypto venues inherit that shape. A report can therefore show a large sale figure that, once matched against an original purchase, turns out to be a modest gain or an outright loss. Reading the reported number as taxable income overstates the liability badly.</p>
<h3>Identity and account scope</h3>
<p>Venues report against verified identity, which is why the account registration details matter more than the trading activity. An account opened in one name, funded from a shared bank account, and used by two people creates a reporting mismatch that is tedious to unwind later. The same applies to business accounts used for personal trades, or personal accounts used for a company&#8217;s treasury.</p>
<h3>What is usually excluded</h3>
<p>Self-custody wallets, activity on venues that do not report in your jurisdiction, peer-to-peer trades, and anything that never touched a reporting entity. This is not a loophole; it is the reason a complete picture requires your own records alongside the reported ones.</p>
<h2>Where exchange tax reporting diverges from your books</h2>
<p>Divergence is normal rather than exceptional. The two datasets are built for different purposes: one for matching identity to transactions, the other for computing a result.</p>
<h3>Transfers in and out</h3>
<p>A withdrawal of coins to a wallet is usually reported as a movement with no gain attached, because nothing was sold. The consequence appears later: when those coins come back and are sold, the venue has proceeds and no basis. If your records also lost track of the original purchase, the same transaction is unattributed on both sides, and the reconstruction becomes the expensive kind.</p>
<h3>Wrapped, rebased and renamed assets</h3>
<p>Wrapped tokens, rebasing balances, and assets that migrate to a new contract all break the simple one-asset-one-history assumption. A venue may report the new ticker, your notes may hold the old one, and the quantities may not match because a rebase changed them without a transaction. Reconciliations fail on these cases far more often than on ordinary trades.</p>
<h3>Fees, rewards and adjustments</h3>
<p>Trading fees are usually visible. Staking distributions, referral credits, and promotional bonuses are less consistently reported, and their treatment varies: some are income at receipt, some reduce cost, some are not reportable until disposal. A venue summary that omits them is not wrong; it is simply reporting a different question.</p>
<h2>Matching reported data against your own records</h2>
<p>The table below maps the usual sources and what each one cannot tell you. Use it to decide where a reconciliation needs a third input.</p>
<div class="slv-table not-prose my-6 overflow-x-auto rounded-2xl border border-ink-800/70 bg-ink-900" data-slv-table><table>
<thead>
<tr>
<th>Record type</th>
<th>Who holds it</th>
<th>What it usually misses</th>
</tr>
</thead>
<tbody>
<tr>
<td>Venue trade history</td>
<td>The exchange</td>
<td>Basis on deposited coins</td>
</tr>
<tr>
<td>Information return or statement</td>
<td>The exchange, sent onward</td>
<td>Losses netting, cross-venue activity</td>
</tr>
<tr>
<td>On-chain transaction log</td>
<td>Public ledger</td>
<td>Price, ownership, intent</td>
</tr>
<tr>
<td>Bank and payment records</td>
<td>Bank, processor</td>
<td>What was bought, at what quantity</td>
</tr>
<tr>
<td>Your own ledger</td>
<td>You</td>
<td>Nothing, if maintained; everything, if not</td>
</tr>
</tbody>
</table></div>
<p>The last row is the uncomfortable one. Every other source is a partial view held by someone else. Only your ledger is designed to answer the question actually being asked, which is what each disposal cost you.</p>
<blockquote><p>Reported data answers &#8220;what did this account do&#8221;. Your records answer &#8220;what did this cost me&#8221;. Tax is computed from the second question, which is why the first one so often looks alarming.</p></blockquote>
<h2>Reconciling exchange tax reporting in six steps</h2>
<p>Run the reconciliation once per year, before any filing deadline rather than during it. The sequence below keeps the two datasets separate until the final comparison, which prevents one from quietly overwriting the other.</p>
<ol>
<li>Export the full transaction history from every venue you used, including closed accounts if the export is still available.</li>
<li>Export your own ledger, or build one, with a row per acquisition and a row per disposal.</li>
<li>Match by timestamp, asset, quantity and reference, starting with the largest amounts rather than the earliest.</li>
<li>Flag every disposal in the venue data that has no matching acquisition in your ledger — these are the deposited coins.</li>
<li>Flag every acquisition in your ledger that has no venue record, which usually means a self-custody buy or a transfer in.</li>
<li>Resolve the flags with a documented assumption: a stated price source, a transfer link, or a labelled estimate.</li>
<li>Recompute totals only after the flags are closed, so the arithmetic is not masking a classification error.</li>
</ol>
<p>Expect a residual list that never fully closes. A handful of small unmatched items is normal; a large unexplained block is not, and it usually points to an account you have forgotten rather than to a venue error.</p>
<h2>What to do when the numbers disagree</h2>
<p>Disagreement is a signal about your records, not about the venue&#8217;s honesty. Start by checking whether the two datasets are measuring the same thing: one may include internal transfers, the other may exclude fees, and both may be correct on their own terms.</p>
<p>If the difference survives that check, document it. Write down the size of the gap, the likely cause, and the treatment you applied. A reconciliation file with a short explanation is worth more than a perfectly matched spreadsheet nobody can audit, because the explanation is what makes the position defensible if anyone asks.</p>
<p>Where the amount is material, the right move is to get local advice rather than to guess at a convention. Rules differ by jurisdiction, thresholds differ, and the treatment of a specific transaction type often turns on facts a general article cannot see. Nothing here is tax or legal advice.</p>
<p>The post <a href="https://www.ladyww.net/exchange-reporting/">What Exchanges Report About You</a> appeared first on <a href="https://www.ladyww.net">LadyChain</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.ladyww.net/exchange-reporting/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
