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 returns coordinator compares an item, its box and the related records.
“The return is done” can mean several different things. Customer service may mean it was approved. The warehouse may mean a box arrived. Finance may mean a credit memo was created. The customer may mean money reached their account. Those statements describe different events.
NetSuite customer-return processing connects those events through related records, but the records still need to be interpreted separately. A return authorization does not establish physical receipt, and a credit memo does not establish a cash refund.
This lesson helps customer-service, warehouse, and finance teams trace one return without losing those distinctions. Processing depends on enabled features, preferences, permissions, and the original sale. Use an approved test environment for practice and keep live payment details outside the exercise.
Identify the customer, the original sale, the item, the quantity sold, and the quantity the customer wants to return. Add the reason for the request and the remedy the customer is seeking. A replacement, an account credit, and money back create different follow-up questions.
Linking the return to the original sale, where the process supports it, helps preserve the relationship to the sold items, quantities, and prices. Still verify that the proposed return is correct. A copied line can carry useful context without proving that the customer's request has been approved.
Keep the scope precise. If a customer bought ten units and asks to return two, the request concerns two units. A reference to the original order does not mean all ten should be received, credited, or refunded.
For the sale-side record relationships, continue with sales orders, fulfillment, and invoices. Understanding the original transaction makes the return easier to trace.
A return authorization records the proposed return and its processing information. Depending on the configuration, it can pass through an approval process before later work proceeds.
The authorization gives the receiving team something to match against an incoming shipment and gives finance a reference for the financial remedy. It helps the teams work from the same return rather than separate messages that may describe different quantities.
However, authorization is still an instruction or approved expectation. It does not prove that the customer has shipped the goods or that your warehouse has received them. Record the authorized quantity and the received quantity separately.
Also avoid treating an authorization's overall status as the whole explanation. A multi-line or partial return can have different progress across items. Inspect the lines and related records when answering a specific question.
Receiving means matching the shipment with the authorized return and recording the items and quantities that arrived. With Advanced Receiving, an authorized return can be received in parts through item receipts.
The record should reflect the shipment, not the quantity the team hoped would arrive. If only one of two authorized units is in the box, receiving both creates an inaccurate starting point for stock and finance.
Confirm the item identity, quantity, relevant location, and condition using the organization's receiving controls. Where serial, lot, bin, or other inventory details apply, the configured process may require additional information. Do not replace those checks with the customer's description alone.
Receipt evidence is useful beyond the warehouse. It explains whether a missing financial step is waiting for goods, whether another shipment is expected, and whether the customer-service team should investigate the outstanding unit.
A returned item may be fit for resale, damaged, incomplete, or subject to inspection. Physical arrival does not automatically establish that it belongs in available stock.
In the applicable Advanced Receiving return process, restock treatment determines whether the returned inventory item increases inventory or is written off. Preferences can supply defaults, but the team still needs to use the approved treatment for the item and its condition.
For example, a damaged unit may arrive and be correctly recorded as received while not increasing saleable inventory. A customer-service user looking only at the receipt could otherwise conclude that stock should have risen.
Have the inventory and finance owners agree the disposition and accounting treatment. Do not change a restock setting simply to make a quantity report match an expectation. First check whether the expectation includes received-but-written-off or otherwise unavailable goods.
A customer credit memo decreases what the customer owes. It can be applied to an open invoice or, where appropriate, retained for a future invoice. A customer refund records money paid back to the customer.
If an invoice is still open, an approved credit may reduce its remaining balance. If the invoice was already paid, the team must determine the approved treatment of the resulting credit or refund. That decision depends on the transaction history and the company's process.
Do not assume every return must produce both a new credit and a separate refund in the same way. The original sale and chosen return route matter. Creating extra transactions to make a checklist look complete can duplicate the remedy.
Inventory treatment also depends on the record's origin. A credit memo created from a return authorization has no inventory impact of its own, while a stand-alone credit memo can affect inventory. This is another reason to trace the related records rather than choosing a transaction type by its name alone.
For how applied credits affect an open invoice, see customer payments and invoice balances. Keep the amount credited and the amount refunded separate when explaining the outcome to the customer.
Suppose a fictional customer bought ten units from Alder Ridge Equipment and is authorized to return two. The company uses an approved process with Advanced Receiving and ordinarily waits for receipt before providing the financial remedy. This is an illustrative configuration, not a universal NetSuite sequence.
Customer service confirms that the authorization covers two units from the original sale. The warehouse receives a shipment containing one unit. The second unit is not in the shipment, and the team has not yet established whether it is still with the customer or in transit.
The receiving record should establish one unit received. The outstanding physical quantity remains one. The team inspects the arrived item and records the approved stock disposition. If the item is not suitable for restocking, the financial and inventory consequences are reviewed accordingly.
Finance then checks which remedy is approved for the received unit under this process. It inspects the original invoice and any existing credit or refund before creating another transaction. The authorization for two units is not treated as proof that both should already have been financially settled.
At this point, a useful status explanation is: “Two units are authorized. One is recorded as received. The arrived unit's disposition has been reviewed. The financial remedy and the outstanding unit each have a named next step.”
That explanation is more precise than “half complete.” The physical quantity is halfway through receipt, but financial progress may not be proportional. A credit could be awaiting approval, already applied, or handled through a different approved route.
When the second unit arrives, the team records its own receipt evidence and reviews the remaining remedy. If it will not arrive, the owner investigates and resolves the outstanding authorization line through the approved process. Closing a line should communicate a decision, not hide an unexplained quantity.
NetSuite return preferences can allow a credit or refund before the item is received. An organization using that setting has a different permitted sequence from the receipt-first example.
This changes timing, not the meaning of the events. An advance refund still does not prove receipt. If money is returned before the goods arrive, the outstanding physical return needs to remain visible and owned.
When reviewing a return, ask which preference and business policy apply. Do not describe every refund-before-receipt as an error, and do not assume the preference authorizes every individual refund. System capability and business approval are separate checks.
A trainer should state the example's configuration before demonstrating the process. Otherwise, learners from two accounts can follow different valid sequences and conclude that one of them is wrong.
Use the return authorization as a starting point, then trace the actual receipts and financial records. For each relevant line, confirm the authorized quantity, received quantity, and unresolved quantity. Check the item disposition rather than inferring it from arrival.
For finance, identify the credit or refund record and what it did. Was a credit applied to an invoice? Is an amount still available? If a refund was recorded, what evidence establishes its processing state? A saved refund record alone should not be used to promise that funds have reached the customer.
Also check whether tax, shipping, restocking charges, currency effects, or other adjustments affect the remedy. The two-unit example deliberately avoids calculating those amounts. Finance should verify the applicable treatment instead of multiplying the original unit price by the received quantity without review.
Use a common reference when handing work between teams. The original sale, return authorization, item receipt, and financial record identifiers let the next person inspect the same event without relying on a copied status description.
If the authorization remains open, inspect the outstanding lines and receipts. A completed receipt for one line may coexist with another line still awaiting goods or an approved closure.
If a credit exists but the customer says no money arrived, first determine whether the agreed remedy was an account credit or a refund. Then inspect the relevant processing evidence. Do not issue a second remedy just because the first record is unfamiliar to the customer-service team.
If inventory differs from the received quantity, inspect restock treatment, item type, location, and the related transaction route. The difference may have a valid explanation that a top-level status cannot show.
If the next action is unavailable, have the administrator check the role, feature setup, preferences, and transaction state. Avoid granting broad permissions simply to force a return through.
A return is understandable when each event has its own evidence. Keep the goods and financial remedy connected, while preserving the distinction between permission, arrival, account credit, and money returned.
For help improving the handoffs around returns, explore CuriousRubik's NetSuite optimization services.