# No name of account on Purchase Invoice

**URL:** <https://forum.manager.io/t/no-name-of-account-on-purchase-invoice/41889>\
**Category:** Uncategorized\
**Created:** [July 9, 2022, 9:03am UTC](https://forum.manager.io/t/no-name-of-account-on-purchase-invoice/41889 "2022-07-09T09:03:02Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![ries](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/ries/32/8988_2.png) [@ries](https://forum.manager.io/u/ries)\
**Post date:** [July 9, 2022, 9:03am UTC](https://forum.manager.io/t/no-name-of-account-on-purchase-invoice/41889/1 "2022-07-09T09:03:02Z")

</div>

Name of account remains empty if Description is used.

 ![inkoopfactuur01](https://us1.discourse-cdn.com/flex019/uploads/manager1/original/3X/8/d/8d4963be96b1b542fcaa74e50664c35dcf30f4b4.jpeg)

 ![inkoopfactuur02](https://us1.discourse-cdn.com/flex019/uploads/manager1/original/3X/4/7/47aec4b3e3bfea7718d0dee110a6bd5846b2f104.jpeg)

---

<div class="post-metadata">

**Author:** ![lubos](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/lubos/32/62798_2.png) [@lubos](https://forum.manager.io/u/lubos)\
**Post date:** [July 9, 2022, 9:23am UTC](https://forum.manager.io/t/no-name-of-account-on-purchase-invoice/41889/2 "2022-07-09T09:23:23Z")

</div>

This is intentional. Basically the idea is that `Account` will show only if item and line description is empty.

Therefore you can hide `Account` on printed document by specifying item or/and line description.

It is desirable to be able to hide `Account`, especially on documents printed for customers and suppliers as `Account` would your internal thing.

But I can see it doesn’t look intuitive if having multiple lines and not using description and item on all of them. So perhaps the improvement should be that `Account` is hidden only if all lines have line description or item specified.

---

<div class="post-metadata">

**Author:** ![eko](https://avatars.discourse-cdn.com/v4/letter/e/a8b319/32.png) [@eko](https://forum.manager.io/u/eko)\
**Post date:** [July 9, 2022, 3:20pm UTC](https://forum.manager.io/t/no-name-of-account-on-purchase-invoice/41889/3 "2022-07-09T15:20:54Z")

</div>

> [@lubos](#):
>
> So perhaps the improvement should be that `Account` is hidden only if all lines have line description or item specified.

Indeed that would be a good solution.

---

<div class="post-metadata">

**Author:** ![Tut](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/tut/32/3286_2.png) [@Tut](https://forum.manager.io/u/Tut)\
**Post date:** [July 9, 2022, 3:34pm UTC](https://forum.manager.io/t/no-name-of-account-on-purchase-invoice/41889/4 "2022-07-09T15:34:15Z")

</div>

> [@lubos](#):
>
> So perhaps the improvement should be that `Account` is hidden only if all lines have line description or item specified.

I suppose there may be a point to having something entered for each line item, rather than leaving it totally blank. But I fail to see why you would ever enter a line on a transaction form with no item or description. That would would be a horrible practice, no different than random postings to accounts. Such a transaction would not be auditable, internally or externally. One would have to guess what it was for after the fact.

A better solution than listing the posting account, in my opinion, would be to throw transactions with blank line items into _Suspense_.

---

<div class="post-metadata">

**Author:** ![eko](https://avatars.discourse-cdn.com/v4/letter/e/a8b319/32.png) [@eko](https://forum.manager.io/u/eko)\
**Post date:** [July 9, 2022, 3:50pm UTC](https://forum.manager.io/t/no-name-of-account-on-purchase-invoice/41889/5 "2022-07-09T15:50:53Z")

</div>

> [@Tut](#):
>
> But I fail to see why you would ever enter a line on a transaction form with no item or description. That would would be a horrible practice, no different than random postings to accounts.

Assume you have an account called electricity bills then you do not need to enter a description as it is self explanatory and acceptable by an audit as well.

---

<div class="post-metadata">

**Author:** ![Ealfardan](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/ealfardan/32/63166_2.png) [@Ealfardan](https://forum.manager.io/u/Ealfardan)\
**Post date:** [July 9, 2022, 4:34pm UTC](https://forum.manager.io/t/no-name-of-account-on-purchase-invoice/41889/6 "2022-07-09T16:34:14Z")

</div>

> [@Tut](#):
>
> A better solution than listing the posting account, in my opinion, would be to throw transactions with blank line items into _Suspense_.

I don’t like this approach.

For some of my clients the COA is setup in such a way that the account names can serve as descriptions, at least for sales. Take this COA setup for example:

- Creative service
- Production
- Event management
- …

In this case it’s completely fine to leave the description blank since the accounts were so aptly named.

So I guess, lubos’ proposed solution is the way to go especially since it’s also the path of least resistance.

---

<div class="post-metadata">

**Author:** ![Tut](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/tut/32/3286_2.png) [@Tut](https://forum.manager.io/u/Tut)\
**Post date:** [July 9, 2022, 4:42pm UTC](https://forum.manager.io/t/no-name-of-account-on-purchase-invoice/41889/7 "2022-07-09T16:42:45Z")

</div>

Well, I guess practices differ. What is acceptable in one location might not pass audit in another. I understand your point of view, although I would never recommend or follow your approach. The proposed solution would make the issue irrelevant for anyone who describes transaction lines by selecting an item or entering a description, so I cannot object too strenuously.

---

<div class="post-metadata">

**Author:** ![Ealfardan](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/ealfardan/32/63166_2.png) [@Ealfardan](https://forum.manager.io/u/Ealfardan)\
**Post date:** [July 5, 2026, 8:12pm UTC](https://forum.manager.io/t/no-name-of-account-on-purchase-invoice/41889/8 "2026-07-05T20:12:54Z")

</div>

Uncategorized topics older than 3 years with no recent activity
