Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add an option to show the final report grouped per transaction type (crypto-to-crypto, crypto-to-fiat, ...) #121

Open
stokaxv opened this issue Jun 14, 2024 · 2 comments

Comments

@stokaxv
Copy link

stokaxv commented Jun 14, 2024

In Spain, we are asked to provide the report defining the transaction type that we have done to close a position. I think it's especially interesting to distinguish the balance when we have changed from one crypto to another, and when we have sold a crypto to obtain EUR. I wonder if this option is already there, since I have not found it. I think it should not be very difficult to obtain, at least looking at my .ods file. Any insights on this?

Thanks in advance and many thanks for this contribution.

@eprbell
Copy link
Owner

eprbell commented Jun 14, 2024

In the US case RP2 generates two tax-specific reports:

  • rp2_full_report: country-agnostic tax report showing lot fractioning and pairing (according to the accounting method), balances, history, etc. This report is useful for most countries.
  • tax_report_us: US-specific report that presents a subset of the information from rp2_full_report in a format mandated by the US government (form 8949). This report is useful only in the US.

I think the above approach is a good pattern for all countries. In the case of Spain we only have rp2_full_report and it would probably be useful to add the Spanish equivalent of tax_report_us, which would generate the data required by the Spanish government, in the format they require (let's call this tax_report_es, for simplicity and homogeneity). The new tax_report_es plugin can generate the needed information by accessing the data structures generated by the tax engine.

As for the specific questions you asked, I'm not sure I understand what you mean exactly by "defining the transaction type that we have when we close the position": do you mean what is the transaction type (gift, sale, etc.) of the last transaction before the amount of crypto goes to zero? Either way it should be possible to capture any needed information from the data structures provided to the plugin by the tax engine.

@eprbell
Copy link
Owner

eprbell commented Jun 14, 2024

Adding a bit more context. The output from tax_report_us is immediately recognized by any US tax accountant as Form 8949. What is the Spanish equivalent of Form 8949? The tax_report_es plugin should generate that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants