Of course, the specific problem that OP outlined here had to do with what
happens in GnuCash *after* transactions have been imported, rather than the
import itself.
David T.
On May 6, 2023, 04:14, at 04:14, R Losey wrote:
>It's issues like this that have made me wary of importing
It's issues like this that have made me wary of importing transactions;
doing them manually doesn't take that much longer.
On Fri, May 5, 2023 at 2:54 AM David T. via gnucash-user <
gnucash-user@gnucash.org> wrote:
> I have seen the exact same behavior, and find it more than just an
>
I have seen the exact same behavior, and find it more than just an annoyance.
This arbitrary reversion to different text strings can result in flawed and
erroneous data entering your books--including entering transactions into
placeholder (i.e., read-only) accounts.
David T.
On May 5, 2023,
This is part 2 of a two-part question about imported transactions.
My bank invariably imports transactions in barely readable technical jargon.
For example, a debit card purchase at Villeneuve & Sons comes into the
Aqbanking importer as:
"[PR]L. VILLENEUVE &"
My problem is that it's
