Last reviewed: 10 October 2026. Product details reflect this review date. Availability and behavior can vary by account, role and release.
Editorial ink illustration: A sequence links a customer choice, warehouse handling and a financial record.
A customer calls to correct an address. You find the customer in NetSuite, notice a different address on an invoice, and wonder which one to change. The answer starts with the purpose of each record and the business event it describes.
NetSuite keeps information in connected records. A customer record describes a business relationship. A contact identifies a person. A sales order describes an order commitment. An invoice records a billing event. Those records can refer to the same customer while answering different questions.
This lesson shows how to trace those relationships before editing anything. The goal is practical: find the right object, identify the field that needs attention, and explain what should change. You can complete the first exercise by reading records in an authorized training account. There is no need to experiment on live customer data.
When someone says “the customer is wrong,” ask what they mean. Is the organization name incorrect? Has the contact left? Is a delivery going to the wrong place? Is a particular invoice addressed incorrectly? Those are separate issues with potentially different owners.
Use a sentence that connects the question to the evidence:
The last two questions matter because an invoice’s original amount and its remaining balance can differ. Likewise, an order quantity and a shipped quantity describe different stages of work. A familiar customer name does not make every number on related records interchangeable.
A list gives you a way to find and work with records. It is not an additional master database that needs its own duplicate customer entry. A search result, a list row, and a linked customer name can all lead to the same underlying customer record.
Treat the list as your starting view. Its columns may show only part of the information you need, and its filters may exclude relevant records. Open the record before concluding that a field is missing or an organization has no history. Check the record type and identifier as well as the display name.
For example, two results called Cedar Works could represent different legal entities, a duplicate that needs review, or different record types. The name alone cannot decide which explanation is correct. Ask your data owner what identifies a unique customer in your business. That might involve a combination of organization details and a controlled reference, rather than a name comparison alone.
Imagine Cedar Works buys installation services. Mara is the person coordinating the purchase. A salesperson records the agreed work on a sales order, and the billing team later creates an invoice associated with the order.
This is a teaching example, not a customer case study. The important relationships are:
Now suppose Mara asks for an invoice explanation. Opening only her contact record will not tell you which service lines were billed. Opening only the invoice will not establish that she is still the right person to receive future commercial correspondence. You may need both, but for different reasons.
Write a short record map before making changes. Include the record type, its identifier, the question it answers, and the connection you verified. This can be a training worksheet; it does not require a new custom record or a change to NetSuite.
Transactions capture events such as ordering, billing, and receiving payment. Some transaction types post to the general ledger; others are non-posting. A sales order is a non-posting commitment. Creating it does not, by itself, recognize revenue.
This distinction helps you avoid a common diagnostic error. If a customer appears on an order, that proves an order record exists. It does not establish that the goods shipped, the customer was billed, payment arrived, or revenue was recognized. Those conclusions need their own evidence.
Before using a transaction to answer a finance question, identify the transaction type, its status, the relevant dates, and the measure you are reading. Where accounting impact matters, ask an authorized finance user to review the applicable posting evidence. Do not infer accounting treatment from a document’s appearance or from an informal label such as “sale.”
For a deeper look at the order itself, continue with ordered, fulfilled, and billed quantities. That lesson separates three progress measures that are often compressed into one conversation.
Return to the address example. Cedar Works has moved its office, but last month’s invoice accurately shows the address used when it was issued. The team should decide whether the request concerns future correspondence, one open order, a billing document, or several of those things.
Do not assume that editing the customer record rewrites all earlier transactions. Equally, do not assume every transaction field always remains independent of the customer record. Field sourcing, transaction state, customizations, and the particular field can affect behavior. Check the actual record and test the relevant behavior in a permitted environment.
A useful correction request contains four parts: the existing value, the requested value, the records in scope, and the reason. “Use the new address for future orders” is more actionable than “fix Cedar Works everywhere.” It also gives the reviewer a way to distinguish an intended update from an unintended historical change.
For bulk corrections, use CSV import validation and recovery after the record-level decision is clear. A larger import should carry out a sound mapping decision, rather than make that decision for the team.
Record access depends on assigned roles and permissions. A user may be able to view a record without being able to create, edit, or delete records of that type. Missing visibility can therefore reflect access restrictions, list filters, or a different account context. It does not automatically mean the data was deleted.
When you cannot find a related record, capture the account context, your active role, the record type, and the identifier you expected to find. Give that bounded question to the record owner or administrator. Avoid asking for broad administrator access merely to finish a lookup.
The roles and permissions access review guide explains how to review access around real tasks. When several teams repeatedly disagree about who should maintain a field, CuriousRubik’s NetSuite administration services can help clarify responsibility and controlled changes.
A correction is ready for review when the intended record and field show the expected value, the related process still works, and the boundaries of the change are understood. A successful save alone cannot establish all three.
For a permitted training exercise, compare the record before and after a small approved change. Then revisit one related record that should change, if applicable, and one historical record whose behavior you specifically want to understand. Record what you observed without generalizing to every field or transaction type.
If the expected value did not appear, investigate the field’s source, the record’s state, your permissions, and relevant customizations. If it appeared somewhere unexpected, pause the broader change. Preserve the example and ask the owner to review the relationship. Repeating the update across more records can make the cause harder to isolate.
Change history can help establish what happened. The System Notes lesson explains how to interpret that evidence without treating a change log as proof of business approval.
Choose one fictitious customer in an authorized training account. Find its contact, one sales order, and one associated invoice if your training data includes them. Stay in read-only review unless a separate exercise has been approved.
For each record, finish the sentence “I would open this when I need to know…” Then explain one thing it cannot establish by itself. For the order, you might write that it establishes the recorded commitment but needs fulfillment evidence to establish shipment.
Before you finish, check:
This habit makes everyday work more reliable. You can explain what the data means before deciding how to change it, and the next person can follow the same evidence.