Ideas to help make categorizing Accounts Receivable easier

[dr00bie]

I have a couple of ideas regarding the behavior of receipts that are categorized as Accounts Receivable.

1. Only show customers that have accounts receivables? Currently the customer dropdown shows all of the customers in the database.

2. Show Invoice Amount in the Invoice dropdown beside of the date. This takes a bit more effort to correctly categorize my Accounts Receivables, as I need to note the date of invoice and amount, then go back to the Receipts and correctly categorize. Having the amount shown would allow me to compare to the receipt amount and make things more efficient.

[Tut]

Your first suggestion is not practical, because it would preclude receipt of advances and deposits from customers.

Your second suggestion is already in the ideas category (although the title does not suggest it):

Invoice search and Apply idea for Cash Applications

Search function for cash applications. When applying cash receipts to customer invoices currently the only mechanism to apply to invoices is to choose the appropriate invoice number from the list values/drop down list. We have numerous customers that provide limited to no ‘remittance advice’ information or simply state ‘July Invoice’ etc. Others are paying the oldest one or two open invoices. It is not therefore always readily possible to quickly identify the correct invoices that the custome…

[dr00bie]

I appreciate your response. Having some control over the behavior would be nice to make the software easier to use for those who never use advances or deposits.

I would not lump my second suggestion in with the one already in ideas. My suggestion would be FAR easier to implement. Considering that the software is already pulling data for the drop down with unique invoice ID’s to use, and it is grabbing the date and invoice # to display, then why couldn’t it concatenate the amount in the same value as date?

[Tut]

You might not consider your suggestion to be part of the idea I linked to. But the developer considers all aspects of a suggestion when implementing improvements from the ideas list. The specifics that would encompass your suggestion are relatively far down in the thread.

Also, while you think your first suggestion might make it easier for you, it would make it harder for the many, many users who do accept deposits or advances.

[dr00bie]

You might not consider your suggestion to be part of the idea I linked to. But the developer considers all aspects of a suggestion when implementing improvements from the ideas list. The specifics that would encompass your suggestion are relatively far down in the thread.

This is an odd way of making improvements. If the improvement has already been requested, but is part of a very complex suggestion, then why can’t a more simple suggestion, that only completes 2% of the

Also, while you think your first suggestion might make it easier for you, it would make it harder for the many, many users who do accept deposits or advances.

Does the ability to change the template make it harder for other users? The suggestion is to allow users to change the way the invoice entry works, if you don’t use advances or deposits, then set to only show customers with open invoices. If you do take deposits, set to show all customers.

[Tut]

@dr00bie

Does the ability to change the template make it harder for other users?

Yes. Every option adds complexity. Inconsistent behavior becomes harder for the average user to diagnose. Instructional Guides become more elaborate and extensive. Features a user wants to employ become more difficult to find. Transaction forms get longer. The Settings tab grows ever harder to navigate. Data entry can be interrupted by the need to back out and set things up differently. I could go on and on.

The bottom line is that what seems attractive to one user can be maddening for others, another box to check, another small functional change. All of it adds up.