Close a vendor return only after you can explain the goods movement, vendor credit and final recovery of value. A shipment back to the supplier, an approved return authorization and an applied credit are separate events. Reconcile their quantities, amounts and dates so a returned item does not become a forgotten supplier claim.
This guide covers the return-to-credit control chain. It is distinct from customer returns and vendor prepayments. The exact transaction behavior depends on account features and item configuration, so test the intended flow and have finance approve inventory, tax and period effects.
Before shipping, establish why the goods are being returned and what the supplier has accepted. Record the supplier's authorization, eligible items and quantities, expected credit, freight responsibility and any restocking charge.
A replacement shipment, a credit against future purchases and a cash refund are different outcomes. Identify which one is expected and who will pursue it. If the supplier has not agreed the amount, retain the estimate separately from the approved credit expectation.
Link the case to the original purchase order, receipt and bill. Include serial or lot evidence where relevant. The reviewer should be able to establish both what left your custody and which commercial obligation should change.
Oracle's Crediting an Authorized Vendor Return explains that a vendor credit records value owed for returned items. It also describes a feature-dependent sequence: with Advanced Shipping, a bill credit can precede shipment; without it, returning and crediting occur together.
That distinction prevents a misleading completion rule. A credit record does not always prove that goods have shipped, and shipping status does not always prove that the vendor credit exists.
Document the account's selected flow and the responsible person at each step. If an integration or warehouse system creates the shipment, identify how its confirmation reaches the return case and how missing confirmations are detected.
Use one case identifier with linked return authorization, shipment or fulfillment, vendor credit, application and refund references. Store expected and actual quantity, expected and actual credit, currency and the date of each event.
Add supplier contact, internal owner, next action and due date. Distinguish awaiting supplier approval, awaiting shipment, shipped awaiting credit, credit disputed, credit available and recovery complete.
These are recommended operational states, not a claim that a standard NetSuite status list contains each label. Implement them through an appropriate report, custom record or case process after verifying the available fields and permissions.
Compare approved return quantity with actual shipment evidence. For partial shipments, preserve the remaining authorized quantity and the reason it has not left. A case should not be marked complete because the first carton shipped.
Check item identity and unit of measure. A vendor authorization expressed in cases can differ from a warehouse record expressed in units. Retain the conversion and verify that both commercial and inventory quantities are correct.
Investigate shortages, rejected items and damaged returns separately. The supplier may accept fewer items than were shipped. Operations supplies the physical evidence, while procurement negotiates the commercial outcome and finance approves the resulting transaction treatment.
A distributor returns 40 units with an expected credit of 3,200. Its shipping evidence shows all 40 units left the warehouse. The supplier issues a credit for 2,960 after deducting a 240 restocking fee that purchasing had not approved.
The case now has a quantity conclusion and a value dispute. The return shipment may be complete, but the 240 difference requires a commercial decision. Finance should not silently reduce the expected credit solely to make the register agree.
If the fee is accepted, retain approval and the accounting treatment. If it is disputed, keep a dated supplier follow-up and show the outstanding claim. This hypothetical example demonstrates why shipment completion and financial recovery need separate statuses.
Before application, verify supplier, subsidiary, currency and the bills to which the credit may be applied. Retain the supplier statement or remittance agreement where it supports the allocation.
A credit can be genuine but applied to an unintended bill, causing an avoidable payment dispute. Make the application evidence visible to the person preparing the next payment run. The payment selection should reflect the approved credit position.
If the supplier will refund cash, follow the documented association and bank-receipt process appropriate to the account. Oracle's vendor-return guidance points to associating a vendor credit with a deposit for a cash or check refund. Test the full chain with finance rather than treating the credit as settled when it is merely available.
A return can cross month-end between authorization, shipment, supplier acceptance and credit receipt. Preserve the dates and evidence for each event so finance can determine the appropriate period treatment.
Do not backdate a credit simply to remove an aged item from the report. Obtain the approved accounting decision, especially when the original receipt, bill or variance posting belongs to a closed period.
Review the interaction with Accrued Purchases and inventory accounts using actual transaction GL impacts. Different item types, feature settings and return sequences can change the path. This article does not prescribe a universal journal entry for every return.
Create an aged view of shipped returns without credits, issued credits without application and promised cash refunds without bank evidence. These are different queues with different owners.
For each case, retain the supplier's latest response and the next escalation date. A generic “waiting on vendor” note should include what the vendor owes: confirmation of receipt, acceptance of quantity, a credit document or payment.
Review repeated disputes by supplier and reason. Frequent restocking charges or missing return references may indicate a purchasing-policy problem rather than an accounting-system defect. Feed that evidence back to procurement before the next order.
Use cases for a full return, partial shipment, partial credit, disputed charge, replacement outcome and cash refund. Include the Advanced Shipping configuration actually in use and a cross-period example.
Check that a reviewer can trace the original receipt through final settlement. Confirm that reopening a case or correcting a credit does not lose the earlier supplier agreement. These are proposed acceptance tests, with no customer-account execution claimed.
For return reports and transaction relationships, CuriousRubik's NetSuite support services can help identify where the operational or accounting chain stops.
Not always. Oracle documents a sequence with Advanced Shipping in which credit can precede shipment. Check the physical shipment evidence separately.
When the approved value has been recovered through an intended bill application, refund or other authorized outcome, and any difference is explained and approved.
Keep the expected credit and actual credit visible, then route the difference to the commercial owner. Finance should approve the eventual accounting treatment.
Use the permitted application and approved allocation. Verify entity, currency and bill references before releasing the payment run.
Include shipped returns without credits, disputed credit amounts, unused credits and refunds awaiting bank evidence. Each needs a named owner and next action.