depending on your erp system, you -could- generate release numbers to allow you to match the shipments with the invoice, and still tie back to the po. you can also send a pro # or manifest number on both the 856 and 810. you probably don't want to put the ucc128 code into the invoice :)
luvinedi wrote: >Hello, hello! > >The company I work for is in the preliminary stages of implementing >EDI, and we plan to start with the 810 (PO), 850 (Invoice) and 856 >(ASN). We are in the retail industry, so our trading partners will >mainly be vendors and manufacturers. > >Here is the planned flow on a broad level: > >1) We generate the PO and transmit to vendor. > >2) They ship what they have and transmit to us an Invoice & ASN. > >3) We put the invoice in a staging table (we do not want to import it >into our ERP system until the goods have been received). > >4) We put the ASN in a staging table (will be used to ensure the >physical goods we receive matches the ASN). > >5) The goods arrive and is checked against the ASN as it is scanned >in. Also, our ERP system assigns a receiver number to this receiving >transaction. > >6) If all matches, the invoice is submitted to the ERP and all is >good; otherwise the invoice and receiver are flagged for manual >review by A/P. > >Now, here is the rub: Since a PO can have multiple receivings and >invoices (for partial shipments), how do we identify what receiving / >ASN belongs to what invoice? If the ASN contains the invoice number >we are home free, but when it does not, on what information do we >link them together? > >For example: > >Document PO # Invoice # Amount >------------ ----- --------- ------- >Original PO 48000 Not known $10,000 >ASN (Monday) 48000 Not known $4,000 >ASN (Tuesday) 48000 Not known $6,000 >Invoice 48000 120 $4,000 >Invoice 48000 121 $6,000 > >As you can see, the PO Number (48000) appears on all documents. The >invoice numbers, however, only appear on the invoices. We will also >have an internal receiver number and ASN number, but again, those >will not be present on any other documents and therefore cannot be >used as linking mechanisms. > >How do you currently get around not having an invoice number on an ASN >document? What data do you use as a link between the 850, 810, and >856's? > >Thank you in advance for any and all guidance! > >-K > > > > > >. >Please use the following Message Identifiers as your subject prefix: <SALES>, ><JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> >Access the list online at: http://groups.yahoo.com/group/EDI-L > >Yahoo! Groups Links > > > > > > > > > > > -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Brian Lehrhoff, EA ([EMAIL PROTECTED]) Messaging Consultant 201-913-4506 Buy 2006 Quickbooks for 15% off at http://www.brianlehrhoff.com Circular 230 Notice is located at http://www.brianlehrhoff.com/230notice.html %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> 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/
