Start a new topic

Customer account numbers

It would be nice to be able to add a customer account number when creating a new customer as well as just their name. Xero has an option to assign account numbers to customers which is handy when sending out statements as customers can use their account number as a reference when making payment. Right now I have to add account numbers manually in xero once the customer has been created in DEAR.


12 people like this idea

There is a unique identifier. The customer name must be unique (but it is not case sensitive). Customer codes are a legacy from days of very expensive storage. They are not very friendly, generally speaking ,and in practice I don't have a single client who is missing them (technical users are perfectly happy with the guid provided by the API) which suggests there are good workarounds. When I first started with migrations I suggested appending the customer code of the old system to the customer name e.g. in []s, so searchable, but no one was ever interested.

Xero, by the way, treats contact names in the same way as Dear. Xero did eventually add an account code field (optional). I should survey my users to see how many use it ... not many, I think. 


The generalised feature request would be for additional attributes to be optionally mandatory and optionally unique. I would like this, particularly being able to make a field mandatory, and I think I already requested this (Unleashed now has 'required' extra fields, but only for products and they are not yet integrated into reporting: Dear is still miles ahead.)


As for payment references, it would be much better for customers to reference an invoice number when making payments, rather than an account code, which wouldn't tell you which invoice is being paid, a funny point when you consider this is a topic about unique identifiers.



2 people like this
Also, just to add my 2c, something as simple as unique identifiers for customers and suppliers is a pretty stock standard component of almost every other accounting, POS and inventory software system out there.

I have implemented half a dozen systems both SaaS and server based and have yet to see one, apart from Dear, that doesn't have a searchable vendor/customer code that is unique for every entry.

While your work-around is fine for a small number of customers it is still time-consuming and not really workable for a large customer database.

 


2 people like this

This would also be helpful when using your integrated POS and setting up a loyalty program. I could offer a loyalty card to customers with a unique barcode or number sequence that represents that customers account number. 


1 person likes this
Dear would be better if had a dedicated customer number field in the customer information screen, preferably above the company name. Id like to use the Xero account number field, why can't that feed back & forth to Dear rather than me having another opportunity of human error. We would have to manually enter this data into additional attributes which creates another step of loading/opening another 2 windows at least. With 4000 customers, it's safe to expect 120-160 mistakes. And then more issues if we decide to change an account number, like we used to upgrade customer number 1830. (Numbers mean cash account) to WSC (letters for customer with a 30 day EoM trading account)

1 person likes this

@Tristan Thomas, I agree about solving problems for the market rather than custom specific requests.


However, the heart of the issue here, is that DEAR does not create or use a unique identifier for Customers. Using customer name as the uniqueness constraint prevents it from syncing properly with QBO.


While using Additional Attributes as you outlined above is interesting, there is no way to enforce a uniqueness constraint in an Additional Attribute.


1 person likes this

i have also asked for this feature. an additional field that can be searched for where we can have a unique number for assiging to that account. 


i have had customers ask what is their account number so that they can include it in EFT payments so that their payment is allocated to their account correctly.


so far we have not had an issue but with well over 1000 active accounts, we expect sooner or later a payment received might be allocated to the wrong account without this simple data.


further more, when i pay all our suppliers, i put in the account number that is on their statement, it helps temp staff allocate payments correctly.


also, lots of our customers still come in and say their old account number because it's quicker for me to put in an account code that search through all the businesses, whose name starts with the town we are opperating in.


in Retail manager that we came from, we used to have letters like "RSSW" as an account code for customers with an account and numbers like "180" for COD customers.


1 person likes this
I completely agree. Name should never be used as a unique identifier. We recently found that Customer name changes in Quickbooks don't sync back to Dear because Dear uses customer names as the unique identifier for Customers. This is poor behavior especially since most other areas of Dear correctly have unique identifiers (like SKUs) Customer Name combined with an Account Number should be the uniqueness constraint. Michael

1 person likes this
If we were to set a unique Customer ID number utilising additional attributes would that number be searchable on the View All Customer page?

 

YES!  Additional Attribute are searched in both the Sale list and the Customer list through the DEAR front-end.  


You CANNOT search for Additional Attributes through the API for either Sales or Customers (at this time; May 2017) 

Note that this field exports to the Xero contact so Xero's link feature gives you a button to take you immediately to the Xero Customer page.

@Michael Davis I don't think it's always fair to want a system to conform to your particular workflow.  Generally the idea behind a unique identifier like an account number is that it never changes.  


Using DEAR, for example, you could assign one Additional Attribute field for a unique ID.  Another Additional Attribute field could be assigned as a drop-down for your various account classes. 


DEAR's in-built functionality allows you to edit a customers credit terms from the customer dashboard.


If you have 4000 customers it would be pretty simple and error-free to use a spreadsheet to update their details rather than do it manually.

Account Code is a standard feature in accounting systems and usually serves as a unique identifier for things like integrations to other systems. More importantly, customers usually use it in the payment references....it's important and really can't be difficult to add, even if it is initially only to pull from Xero.
@Tristan Thomas, I think you're a bit harsh suggesting I want a custom solution. I'm trying to help Dear improve by suggesting improvements. This is a simple feature that me and others would appreciate. Next time I won't bother. Also, I support @Michael Kuzyk's comments. I use Additional Attributes for less important details. Customer and supplier unique identifiers are a basic detail that you should implement. If nothing else, it might stop duplicating suppliers in Xero. If the Dear architecture can't allow it, say so. There are other "custom" solutions that I'd like too that I'm sure I'm not the only Dear user to need; 1- a search feature for quotes by docket & product inside customer window like sales. ( its like searching for a needle in a haystack currently if you do lots of quotes, even if you split it to different customers) 2- a pricing matrix / system that increases sell prices if cost price increases. 3- a method to find out how many sales per week/month/year in the product window. (How are we supposed to forecast and create purchase orders or we have to run a report which is for every product when we only want details on one item. ) Again thanks to @Michael Kuzyk. I was going to give up.

@Michael Davis I'm not suggesting you don't try to improve DEAR by logging requests for improvements.  I'm just trying to show that it's often impossible to implement existing workflows with new software and sometimes there are functional work-arounds which you can use rather than waiting for the software to be built.  


I'd love to see your (1) and (2) suggestions implemented.  Why don't you start a new Feature Request for each of these and see if other DEAR users agree?


For (3) you can search a Sales by Product Details Report for a single SKU giving sales info on just that one product.

Login or Signup to post a comment