# Import bank statement - "Reference" field no longer recognized

**URL:** <https://forum.manager.io/t/import-bank-statement-reference-field-no-longer-recognized/53406>\
**Category:** Uncategorized\
**Created:** [May 7, 2024, 4:19am UTC](https://forum.manager.io/t/import-bank-statement-reference-field-no-longer-recognized/53406 "2024-05-07T04:19:24Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![jfaleiro](https://avatars.discourse-cdn.com/v4/letter/j/77aa72/32.png) [@jfaleiro](https://forum.manager.io/u/jfaleiro)\
**Post date:** [September 1, 2026, 9:45pm UTC](https://forum.manager.io/t/import-bank-statement-reference-field-no-longer-recognized/53406/21 "2026-09-01T21:45:18Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![shobhit](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/shobhit/32/21847_2.png) [@shobhit](https://forum.manager.io/u/shobhit)\
**Post date:** [September 2, 2026, 6:49am UTC](https://forum.manager.io/t/import-bank-statement-reference-field-no-longer-recognized/53406/22 "2026-09-02T06:49:10Z")

</div>

I had to stop using the “Import bank statement” feature as it just doesn’t work without an “External Reference” field for me. The workaround that I found was to create the Payments and Receipts in google sheet and then use the bulk create feature. This way I can add my own Reference value in the same way as it used to work via the import bank statement earlier.

Don’t think the “External Reference” field will be added - the topic was never added in ideas.

---

<div class="post-metadata">

**Author:** ![jfaleiro](https://avatars.discourse-cdn.com/v4/letter/j/77aa72/32.png) [@jfaleiro](https://forum.manager.io/u/jfaleiro)\
**Post date:** [September 2, 2026, 5:46pm UTC](https://forum.manager.io/t/import-bank-statement-reference-field-no-longer-recognized/53406/23 "2026-09-02T17:46:35Z")

</div>

My other post titled “[How to improve general ledger transaction presentation?](https://forum.manager.io/t/how-to-improve-general-ledger-transaction-presentation/69544)” was merged into this post, but I don’t think they address the same issue.

This post is on the reference field; the other post is asking for best practices on how to live with the current general ledger transaction report when you have a convoluted description (the convoluted description is partially a result of the prepending of references, but mainly a result of how banks use descriptions to send all kinds of garbage).

[Previous page](https://forum.manager.io/t/import-bank-statement-reference-field-no-longer-recognized/53406.md?page=1)
