In the invoicing and reconciliation article I followed a delivery forward: one shipment, two invoices, and a period end where both companies have to agree. Today I want to run the same chain backwards. Goods come back, or a credit is owed without anything coming back, and the question is how to make that correction land in both legal entities at once, at the right value, without anyone keying a manual journal at month end. Returns are a small share of intercompany volume and, in my experience, a large share of intercompany reconciliation differences, almost always because the two sides corrected the same event in two different ways.
TWO SHAPES OF INTERCOMPANY RETURN
There are two situations, and it helps to name them before touching any setup.
• The simple return. The buying company holds stock it purchased from the selling company and sends it back: wrong item, quality problem, overstock agreed to be taken back. Two entities, no external party.
• The direct delivery return. The sales company sold to an external customer, the goods shipped straight from the source company (the pattern I described in the order chain article), and now the customer wants to return them. Three documents are involved, and the goods usually should travel back to where they came from, not to a sales company that may not even run a warehouse.
Both rest on the same mechanism: a return document in one company generates its mirror image in the other, exactly as a forward order does.
THE SIMPLE RETURN: A MIRRORED PAIR
In the buying company, the vendor return is a purchase order of type Returned order with negative quantities. In the selling company, the customer return is a return order carrying an RMA number. For an intercompany vendor and customer pair, creating either one generates the other. I prefer to start in the buying company, because that is where the decision to send goods back is actually made, but starting from the selling company's return order works just as well when the seller is recalling stock.
Three details matter more than the rest.
• The RMA number belongs to the selling company. A vendor return normally needs an RMA number typed in from the vendor; in the intercompany case it is taken from the generated return order, so the same number identifies the return in both entities. Put it on the shipping paperwork. It is the best matching key you will get.
• Reference the original receipt. On the purchase side, the return lot ID ties the negative line to the product receipt it reverses; on the sales side, Find sales order does the same against the original invoice. That link is what makes the goods leave the buyer and re-enter the seller at their original values, not at whatever the price or cost happens to be today.
• The direction of the trigger reverses. On a forward order the seller ships and the buyer's receipt follows. On a return the buyer physically ships first, and the seller's arrival comes later. Decide explicitly which posting drives the other and test it with your own automatic posting settings from the trade setup article, because the default assumption (the selling side leads) leaves returned goods sitting in the buyer's inventory on paper while they are on a truck.
RETURNING A DIRECT DELIVERY
For a customer return of a direct delivery, the return order is created in the sales company against the external customer, and the Direct delivery option is set on the return order header before the lines are added through Find sales order. That one field changes what happens next: the sales company gets an intercompany purchase order of type Returned order, the source company gets an intercompany return order, and the customer is instructed to ship to the source company's warehouse. The sales company never receives anything physically. Its side completes financially when the source company processes the arrival and the documents post back along the chain.
If the option is left off, the return is an ordinary one: the goods arrive in the sales company's own warehouse and stay there. That is sometimes the right answer (the sales company can resell locally), but it should be a decision, not an oversight. Once lines exist, changing your mind means cancelling and starting again.
ARRIVAL AND DISPOSITION ACROSS ENTITIES
Arrival and disposition happen where the goods land, which means in the selling or source company. The person inspecting the item there chooses the disposition code, and that choice decides whether the stock goes back to available inventory, is scrapped, or is sent back again. Two consequences follow.
First, the entity that talks to the customer is not the entity that judges the goods. If the sales company has promised a full credit and the source company's inspection disagrees, the system will not resolve that for you. Agree the rule beforehand: who has authority over the disposition, and how the result is communicated back before the external credit note goes out.
Second, keep the disposition codes used for intercompany returns simple. Credit and scrap behave predictably across the chain. Dispositions that create a replacement order are designed around a single company, and I have found it cleaner to treat a replacement as a new forward intercompany order, with its own chain, than to expect the return to produce one across two entities. Reason codes and return charges are also company-specific data, so align the code lists in both companies if you want to report on return reasons group-wide.
WHEN A CREDIT NOTE ALONE IS ENOUGH
Not every correction deserves a truck. I separate three cases, because each one needs a different document.
The physical return is the full chain described above. Credit only is still a return order chain, but with a disposition code whose action is credit only: no arrival is expected, the seller credits, and the buyer's stock has to be written off or scrapped locally, since it is still physically there. That last step is the one people forget. The buyer's purchase is reversed, so the buying company must deliberately remove the quantity, or it will hold stock it no longer owns on paper, or the opposite.
The price correction is different in kind: quantity and stock were right, only the price was wrong. Here I credit the original line and invoice it again at the correct price, as a negative and a positive line on the intercompany sales order so that both mirror into the purchase order. The buyer's inventory value is then adjusted through its own costing, and the two ledgers still agree.
What I avoid is the shortcut of a free text invoice credit in the selling company. It is quick, it has no order behind it, and nothing is generated in the buying company. Someone has to remember to book the other half, and at period end nobody does.
THE VALUE OF A RETURN
A return carries two values, and both need attention. The first is the transfer price on the credit note. With the original invoice referenced, the credit uses the price that was actually charged. Without it, the order picks up the price that is valid today, and if the transfer price has changed since the sale (see the pricing article), the credit will not equal the invoice it reverses. The second is the cost at which goods re-enter the seller's inventory. Linked to the original sale, they come back at the cost they left with; unlinked, they take the return cost price on the line, which is frequently a default nobody reviewed.
There is also a group-level effect. A return of goods that were still in the buyer's stock reverses internal margin that was sitting unrealised in inventory, so the elimination figure for the period changes. Tell whoever runs consolidation about material returns; do not let them find it as an unexplained movement.
WHAT GOES WRONG
• The return is created without a reference to the original document, so price and cost come from today's data and the pair never nets to zero against the original invoices.
• Direct delivery is not selected on the return order, and customer goods arrive at a sales company with no warehouse process to receive them.
• The buyer posts its negative receipt in one period and the seller completes arrival and credit in the next. The balances differ at close by exactly the value of goods in transit.
• A credit only disposition is used and the buying company never removes the stock.
• One side corrects with an order and the other with a journal, so the weekly matching query has nothing to join on.
• Quantities are edited on one document after partial posting, and the mirror no longer matches. Correct both through the chain, or cancel the remainder on both.
My checklist before allowing intercompany returns in production is short: both return scenarios tested end to end in both directions, the RMA number visible on both documents and on the paperwork, a rule for who decides the disposition, credit only write-off assigned to a named role in the buying company, and returns included in the same period-end matching as invoices.
Next time I will look at intercompany with Advanced WMS: how shipments and receipts between entities behave when both warehouses run warehouse management processes, what the packing slip can carry across, and how to get close to an ASN-style receipt between your own companies.
In this series: previous article Intercompany Invoicing and Reconciliation in D365: Auto Posting, Due To and Due From, Eliminations
In the invoicing and reconciliation article I followed a delivery forward: one shipment, two invoices, and a period end where both companies have to agree. Today I want to run the same chain backwards. Goods come back, or a credit is owed without anything coming back, and the question is how to make that correction land in both legal entities at once, at the right value, without anyone keying a manual journal at month end. Returns are a small share of intercompany volume and, in my experience, a large share of intercompany reconciliation differences, almost always because the two sides corrected the same event in two different ways.
TWO SHAPES OF INTERCOMPANY RETURN
There are two situations, and it helps to name them before touching any setup.
• The simple return. The buying company holds stock it purchased from the selling company and sends it back: wrong item, quality problem, overstock agreed to be taken back. Two entities, no external party.
• The direct delivery return. The sales company sold to an external customer, the goods shipped straight from the source company (the pattern I described in the order chain article), and now the customer wants to return them. Three documents are involved, and the goods usually should travel back to where they came from, not to a sales company that may not even run a warehouse.
Both rest on the same mechanism: a return document in one company generates its mirror image in the other, exactly as a forward order does.
THE SIMPLE RETURN: A MIRRORED PAIR
In the buying company, the vendor return is a purchase order of type Returned order with negative quantities. In the selling company, the customer return is a return order carrying an RMA number. For an intercompany vendor and customer pair, creating either one generates the other. I prefer to start in the buying company, because that is where the decision to send goods back is actually made, but starting from the selling company's return order works just as well when the seller is recalling stock.
Three details matter more than the rest.
• The RMA number belongs to the selling company. A vendor return normally needs an RMA number typed in from the vendor; in the intercompany case it is taken from the generated return order, so the same number identifies the return in both entities. Put it on the shipping paperwork. It is the best matching key you will get.
• Reference the original receipt. On the purchase side, the return lot ID ties the negative line to the product receipt it reverses; on the sales side, Find sales order does the same against the original invoice. That link is what makes the goods leave the buyer and re-enter the seller at their original values, not at whatever the price or cost happens to be today.
• The direction of the trigger reverses. On a forward order the seller ships and the buyer's receipt follows. On a return the buyer physically ships first, and the seller's arrival comes later. Decide explicitly which posting drives the other and test it with your own automatic posting settings from the trade setup article, because the default assumption (the selling side leads) leaves returned goods sitting in the buyer's inventory on paper while they are on a truck.
RETURNING A DIRECT DELIVERY
For a customer return of a direct delivery, the return order is created in the sales company against the external customer, and the Direct delivery option is set on the return order header before the lines are added through Find sales order. That one field changes what happens next: the sales company gets an intercompany purchase order of type Returned order, the source company gets an intercompany return order, and the customer is instructed to ship to the source company's warehouse. The sales company never receives anything physically. Its side completes financially when the source company processes the arrival and the documents post back along the chain.
If the option is left off, the return is an ordinary one: the goods arrive in the sales company's own warehouse and stay there. That is sometimes the right answer (the sales company can resell locally), but it should be a decision, not an oversight. Once lines exist, changing your mind means cancelling and starting again.
ARRIVAL AND DISPOSITION ACROSS ENTITIES
Arrival and disposition happen where the goods land, which means in the selling or source company. The person inspecting the item there chooses the disposition code, and that choice decides whether the stock goes back to available inventory, is scrapped, or is sent back again. Two consequences follow.
First, the entity that talks to the customer is not the entity that judges the goods. If the sales company has promised a full credit and the source company's inspection disagrees, the system will not resolve that for you. Agree the rule beforehand: who has authority over the disposition, and how the result is communicated back before the external credit note goes out.
Second, keep the disposition codes used for intercompany returns simple. Credit and scrap behave predictably across the chain. Dispositions that create a replacement order are designed around a single company, and I have found it cleaner to treat a replacement as a new forward intercompany order, with its own chain, than to expect the return to produce one across two entities. Reason codes and return charges are also company-specific data, so align the code lists in both companies if you want to report on return reasons group-wide.
WHEN A CREDIT NOTE ALONE IS ENOUGH
Not every correction deserves a truck. I separate three cases, because each one needs a different document.
The physical return is the full chain described above. Credit only is still a return order chain, but with a disposition code whose action is credit only: no arrival is expected, the seller credits, and the buyer's stock has to be written off or scrapped locally, since it is still physically there. That last step is the one people forget. The buyer's purchase is reversed, so the buying company must deliberately remove the quantity, or it will hold stock it no longer owns on paper, or the opposite.
The price correction is different in kind: quantity and stock were right, only the price was wrong. Here I credit the original line and invoice it again at the correct price, as a negative and a positive line on the intercompany sales order so that both mirror into the purchase order. The buyer's inventory value is then adjusted through its own costing, and the two ledgers still agree.
What I avoid is the shortcut of a free text invoice credit in the selling company. It is quick, it has no order behind it, and nothing is generated in the buying company. Someone has to remember to book the other half, and at period end nobody does.
THE VALUE OF A RETURN
A return carries two values, and both need attention. The first is the transfer price on the credit note. With the original invoice referenced, the credit uses the price that was actually charged. Without it, the order picks up the price that is valid today, and if the transfer price has changed since the sale (see the pricing article), the credit will not equal the invoice it reverses. The second is the cost at which goods re-enter the seller's inventory. Linked to the original sale, they come back at the cost they left with; unlinked, they take the return cost price on the line, which is frequently a default nobody reviewed.
There is also a group-level effect. A return of goods that were still in the buyer's stock reverses internal margin that was sitting unrealised in inventory, so the elimination figure for the period changes. Tell whoever runs consolidation about material returns; do not let them find it as an unexplained movement.
WHAT GOES WRONG
• The return is created without a reference to the original document, so price and cost come from today's data and the pair never nets to zero against the original invoices.
• Direct delivery is not selected on the return order, and customer goods arrive at a sales company with no warehouse process to receive them.
• The buyer posts its negative receipt in one period and the seller completes arrival and credit in the next. The balances differ at close by exactly the value of goods in transit.
• A credit only disposition is used and the buying company never removes the stock.
• One side corrects with an order and the other with a journal, so the weekly matching query has nothing to join on.
• Quantities are edited on one document after partial posting, and the mirror no longer matches. Correct both through the chain, or cancel the remainder on both.
My checklist before allowing intercompany returns in production is short: both return scenarios tested end to end in both directions, the RMA number visible on both documents and on the paperwork, a rule for who decides the disposition, credit only write-off assigned to a named role in the buying company, and returns included in the same period-end matching as invoices.
Next time I will look at intercompany with Advanced WMS: how shipments and receipts between entities behave when both warehouses run warehouse management processes, what the packing slip can carry across, and how to get close to an ASN-style receipt between your own companies.
In this series: previous article Intercompany Invoicing and Reconciliation in D365: Auto Posting, Due To and Due From, Eliminations
No comments yet. Be the first to comment!