Seeking advice from the group with respect to how credits should be
handled within an 820 remittance advice document. I don't see a lot
of consistency out there in the EDI world, or at least haven't as of yet.
I have seen two types of credits - those that relate to an invoice and
those that don't (compliance issues, etc). There appears to be an
opportunity to express each type within the various ADX loops offered
in the document.
One option appears to be as follows:
1) Lay out all of the credits unrelated to an invoice within as many
ADX segments as you need.
2) When #1 is complete, enter into the RMR loop and list invoices to pay.
3) If any of the invoices need to be offset by a credit of some sort
(cost discrepancy / paying short), then the use of an ADX loop within
the RMR would be warranted.
Another option...
I have seen where #1 is handled differently. They don't use this ADX
loop at all, and instead, use a CM qualifier within the RMR segment to
reference a credit.
Now, given that the definition of an RMR segment is meant to refer to
an open A/R item of the receiver, it seems like this is not a proper
approach as the credit invoice # in question is often made up by the
sender...and thus would violate this definition.
Any and all thoughts on the topic above would be appreciated.
Thanks.
...
Please use the following Message Identifiers as your subject prefix: <SALES>,
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Job postings are welcome, but for job postings or requests for work: <JOBS> IS
REQUIRED in the subject line as a prefix.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/EDI-L/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/EDI-L/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
