Link vendor account in D365 to another vendor outside of D365 (ISV)

(0) Share

Report

Posted on by lmai

2,432

Hi All,

We are integrating D365 with another Supply Chain software (ISV). The vendor name is the same in both systems. The vendor accounts, however, are different in both systems. Let say my vendor in both systems is Iron Mountain.

In D365, the vendor account is 12345.

In the ISV, the vendor account is 19191919.

So, they are different digits and different numbers. Any suggestion on how I can link these two vendor accounts; because ultimately, they are the same vendor. The goal is, when I paid this vendor in D365, it integrates/updates this payment to the right vendor account in the ISV.

Thanks so much for your feedback.

All responses (3)

Answers (0)

JJ_Yadav on at

Like (0)

Report

RE: Link vendor account in D365 to another vendor outside of D365 (ISV)

There are many way to address such requirements for data integration -

1. You can maintain custom field/alternate out of the box field (ex. YourAccountNum)/custom table to store the account number mapped from other system and let integration translate the mapping during the integration.

2. There is also External code feature out of the box for many of such master data such as vendor, customer , product to define external code and that can be further utilized for integration and other processes.
lmai 2,432 on at

Like (0)

Report

RE: Link vendor account in D365 to another vendor outside of D365 (ISV)

Thanks, JJYadav, for your response. Could you tell me more about the External Code? Yes, it is for integrate D365 with another ISV. Same vendor name and address, but vendor code/vendor number in bother systems are different.
JJ_Yadav on at

Like (0)

Report

RE: Link vendor account in D365 to another vendor outside of D365 (ISV)

There are many way to address such requirements for data integration -

1. You can maintain custom field/alternate out of the box field (ex. YourAccountNum)/custom table to store the account number mapped from other system and let integration translate the mapping during the integration.

2. There is also External code feature out of the box for many of such master data such as vendor, customer , product to define external code and that can be further utilized for integration and other processes.