I normally create bank transactions from CSV files with date, description, reference, and amount. I use several automatic rules to normalize the transaction before importing, and it has so far been working fine.
Now, I just found out that the reference field from the CSV is no longer being imported, and instead, it is pre-pended to the description of the bank transaction.
The result is that general ledger transactions for cash and cash equivalent accounts are very convoluted - the bank description, which usually comes out from the bank a mess, now has a reference prepended to it. For example, one of the lines in the general ledger transaction report (just the date, description, amount, and the running balance on the account):
| 2026-01-02 — COMPANY — 5234270 AUTOMATED PAYMENT - OUR COMPANY LOAN ADM LOAN PAYMT 4768112890 | 9,329.51 53,180.63 Dr |
|---|---|
Repeat that for thousands of lines in a report, and you get the picture.
What is your recommendation for a workflow to produce a cleaner report? Anything that could be done to decouple the description of the CSV from the report with rules, or additional CSV fields, or maybe a report configuration option?
Thanks for your time, and congratulations on the product.