[UPSTREAM] Bitcoin.tax cost-basis and closing report discrepancies #51

New Issue

2024-05-11T04:06:22Z

AaronFiore commented

2024-05-11 04:06:22 +00:00

(Migrated from gitea.com)

As mentioned in https://gitea.com/EvergreenCrypto/docker-finance/pulls/50#issuecomment-822184

Issues related to calculating cost-basis when using Total/Volume and not using Price (fiat and non-fiat pairings)
Closing report balance issues when using Total/Volume but not the including Fee (which will break cost-basis if added)

This affects multiple accounts (not only Coinbase).

A resolution will require upstream clarification, as the documentation appears to not provide the needed clarity.

As mentioned in https://gitea.com/EvergreenCrypto/docker-finance/pulls/50#issuecomment-822184 - Issues related to calculating cost-basis when using `Total`/`Volume` and not using `Price` (fiat and non-fiat pairings) - Closing report balance issues when using `Total`/`Volume` but not the including `Fee` (which will break cost-basis if added) This affects multiple accounts (not only Coinbase). A resolution will require upstream clarification, as the documentation appears to not provide the needed clarity.

AaronFiore commented

2024-05-15 23:01:20 +00:00

(Migrated from gitea.com)

Email sent Monday evening, May 13th. No response yet.

AaronFiore commented

2024-05-25 00:52:23 +00:00

(Migrated from gitea.com)

No response yet. I've sent another message via another channel.

AaronFiore commented

2024-06-07 02:35:14 +00:00

(Migrated from gitea.com)

A response was received this Monday, June 3rd, confirming my concerns. Awaiting resolutions and/or further guidance.

AaronFiore commented

2024-07-11 03:05:29 +00:00

(Migrated from gitea.com)

No further response was received so I had sent a follow-up message on June 24th. The counter-response was an automated Zendesk email stating that a new ticket had been opened (Bitcoin.tax may have closed my original ticket despite there being no resolution).

Monday, June 24th, 2024 at 5:59 PM
Your request (26113) has been received. Our regular response time is typically between 24-48 hours.

Today, July 10th, I've still not received a response so I've sent another follow-up email. This time, however, no new ticket appears to have been opened (currently 26113).

No further response was received so I had sent a follow-up message on June 24th. The counter-response was an automated Zendesk email stating that a new ticket had been opened (Bitcoin.tax may have closed my original ticket despite there being no resolution). >Monday, June 24th, 2024 at 5:59 PM >Your request (26113) has been received. Our regular response time is typically between 24-48 hours. Today, July 10th, I've still not received a response so I've sent another follow-up email. This time, however, no new ticket appears to have been opened (currently 26113).

AaronFiore commented

2024-07-23 05:17:09 +00:00

(Migrated from gitea.com)

I received a helpful response July 17th and July 22nd. I appreciate their good-faith effort to resolve my concerns (which is ongoing).

Awaiting further response before applying any local patches.

I received a helpful response July 17th and July 22nd. I appreciate their good-faith effort to resolve my concerns (which is ongoing). Awaiting further response before applying any local patches.

AaronFiore commented

2024-07-27 08:41:21 +00:00

(Migrated from gitea.com)

No response yet. I can't wait any longer (next release is next week).

#96 has been opened and should work enough for now.

No response yet. I can't wait any longer (next release is next week). #96 has been opened and should work enough for now.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Reference: EvergreenCrypto/docker-finance#51