# Supplier return authorization records | SourceX

Canonical: https://refer.sourcex.si/guides/workflow-supplier-return-authorization
Last updated: 2026-10-18

The records that explain a supplier return authorization exception are the return request and RMA number, the return shipment, the supplier's inspection notes with accepted and rejected quantities, the buyer's appeal or dispute, any write-off approval, and the credit memos matched in accounts payable. Together they follow a return from request to settled credit, including the part the supplier refused. A retail finance advisor should confirm these exist at metadata level and introduce the merchandise operations director.

## When does a supplier return become an exception?

A fully accepted return is routine. ERP systems model it as a short sequence. In NetSuite with Advanced Shipping, a vendor return authorization moves from Pending Approval to Pending Return (approved, awaiting shipment to the vendor) to Pending Credit (all items shipped, credit still to be created). In Dynamics 365 Supply Chain Management, a Returned order purchase order requires the vendor's RMA number and carries negative line quantities. On SAP Business Network, a supplier creates a credit memo from the order's return items, can adjust the price to the actual return value if items were damaged, and cannot credit more than the return quantity.

Those rules describe the happy path and its limits. The exception is a split decision: the supplier inspects the units and accepts some, rejects others, or credits less than full value. The system then shows a credit smaller than the return, and only the inspection notes, the correspondence and the internal approvals explain the difference. A split decision shows how a company argues its case, decides when to stop, and closes the books.

## Worked example: 120 lamps, three outcomes

Illustrative only. A 520-person home goods retailer returns 120 table lamps with a wiring defect, bought at $35 a unit, and requests $4,200 of credit.

| Stage | Units | Value | Record that proves it | Held by |
|---|---|---|---|---|
| Return requested, RMA issued | 120 | $4,200 | Return request and RMA number | ERP and supplier portal |
| Supplier inspection: accepted | 84 | $2,940 | Inspection report, first credit memo | Supplier portal |
| Supplier inspection: rejected as customer damage | 36 | $1,260 | Inspection report with reason | Supplier portal |
| Retailer appeal with store photos: accepted | 12 | $420 | Appeal email, second credit memo | Email and supplier portal |
| Written off after review | 24 | $840 | Write-off approval with reason | ERP |
| Settled in accounts payable | 120 | $4,200 | Credits of $3,360 plus $840 write-off, matched to the RMA | ERP |

The authorized action is the decision in rows four and five: the merchandise operations director approved appealing 12 units with evidence and writing off the other 24. The checked result is the last row, where accounts payable matched both credit memos and the write-off to the original RMA so the return closed at zero variance. That chain, from problem through judgment to a reconciled outcome, is the kind of operational history SourceX reviews when a company considers licensing data for AI training and evaluation; whether a given company's returns are selected is decided only in that review.

## What each record adds to the story

Map return requests, inspection notes and credit receipts to what they prove. Remove any one and part of the case can no longer be explained.

- **Return request and RMA:** the claim as made, with units, value and reason. Without it, the credits have nothing to reconcile against.
- **Inspection notes:** the supplier's unit-level decision and its reason. Without them, a reader sees a short credit and cannot tell whether it was a dispute, a pricing adjustment or an error.
- **Appeal correspondence:** the evidence the buyer offered and the supplier's response. This is where judgment shows.
- **Write-off approval:** who decided to stop arguing, for how much, and why.
- **Credit memos and the accounts payable match:** proof that the books closed and the return reached zero variance.

The [logistics exceptions guide](/guides/how-to-identify-logistics-exceptions-and-their-documented-resolutions) uses the same problem, action and result test for shipments, and the [procurement exceptions guide](/guides/how-to-assess-procurement-approvals-and-exception-workflows) covers the approval side.

## Questions for the merchandise operations director

Keep discovery at metadata level: what exists, how much, how long, which system and who owns it.

- Roughly how many supplier returns a year, and what share end in a partial credit?
- Are supplier inspection reports stored in the ERP, or only on supplier portals?
- Are appeals tracked as cases, or handled in buyer email?
- Do write-offs carry a reason code and an approver?
- How many years of RMAs and matched credits does the ERP hold?
- Who could authorize a discussion about licensing these records?

The [metadata-only NetSuite inventory template](/resources/a-metadata-only-netsuite-inventory-template-for-company-introductions) shows how to describe an ERP without exporting from it.

## Does the company qualify, and what stays unknown?

The company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the data is in English.

Unknown until SourceX reviews the opportunity with the company: current buyer interest in return records, whether records held on supplier portals can be included (see [why data rights matter](/proof/why-data-rights-matter)), which records would be selected, and any offer. Related record types are covered under [procurement and vendor workflows](/data-types/procurement-and-vendor-workflows) and [supplier expediting](/data-types/supplier-expediting-process); distributors held by investors are covered in [specialty distribution](/industries/specialty-distribution-private-equity), and the [industries hub](/industries) lists more.

## Go deeper on supplier return authorization

- [Supplier return records across systems](/guides/supplier-return-authorization-records-across-systems): a field map joining RMAs, inspection reports and credit memos.
- [Who can license supplier return records](/questions/who-can-license-supplier-return-authorization-records): a short answer on which decision-maker to introduce.
- [Preserving return history before a supplier renegotiation](/guides/preserve-supplier-return-authorization-records): an inventory checklist for portal and contact changes.
- [Supplier return authorization referral brief template](/resources/supplier-return-authorization-referral-brief-template): a fill-in template for the introduction.

## Next step

> **Refer a company. Earn up to $100,000.** Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a retailer or distributor can trace its split return decisions from RMA to matched credit, [register as a partner](/register), check the company against [who qualifies](/who-qualifies), and read the [terms](/terms) before you introduce the merchandise operations director.

## Sources

- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N2387708.html
- https://learn.microsoft.com/en-us/dynamics365/supply-chain/procurement/purchase-order-overview
- https://help.sap.com/docs/business-network-for-trading-partners/creating-and-managing-invoices-credit-memos-and-debit-memos/93c8bb94b2eb4317ba270bb6a12d0919.html
- https://refer.sourcex.si/terms