EDI transactions for Credit/Debit Memos and Returns

Stace Webley

We have a vendor that has been sending us Credit/Debit Memos and Returns via EDI.  They come in as an 810, but error out and land in EDI Work.  The error is that the PO number being referenced isn't valid because the number they use does not tie back to a PO in our system.  I have requested that they turn these transactions types off of EDI and email them to our AP team instead.  We should only be receiving EDI invoices for the PO's we've submitted through EDI.  Has anyone else experienced this and what actions have you taken?  Is there a mapping entry I could make to the substitution table to get these to work in EDI?  Thank you.

andy

We have the same issue. These non-matching invoices can still be sent even if you request the vendor suppress them, or at least that has been our experience with some vendors.

However, this issue was discussed at length on the last EDI Ask the Experts call, and there were a variety of potential solutions discussed. The main challenge with interfacing non-matching invoices through EDI is the fact the non-matching / expense invoices do not have any associated PayablesInvoiceDetail records, so the question is where do you store the EDI line data on the PayablesInvoice? Do you map it to distribution records, if so how do you determine the account string to use? Also how do you classify and EDI 810 as a non-matching / expense invoice? What segment in the 810 indicates the invoice is an expense invoice? 

As I recall the action item take away for Infor dev on the call was to explore a data sub option to allow for EDI works to be translated successfully with the header only if the PO number is invalid (e.g. non integer chars).