Supplier return authorization system map: how the RMA number joins ERP, carrier, portal and AP records

Short answer

The RMA number is the spine of a supplier return. To reconstruct a return across business systems, every other record has to carry it or a field that leads back to it: the ERP return order, the carrier shipment, the supplier's inspection report, the credit memo and the accounts payable match. Where a record carries a lot number, a packing slip number or only a supplier email thread instead, that join has to be named, because it is where reconstruction slows or fails.

Visual briefFull-size diagram
A hub-and-spoke map with return authorization number RA-5521 at the center and four system nodes around it (ERP return order, carrier shipment, supplier inspection, AP match); spokes draw out in turn, and the inspection link is orange because it also relies on a lot number.
Illustrative: the authorization, order and lot numbers are invented to show how one return joins.

This system map is part of the supplier return authorization guide. It sets out which system holds each record, the key that links it, who owns it, and what one fully joined return looks like.

Five systems around one number

A supplier return touches more systems than most finance teams expect:

  • ERP: the return order or vendor return authorization, with the RMA number and negative quantities.
  • Warehouse and carrier systems: the pick, the packing slip and the tracking number for units that left.
  • Supplier portal or supplier email: the RMA as issued, the inspection report and any dispute.
  • Supplier credit memos: issued on the supplier's side, then received into the ERP.
  • Accounts payable: the match of credits and any write-off against the original return.

ERP vendors model the first step in similar ways. In Dynamics 365 Supply Chain Management, a Returned order purchase order requires the vendor's RMA number and carries negative line quantities, according to Microsoft. In NetSuite with Advanced Shipping, a vendor return authorization moves from Pending Approval to Pending Return to Pending Credit, according to Oracle's help. Either way, the RMA enters the ERP at the start, and the question is whether it survives to the end.

The system map

SystemRecordLinking keyJoins toOwnerTypical gap
ERPReturn request or vendor return authorizationRMA number, return order numberShipment, credit memoMerchandise operationsRMA typed into a note field, not the RMA field
Warehouse or carrierPacking slip and trackingReturn order number, tracking numberSupplier receiptDistribution center leadTracking kept only in the carrier portal
Supplier portalRMA as issuedRMA numberInspection reportSupplier, viewed by buyerAccess ends when the account changes
Supplier portal or emailInspection report with accepted and rejected unitsAuthorization number, or lot or serial rangeCredit memo, disputeSupplier, received by buyerReasons only in email
Buyer mailboxDispute correspondenceAuthorization number quoted in subject, if at allSecond credit memoCategory managerThread stays with the person
Supplier side, then ERPCredit memoRMA or original order numberAP matchFinanceMemo cites the order, not the RMA
ERPWrite-off approvalRMA, reason codeAP matchFinance controllerNo reason code
ERPAP matchRMA total versus credits plus write-offClosed returnAccounts payableMatched by amount only

One fully joined return (Illustrative)

A fictional 380-person sporting goods retailer returns 200 bicycle helmets with faulty buckles. Every number below is invented.

StepSystemKey recordedUnits
Return approvedERPRA-5521 on return order RO-3307200
Shipped to supplierCarrierRO-3307, tracking number200
InspectedSupplier portalRA-5521, lot L-0914170 accepted, 30 rejected
First creditSupplier credit memoRA-5521170
Dispute on 30 unitsBuyer emailSubject quotes RA-552130
Second credit after disputeSupplier credit memoRA-552110
Write-off of the restERPRA-5521, reason code "supplier rejected, evidence insufficient"20
Closed in APERPRA-5521: 180 credited plus 20 written off equals 200200

Walk the chain backward from the AP match and every step returns to RA-5521. The inspection report is the only record that also needs a lot number, because the supplier inspected by lot. That is fine as long as someone wrote down that the lot belongs to this RMA.

SAP's documentation shows why the credit memo step matters. On SAP Business Network, a supplier creates a credit memo for return items from the order, can adjust the price to the actual return value if items were damaged, and cannot credit more than the return quantity. A partial or reduced credit is where a split decision shows up in money; the inspection report and any dispute thread explain it.

Where the chain usually breaks

Three breaks come up again and again, and each is worth one question to whoever runs returns day to day.

  1. Inspection to credit. The supplier's inspection reasons sit on its portal or in email and never reach the ERP. Ask whether inspection reports are attached to the return order or only viewed on the supplier side.
  2. Dispute to second credit. The pushback is an email thread with no case number. Ask whether buyers quote the authorization number in subject lines, or whether disputes are tracked anywhere.
  3. Credit to AP match. Credits are matched to the original purchase order rather than the RMA, so a return closes on amount alone. Ask whether AP matches against the RMA total.

Where a link is missing, say so plainly in the inventory: "inspection reasons held only in supplier emails" is useful information, not a failure. Records held on a supplier's portal also raise a control question; the preservation timeline covers what a renegotiation can change. For describing the ERP without exporting from it, use the metadata-only NetSuite inventory template.

Qualification and what stays unknown

The introduced company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license 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: whether records held on supplier portals can be included, which years and return types a buyer would want, and whether an offer follows. Who should receive the introduction is set out in who can license supplier return records. Related histories include warranty claims data and distributors in specialty distribution. If the company you know is the supplier, read whether you can refer a supplier your company buys from.

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 follow most returns from RMA to AP match by the RMA number alone, register as a partner, check the company against who qualifies and read the program terms before introducing its merchandise operations director.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardYour 25% of the actual supplier payout. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

What if the supplier's inspection report never mentions the RMA?

Record the join it does use, such as a lot or serial range, and say so in the inventory. A weaker join is still a join; what matters is that someone can explain how the report was matched to the return.

Do partners need ERP access to build this map?

No. The merchandise operations director and an AP lead can describe each system and key in a short call. The partner writes down the answers and never opens the systems.

Sources

  1. learn.microsoft.com/en-us/dynamics365/supply-chain/procurement/p…
  2. docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/sectio…
  3. help.sap.com/docs/business-network-for-trading-partners/c…
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 90% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment