QuickBooks Online Users Puzzled by Customer Notes That Reach Invoices

A question that keeps returning to QuickBooks Online communities is deceptively small: how do you add and use notes on a customer? The accepted answer matters more than the question suggests. A customer profile holds two different note types. Only one of them stays between you and your books. The other travels with the invoice, and that single difference sits behind most of the confusion.

The accepted answer comes from the vendor’s own guidance and walks through both types step by step. We have condensed it here, with the visibility rules pulled to the front, because those rules are the part that prevents surprises.

Two note types, two destinations

The first type is the simple note. It appears on the customer profile page and, just as important, on the invoices you send to that customer. The field accepts up to 4000 characters, which is roomy for a billing message and tight for a full account history.

The second type is the date-stamped note. Each entry carries its own time and date, entries stack in the order you add them, and they appear only on the profile page. Nothing in this bucket reaches an invoice. It is the right home for call summaries, payment promises, disputes, and anything else meant for internal eyes.

The two types are not labeled by audience, though. Nothing on screen says that one prints and the other does not, which is exactly where users get caught.

The notes field is not in plain sight

Part of the difficulty is finding the field at all. In the current layout, the simple note sits behind a dropdown inside the customer edit panel.

The path runs like this. Open the apps menu and go to the Customer Center. Choose the customers and leads area and select the customer; if the customer is not on the list yet, add them first. Edit the profile, and the panel that appears includes a notes and attachments section. Expand it, type the text, attach a file if it helps, and save. Attachments added this way can be removed later when they stop being useful.

The timestamped notes live in their own tab

On the same customer, switch to the notes tab and use the add-note button. Write the entry and post it, and the note keeps its timestamp from then on. The order is fixed by posting time, so the tab reads like a log. You can star the entries that matter most, and starred notes stay easier to reach as the history grows.

Edits and deletions behave differently

Simple notes are revised in the same panel where they were created: open it, update the text, and save. Timestamped notes are handled one at a time. Open the note, choose edit, make the change, and post it again. Deleting asks for a confirmation, and once you confirm, the note is gone. Treat the delete step as final.

Which note belongs on an invoice?

The answer is a habit, not a setting. Treat the simple note as public space: payment instructions, thank-you lines, delivery windows. That field prints, so everything in it should be fit for the customer to read. Treat the timestamped note as the internal record: collections history, credit conversations, service disputes. That field stays on the profile.

Nothing in the workflow flags the difference at the moment you send. The invoice simply carries whatever the simple note holds. Users who learned this the hard way tend to move everything internal into the timestamped tab and keep the simple note short, polite, and customer-ready.

The character ceiling deserves a mention. At 4000 characters, a simple note can hold a real message, but it is not a customer relationship tool. Long histories belong in the timestamped tab, where entries stack instead of competing for a single field.

Our read

This is a labeling problem more than a bug. Two fields with similar names serve different audiences, and the interface never says so plainly. Until that changes, the safe rule costs nothing: write every simple note as if the customer will read it, because sooner or later one will.