[PR #5344] Fix Boursorama GoCardless transaction ordering #12939

Closed
opened 2026-04-10 21:42:51 -05:00 by GiteaMirror · 0 comments
Owner

Original Pull Request: https://github.com/actualbudget/actual/pull/5344

State: closed
Merged: Yes


I wrongly thought that all the card transactions will always have their first line with the CARTE identifier. But as I have seen recently, it's not the case, and we shouldn't rely on the ordering of the array returned by the Boursorama GoCardless integration.

Thus, check for transaction patterns in all of the lines of the unstructured array.

This addresses a true case (added in test) where the payee name was wrongly extracted as being 110,04 Gbp / 1 Euro = 0,860763454.

**Original Pull Request:** https://github.com/actualbudget/actual/pull/5344 **State:** closed **Merged:** Yes --- I wrongly thought that all the card transactions will always have their first line with the `CARTE` identifier. But as I have seen recently, it's not the case, and we shouldn't rely on the ordering of the array returned by the Boursorama GoCardless integration. Thus, check for transaction patterns in all of the lines of the unstructured array. This addresses a true case (added in test) where the payee name was wrongly extracted as being `110,04 Gbp / 1 Euro = 0,860763454`. <!-- Thank you for submitting a pull request! Make sure to follow the instructions to write release notes for your PR — it should only take a minute or two: https://github.com/actualbudget/docs#writing-good-release-notes. Try running yarn generate:release-notes *before* pushing your PR for an interactive experience. -->
GiteaMirror added the pull-request label 2026-04-10 21:42:51 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#12939