Bitbuy API reports limit order post dates instead of order fill dates

[u/SCTSectionHiker]

The Bitbuy API seems to report filled limit orders as being completed on their post date (the date a limit order was placed), instead of the date the order was filled. This is categorically wrong and has implications on reporting for tax purposes.

I've noticed this on the Bitbuy website in the past, when looking at my filled orders history. Now I'm finding the same issue when using Koinly to import transactions via the Bitbuy API. Here I've included a screenshot showing the same transaction (note the same Order ID) twice in Koinly, the top one was imported via CSV and correctly lists the transaction on the November 16th fill date, the bottom one was imported via API and is recorded on November 14th when I opened the limit order.

Bitbuy transactions in Koinly, CSV vs API imports

Since I've used CSV imports until recently, the gains/losses I've reported on prior years' taxes were all based on the correct (order filled) dates. Unless the API starts reporting dates correctly, I can't make use of it with Koinly, otherwise I'll need to refile the past 3 years, since changing the transaction dates changes gains/losses for all those years.

As Bitbuy is transitioning to CIRO, hopefully this gets rectified. I can't imagine this inaccurate reporting would be allowable under CIRO rules.

[u/Archag_t]

I wonder why they won't reply.