Ironically, a previous employer used to use the ITD segment for . well, something.
When a PO was set up, the vendor specific terms default into the PO and may have been modified by the buying department, as needed. Those terms went out in our 850 document. When the vendor/supplier would send us the 810 invoice, we'd map the ITD data into a field and then it was included in a paper report generated and given to the AP department. Yes, while with EDI we were trying to eliminate some paper, the AP department was woefully stuck in . 1962. Everything had to have a paper trail. And all of those papers associated with that PO - receiving worksheets, copies of the PO, and so much more - where all a part of the paper trail - including copies of checks to pay for partial invoices for partial shipments. sometimes, those stacks of papers could be thicker than the ANSI-X12 Book of Standard I kept on the desk!!! Anyway, the way that they used the data in the ITD segment was that, in the printed copy of the EDI invoice, there was the "system" due/terms date and then the vendor's due/terms date. Then whomever was responsible for that vendors invoices would compare the two dates. Whichever date was more advantageous to the company would be used. So if our system due date was 10/31 and the vendor sent us 11/01, we'd use their due date. I wonder if there are more companies using this kind of philosophy out there - taking the best due date and terms that they can get, holding on to their money for as long as they can.. Craig Dunham Bear Necessities Computing EDI Sherpa Author/blogger <http://www.retailedi.com/> RetailEDI.com <http://editalk.com/> EDITalk.com Sounds reasonable to me; and "sounds reasonable" is about all you can expect from anyone here . In Real Life, the ITD segment is rarely read and acted upon by the purchaser, the terms of payment being defined outside of electronic documents, eg in an electronic trading partner agreement (and/or associated Implementation Guide) or a blanket PO number. In my experience the recipient will record the vendor's invoice number and date, the amount subject to terms (if applicable) and the purchase order number and then just turn it over to their own A/P department, who will pay the invoice consistent with its own policies for paying that particular vendor. (Didn't we just have a question related to this last week? Someone wondering how to map an inbound ITD Segment? And IIRC that member said his company basically pays on its own terms anyway so I suggested he just ignore the due and discount dates in the ITD segment, since he wasn't going to use 'em anyway.) Your Mileage May Vary. Michael C. Mattias Tal Systems Inc. Racine WI <mailto:mmattias%40talsystems.com> [email protected] [Non-text portions of this message have been removed] ------------------------------------ ... 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: [email protected] [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/
