I don't think it is the integration itself. I think we need to look at a couple of different things:
1) how we are using the Vendor card fields in BC
2) what field needs to be called back to MV (Metaviewer) for identifying the vendor.
Here is a scenario:
Company ABC sends an invoice. It is uploaded to MV. MV tries to auto identify the vendor and populate all fields it identifies with in MV. Company ABC has both a "legal/parent" company name and a dba name. The invoice comes in with the dba name on the invoice. We have the vendor card in BC set up with the dba name, so it makes a match. Everything is good.
It's 1099 time and we pull data for the applicable vendors, being in healthcare, we have a lot of instances where one company will own several facilities we use. 1099 data is pulled by vendor and so all the vendor payments are associated with the dba names, not the "parent or legal" company names. We create 1099s based on the dba name, since that name is associated with the payment, and we get major notices when trying to upload the data to our third party 1099 processor that we have multiple companies with the same Fed ID. Plus, when the government processes the 1099s, we get notices form them.
We need to understand how to set up the fields in BC to accommodate both names and sometimes different addresses (which can be different than the remit address) so that we satisfy both what MV needs to identify the vendor, regardless of if it is the legal name or dba on the invoice and still produce 1099s correctly. Right now, MV only looks at the Vendor Name from the Vendor card to try to match to the invoice it is processing. And of course. when invoices are processed manually by the AP people, they have the same scenario when trying to identify the vendor.
If we need multiple fields populated in BC to accommodate both MV and government reporting, we need to determine what fields to send to MV.
Sorry for the long post. We have asked Metafile to provide a few names of their customers that use BC so that we could reach out or have them contact us about the issue and they said they cannot do that, that is why I am here :)
