Glossary

QuickBooks Customer Display Name

The customer display name is the required name field on a QuickBooks Online customer record, the one name the customer is listed and selected by, and it must not be shared with any other customer, supplier or employee in the same company file.

Also called: display name, customer display name, Customer display name field, DisplayName, duplicate customer name

14-day free trial · card required · cancel anytime

Definition

A QuickBooks customer record has plenty of name fields: title, first name, last name, company name. Only one of them is the name the rest of QuickBooks uses. That is the display name. It is what appears in the customer list, in the payee dropdown on a transaction, on reports such as Sales by Customer, and on the customer line of every invoice and sales receipt.

Intuit treats it as mandatory. When you add a customer, Intuit’s instruction is to enter a name “in the Customer display name field”, and the field is marked required. The other name fields can be blank. This one cannot.

It also has to be unique, and the uniqueness rule is wider than most people expect. A display name cannot repeat across customers, suppliers and employees combined. Try to reuse one and QuickBooks refuses with an error that reads “Another customer, supplier, or employee is already using this name.” A business that buys from and sells to the same company runs into this the first time it tries to set that company up twice.

That combination, required and unique and shown everywhere, is why the display name is the field an integration reaches for when it needs to decide whether a customer already exists.

Key points

  • +The display name is the required name on a QuickBooks Online customer. Every other name field is optional.
  • +It is the name shown in lists, dropdowns, reports and on the customer line of each transaction.
  • +It must be unique across customers, suppliers and employees in the same company file.
  • +Intuit’s duplicate error: “Another customer, supplier, or employee is already using this name.”
  • +Merging two customers in QuickBooks works by renaming one display name to match the other, and Intuit says the merge “is permanent and can’t be undone.”
  • +Under QuickBooks multicurrency a customer carries one currency, so a customer billed in two currencies needs two records with two display names.
  • +Acodei matches a Stripe customer to a QuickBooks customer on the display name: case-insensitive, but otherwise character for character.

Why Acme Inc and Acme, Inc. are two different customers

To a person, Acme Inc, Acme, Inc. and Acme Incorporated are the same company. To any system matching on a name, they are three strings. One comma, one period or one extra space is enough to make them different.

QuickBooks itself is fine with that. All three can exist as separate customers, because none of them is an exact repeat of another. The uniqueness rule only blocks identical names, so near-duplicates sail through and sit side by side in the customer list.

The cost shows up later, in reports. Sales by Customer splits the company’s revenue across three lines. An ageing report shows three small balances instead of one real one. A customer statement run against one record leaves out the invoices on the other two. Nothing is wrong with any single record. The relationship is just spread across records nobody meant to create.

The fix is a naming convention decided once, before the list grows. Pick a form for legal suffixes, a rule for punctuation, and whether individuals are First Last or Last, First. Then hold every system that creates customers to the same rule, because a convention that only the bookkeeper follows still leaves the other systems creating near-duplicates.

The uniqueness rule, and the fixes Intuit suggests

The collision that stops people is the exact one: a supplier already called Acme Inc when you try to add a customer called Acme Inc. QuickBooks will not allow it, because the display name is shared across customers, suppliers and employees.

Intuit’s suggested ways out are practical. Find the existing record, then either rename it, for example by adding “a middle initial or a [1] at the end”, or make it inactive if it is no longer used.

Intuit also lists a cause that surprises people: turning on payroll after adding employees. The employee names then count against the same pool as customer and supplier names.

Any suffix you add changes the string. That is fine for a human picking from a dropdown. It matters as soon as another system is matching names, because a record called Acme Inc [1] no longer matches Acme Inc.

Merging duplicate customers runs through the display name

In QuickBooks, merging two customers runs through the display name itself. Intuit’s steps are to open the customer you do not want to keep, choose Merge contacts, note its display name, and “change the Display name to be an exact match of the duplicate customer profile you want to merge.” On save, QuickBooks asks you to confirm, and the two become one record with both histories.

Two cautions come with it. Intuit says to “check that neither customer has sub-customers before you merge them”, and that includes projects linked to the customer. And the merge “is permanent and can’t be undone”, so a wrong merge is fixed by hand, transaction by transaction.

Before merging a pair that a sync created, check why there are two. If the second record exists because a source system spells the name differently, merging cleans up the past and changes nothing about the next transaction, which will arrive with the same spelling.

One currency per customer, and the suffix it creates

With multicurrency switched on, QuickBooks lets you assign a single currency to each customer. Intuit’s note is that you can assign a single currency to most types of accounts, “including customers”. A customer you invoice in USD cannot also be invoiced in CAD on the same record.

Intuit’s own answer is a second customer record in the second currency, and the uniqueness rule then forces a second display name. Intuit’s instructions for that new record include the step “Add a currency to their display name, then select Save.”

So a customer list with Acme Inc and Acme Inc - CAD in it is not a duplicate to clean up. It is QuickBooks requiring one record per currency, and merging the two would undo the reason they exist.

How Acodei uses the display name

Acodei matches on it. When a Stripe transaction needs a customer, Acodei takes the name from the Name field on the Stripe Customer object, or the billing name on the charge if that is empty, and looks for a QuickBooks customer whose display name matches. The match is case-insensitive, so ACME INC finds Acme Inc, but otherwise it must be character for character identical. Acme, Inc. in Stripe will not find Acme Inc in QuickBooks, and when there is no match Acodei creates a new customer.

Once a Stripe customer is linked, Acodei holds the link by the QuickBooks customer id rather than by the name. Renaming the customer in QuickBooks keeps the link, and later transactions keep posting to the renamed record. Changing the name on the Stripe side does the opposite: the new name finds no match, and Acodei creates a new QuickBooks customer. Acodei also does not update a customer after it creates or matches one, so a name you correct in QuickBooks stays corrected.

Two naming rules come from QuickBooks itself. If a vendor already has the display name, Acodei creates the customer with -C added to the end, for example Acme Inc-C. And with Multicurrency Support, which the Acodei team enables on request, a transaction in a currency other than the existing customer’s produces a record named with the currency code, for example Acme - CAD. That is designed behavior, because QuickBooks fixes one currency per customer.

When a Stripe customer has no name at all, the Customer Management settings decide: create the customer from the email address, use a default name you choose, or leave the name empty, which results in an Unnamed Customer record or a sync failure. Acodei does not read names from Stripe metadata, and there is no manual control for pairing a specific Stripe customer with a specific QuickBooks customer. If a name was wrong, fix it, then resync the affected transactions from the Data Feed.

Want to see this on your own Stripe data?

Start a free trial

14-day free trial · card required · cancel anytime

Frequently asked questions

What is the display name on a QuickBooks customer?

It is the required name field on a QuickBooks Online customer record, and the name QuickBooks uses everywhere the customer appears: the customer list, transaction dropdowns, reports and the customer line of invoices and sales receipts. Other name fields such as first name or company name are optional, but the display name must be filled in.

Why does QuickBooks say another customer, supplier, or employee is already using this name?

Because display names must be unique across customers, suppliers and employees together, not just within the customer list. A supplier called Acme Inc blocks a customer called Acme Inc. Intuit suggests finding the existing record and renaming it, for example by adding a middle initial or a number, or making it inactive if it is no longer used.

Can two QuickBooks customers have almost the same name?

Yes. The uniqueness rule only blocks identical names, so Acme Inc and Acme, Inc. can both exist. That is how near-duplicate customers build up, and it splits one relationship across reports such as Sales by Customer and the receivables ageing. A naming convention applied by every system that creates customers is the way to stop it.

How do I merge two customers in QuickBooks Online?

Open the customer you do not want to keep, choose Merge contacts, and change its display name to exactly match the customer you are keeping. QuickBooks asks you to confirm, then combines the two. Intuit warns that neither customer can have sub-customers or linked projects, and that the merge is permanent and cannot be undone.

Why did a Stripe sync create a second customer with almost the same name?

With Acodei, a Stripe customer is matched to a QuickBooks customer on the display name, case-insensitive but otherwise exact. If the spelling differs by a comma, a period or a space, there is no match and Acodei creates a new customer. Fix the name on one side so the two match, then resync the affected transactions from the Data Feed.

Why does a synced customer end in -C?

Because a vendor in the same QuickBooks company already uses that display name, and QuickBooks does not allow a customer and a vendor to share one. Acodei creates the customer with -C added to the end, such as Acme Inc-C, so the customer can exist alongside the vendor.

What customers say about running Stripe through Acodei

Stripe Verified Partner BadgeIntuit QuickBooks
★★★★★
“If you're testing out all the different Stripe/QuickBooks integration apps right now, let me save you some time. This one is the best one by far.”
RyanOwner at Indie Music Academy
★★★★★
“Works well and is really helpful for massive transactions. The support is really fast and helpful. 100% recommended.”
AndresCo-founder and CEO at Kanguro Collections and Reinsurance

Related reading

More glossary terms

See the full glossary

Ready to try Acodei?

Connect Stripe to QuickBooks Online in minutes and let the fees, refunds, and payouts land where your accountant expects them.

14-day free trial · card required · cancel anytime