


Ask the community...
Have you tried reconstructing your transactions using a crypto tax software like Koinly or CoinTracker? You can import your wallet addresses and they'll scan the blockchain for all your transactions. Not perfect, but better than nothing. I went through something similar last year. Had about $20k in crypto transactions but minimal documentation. I ended up creating a detailed spreadsheet showing my best estimates with notes explaining my methodology. I attached this to my return with a statement explaining the limited documentation situation. The fact that you have bank statements showing the money going in and out is actually a really good starting point. That establishes your overall profit margin pretty clearly.
I tried CoinTracker but the problem is some of my transactions were on smaller exchanges that don't connect well with these services. Plus I did some peer-to-peer transactions that don't show up on the blockchain in an obvious way. Do you think the IRS would accept a combination of blockchain data and my personal records?
Yes, a combination of blockchain data and personal records is a solid approach. The IRS understands that crypto documentation can be challenging. They mainly want to see that you're making a good-faith effort to report accurately. For those peer-to-peer transactions, create a separate log with as much detail as possible - dates, amounts, parties involved (you can anonymize the other party), and the purpose. If you have any chat logs, emails, or other evidence of these transactions, save those too. The more supporting evidence you can compile, the stronger your position will be if questioned.
For what it's worth, if you end up getting audited, remember that the burden of proof is on the IRS to show why your reported numbers are wrong IF you have some reasonable documentation. They can't just say "we don't believe you" without evidence. I went through an audit last year over some stock sales where I was missing basis documentation. I provided my best reconstruction with explanations and they actually accepted most of it. Only had to pay additional tax on a small portion where I really couldn't substantiate anything. Make sure to keep EVERYTHING - notes, screenshots, emails about transactions, bank statements. If the worst happens, hire a tax pro who specializes in crypto. They've seen it all and know how to deal with the IRS in these situations.
I've been trying to submit my taxes electronically since yesterday but I keep hitting a wall. Every time I submit, I get a rejection email with this weird error: Issue: Business Rule X0000-005 - The XML data has failed schema validation. cvc-complex-type.2.4.a. Invalid content was found starting with element 'WagesNotShownAmt'. One of '{"http://www.irs.gov/efile":WagesLiteralCd}' is expected. It also says: Field/Xpath: /efile:Return[1]/efile:ReturnData[1]/efile:WagesNotShownSchedule[1]/efile:WagesNotShownSch[1]/efile:WagesNotShownAmt[1] This might as well be in another language! I have two different W-2s and I've entered everything correctly as far as I can tell. Why is it saying "not shown"? I saw an old post suggesting it might be related to punctuation in the forms, so I went through and removed everything except spaces and hyphens. Still no luck after checking everything three times. Do I have to give up on e-filing and mail this thing in? My refund is pretty decent this year and I don't want to wait forever to get it. Has anyone run into this specific error before? UPDATE: I figured it out! Posting the solution in case anyone else gets stuck with this same issue. I had put my total wages in both the white box on the left side of Line 1 AND in the column on the right. Apparently you're only supposed to put the final number in the right column. When I cleared out the white box on the left and only kept the number in the right column, the system accepted my return immediately. Such a small thing causing so much frustration!
Just so others know - these XML schema validation errors usually happen with fields that have specific format requirements. The one that got me last year was putting cents in my estimated tax payments using a decimal point (like 1500.00) when the field was only supposed to have whole numbers (1500). Took me forever to figure out!
Wait really? So we're not supposed to use decimal points at all in the tax forms? I've been doing mine wrong for years then...
It depends on the specific field in the tax software. Some fields accept decimals, while others require whole numbers only. The problem is that most tax software doesn't warn you about this until you try to e-file and get rejected. For example, estimated tax payment fields typically want whole dollars only, no cents. But some deduction fields might accept exact amounts with cents. The IRS e-file specifications are incredibly detailed about which fields accept which formats, but regular taxpayers never see these rules. That's why these errors are so frustrating - we're basically being asked to comply with technical specifications we can't see.
Throwing in another tip - sometimes these XML errors can be caused by special characters in name fields. I got rejected because I had "O'Brien" as my employer name, and the apostrophe caused an XML validation error. Had to remove it to get accepted.
OMG thank you!!! I think this might be my issue. My employer's name has an ampersand in it (Something & Sons LLC) and I keep getting rejected. Going to try removing it now!
One thing nobody has mentioned yet is that you need to be careful about wash sales when dealing with capital losses. If you sell an investment at a loss and then buy the same or a "substantially identical" investment within 30 days before or after the sale, it's considered a wash sale and you can't claim the loss on your taxes right away. I learned this the hard way when I thought I had $8k in losses to carry over, but because I had rebought some of the same stocks within the 30-day window, about $3k of my losses were disallowed as wash sales. The loss doesn't disappear forever, but it gets added to the cost basis of the replacement shares, so you don't get the tax benefit until you eventually sell those shares.
How exactly do you track this stuff? Like if I sold some Tesla at a loss in December but then bought some again in January, do I have to manually figure out the wash sale or will my brokerage statement show it? This whole capital loss thing is making my head spin.
Most brokerages will track wash sales for you on your 1099-B forms and year-end tax statements. They'll have a column that shows "Wash Sale Loss Disallowed" or something similar. However, they only track wash sales within the same brokerage account - they won't know if you sold in one account and bought in another, or if your spouse bought the same security in their account. If you're doing your taxes with software like TurboTax or H&R Block, they'll usually flag potential wash sales when you enter your trading information. But it's always good to review your brokerage statements carefully and look for those wash sale notations, especially if you're an active trader or if you're trading the same securities across multiple accounts.
Also, make sure you understand the difference between short-term and long-term capital gains/losses. If you held the investment for less than a year before selling at a loss, it's short-term. More than a year, it's long-term. When you apply carried-over losses, short-term losses first offset short-term gains (taxed at your ordinary income rate), and long-term losses offset long-term gains (taxed at the preferential capital gains rates). Only after you've offset gains of the same type can you apply remaining losses to the other type. This order of operations can make a big difference in your tax bill if you have a mix of short and long-term transactions! Many people miss this nuance.
Great point! I just want to add that this is why tax software can sometimes get this wrong. It gets complicated fast when you have multiple types of gains and losses from different years. My tax guy showed me how one year I had long-term losses but short-term gains the next year, and the software didn't optimize how they offset each other. Had to manually override it which saved me almost $900.
Just to add a practical tip - when I was learning 1.960-2, I created a simple Excel template that breaks down the deemed paid credit calculation formula. The key is tracking: 1) The US shareholder's pro rata share of the CFC's Subpart F/GILTI 2) The CFC's foreign income taxes paid 3) The CFC's total earnings and profits The basic concept is that you're essentially figuring out what percentage of the foreign corp's income is coming to the US as Subpart F/GILTI, then allowing that same percentage of foreign taxes as a deemed paid credit.
That Excel approach sounds really helpful! Would you be willing to share a sanitized version of that template? I'm trying to create something similar but want to make sure I'm setting it up correctly.
I can't share the actual file for confidentiality reasons, but I can describe the basic structure. I have columns for each relevant CFCs and rows that calculate: The CFC's total E&P for the year, then the portion that's Subpart F and the portion that's GILTI. Below that, I list the total foreign taxes paid by the CFC. Then I compute the deemed paid taxes by multiplying the foreign taxes by the ratio of included income (Subpart F or GILTI) to total E&P. Don't forget that for GILTI inclusions under 960(d), you only get 80% of the deemed paid taxes. And everything needs to be tracked by separate income baskets too!
Just fyi, it's worth noting that the TCJA really changed how 960 works. Before 2018, we used to have this pooling approach for deemed paid credits, but now it's calculated on a current-year basis. If you're studying older materials, make sure they reflect the post-TCJA rules!
Theodore Nelson
5 To address your question about suing the government - it's extremely unlikely you'd succeed. The Supreme Court has previously ruled (in Flemming v. Nestor, 1960) that Americans don't have a legal right to Social Security benefits. Congress can change the rules at any time. That said, completely eliminating Social Security is politically unfeasible. About 65 million Americans receive benefits, and they vote in high numbers. Any politician suggesting complete elimination without replacement would face enormous backlash.
0 coins
Theodore Nelson
ā¢14 Wait, we don't have a legal right to benefits even though we're forced to pay into the system? That seems completely unfair! How is that constitutional?
0 coins
Theodore Nelson
ā¢5 The court essentially ruled that Social Security is a social program, not a contract, and Congress retains the right to alter, amend, or repeal any provision of the Social Security Act. The case specifically involved a person who was denied benefits after being deported for being a member of the Communist party. While it might seem unfair, the constitutional basis is that Congress has broad powers to tax and spend for the general welfare. The FICA tax is considered a valid exercise of this power, and benefits are authorized spending programs that can be modified. This is different from private contracts or property rights that have stronger constitutional protections.
0 coins
Theodore Nelson
3 Something important to consider: eliminating Social Security would create a massive surge in poverty among elderly Americans. Before Social Security, about 50% of seniors lived in poverty. Today it's around 9%. For about 40% of elderly Americans, Social Security provides at least 50% of their income. For about 14%, it provides 90% or more of their income. Any complete elimination would need to address this reality or we'd see catastrophic consequences.
0 coins
Theodore Nelson
ā¢17 This is why I'm always confused when younger people say they're planning as if Social Security won't exist. Even if it faces funding challenges, some version of it will almost certainly continue. The political consequences of eliminating it would be too severe.
0 coins