Hello,
I mentioned the one time vendor just for the sake of completeness. Its really not a good way to use it, unless you really have a one time vendor.
The effort would be very similar, you still have to create a vendor record and link it to the employee. Just the information necessary on the vendor would be less fields to populate.
Would you could do to automate the process if it is really worth in your business case is to create vendors via Power Automate. This might become very complex which raises the question if it is worth it or not.
Let me explain briefly how it could work.
1. When an employee is created, a business event needs to be created for Power automate. Eventually you need to create this business event if it is not in standard
2. In the power automate flow a vendor can be created via the entity Vendors (V3), taking the name and other information from the employee record.
Question is, where do you get the information that you need on the vendor record, but you dont have on the employee record. If you have somewhere the bank information digitally stored, you could pull that information via API request from Power automate and insert it in the newly created vendor.
If you dont have that information digitally stored, then you could implement a semi-automated process, where Power automate creates the vendor and sends an email\Teams message to someone to fill out the rest of the information necessary on the vendor account.
Kind regards, Adis
If this helped, please mark it as "Verified" for others facing the same issue
Keep in mind that it is possible to mark more than one answer as verified
