Data contents of the Business Entity Filings Transaction Set (105) for use within the context of an Electronic Data Interchange (EDI) environment. This bidirectional transaction set can be used by business entities, governmental administrators and regulators to exchange required business entity filing information, such as annual reports, registered agent changes and changes of officers, partners and directors, and may include information about any required fees.

Data contents of the Motor Carrier Rate Proposal Transaction Set (106) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by a motor carrier to propose rates and services to a shipper, receiver, or other relevant party.

Data contents of the Request for Motor Carrier Rate Proposal Transaction Set (107) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by a shipper, receiver, or other relevant party to request that a motor carrier provide a rate and service proposal.

Data contents of the Response to a Motor Carrier Rate Proposal Transaction Set (108) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by a shipper, receiver, or other relevant party to respond to a motor carrier's rate and service proposal.

Data content of the format and establishes the data contents of the Vessel Content Details Transaction Set (109) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide all the information necessary to report event details for a shipment and status for one or more containers bound for a port. It is intended to accommodate the details for one status or event associated with many containers, as well as more than one status or event for one shipment.

Data contents of the Air Freight Details and Invoice Transaction Set (110) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide a customer with an air invoice for transportation and other charges related to shipments, including Original Invoices, Past Due Billings, Balance Due Bills and Revisions.

This X12 Transaction Set contains the format and establishes the data contents of the Individual Insurance Policy and Client Information Transaction Set (111) for use within the context of an Electronic Data Interchange (EDI) environment. This standard can be used to exchange policy and client information among organizations administering individual life and health insurance contracts and their trading partners (e.g., agents, brokers). It is not intended to be used for group insurance. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

Data context of an Electronic Data Interchange (EDI) environment. This transaction set will be used to provide property damage information between property and casualty insurance companies, independent agents, service and information providers. This information includes, but is not limited to providing cost estimates involving functions such as demolishing, new constructions, damage repair and replacement.

This X12 Transaction Set contains the format and establishes the data contents of the Election Campaign and Lobbyist Reporting Transaction Set (113) for use within the context of an Electronic Data Interchange (EDI) environment. This Bi-directional transaction set can be used by candidates, candidate committees, party committees, political action groups, lobbyists and other entities to exchange disclosure data. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

This Draft Standard for Trial Use contains the format and establishes the data contents of the Air Shipment Status Message Transaction Set (114) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide the shipper and consignee with status information on current shipments. This transaction set can provide shippers, consignees and their agents with the status of shipments in terms of 1) dates, 2) times, 3) locations, 4) charges, 5) route, and 6) identifying numbers. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

Data contents of the Vehicle Shipping Order Transaction Set (120) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to notify a carrier of the impending arrival of a motor vehicle which the carrier is to ship to the destination herein specified or on which that carrier is to perform a service. It may be sent to a carrier by the vehicle manufacturer, by another carrier, or by an agent of the manufacturer.

Data contents of the Vehicle Service Transaction Set (121) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by a carrier to notify a Vehicle Manufacturer that a requested movement or service has been performed on motor vehicles or that a change in status has occurred.

Data contents of the Vehicle Damage Transaction Set (124) for use within the context of an Electronic Data Interchange (EDI) environment. This standard can be used to provide vehicle damage information flow between Property & Casualty (P&C) insurance companies, independent agents, service providers, information providers, selfinsurers and financial institutions. Business functions consist of the estimating of vehicle damage and the detailed reporting of parts and labor cost connected with repairing the estimated damage.

Data contents of the Multilevel Railcar Load Details Transaction Set (125) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by the origin rail carrier or loading contractor to report the departure of a multilevel railcar and its contents to the vehicle manufacturer. It is used by the vehicle manufacturer, origin rail carrier, or loading contractor to forward data pertaining to the loaded railcar and its contents to the destination rail carrier or haulaway carrier(s) or both upon departure. It is also used by the destination rail carrier, or unloading contractor to report to the vehicle manufacturer, the arrival of a railcar at the destination rail ramp.

Data contents of the Vehicle Application Advice Transaction Set (126) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by the vehicle manufacturer to notify a carrier as to the result of processing the transactions received from the carrier during the previous day or payments being released today or both.

Data contents of the Vehicle Baying Order Transaction Set (127) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to request or report the assignment of a motor vehicle to a specific predetermined bay (parking space) in a storage or shipping facility and to report conditions of a storage or shipping facility.

Data contents of the Dealer Information Transaction Set (128) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by the shipper to notify carriers of the establishment of a new "Ship To" Location (e.g. Retail Dealer, Drop Ship Point, or Body Vendor) or profile change to an existing "Ship To" Location in the carrier's area of service.

Data contents of the Vehicle Carrier Rate Update Transaction Set (129) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by either a carrier or the vehicle manufacturer to transmit new freight rates either as the result of a rate adjustment or as a rate proposal for new business.

Data contents of a Student Educational Record (Transcript) Transaction Set (130) for use within the context of an Electronic Data Interchange (EDI) environment. The student transcript is used by schools and school districts and by postsecondary educational institutions to transmit current and historical records of educational accomplishments and other significant information for students enrolled at the sending schools and institutions. The transcript may be sent to other educational institutions, to other agencies, or to prospective or current employers. When a student transfers from one educational institution to another, it is essential that the student's prior educational record be made available to the institution to which the student wishes to transfer. For students in PreKindergarten through Grade 12, prompt records transfer will assist receiving schools in making an appropriate initial educational placement of student. It is important that this information be available on a timely basis. In some cases for postsecondary students, it is this record which determines whether the student will be accepted at the receiving institution. In all cases, it is important to know what course work the student has already completed so that the student may be properly placed in courses and educational programs at the next institution. When a student seeks employment or wishes to inform another agency of the student's academic accomplishments, the student transcript may be sent to a prospective employer, branch of the military, or another government agency. The student transcript contains personal history and identifying information about the student, the current academic status, dates of attendance, courses completed with grades earned, degrees and diplomas awarded, health information (PreKindergarten through Grade 12 only), and testing information.

Data contents of the Student Educational Record (Transcript) Acknowledgment Transaction Set (131) for use within the context of an Electronic Data Interchange (EDI) environment. The Student Educational Record (Transcript) Acknowledgment record is used to ensure that the original transcript did, in fact, come from the proper office at the educational institution indicated as the sender and that certain key elements of the transcript were received as they were sent. It also provides the sending institution with confirmation that the original record was received by the intended recipient and the date it was received. This information may then be relayed to the student or other individual who requested the record transfer.

This X12 Transaction Set contains the format and establishes the data contents of the Human Resource Information Transaction Set (132) for use within the context of an Electronic Data Interchange (EDI) environment. The Human Resource Information Transaction Set is used to transmit current and historical records of employment status, education, teaching credentials, work experience, and other significant information on employees in an education environment. Data contained in this transaction set may be sent to educational institutions, school districts, retirement systems, and state or other agencies. This information can be useful in establishing credentials for consideration for employment, certification, and administrative and statistical reporting, or community services. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

This X12 Transaction Set contains the format and establishes the data contents of the Educational Institution Record Transaction Set (133) for use within the context of an Electronic Data Interchange (EDI) environment. The Educational Institution Record conveys descriptive characteristics of postsecondary and elementary/secondary educational institutions. Data contained in this record includes information about institutional location, type, student enrollment, staffing governance, finance, programs, and services at an educational institution. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

Data contents of the Student Loan Application Transaction Set (135) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by lending institutions ("lenders"), colleges, universities and trade schools ("schools"), and loan guarantee agencies ("guarantors") to exchange information relating to the certification, approval, and guarantee of specific student loan applications. This information includes, but is not limited to, student and applicant identification, school enrollment data, borrowing history, and the terms of the loan. The student loan application process typically begins with an applicant submitting a student loan application to the financial aid officer at the student's school. The financial aid officer adds schoolrelated information and certifies the application. The school then forwards the loan application to the lender for review. If the review is satisfactory, the lender adds information to the application, approves the loan, and forwards the application to the guarantor. The guarantor reviews the lenderapproved application and if appropriate, issues a guarantee. The lender disburses the loan proceeds when a guarantee is received.

Data contents of the Testing Results Request and Report Transaction Set (138) for use within the context of an Electronic Data Interchange (EDI) environment. This standard can be used to request and receive the results of testing programs by educational institutions and employers. This information includes one testtaker's identification, test identification, testing conditions, scoring results, and test normalization analysis including national, regional, and local norms.

Data contents of the Student Loan Guarantee Result Transaction Set (139) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by guarantee agencies ("guarantors") to inform a lender, a school, or both as to the status of a student loan guarantee. The guarantee result information includes, but is not limited to, the conditions of approval or denial of a loan guarantee, notice of guarantee and loan disclosure terms, and information regarding previously guaranteed loans. The student loan guarantee result is the second phase of the student loan application process. After the guarantor reviews the lenderapproved student loan application, the agency issues a guarantee result. Subsequent lender processing of the student loan application is based on the information contained in the result transaction. After the lender receives a loan guarantee approval, the federally required loan disclosure is generated, and the loan proceeds are disbursed. If the lender receives a loan guarantee rejection, the lender may correct and resubmit the loan application, or the application may remain in a rejected status.

Data contents of the Product Registration Transaction Set (140) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to specify the manufacturer, seller, secondary warranter, and purchaser or lessee of the product. It can specify the date the product was sold, delivered, and placed in service as well as identify the product model and serial numbers. It can specify the class of service expected from this individual sale, for example: industrial, commercial, or household. This registration information can be used to divide sales commissions among sales associates or attribute license fees to the proper manufacturer. It can be used to submit many product registrations at one time to one receiving organization.

Data contents of the Product Service Claim Response Transaction Set (141) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit the status of a product service claim and the items accepted and rejected for payment from the product service claim. Each product service claim submission could have represented the repair of several individual products and each pair could have consisted of several repair actions involving parts and labor.

Data contents of the Product Service Claim Transaction Set (142) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit the servicing organization, claimant, manufacturer, seller, and purchaser of the product. It can specify the product's current usage, date the product was sold, delivered, and placed in service as well as identify product model and serial numbers and serial numbers of any subassemblies. It can specify a malfunction or recall condition, service performed, labor, parts, and any other associated costs. It can show the costs of the repair and the date service was requested and when it was available to be placed back in service.

Data contents of the Product Service Notification Transaction Set (143) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit either a mandatory or a voluntary recall. While the recall transaction could be sent to a consumer, it is more likely to be sent to a servicing organization to provide them notice of the recall and to establish their authority to service the items specified in the recall notice. It could be sent to the seller if they are required to notify the purchaser, and it could be sent to an owning organization where they are capable of receiving EDI transactions, such as a large fleet owner of automobiles. It could be a recall from the distribution channel of products. One recall notice is limited to one set of items sharing the possibility of the same problem. The notice also can be a service bulletin which could specify a repair, engineering change, a field replacement, or other such action to a product. The service action could be specified for the next time that product is being serviced. It could just as well specify that the action must take place as soon as possible or it could be at a specified particular date and time so as to coordinate the change at many product locations. This could happen, for example, in an interconnected computer system or a telephone switching system.

Data contents of the Student Loan Transfer and Status Verification Transaction Set (144) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set is used by lending institutions ("lenders"), guarantee agencies ("guarantors"), and secondary markets to send and receive information regarding the transfer of ownership of a student loan. It can also be used to verify the status of a student loan prior to and subsequent to the purchase of the loan. The loan status verification and transfer data includes, but is not limited to, borrower, student, and loan detail information. A potential purchaser of a student loan would use this transaction set to request information, from the guarantor of the loan, regarding loan status. This transaction set would in turn be used by the guarantor to return the verified loan status information to the requester. Subsequent to the purchase of the loan, this transaction set would be used by the purchaser to notify the guarantor of a transfer of ownership.

Data contents of The Request for Student Educational Record (Transcript) Transaction Set (146) within the context of an Electronic Data Interchange (EDI) environment. This transaction set is used by educational institutions to which a student has applied for admission. This request is then sent to the educational institution which the student is currently attending or previously attended.

Data contents of a Response to Request for Student Educational Record (Transcript) Transaction Set (147) within the context of an Electronic Data Interchange (EDI) environment. This transaction set is used to advise the requesting institution regarding when the record will be sent or why it will not be sent.

Data contents of the Report of Injury, Illness or Incident Transaction Set (148) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to report information pertaining to an injury, illness or incident to entities interested in the information for statistical, legal, and claims and risk management processing requirements.

Data contents of the Notice of Tax Adjustment or Assessment Transaction Set (149) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by a taxing authority to transmit to a taxpayer either a notice of adjustment to a prior tax filing, or a notice of assessment of taxes due to the taxing authority, which may be a notice of warrant.

Data contents of the Tax Rate Notification Transaction Set (150) for use within an Electronic Data Interchange (EDI) environment. This transaction set can be used by taxing authorities to electronically transmit information concerning tax rates.

Data contents of the Electronic Filing of Tax Return Data Acknowledgment Transaction Set (151) within the context of an Electronic Data Interchange (EDI) environment. This transaction set is used to electronically acknowledge receipt of each tax return filed using the Electronic Filing of Tax Return Data Transaction Set (813) and may indicate any error conditions. This transaction set can be used by a federal, state, or local taxing authority to acknowledge the status of an electronically filed tax return which has been electronically filed using Transaction Set 813.

Data contents of the Statistical Government Information Transaction Set (152) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to report predefined statistical government information.

Data contents of the Unemployment Insurance Tax Claim or Charge Information Transaction Set (153) for use within the context of an Electronic Data Interchange (EDI) environment. This bidirectional transaction set can be used by employment security agencies to notify employers or other agencies of a possible charge to their employers' unemployment insurance tax account and by employers responding to the notice with supplemental information that might affect the chargeability of the claim. This transaction set can also be used by employers to notify claimant(s)' representative, e.g., union, to protest a claim.

Data contents of the Uniform Commercial Code Filing Transaction Set (154) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to file Uniform Commercial Code (UCC) financing statement forms and to exchange UCC filing information.

Data contents of the Business Credit Report Transaction Set (155) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to transmit business credit information to a trading partner. This transaction set may be used to convey identification, location, financial, payment experiences, banking, suits, liens, judgements and public filing details, operational, affiliate, organizational, credit rating, and other information about a business to support automated business decision processing and update business data bases.

Data contents of the Notice of Power of Attorney Transaction Set (157) for use within the context of an Electronic Data Interchange (EDI) environment. This bidirectional transaction set can be used to notify entities of the existence of a power of attorney and to provide information as to its applicability. The transaction set may also be used to acknowledge powers of attorney or their cancellation.

This Draft Standard for Trial Use contains the format and establishes the contents of the Tax Jurisdiction Sourcing Transaction Set (158) for use within the context of an Electronic Data Interchange (EDI) environment. This standard can be used to transmit any address, in US Postal Service format, from a wireless telecommunications vendor to the holder of tax jurisdiction sourcing information for the state in which the address resides, and to receive in return a sourcing of all tax jurisdictions which have governance over the address in question. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

Data contents of the Motion Picture Booking Confirmation Transaction Set (159) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to confirm Motion Picture business terms, conditions, and licensing agreement information from distributor to exhibitor.

Data contents of the Transportation Automatic Equipment Identification Transaction Set (160) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to allow participants to share automatic identification equipment information and data at interchange points.

Data contents of the Train Sheet Transaction Set (161) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to allow railroads to exchange train sheet information and ensure that crews operating equipment on other railroads are aware of current operating conditions.

Data contents of the Transportation Appointment Schedule Information Transaction Set (163) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by transportation carriers and their trading partners to request and accept freight pickup and delivery appointments.

Data content of the Revenue Receipts Statement Transaction Set (170) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set is used to report daily ticket sales information for each show within a contract week. A contract week is normally a Friday through Thursday and is the period a film is shown in a theatre. Daily information is presented by show and includes ticket category, price, attendance and time of entertainment events. The transaction set is designed to report multiple levels of detail from individual points of occurrence or form consolidated points such as holding companies (circuits).

Data contents of the Court and Law Enforcement Notice Transaction Set (175) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to notify interested parties about important court events and actions related to a specific court case. It may also be used to transmit information about a specific law enforcement or administration of justice event to interested parties. This may include events like case dispositions, notices about criminal offenses, accidents or incidents, arrest warrants, court orders, and administrative actions.

Data contents of the Court Submission Transaction Set (176) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to submit a legal document or claim and supporting documentation to a court or other designated recipient. It can be transmitted to the submitter to indicate the date and docket information assigned, or it can be transmitted to the submitter to indicate claim disposition or an opinion deciding a case.

This X12 Transaction Set contains the format and establishes the data contents of the Environmental Compliance Reporting Transaction Set (179) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by commercial and public facilities to submit environmental compliance reports to the Environmental Protection Agency and state and local environmental agencies. The transaction set can also be used to forward data or exchange environmental compliance data amongst environmental agencies at all levels of government, and to return status to the submitter. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

Data contents of the Return Merchandise Authorization and Notification Transaction Set (180) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can provide for customary and established business and industry practice relative to the returning of merchandise to the vendor. This transaction set may satisfy request for returns, authorization or disposition of the return, notification of return, or notification of consumer return.

Data contents of the Royalty Regulatory Report Transaction Set (185) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide royalty regulatory data for extraction of minerals and petroleum products from leased property. The data can be sent to federal and state government agencies to meet regulatory requirements. The data can be exchanged between private industry trading partners for information purposes.

Data contents of the Insurance Underwriting Requirements Reporting Transaction Set (186) for use within the context of an Electronic Data Interchange (EDI) environment. The standard can be used by the information providers to report the results of specific services to their trading partners for information to complete the insurance underwriting process on individually underwritten life and health insurance.

This X12 Transaction Set contains the format and establishes the data contents of the Premium Audit Request and Return Transaction Set (187) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to communicate premium audit information between property and casualty insurers, and independent premium audit service providers. This information includes, but is not limited to: premium audit request information (i.e., type of audit being requested, policyholder name, business locations, class codes, estimated exposures, date of coverage, producing agency, endorsements); and completed audit information (i.e., actual classification codes and exposures, description of operations, sources of financial information, subcontractor exposures) for the auditable general liability, commercial automobile and worker's compensation lines of insurance. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

Data contents of the Educational Course Inventory Transaction Set (188) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by schools and school districts and by postsecondary educational institutions to request and to transmit information about educational courses that are currently being offered or that have been offered in the past by the school, school district or postsecondary institution.

Data contents of the Application for Admission to Educational Institutions Transaction Set (189) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set contains all the information, except for official transcripts, that students use to apply for admission to educational institutions. The individual student may send the application for admission directly to the educational institution. In addition, entities other than the student may route or handle the application for admission. These entities include high schools, high school counselors, admission application service providers and clearinghouses, other educational institutions, testing agencies, and recommenders.

Data contents of the Student Enrollment Verification Transaction Set (190) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by guarantee agencies ("guarantors"), lending institutions ("lenders"), educational institutions ("schools"), secondary markets, and others to request and receive information required to verify a student's enrollment status. Federal regulations require lenders, guarantors, and schools to exchange student enrollment status information. This information includes, but is not limited to, student identification, enrollment status and dates, and school detail. The student's current enrollment status affects various aspects of the student loan process, such as the student's disbursement terms, deferment terms, deferment status, and repayment terms. Other entities such as insurance companies and student lending processors require additional information including student address, grade point average, and expected degree date.

Data contents of the Student Loan PreClaims and Claims Transaction Set (191) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by lending institutions (lenders), secondary markets, or student loan servicers to exchange information with guarantee agencies (guarantors) regarding preclaims assistance on student loans that are approaching a default status and claim payment requests for defaulted student loans. This information includes, but is not limited to, borrower identification, loan detail, payment history, and due diligence history. Federal regulations require loan owners to file a preclaims assistance request as part of their due diligence process, prior to filing a claim for default reimbursement. Loan owners are also required to file specific information to submit a claim payment request.

Data contents of the Grant or Assistance Application Transaction Set (194) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by organizations submitting applications for grants, cooperative agreements, and other assistance. These applications will typically include project, budget, personnel, descriptive, and other related data.

Data contents of the Federal Communications Commission (FCC) License Application Transaction Set (195) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set provides a uniform, singular, transmittal medium between applicants, coordinators, and license granting authorities, for the submission, acknowledgment of new applications, and the resubmittal of corrections to previously transmitted Federal Communications Commission (FCC) License Application.

Data contents of the Contractor Cost Data Reporting Transaction Set (196) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to support contractor cost reporting requirements for actual costs and estimates at completion associated with major research and development (R&D) and production contracts or programs. This includes nonrecurring and recurring costs by work breakdown structure elements summarizing all activities on a contract or proposal; non recurring and recurring functional cost or hour categories for selected work breakdown structure elements; progress curve (learning curve) information detailing unit or average lot data by functional cost or hour categories; and summary contractor business base information such as indirect expenses, rates, and resources. This information can be used to evaluate contractor proposals, make cost projections of a given program, develop historical data bases to develop statistical techniques, and make independent cost analysis of new acquisitions. This transaction set can be used to convey proposed, initial, progress, updated, or final (end of contract) cost information.

Data contents of the Real Estate Title Evidence Transaction Set (197) for use within the context of an Electronic Data Interchange (EDI) environment. This standard can be used to transfer the data contained in standard Title Reports, Title Commitments, and Title Policy Forms of the American Land Title Association, as well as the corresponding State Forms or other title evidence formats indicating the results of the title examination process.

Data contents of the Loan Verification Information Transaction Set (198) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to request, validate, or exchange standard loan verification information among entities involved in the loan lifecycle. These entities may include lenders, employers, depository institutions, credit agencies, investors, mortgage insurance companies, and so on.

Data contents of the Real Estate Settlement Information Transaction Set (199) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to transfer real estate settlement information among mortgage lenders, real estate closing agents, and other interested parties.

Data contents of the Mortgage Credit Report Transaction Set (200) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to transmit the data that comprises a mortgage credit report. It is the electronic response to the Mortgage Credit Report Order Transaction Set (833).

Data contents of the Residential Loan Application Transaction Set (201) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to transfer the data contained in the Uniform Residential Loan Application between mortgage lenders, mortgage service vendors, insurance companies, credit reporting agencies and secondary market organizations.

Data contents of the Secondary Mortgage Market Loan Delivery Transaction Set (202) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to report mortgage loan information (i.e., borrower, property, underwriting information, etc.) among mortgage lenders, mortgage service vendors, and secondary mortgage market organizations.

Data contents of the Secondary Mortgage Market Investor Report Transaction Set (203) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used for the transfer and reporting of mortgage servicing information between mortgage servicers, mortgage service bureaus, and secondary mortgage market organizations.

Data contents of the Motor Carrier Load Tender Transaction Set (204) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to allow shippers or other interested parties to offer (tender) a shipment to a full load (truckload) motor carrier including detailed scheduling, equipment requirements, commodities, and shipping instructions pertinent to a load tender. It is not to be used to provide a motor carrier with data relative to a LessthanTruckload bill of lading, pickup notification, or manifest.

Data contents of the Mortgage Note Transaction Set (205) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by mortgage originators, settlement agents, warehouse lenders, document custodians, secondary market entities and other industry participants to exchange the data comprising the mortgage note and mortgage characteristics.

Data contents of the Real Estate Inspection Transaction Set (206) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by mortgage lenders, insurance companies or others to initiate, modify or cancel a site inspection by a field service organization, home inspection company, insurance vendor or other industry participant. It can also be used by a field service organization, home inspection company, insurance inspection vendor, or other industry participant to report the results of a site inspection.

Data contents of the Motor Carrier Freight Details and Invoice Transaction Set (210) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide detail information for charges for services rendered by a motor carrier. It is used both as a motor carrier invoice to request payment or as details pertaining to motor freight shipment(s) charges.

Data contents of the Motor Carrier Bill of Lading Transaction Set (211) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to allow shippers or other parties, responsible for contracting with a motor carrier, to provide a legal bill of lading for a shipment. It is not to be used to provide a motor carrier with data relative to a load tender, pickup manifest, or appointment scheduling.

Data contents of the Motor Carrier Delivery Trailer Manifest Transaction Set (212) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to allow motor carriers to provide consignees or other interested parties with the contents of a trailer, containing multiple shipments, that has been tendered for delivery. It is not to be used to provide the recipient with data relative to a full truckload shipment.

Data contents of the Motor Carrier Shipment Status Inquiry Transaction Set (213) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to request shipment status from a motor carrier. The requestor may be a shipper or consignee.

Data contents of the Transportation Carrier Shipment Status Message Transaction Set (214) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by a transportation carrier to provide shippers, consignees, and their agents with the status of shipments in terms of dates, times, locations, route, identifying numbers, and conveyance.

Data contents of the Motor Carrier Pickup Manifest Transaction Set (215) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to allow shippers, or other parties, to provide a motor carrier with a manifest of all of the shipments tendered to a carrier. It is not to be used to provide a motor carrier with data relative to a load tender, legal bill of lading, pickup notification, or appointment scheduling.

Data contents of the Motor Carrier Shipment Pickup Notification Transaction Set (216) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to allow shippers or other interested parties to provide a motor carrier with notification that a shipment is available for pickup. It is not to be used to provide a motor carrier with data relative to a legal bill of lading, rating, pricing, or appointment scheduling.

Data contents of the Motor Carrier Loading and Route Guide Transaction Set (217) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide interested parties with a motor carrier's loading instructions and/or routing guide. A transmission may include a list of the motor carrier's terminals, a list of all points served, or a matrix of all points served showing the advertised service times. The motor carrier may also indicate its breakbulk terminal(s) to be used for each point for loading purposes.

Data contents of the Motor Carrier Tariff Information Transaction Set (218) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for the interchange of processable data extracted from a motor carrier's tariff or pricing information database. It can be used by any producer of motor carrier tariffs or rates to transmit tariff and rate information to shippers or other interested parties. This transaction set is not intended to transmit a complete, legal tariff; rather, it is intended to provide rate information upon the request of shippers or other interested parties. Users of this data should continue to rely on legally filed tariffs as the basis of the legal agreement between themselves and their carriers.

Data contents of the Logistics Service Request Transaction Set (219) for use within the context of an Electronic Data Interchange (EDI) environment. This set can be used by a shipper to transmit data to a logistics related organization to provide order detail relevant to upcoming transportation requirements.

Data contents of the Logistics Service Response Transaction Set (220) for use within the context of an Electronic Data Interchange (EDI) environment. This set can be used by a logistics related organization to transmit data to a shipper in response to a logistics service request.

Data contents of the Cartage Work Assignment Transaction Set (222) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to provide the cartage carrier with placement, rating, and scheduling information pertinent to the movement of equipment by a cartage carrier.

Data contents of the Consolidators Freight Bill and Invoice Transaction Set (223) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by a freight consolidator to transmit invoice and freight bill data to the appropriate party. The freight bill services may be provided by the consolidator or a motor carrier unrelated to the consolidator. This transaction shall not be used to transmit freight bill data without consolidator's invoice data.

Data contents of the Motor Carrier Summary Freight Bill Manifest Transaction Set (224) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to transmit multiple freight bills at the summary level to a single payor.

Data contents of the Response to a Cartage Work Assignment Transaction Set (225) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by a cartage carrier to provide for customary and established business practice relative to a response to a cartage work assignment. The transaction set includes either acceptance or decline of the work assignment and any related reference numbers.

This X12 Transaction Set contains the format and establishes the data contents of the Trailer Usage Report Transaction Set (227) for use within the context of an Electronic Data Interchange (EDI) environment. This standard can be used to transmit information related to the shipper's, consignee's, or third party's planned usage of a trailer supplied by a motor carrier for trailer inventory reporting purposes only. This transaction set is used to provide the motor carrier with information related to the loading of a trailer, rejection of the trailer, and reported location. It is not to be used to provide a motor carrier with data relative to a load tender or pickup notification and requires no response. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

This X12 Transaction Set contains the format and establishes the data contents of the Motor Carrier Package Status Transaction Set (240) for use within the context of an Electronic Data Interchange (EDI) environment. This standard can be used to provide the status of a package, packages, or group of packages considered a shipment by a motor carrier. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

Data contents of the Data Status Tracking Transaction Set (242) within the context of an Electronic Data Interchange (EDI) environment. This management transaction set is the vehicle by which the transmission status information is conveyed by a service request handler to the interchange sender, interchange receiver, or both; it can be used to provide status information regarding interchange as it flows from an interchange sender through one or more service request handlers to an interchange receiver during its transmission cycle. It can be used by the interchange sender or interchange receiver to request from a service request handler ad hoc or periodic reports containing status information regarding interchanges.

Data contents of the Product Source Information Transaction Set (244) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction can be used to transmit classification and categorization data of company's products, processes, and facilities to existing and prospective trading partners or listing agencies.

This X12 Transaction Set (DSTU) contains the format and establishes the data content of the Real Estate Tax Response Transaction Set (245) for use within an Electronic Data Interchange (EDI) environment. This transaction set can be used to respond to requests for information, modifications to loan status, complete property tax data necessary for paying tax bills, or cancellations of real estate property data. This transaction set facilitates the transfer of property tax information among real estate industry participants. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

Data contents of the Account Assignment/Inquiry and Service/Status Transaction Set (248) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used for twoway, multitransactional purposes of assigning accounts for collection, reporting status inquiries and inquiry responses and to update accounts between entities.

Data contents of the Animal Toxicological Data Transaction Set (249) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to exchange animal toxicology data collected from studies conducted on pesticides, drugs, or other substances. This transaction set accommodates the lowest reportable level of individual animal toxicology data for transfer between industry and the government, within industry itself, and between government agencies. The transaction set will enable the exchange of both definitive end points or inlife study data, as well as observational or opinion type data.

Data contents of the Purchase Order Shipment Management Document Transaction Set (250) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to allow a retailer or manufacturer to communicate purchase order data, to a transportation provider, for the purpose of managing the purchase order cycle from the time of pickup request through delivery.

Data contents of the Pricing Support Transaction Set (251) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to request or transmit budget or actual data for labor and overhead rates, factors, and other supporting data for a specified period of time. This bidirectional transaction set can stand alone, or can be used to support the Contract Pricing Proposal (805) Transaction Set.

Data contents of the Insurance Producer Administration Transaction Set (252) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set is used to transmit insurance producer information (licensing and appointment data, background information, etc.) among insurance companies and insurance distributors such as agents, brokers, and their organizations.

Data contents of the Underwriting Information Services Transaction Set (255) for use within the context of an Electronic Data Interchange (EDI) environment. This standard can be used to request specific services from information providers in support of the underwriting process. In addition, the standard can be used between trading partners to request/receive status information on outstanding requests.

Data contents of the Periodic Compensation Transaction Set (256) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set is used to report compensation data, including compensation amounts, compensation earned, compensation paid, adjustments and balances.

If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

Data contents of the Application for Mortgage Insurance Benefits Transaction Set (260) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by mortgage lenders to file claims with both government agencies and private mortgage insurers in the event that defaults or foreclosure activity allow for the collection of a thirdparty guarantee/insurance benefit. The information in a standard format will allow all mortgage insurance claim payments to be requested similarly, whether they be to an investor, insurer, or guarantor.

Data content of the Real Estate Information Request Transaction Set (261) for use within an Electronic Data Interchange (EDI) environment. This transaction set can be used to initiate, modify or cancel a request for real estate information. This transaction set will be used to transfer information among real estate industry participants.

Data contents of the Real Estate Information Report Transaction Set (262) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used for the transfer and reporting of real estate information among real estate industry participants.

Data contents of the Residential Mortgage Insurance Application Response Transaction Set (263) for use within the context of an Electronic Data Interchange (EDI) environment. This standard is used by a mortgage insurance company to communicate the receipt and disposition of a Residential Mortgage Insurance Application Transaction Set (872). It will be used to provide the mortgage originator with the results of the insurance application and, if accepted, will provide basic information about the insurance coverage. It can also be used to confirm certification of coverage. It is not intended to replace the legal commitment (Certificate of Coverage of Insurance) which will continue to be delivered in its current form.

Data contents of the Mortgage Loan Default Status Transaction Set (264) for use within an Electronic Data Interchange (EDI) environment. This transaction set will allow all notifications of mortgage loan default/foreclosure status to be filed similarly, whether they be to an insurer, guarantor, investor, or servicer. This transaction set can be used to submit notification of delinquent mortgage loans that could potentially result in foreclosure activity leading to the collection of a thirdparty guarantee/insurance benefit. This transaction set can also be used to file default status reports, as well as foreclosure and bankruptcy information with servicers, attorneys, trustees, government agencies, private mortgage insurers and investors.

Data contents for the Real Estate Title Insurance Services Order (265) Transaction Set for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by a real estate agent, mortgage lender, or other real estate company to order, update, or cancel title services from a title insurance services company. This standard can also be used by the title services company to return title information to the party originating the order. This transaction set replaces the paper forms used to request services such as title searches and insurance, and replaces mortgage closing documents.

Data contents of the Mortgage or Property Record Change Notification Transaction Set (266) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by financial institutions such as Mortgagees, Lienholders, and Lessors to inform interested parties such as Insurers, Investors, and Taxing Authorities of mortgage or property record changes. This transaction set is intended to be used by financial institutions to communicate change notifications, such as the sale of mortgages, assumptions, transfers, and terminations of interest.

Data contents of the Individual Life, Annuity and Disability Application Transaction Set (267) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set is used to transmit new business application information among distributors (agents, broker/dealers, etc.), insurance companies and reinsurance companies for the purpose of underwriting an individual life, annuity or disability contract.

Data contents of the Annuity Activity Transaction Set (268) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set is used to convey annuity account activity from annuity providers to distributors (e.g., broker/dealers, financial planners, banks, savings and loans) for the purpose of communicating account positions and transaction activity.

This X12 Transaction Set contains the format and establishes the data contents of the Health Care Benefit Coordination Verification Transaction Set (269) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to transmit Health Care Benefit coordination information such as claim identification, previous adjudication details, and adjudication verification from one Health Care Payer to another. The transaction can be used as a notification of benefit coordination information, a request for verification of benefit coordination information, or as the response to a verification of benefit coordination information request. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

Data contents of the Eligibility, Coverage or Benefit Inquiry Transaction Set (270) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to inquire about the eligibility, coverages or benefits associated with a benefit plan, employer, plan sponsor, subscriber or a dependent under the subscriber's policy. The transaction set is intended to be used by all lines of insurance such as Health, Life, and Property and Casualty.

Data contents of the Eligibility, Coverage or Benefit Information Transaction Set (271) for use within the context of an Electronic Data Interchange (EDI) environment. \This transaction set can be used to communicate information about or changes to eligibility, coverage or benefits from information sources (such as insurers, sponsors, payors) to information receivers (such as physicians, hospitals, repair facilities, third party administrators, governmental agencies). This information includes but is not limited to: benefit status, explanation of benefits, coverages, dependent coverage level, effective dates, amounts for coinsurance, copays, deductibles, exclusions and limitations.

Data contents of the Property and Casualty Loss Notification Transaction Set (272) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide loss information flow between property and casualty (P & C) insurance companies, agents, service providers, and industry bureaus. Expected users are property and casualty insurance companies, agents, service providers (e.g., adjusters or glaziers), and industry bureaus (e.g., National Insurance Crime Bureau (NICB) or the Index System). Business functions consist of loss notification, work assignments and reporting.

Data contents of the Insurance/Annuity Application Status Transaction Set (273) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by insurance providers to inform their trading partners of the current status of a life insurance or annuity application during the underwriting process.

This X12 Transaction Set contains the format and establishes the data contents of the Healthcare Provider Information Transaction Set (274) for use within the context of an Electronic Data Interchange (EDI) environment. This standard can be used to exchange demographic and educational/professional qualifications about healthcare providers between providers, provider networks or any other entity that maintains or verifies healthcare provider information. Such exchanges include the transmitting, inquirying, or responding to an inquiry. Healthcare provider information is routinely exchanged for the purpose of 1) maintaining provider data bases for claim adjudication, provider directories, patient referrals, and reporting provider information, 2) submitting an application to join a provider organization or provider network such as, but not limited to, a hospital, preferred provider organization (PPO) or health maintenance organization (HMO), and 3) verifying credentials such as educational/professional qualifications, licenses, and malpractice coverage/history. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

Data contents of the Patient Information Transaction Set (275) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to communicate individual patient information requests and patient information (either solicited or unsolicited) between separate health care entities in a variety of settings to be consistent with confidentiality and use requirements. Patient information consists of demographic, clinical, and other supporting data.

Data contents of the Health Care Claim Status Request Transaction Set (276) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by a provider, recipient of health care products or services, or their authorized agent to request the status of a health care claim or encounter from a health care payer. This transaction set is not intended to replace the Health Care Claim Transaction Set (837), but rather to occur after the receipt of a claim or encounter information. The request may occur at the summary or service line detail level.

Data contents of the Health Care Claim Status Notification Transaction Set (277) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by a health care payer or authorized agent to notify a provider, recipient, or authorized agent regarding the status of a health care claim or encounter or to request additional information from the provider regarding a health care claim or encounter. This transaction set is not intended to replace the Health Care Claim Payment/Advice Transaction Set (835) and therefore, will not be used for account payment posting. The notification may be at a summary or service line detail level. The notification may be solicited or unsolicited.

Data contents of the Health Care Services Review Information Transaction Set (278) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to transmit health care service information, such as subscriber, patient, demographic, diagnosis or treatment data for the purpose of request for review, certification, notification or reporting the outcome of a health care services review. Expected users of this transaction set are payors, plan sponsors, providers, utilization management and other entities involved in health care services review.

Data contents of the Voter Registration Information Transaction Set (280) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to submit voter registration application information and to transmit information regarding a previously registered voter and changes to such information.

This X12 Transaction Set contains the format and establishes the data contents of the Tax or Fee Exemption Certification Transaction Set (283) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be transmitted by buyer to seller to certify as to the tax exempt status of one or more business transactions, and from a seller to a Taxing Authority to verify that proper exemption certification has been obtained for the transaction(s). Exemption certification protects the claim of exemption from various taxes and fees for buyers and sellers. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

This X12 Transaction Set contains the format and establishes the data contents of the Commercial Vehicle Safety Reports Transaction Set (284) for use within the context of an Electronic Data Interchange (EDI) environment. This bi-directional transaction set can be used by authorized parties to electronically request and send reports on information related to the safe operation of commercial road vehicles, such as inspection reports, safety and compliance review reports, and hazardous material incident reports. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

Data contents of the Commercial Vehicle Safety and Credentials Information Exchange Transaction Set (285) for use within the context of an Electronic Data Interchange (EDI) environment. This standard can be used by enforcement officials, government administrators and other authorized parties to electronically ask for information on the safety performance, regulatory compliance and credentials status of commercial motor vehicles, carriers and drivers. It can also be used by sources that maintain such data to respond to such requests.

Data contents of the Commercial Vehicle Credentials Transaction Set (286) for use within the context of an Electronic Data Interchange (EDI) environment. This bidirectional transaction set can be used by owners, lessees, and drivers of commercial motor vehicles to electronically apply for credentials necessary to legally operate those vehicles, and by authorizing jurisdictions to electronically transmit credential data to applicants and other authorized entities.

Data contents of the Wage Determination Transaction Set (288) for use within the context of an Electronic Data Interchange (EDI) environment. This bidirectional transaction set can be used to request and respond to requests for wage information such as prevailing wage rates. This information can be determined by occupational categories, geographical area, nature of the workforce, and contract status.

Data contents of the Cooperative Advertising Agreements Transaction Set (290) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set is used to initiate, review, and conclude a cooperative advertising agreement. It is designed to be used iteratively. The transaction set can be used to request advertising support, provide guidelines for local advertising, provide cost or budget estimates, issue a cooperative advertising commitment, and provide the actual expenses.

Data contents of the Reservation (Booking Request) (Ocean) Transaction Set (300) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by a shipper or a forwarder to reserve space, containers and equipment for transport by ocean vessel.

Data contents of the Confirmation (Ocean) Transaction Set (301) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide all the information necessary for an ocean carrier to confirm space, container, and equipment availability in response to the Reservation (Booking Request) (Ocean) Transaction Set (300); or to notify other parties such as terminal operators or other ocean carriers.

Data contents of the Booking Cancellation (Ocean) Transaction Set (303) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide all the information necessary for a shipper or forwarder to cancel a previous booking request.

Data contents of the Shipment Instructions Transaction Set (304) for use within the context of an Electronic Data Interchange (EDI) environment. When this transaction set is transmitted to an ocean carrier, it provides all the information necessary to prepare and distribute a contract of carriage such as an ocean bill of lading, sea waybill, and other shipping documents. When this transaction set is transmitted to a freight forwarder or customs broker, it provides for the transmission of shipping and financial information required by the forwarder or customs broker to move cargo and provide the services requested.

Data contents of the U.S. Customs Manifest Transaction Set (309) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by carriers, terminal operators, port authorities, or service centers to provide U.S. Customs with manifest data on cargo arriving in or departing from the U.S. on oceangoing vessels, railroad trains, or other types of conveyances. The transaction set can be also used by carriers to provide terminal operators, port authorities, or service centers with manifest data on cargo arriving at their facilities via the conveyances mentioned above.

Data contents of the Freight Receipt and Invoice (Ocean) Transaction Set (310) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide ocean bill of lading information. It is sent by ocean carriers to interested parties and can be used as the receipt for the shipment; to substitute for a paper bill of lading where the parties have agreed that a paper bill of lading is not necessary; to allow shipper or forwarder to verify bill of lading information before an original is printed and released; for information purposes, i.e., as a bill of lading copy; by the carrier to convey manifest information to a terminal operator; and as an invoice for freight.

Data contents of the Canadian Customs Information Transaction Set (311) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set provides all information necessary for an ocean or rail carrier or freight forwarder to report input and export conveyance and consignment information to Canadian Customs.

Data contents of the Arrival Notice (Ocean) Transaction Set (312) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide all the information necessary for a consignee to receive a shipment including customs, payments due, and estimated arrival date and time of shipment.

Data contents of the Shipment Status Inquiry (Ocean) Transaction Set (313) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide all the information necessary for an authorized party to an ocean shipment to inquire of the ocean carrier as to the status of a shipment.

Data contents of the Status Details (Ocean) Transaction Set (315) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide all the information necessary to report status or event details for selected shipments or containers. It is intended to accommodate the details for one status or event associated with many shipments or containers, as well as more than one status or event for one shipment or container.

Data contents of the Delivery/Pickup Order Transaction Set (317) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by importers or their agents to provide marine terminal operators with orders for the delivery or pickup of goods.

Data contents of the Terminal Information Transaction Set (319) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by terminal operators to provide shipment arrival event information to authorized parties. It can be used to transmit information such as arrival of the shipment, availability for pickup, or the actual pickup of the shipment. Some of the authorized parties to shipment are customs house brokers, freight forwarders, or consignees.

Data contents of the Terminal Operations and Intermodal Ramp Activity Transaction Set (322) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide all the information necessary for a terminal operation, port authority or intermodal ramp to communicate terminal and intermodal ramp activities (e.g., "ingates" and "outgates") to authorized parties to a shipment.

Data contents of the Vessel Schedule and Itinerary (Ocean) Transaction Set (323) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide all the information necessary for an ocean carrier to communicate the schedule and itinerary of an ocean vessel to interested parties.

Data contents of the Vessel Stow Plan (Ocean) Transaction Set (324) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide all the information relative to the stowage of equipment and cargo on a vessel.

Data content of the Consolidation of Goods in Container Transaction Set (325) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set is used to provide information on the goods loaded into a container. It is sent by a consolidator to the deconsolidator or to the consignee.

Data contents of the Consignment Summary List Transaction Set (326) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set is used to provide a list to a customer of all consignments for which an ocean carrier has accepted or is expected to accept responsibility for the transport of goods. It is sent by an ocean carrier or consolidator to a shipper, freight forwarder, consignee, customs broker, or any other interested party.

Data contents of the U.S. Customs Status Information Transaction Set (350) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by the U.S. Customs Service (USCS) to supply carriers, terminal operators, port authorities and service providers with cargo release and cargo hold information for import shipments. It can also be used by the USCS to provide exporters or their agents, carriers, and service providers with information pertaining to export shipments.

Data contents of the U.S. Customs Carrier General Order Status Transaction Set (352) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by carriers, terminal operators, port authorities, or service centers to provide U.S. Customs or consignees with bill of lading status information for cargo in or about to go into "General Order" and entry and release information.

Data contents of the U.S. Customs Events Advisory Details Transaction Set (353) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by carriers to notify U.S. Customs of events concerning cargo moving inbond, or of conveyance arrivals or departures. These events include the arrival of containers, or cargo covered by individual ocean bills of lading or inbond numbers, which have moved inbond to an inland destination or which have been exported from the United States. Carriers can also use this transaction set to notify U.S. Customs of the arrival or departure of a conveyance for which an electronic manifest has been filed and for the transfer of custodial liability when an inbond movement involves multiple legs.

Data contents of the U.S. Customs Automated Manifest Archive Status Transaction Set (354) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by U.S. Customs to inform carriers, terminal operators, port authorities, and service centers that the manifest for a specific vessel or voyage is going to be removed from the system. This means that either all bills of lading on a manifest have been reconciled (or closed) or that a number of them are still open and will be reconciled manually.

Data contents of the U.S. Customs Acceptance/Rejection Transaction Set (355) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by U.S. Customs to report errors and discrepancies discovered in the U.S. Customs transaction sets to ocean carriers, terminal operators, port authorities and service centers.

Data contents of the U.S. Customs Permit to Transfer Request Transaction Set (356) for use within the context of an Electronic Data Interchange (EDI) environment. It is sent by requesting trade entities to U.S. Customs to request a Permit To Transfer (PTT).

Data contents of the U.S. Customs InBond Information Transaction Set (357) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by transportation carriers, terminal operators, port authorities, and service centers to request authorization for inbond movements and to add additional legs on to preexisting inbond movements.

Data contents of the U.S. Customs Consist Information Transaction Set (358) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by transportation carriers, terminal operators, port authorities and service centers to provide a list of bills of lading to be carried on a specific conveyance and trip number for which an electronic manifest has been previously filed.

Data contents of the Carrier Interchange Agreement (Ocean) Transaction Set (361) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide all the information necessary for an ocean carrier to tell a terminal operator if motor carriers are authorized to carry its cargo.

Data contents of the Cargo Insurance Advice of Shipment Transaction Set (362) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by shippers to notify their cargo insurance company of a shipment(s) of merchandise insured under their cargo policy.

Data contents of the Rail Carrier Shipment Information Transaction Set (404) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit railcarrierspecific bill of lading information to a railroad. It is the initial tender of a shipment between a consignor and a rail carrier and can be used as notification of equipment release and/or a legal bill of lading.

Data contents of the Rail Carrier Freight Details and Invoice Transaction Set (410) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide detailed information of charges associated with a rail movement. The information is provided by a rail carrier and is sent to the freight payer.

This X12 Transaction Set contains the format and establishes the data contents of the Trailer or Container Repair Billing Transaction Set (412) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set will provide the ability to electronically Invoice the responsible party for repairs to trailers and containers being transported by railroads. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

Data contents of the Rail Carhire Settlements Transaction Set (414) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for the exchange of Carhire Settlement data including, but not limited to, the following: Current Settlements, First Adjustment Settlements (no penalty), Prior Settlements (penalty on foreign equipment), Summary Transactions and Reclaim Transactions.

Data contents of the Rail Carrier Waybill Interchange Transaction Set (417) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide the rail carrier with detailed movement instructions pertinent to a rail carrier shipment and is used by all Class I rail carriers in the United States and Canada.

Data contents of the Rail Advance Interchange Consist Transaction Set (418) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit advance information on equipment being interchanged to a connection rail carrier, from a consignor or to a consignee.

Data contents of the Advance Car Disposition Transaction Set (419) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide the receiving rail carrier with advance notification of cars being offered for interchange directly or via a switching carrier, to allow for disposition prior to the actual interchange.

Data contents of the Car Handling Information Transaction Set (420) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide a carrier which is going to receive a rail car from another rail carrier the means to redirect a home route or preblock a rail car prior to actual interchange.

Data contents of the Estimated Time of Arrival and Car Scheduling Transaction Set (421) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to allow railroads to exchange car scheduling and estimated time of arrival data between carriers.

Data contents of the Shipper's Car Order Transaction Set (422) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to allow a rail carrier or shipper to order required equipment relative to transportation needs.

Data contents of the Rail Industrial Switch List Transaction Set (423) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set is intended solely for producing switch lists and equipment notifications. It is not for recording release times and the ordering of empty equipment. It is also to provide switching information agreed to between customer and carrier to show car identity, placement, pull and destination information.

This X12 Transaction Set contains the format and establishes the data contents of the Rail Carrier Services Settlement Transaction Set (424) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to provide detailed information of charges associated with rail services. The information is provided by a rail carrier and is sent to a rail carrier on whose behalf the services were performed. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

Data contents of the Rail Waybill Request Transaction Set (425) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to request a copy of a revenue or movement waybill from the origin or previous rail carrier. This will be used only when the requesting carrier is unable to locate the original transmission.

Data contents of the Rail Revenue Waybill Transaction Set (426) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to respond to a request for a rail revenue waybill. Revenue waybill information includes movement, rates, and charges information required to collect revenue from the paying party or parties.

Data contents of the Railroad Retirement Activity Transaction Set (429) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set provides the sender with the capability to transmit information pertaining to the processing of railroad employee sickness and unemployment benefit claims against retirement funds. This transaction set will support the transfer of claim information from the Retirement Board to carriers as well as supporting corresponding response from a carrier to the Retirement Board.

Data contents of the Railroad Station Master File Transaction Set (431) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set will be used by the Association of American Railroads (AAR) and the rail carriers to apply and disseminate information concerning the railroad stations. Rail carriers report to the AAR the addition or deletion of, or changes to, the list of stations they serve as updates to the centrally maintained master file. The AAR in turn provides all updates to the rail carriers and other subscribers to the system.

Data contents of the Rail Deprescription Transaction Set (432) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by fleet owners to deprescribe their rail cars, and distribute new rates to other participants.

Data contents of the Railroad Reciprocal Switch File Transaction Set (433) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide electronic updates for the reciprocal switch status (open, closed or conditionally open) of railroad customers.

Data contents of the Railroad Mark Register Update Activity Transaction Set (434) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to allow the Railroad Industry Reference File central site to communicate Mark Register update activity to subscribers. This information includes the assignment and expiration of railroad reporting marks, Standard Carrier Alpha Codes (SCAC) and unit initials.

Data contents of the Standard Transportation Commodity Code Master Transaction Set (435) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set is used to transmit Standard Transportation Commodity Codes and associated information.

Data contents of the Locomotive Information Transaction Set (436) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to provide the rail carriers with locomotive status and location information.

Data contents of the Railroad Junctions and Interchanges Activity Transaction Set (437) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set allows the Railroad Industry Reference File central site to communicate junction and interchange update activity to subscribers. This information would include the creation and expiration of interchange agreements.

Data contents of the Shipment Weights Transaction Set (440) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit weights and scale information between any two interested parties.

Data contents of the Railroad Event Report Transaction Set (451) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by a service provider to communicate activities associated with the movement of goods.

Data contents of the Railroad Problem Log Inquiry or Advice Transaction Set (452) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used in the following ways: (1) for a service provider or sponsor to communicate and register a problem; (2) for a party to a movement event to request information about problem logs created; and (3) to provide problem log data in response to a request.

Data contents of the Railroad Service Commitment Advice Transaction Set (453) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by a Rail Interline Service Management shipment sponsor to communicate service commitment details to transportation service providers.

Data contents of the Railroad Service Commitment Advice Transaction Set (453) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by a Rail Interline Service Management shipment sponsor to communicate service commitment details to transportation service providers.

Data contents of the Railroad Equipment Inquiry or Advice Transaction Set (456) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used in the following ways: (1) for a provider of equipment or transportation service to provide information to a qualified customer; (2) for a qualified customer to inquire as to the location of equipment or shipments; and (3) for one company to provide another company with equipment or shipment information.

Data contents of the Railroad Equipment Inquiry or Advice Transaction Set (456) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used in the following ways: (1) for a provider of equipment or transportation service to provide information to a qualified customer; (2) for a qualified customer to inquire as to the location of equipment or shipments; and (3) for one company to provide another company with equipment or shipment information.

Data contents of the Rail Rate Reply Transaction Set (463) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to reply to a Rail Rate Transaction from the receiver's application process based on data content or business rules. This transaction set is used as an application acceptance, application rejection or to indicate that no data was found for a request.

Data contents of the Rate Request Transaction Set (466) for use within the context of Electronic Data Interchange (EDI) environment. The transaction set can be used to request rail rates applicable to specific movements.

Data contents of the Rate Docket Journal Log Transaction Set (468) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit comments about rates contained in a rate docket.

Data contents of the Rail Clearance Transaction Set (470) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide the means to request or respond to clearances for dimensional and heavy shipments by Rail.

Data contents of the Rail Route File Maintenance Transaction Set (475) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set is used to distribute route file updates of the rail industry route file.

Data contents of the Ratemaking Action Transaction Set (485) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit ratemaking activities related to concurrence, factor change, publisher change, or proposal rejection or trace.

Data contents of the Rate Docket Expiration Transaction Set (486) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit the expiration date of a docket.

Data contents of the Rate Group Definition Transaction Set (490) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to define and name a group of elements (patron, geography, commodity, shipment conditions) pertinent to a tariff.

Data contents of the Miscellaneous Rates Transaction Set (492) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit rail rates for demurrage, detention, and storage.

Data contents of the Rail Scale Rates Transaction Set (494) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit rail scale rate tables.

Data contents of the Medical Event Reporting Transaction Set (500) for use within the context of an Electronic Data Interchange (EDI) environment. This standard can be used to make voluntary, mandatory, baseline, annual and semiannual reports on medication and medical device adverse effects and product problems.

Data contents of the Vendor Performance Review Transaction Set (501) for use within the context of an Electronic Data Interchange (EDI) environment. This bidirectional transaction set can be used to request and receive past performance information. The transaction set may also be used to challenge the validity of the information received and to respond to challenges. This transaction set can be used by selling parties to request, receive, and challenge historic information regarding their performance on contracts in the areas of capability, eligibility, quality assurance, and delivery performance.

Data contents of the Pricing History Transaction Set (503) for use within the context of an Electronic Data Interchange (EDI) environment. This bidirectional transaction set can be used by a purchasing party or vendor to request pricing history information for an item. The transaction set can also be used to respond to a request for pricing history information.

Data contents of the Clauses and Provisions Transaction Set (504) for use within the context of an Electronic Data Interchange (EDI) environment. This bidirectional transaction set can be used to request or respond to requests for clauses and special provisions.

Data contents of the Requisition Transaction Set (511) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to requisition needed material and equipment from a supply distribution system for immediate consumption or stockage against projected requirements. The originator can also use this transaction set to inquire about the status of, amend, or terminate the original requisition.This transaction set may be used to convey a description and quantity of the required material, delivery and billing information, and other logistics information necessary to evaluate and meet the material needs of the originator. This transaction set is not used to establish a contractual relationship between trading partners, and may precede the use of a purchase order.

Data contents of the Material Obligation Validation Transaction Set (517) for use within the context of an Electronic Data Interchange (EDI) environment. The material obligation validation transaction set may be used to: (1) verify the continued need for open orders, (2) confirm open order quantities and order priority, (3) request reinstatement of erroneously cancelled open orders, and (4) validate Government Furnished Material (GFM) orders. The transaction set may convey a description of the material, the urgency of need associated with the transaction and quantity of required material. This transaction set is bidirectional between trading partners.

Data contents of the Income or Asset Offset Transaction Set (521) for use within the context of an Electronic Data Interchange (EDI) environment. This bidirectional transaction set can be created by an agency or entity to require an employer or asset holder to withhold and deliver assets or income on behalf of a person or entity to whom they are owed, as in a levy, lien, or garnishment. It can also be used to confirm or modify a prior notification. This transaction set can also be used by the employer or third party to report the ability to comply with the requirement and the terms of that compliance and may be used to initiate an electronic funds transfer in order to satisfy the requirement.

Data contents of the Material DueIn and Receipt Transaction Set (527) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide advanced notification of scheduled material receipts, to report receipts, and to inquire about the status of receipt reporting. This transaction set may be used to convey a description of the material, receiving conditions and quantities, necessary contract information, and other logistics information. This transaction set is bidirectional between trading partners.

Data contents of the Logistics Reassignment Transaction Set (536) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set is used to provide information necessary to transfer management responsibility between an old and new managing organization. This transaction set may be used to convey a description and quantity of the transferred material, specific inventory locations, product quality information, technical data, open contract information, demand data, procurement history, and other information necessary for the new managing organization to evaluate and meet the material needs of customers.

Data contents of the Notice of Employment Status Transaction Set (540) for use within the context of an Electronic Data Interchange (EDI) environment. This standard can be used to notify government agencies or authorized parties of the identity of newly hired employees, of the termination of employees, or to confirm employment status. The transaction set may also be used to convey this information between authorized parties, or to convey responses from the agency if necessary.

Data contents of the Contract Abstract Transaction Set (561) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to abstract a new contract, abstract a change in terms of a previously abstracted contract, or to correct a previously transmitted abstract. This bidirectional transaction set includes the information necessary to administer a contract, including modifications and corrections to that contract, and provides an acknowledgment mechanism to enable management of the contract administration process. This transaction set is typically used internally within a business entity as a postaward management report, when the purchasing and contract administration functions are separated within that entity.

Data contents of the Contract Completion Status Transaction Set (567) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to report administrative closure status on completed contracts. The originator can use this transaction set to close contract files, to indicate why contract files will not be closed within established milestones, or to extend contract closeout milestone dates. This transaction set may be used to convey contract summary data, financial information, dates pertinent to the administrative closing of a contract file, and logistics information necessary to evaluate contract closeout status.

Data contents of the Contract Payment Management Report Transaction Set (568) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to enable the transmission of a management report to provide the details of payments and collections made against funds obligated on contracts, orders, and other services.

Data contents of the U.S. Customs Export Shipment Information Transaction Set (601) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by exporters or their agents, carriers, and service providers to transmit export shipment information to the U.S. Customs Service (USCS).

Data contents of the Transportation Services Tender Transaction Set (602) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to communicate rates and tender information. The transaction set permits the transmission of one docket containing all data for tender, such as names of parties, commodities, location points, shipment conditions, notes, rates (pointtopoint, scale), and other charges. This transaction set is used by a carrier to submit a new tender or amendments to an existing tender. This transaction set is also used by the government to distribute transportation rates to interested parties. This transaction set fulfills the U.S. government requirements for tender offers but is not restricted to government use only. This transaction set is multidirectional between trading parties.

Data contents of the Excavation Communication Transaction Set (620) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to communicate information related to excavations for the purposes of attaining either clearance for the excavation or to have the potentially impacted parties locate any affected assets and supervise the excavation process or both.

This Draft Standard for Trial Use contains the format and establishes the data contents of the Intermodal Ramp Activity Transaction Set (622) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit specific intermodal ramp facility activities to consignors and other carriers or shippers' agents, when the activity takes place. This activity includes in-gate, out-gate, ramp, and de-ramp. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

Data content of the Well Information Transaction Set (625) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set facilitates the exchange of engineering, geological and environmental information related to nonfinancial well activities. The transaction set can be used between private industry trading partners to relay information about joint venture well activities or between private industry and government agencies. This transaction set shall not be used to relay financial information such as regulatory royalty payment information or costs associated with well activities.

Data data contents of the Maintenance Service Order Transaction Set (650) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set provides a uniform, singular medium for the exchange of maintenance related information among organizations involved in the reporting, requesting, scheduling, planning, estimating, coordinating and performing of maintenance actions. It provides the structure to convey maintenancerelated information, including maintenance action directives, maintenance actions, cost estimates, maintenance action assignments, maintenance action status, and completion reports. This transaction set can be used in a bidirectional environment alone or in conjunction with the Project Schedule Reporting Transaction Set (806) to link schedule and maintenance action information as well as with the Specifications/Technical Information Transaction Set (841) to link maintenancerelated, media independent, technical data.

Data contents of the Intermodal Group Loading Plan Transaction Set (715) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by intermodal or domestic shippers and carriers to provide detailed information on the stowage of containers and other equipment aboard a train. The stowage information may be planned or actual and may be by block or by railcar.

This X12 Transaction Set contains the format and establishes the data contents of the Request for Routing Instructions Transaction Set (753) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to request routing instructions and provide general information about merchandise that is ready to be shipped. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

This X12 Transaction Set contains the format and establishes the data contents of the Routing Instructions Transaction Set (754) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set is used to communicate routing instructions to a supplier for a specific shipment. It can be used also to respond to a Request for Routing Instructions Transaction Set (753). If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

Data contents of the Contract Pricing Proposal Transaction Set (805) cover sheet and pricing support detail for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set enables the transmission of cost and pricing data for a given contract action and provides pricing support detail data or references where that data can be found in the proposal.

Data contents of the Project Schedule Reporting Transaction Set (806) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set provides for the transmission of planning, scheduling, and status information. The purpose of this transaction set is to establish an initial plan, report progress against the plan, and report changes to the plan. It is designed to serve the needs of government agencies, prime contractors and their subcontractors.

Data contents of the Invoice Transaction Set (810) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to the billing for goods and services provided. The EDI X12 810 transaction set is an Invoice document. It can be used to create new Invoice document that will be sent later on to the trading partner. When you want to bill your customers, just create an Invoice using our set of easy to use EDI tools and we will make sure that your customer gets the Invoice quickly (in less then ten minutes), that way you will guaranty the a faster, more reliable payments into your business account and improve your cash flow! We can create an X12 810 Invoice. By creating an X12 810 Purchase Order you will save time and money and you will benefits from preventing typing errors! That's the big plus on creating new X12 810 Invoice document. Using X12 810 Invoice can automate your business process and help you increase your revenues. We not only offer the X12 810 Purchase Order, but we also offer the 810 Invoice as complementary solution that you might need. Using EDI X12 810 Invoice is just another great way help your business grow and get where you want it to be. The X12 997 transaction set we generate against every X12 810 Invoice and is free and you can generate as many Ack. as you wants, we won't charge you.

Data contents of the Consolidated Service Invoice/Statement Transaction Set (811) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set provides for the billing or reporting of complex and structured service invoice/statement detail. This standard can be used by organizations who are interested in sending or receiving either consolidated or standalone invoices for service arrangements which require processing other than that done for the typical product invoice. The Consolidated Service Invoice/Statement can be used as a credit/debit memo to differentiate between payable invoice items and informationonly memo items. This transaction set should not be used as a standalone notification of a credit/debit adjustment.

Data contents of the Credit/Debit Adjustment Transaction Set (812) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to notify a trading partner of an adjustment or billback and may be used to request an adjustment or billback. It identifies and contains the details and amounts covering exceptions, adjustments, credits, or debits for goods or services. This transaction set is multidirectional between trading partners.

Data contents of the Electronic Filing of Tax Return Data Transaction Set (813) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by tax filers to electronically file tax returns with a federal, state, or local taxing authority and which may initiate payments related to the tax return.

Data contents of the General Request, Response or Confirmation Transaction Set (814) for use within the context of an Electronic Data Interchange (EDI) environment. This standard can be used to request actions to be performed, to respond to a request for actions to be performed or to confirm information related to actions performed.

Data contents of the Cryptographic Service Message Transaction Set (815) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide the data format required for cryptographic key management including the automated distribution and exchange of keys. The mechanism uses X12 structures and data formats and is based on existing standards such as X509 and ANSI X3 and X9 developed by the Accredited Standards Committees (ASCs) X9 and X12. The standard provides an X12 format for key distribution and exchange. The Cryptographic Service Message (CSM) transaction conveys the pertinent keying material for use in the EDI environment. The business requirements addressed in this standard for the key management data encompasses distribution and exchange of keying material in support of authentication, encryption and assurances.

Data contents of the Organizational Relationships Transaction Set (816) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to transmit pertinent information about a parent organization, its members and the relationship of a member to another member, and/or to the parent organization. A parent organization could be an association, a multihospital system, a chain of retail stores, a holding company, etc. This transaction set can be used to convey the identity and relationship of members to a parent organization; identify eligibility to purchase under the terms and conditions negotiated by a parent organization on behalf of its members; and to update application databases.

Data contents of the Commission Sales Report Transaction Set (818) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to allow a retailer to advise a trading partner of commission sales and salary information. Commission data enables a trading partner to reconcile commission payments and salary support.

Data contents of the Operating Expense Statement Transaction Set (819) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit periodic expense details from the operator of an asset to the various owners of that asset (e.g., the operation of a petroleum lease or property having multiple owners).

Data contents of the Payment Order/Remittance Advice Transaction Set (820) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to make a payment, send a remittance advice, or make a payment and send a remittance advice. This transaction set can be an order to a financial institution to make a payment to a payee. It can also be a remittance advice identifying the detail needed to perform cash application to the payee's accounts receivable system. The remittance advice can go directly from payer to payee, through a financial institution, or through a third party agent.

Data contents of the Financial Information Reporting Transaction Set (821) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to report balances, detail and summary financial transactions, and other related financial account information.

Data contents of the Account Analysis Transaction Set (822) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit detailed balance, service charge and adjustment detail primarily from a bank to its corporate clients. However, this transaction set can also be used between or within corporations.

Data contents of the Lockbox Transaction Set (823) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit lockbox (incoming payments) information and totals from a bank or any other lockbox service provider to a company.

Data contents of the Application Advice Transaction Set (824) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide the ability to report the results of an application system's data content edits of transaction sets. The results of editing transaction sets can be reported at the functional group and transaction set level, in either coded or freeform format. It is designed to accommodate the business need of reporting the acceptance, rejection or acceptance with change of any transaction set. The Application Advice should not be used in place of a transaction set designed as a specific response to another transaction set (e.g., purchase order acknowledgment sent in response to a purchase order).

Data contents of the Tax Information Exchange Transaction Set (826) for use within the context of an Electronic Data Interchange (EDI) environment. This bidirectional transaction set can be used to exchange tax information between various tax agencies and other authorized parties.

Data contents of the Financial Return Notice Transaction Set (827) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to report to the originator the inability of the originating financial institution to have the Payment Order/Remittance Advice Transaction Set (820) processed.

Data contents of the Debit Authorization Transaction Set (828) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to provide information from the paying entity to the financial institution regarding debits that the paying entity has authorized against its account. The financial institution would hold this information then match it against incoming debits to determine whether those debits have been authorized by the account holder. This transaction set can be used to add new authorizations or cancel existing authorizations. With regard to electronic debits, this would be used for ACH debit processing only. This transaction set can also be used for paperbased debits (i.e., checks). In the paperbased world, this transaction set would serve the purpose of the "issuance file" or "check register" used in account reconciliation applications. Either onetime or recurring debits can be authorized with this transaction set. One transaction set can be used to identify multiple debit authorization details against one bank account.

Data contents of the Payment Cancellation Request Transaction Set (829) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to cancel a previously transmitted electronic payment between an originating company and its originating financial institution before funds are released.

Data contents of the Planning Schedule with Release Capability Transaction Set (830) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business practice relative to the transfer of forecasting/material release information between organizations. The planning schedule transaction may be used in various ways or in a combination of ways, such as: (1) a simple forecast; (2) a forecast with the buyer's authorization for the seller to commit to resources, such as labor or material; (3) a forecast that is also used as an order release mechanism, containing such elements as resource authorizations, periodtodate cumulative quantities, and specific ship/delivery patterns for requirements that have been represented in "buckets," such as weekly, monthly, or quarterly. The order release forecast may also contain all data related to purchase orders, as required, because the order release capability eliminates the need for discrete generation of purchase orders.

Data content of the Application Control Totals Transaction Set (831) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit totals associated with a collection of like transactions. The items reported in this transaction set must be of the same transaction set ID code.

Data contents of the Price/Sales Catalog Transaction Set (832) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to furnishing or requesting the price of goods or services in the form of a catalog.

Data contents of the Mortgage Credit Report Order Transaction Set (833) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by a mortgage originator to request, track, and cancel a series of valueadded, investigative credit reports which are typically required in mortgage lending. It is a collection of borrower information that is needed to order a mortgage credit report.

Data contents of the Benefit Enrollment and Maintenance Transaction Set (834) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to establish communication between the sponsor of the insurance product and the payer. Such transaction(s) may or may not take place through a third party administrator (TPA). For the purpose of this standard, the sponsor is the party or entity that ultimately pays for the coverage, benefit or product. A sponsor can be an employer, union, government agency, association, or insurance agency. The payer refers to an entity that pays claims, administers the insurance product or benefit, or both. A payer can be an insurance company, health maintenance organization (HMO), preferred provider organization (PPO), government agency (Medicare, Medicaid, Champus, etc.), or an entity that may be contracted by one of these former groups. For the purpose of the 834 transaction set, a third party administrator (TPA) can be contracted by a sponsor to handle data gathering from those covered by the sponsor if the sponsor does not elect to perform this function itself.

Data contents of the Health Care Claim Payment/Advice Transaction Set (835) for use within the context of the Electronic Data Interchange (EDI) environment. This transaction set can be used to make a payment, send an Explanation of Benefits (EOB) remittance advice, or make a payment and send an EOB remittance advice only from a health insurer to a health care provider either directly or via a financial institution.

Data contents of the Procurement Notices Transaction Set (836) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by the buyer to notify the seller or other interested parties of the award or pending award of a contract which may contain some indefinite features, such as delivery schedule, location, and/or quantities. This transaction set can also be used for purchasing actions such as the notification of intent to award or actual award of a small business setaside purchase, notification of being outside of the competitive range, notice of receipt of protest, notice of receipt of a late bid, notice of bid rejection, notice of the disposition of an unsolicited proposal, public notice of the abstract of bids, and the notification of the award of a requirements type contract.

Data contents of the Health Care Claim Transaction Set (837) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to submit health care claim billing information, encounter information, or both, from providers of health care services to payers, either directly or via intermediary billers and claims clearinghouses. It can also be used to transmit health care claims and billing payment information between payers with different payment responsibilities where coordination of benefits is required or between payers and regulatory agencies to monitor the rendering, billing, and/or payment of health care services within a specific health care/insurance industry segment. For purposes of this standard, providers of health care products or services may include entities such as physicians, hospitals and other medical facilities or suppliers, dentists, and pharmacies, and entities providing medical information to meet regulatory requirements. The payer refers to a third party entity that pays claims or administers the insurance product or benefit or both. For example, a payer may be an insurance company, health maintenance organization (HMO), preferred provider organization (PPO), government agency (Medicare, Medicaid, Civilian Health and Medical Program of the Uniformed Services (CHAMPUS), etc.) or an entity such as a third party administrator (TPA) or third party organization (TPO) that may be contracted by one of those groups. A regulatory agency is an entity responsible, by law or rule, for administering and monitoring a statutory benefits program or a specific health care/insurance industry segment.

Data contents of the Trading Partner Profile Transaction Set (838) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to request, change, verify or transmit business profile information to or from a trading partner. This information can be used by the receiver to facilitate the processing of the sender's business transactions. The transaction set may be used to convey government survey information, business classification, general survey information, summary supplier ratings, changes in the EDI environment information, tax information, entity relationships, and general business profile information to update automated information data bases between trading partners.

Data contents of the Project Cost Reporting Transaction Set (839) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set provides the transmission of cost and schedule information to support performance measurement (earned value), program management reporting, and contract funds status reporting. This transaction set will also support the Department of Defense (DoD), Department of Energy (DoE), NASA, and other government agency Cost/Schedule Control Systems Criteria (C/SCSC) and funds status reporting requirements. It is designed to serve the needs of government agencies, prime contractors, and their subcontractors.

Data contents of the Request for Quotation Transaction Set (840) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide potential buyers with the ability to solicit price, delivery schedule, and other items from potential sellers of goods and services.

Data contents of the Specifications/Technical Information Transaction Set (841) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit or request specifications or technical information between trading partners. It can be used to transmit engineering change and engineering change requests. It can also be used to allow EDI trading partners the ability to exchange a complete or partial technical description of a product, process, service, etc. over the same path as any other EDI transaction. The detail area can include graphic, text, parametric, tabular, image, spectral, or audio data. A transmission includes identification information to assist the receiver in interpreting and utilizing the information included in the transaction. Further action as a consequence of the receipt and initial processing of the specification or other technical data may or may not require human intervention. The transmission and receipt of the data may require private agreement between the trading partners to automate the receipt of the data. The total transaction must be in the general form of all ASC X12 transactions so that an EDI computer system will be able to automatically recognize it as a Specification/Technical Information Transaction Set and pass it on for processing of the data itself. The transaction set is not media dependent. The detail area of the Specification/Technical Information Transaction Set provides a structure which allows for the exchange of a variety of specification information. For example, if the transaction contains information describing a complete assembly, it would be necessary to include the assembly model, the models for each of the individual parts, and the associated specifications. In the case of a process it may be necessary to transmit the specification of the product along with the specifications of the process and raw materials. This transaction set can also be linked to other transaction sets. This transaction set is not limited to a specific transmission protocol and uses other standards as applicable where they do not conflict with these requirements for specification transaction.

Data contents of the Nonconformance Report Transaction Set (842) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to report products and processes that do not fulfill specifications or requirements. The Nonconformance Report Transaction Set provides the ability for the sender to report the nonconformance at the level of detail that is required. It also provides the ability to report the specific nonconformances of a component/ part while identifying the assembly as the product that is in nonconformance. The Nonconformance Report Transaction Set may be used to report, initiate, or request actions related to the nonconformance being reported. Financial and accounting information is provided for reporting purposes only. The Nonconformance Report Transaction Set has the capability to report the cause of the nonconformance and to state the proposed action to be followed to prevent a repetition of the problem.

Data contents of the Response to Request for Quotation Transaction Set (843) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide potential buyers with price, delivery schedule, and other terms from potential sellers of goods and services, in response to a request for such information.

Data contents of the Product Transfer Account Adjustment Transaction Set (844) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit specific data in the form of a debit, credit, or request for credit relating to preauthorized product transfer actions.

Data content of the Price Authorization Acknowledgment/Status Transaction Set (845) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by a vendor or manufacturer to transmit specific data relative to the status of or changes to outstanding price authorizations.

Data contents of the Inventory Inquiry/Advice Transaction Set (846) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used in the following ways: (1) for a seller of goods and services to provide inventory information to a prospective purchaser, with no obligation to the purchaser to acquire these goods or services; (2) for a representative of a seller of goods and services to supply inventory information to that seller; (3) for one location to supply another location with inventory information; and (4) for an inquiry as to the availability of inventory with no obligation on the seller of goods and services to reserve that inventory.

Data contents of the Material Claim Transaction Set (847) for use within the context of an Electronic Data Interchange (EDI) environment. This standard provides trading partners a means to advise each other of costs and charges involved in fabricated or purchased material or both which has been deemed damaged, unusable, or obsolete. This transaction set is not to be used to submit claims against transportation or insurance carriers. The Material Claim Transaction Set (847) can be used in the following ways: (1) for a seller of material to advise the buyer of costs and charges resulting from order cancellation or change and must be based on the buyer's authorization to fabricate or purchase material or both; (2) for a buyer of material to advise the seller of costs and charges resulting from material which was deemed damaged or unusable.

Data contents of the Material Safety Data Sheet Transaction Set (848) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to communicate chemical characteristics, hazards, and precautions for the safe handling and use of a material. The transaction set is intended to convey the information required for a Material Safety Data Sheet (MSDS) as defined by the Occupational Safety and Health Administration (OSHA) Hazard Communication Standard, 29 CFR 1910.1200 in the United States, and Workplace Hazardous Materials Information System (WHIMS) in Canada, and various state, province, and local requirements under righttoknow legislation. The MSDS provides the receiver with detailed information concerning material identity, emergency response, chemical and physical characteristics, toxicology, and industrial hygiene procedures. State and federal law dictate who is obligated to provide the MSDS and to whom it should be issued. In addition, thirdparty providers or others with no statutory obligation may voluntarily provide an MSDS to anyone. This transaction set allows for transmission of MSDS data in a structured, unstructured, or semistructured form. CAUTION: With this transaction set, text format is critical due to the MSDS's primary role as a vehicle for hazards communication. The risk if this information is not transmitted clearly and accurately could be harmful to human life, harmful to the environment, could cause mishandling of product, could result in regulatory noncompliance, and could result in liability. Trading partners need to agree on how to interpret, store, and display/print MSDS text, especially text contained in the MSG and SD1 segments. For example, a sender may wish to format text so that one print line is mapped to one MSG segment. Segment terminator and data element delimiter characters shall not appear in any MSDS data. WARNING: Alteration of the original document will occur if the EDI translator or application software converts characters to uppercase. This may adversely affect the appearance, effectiveness, clarity, readability, and communicability of the printed MSDS document.

Data contents of the Response to Product Transfer Account Adjustment Transaction Set (849) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit a detailed or summary response to a party requesting an accounting adjustment relating to a preauthorized product transfer.

Data contents of the Purchase Order Transaction Set (850) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to the placement of purchase orders for goods and services. This transaction set should not be used to convey purchase order changes or purchase order acknowledgment information. The EDI X12 850 transaction set is a Purchase Order document. Each X12 850 Purchase Order can be used to create new Purchase Order document that will be sent later on to the trading partner. We, at Amosoft, can create an X12 850 Purchase Order. By creating an X12 850 Purchase Order you will save time and money and you will benefits from preventing typing errors! That's the big plus on creating new X12 850 Purchase Order document. Using X12 850 Purchase Order can automate your business process and help you increase your revenues. We not only offer the X12 850 Purchase Order, but we also offer the 810 Invoice as complementary solution that you might need. TurnAround X12 850 Purchase Order into a X12 810 Invoice is just another great way help your business grow and get where you want it to be. The X12 997 transaction set we generate against every X12 850 Purchase Order and is free and you can generate as many acknowledgements as you want, we won't charge you. Same goes for using X12 850 Purchase Order.

Data contents of the Asset Schedule Transaction Set (851) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set provides for the customary and established business and industry practice relative to establishing a schedule of assets and the contractual terms and conditions relating to those assets agreed upon between lessor, lessee, buyer, seller, or any other party needing to establish a precise list of assets.

Data contents of the Product Activity Data Transaction Set (852) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by a distributor, warehouse, or retailer to advise a trading partner of inventory, sales, and other product activity information. Product activity data enables a trading partner to plan and ship, or propose inventory replenishment quantities, for distribution centers, warehouses or retail outlets. The receiver of the transaction set will maintain some type of inventory/product movement records for its trading partners to enable replenishment calculations based on data provided by the distributor, warehouse or retailer.

Data contents of the Product Activity Data Transaction Set (852) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by a distributor, warehouse, or retailer to advise a trading partner of inventory, sales, and other product activity information. Product activity data enables a trading partner to plan and ship, or propose inventory replenishment quantities, for distribution centers, warehouses or retail outlets. The receiver of the transaction set will maintain some type of inventory/product movement records for its trading partners to enable replenishment calculations based on data provided by the distributor, warehouse or retailer.

Data contents of the Routing and Carrier Instruction Transaction Set (853) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set provides the sender with the capability to transmit detailed routing and carrier information pertinent to a route. This transaction set only provides routing information and does not convey information about a shipping event or provide shipping authorization.

Data contents of the Shipment Delivery Discrepancy Information Transaction Set (854) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set is used to enable a carrier to notify a shipper or consignee of discrepancies between tendered freight and actual delivered freight. Delivery discrepancy data enables a party to track and control damages, overages, and shortages. This transaction set is not used to acknowledge receipt of goods.

Data contents of the Purchase Order Acknowledgment Transaction Set (855) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to a seller's acknowledgment of a buyer's purchase order. This transaction set can also be used as notification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise as prearranged in their partnership.

Data contents of the Ship Notice/Manifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information. The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.

Data contents of the Shipment and Billing Notice Transaction Set (857) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set provides the recipient of a shipment with data for both receipt planning and payment generation. EDI and telecommunications technologies suggest efficiencies in the way business data is processed. For example, the sender of a shipment may send the recipient's receiving function a Ship Notice/Manifest (856), and the payables function an Invoice (810), even though the contents of these two documents may be largely redundant. In certain business environments, the Shipment and Billing Notice permits the consolidation of these two documents into one. Specifically, this transaction set is appropriate where the shipment data, when it includes terms and item prices, can be used both to plan receipts and to generate payment. In this environment, the exact prices for the items shipped may not be known in advance by both parties. This transaction set is not appropriate in socalled Evaluated Receipts Settlement (ERS) environments, in which the exact prices for the items shipped have been agreed upon by, and are known to, both parties in advance. This transaction set is not to be used to replace the Ship Notice/Manifest (856) or Invoice (810) individually, but only to replace both, together. For example, do not use this transaction set in place of a Ship Notice/Manifest while continuing to send either paper or electronic invoice.

Data contents of the Shipment Information Transaction Set (858) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide the sender with the capability to transmit detailed billoflading, rating, and/or scheduling information pertinent to a shipment. This transaction set can also be used to exchange Government Bills of Lading (GBLs), Commercial Bills of Lading (CBLs), Transportation Control and Movement Documents (TCMDs), and Personal Property Government Bills of Lading (PPGBLs). It may be used by the U.S. Civilian Government, U.S. Department of Defense, and any of their trading partners to exchange information about the shipment of freight, household goods, and passengers. This transaction set fulfills information requirements established by U.S. Government transportation movement rules and regulations.

Data contents of the Freight Invoice Transaction Set (859) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide the sender with the capability to transmit an invoice, including charges, allowances, and details, for transportation services rendered. This transaction set can also be used to exchange transportation services invoice information based on services provided in accordance with Government transportation rules and regulations. It may be used by the U.S. Civilian Government, U.S. Department of Defense, and any of their trading partners to exchange invoice information resulting from the shipment of freight, household goods, and passengers. This transaction set fulfills financial information requirements established by the U.S. Government.

Data contents of the Purchase Order Change Request Buyer Initiated Transaction Set (860) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide the information required for the customary and established business and industry practice relative to a purchase order change. This transaction can be used: (1) by a buyer to request a change to a previously submitted purchase order or (2) by a buyer to confirm acceptance of a purchase order change initiated by the seller or by mutual agreement of the two parties.

Data contents of the Receiving Advice/Acceptance Certificate Transaction Set (861) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to the notification of receipt or formal acceptance of goods and services.

Data contents of the Shipping Schedule Transaction Set (862) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by a customer to convey precise shipping schedule requirements to a supplier, and is intended to supplement the planning schedule transaction set (830). The shipping schedule transaction set will supersede certain shipping and delivery information transmitted in a previous planning schedule transaction, but it does not replace the 830 transaction set. The shipping schedule transaction set shall not be used to authorize labor, materials or other resources. The use of this transaction set will facilitate the practice of JustInTime (JIT) manufacturing by providing the customer with a mechanism to issue precise shipping schedule requirements on a more frequent basis than with the issuance of a planning schedule transaction, e.g., daily shipping schedules versus weekly planning schedules. The shipping schedule transaction also provides the ability for a customer location to issue shipping requirements independent of other customer locations when planning schedule transactions are issued by a consolidated scheduling organization.

Data contents of the Report of Test Results Transaction Set (863) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit the results of tests performed to satisfy a specified product or process requirement. This includes, but is not limited to, test data such as inspection data, certification data, and statistical process control measurements.

Data content of the Text Message Transaction Set (864) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide users with a capability to electronically move messages, contracts, explanations, and other onetime communications. It is the intent of this transaction set to provide electronic communication (messages) for people, not for computer processing. The use of the transaction set to transmit quasi or unique transaction set standards is discouraged. The use of the Text Message transaction set demands of the sender certain detailed information about the recipient. The transaction set's purpose is to provide communication to the recipient in some humanreadable form. The recipient's network will dictate what capabilities are available for delivery of the information. It is the responsibility of the sender to obtain this information and include it in the transmission.

Data contents of the Purchase Order Change Acknowledgment/Request Seller Initiated Transaction Set (865) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to convey acceptance or rejection of changes to a previously submitted purchase order by the seller or to notify the buyer of changes initiated by the seller to a previously submitted purchase order by the seller.

Data contents of the Production Sequence Transaction Set (866) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for the receiver of goods to request the order in which shipments of goods arrive at one or more locations, or to specify the order in which the goods are to be unloaded from the conveyance method, or both. This specifies the sequence in which the goods are to enter the materials handling process, or are to be consumed in the production process, or both. This transaction set shall not be used to authorize labor, materials, or other resources. This transaction set shall not be used to revise any product characteristic specification.

Data contents of the Product Transfer and Resale Report Transaction Set (867) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to: (1) report information about product that has been transferred from one location to another; (2) report sales of product from one or more locations to an end customer; or (3) report sales of a product from one or more locations to an end customer, and demand beyond actual sales (lost orders). Report may be issued by either buyer or seller.

Data contents of the Electronic Form Structure Transaction Set (868) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide a structure for transfer of EDI standards, or portions thereof in an electronic form. These EDI standards include but are not limited to: ANSI X12 standards, approved ASCX12 draft standards for trial use, UN/EDIFACT standard messages, and industry EDI conventions and guidelines. It is intended to provide users with the following: The ability to send and receive EDI standards data which can be used to update application or translation software. The ability to exchange data maintenance information with trading partners about transaction sets, segments, elements and codes that will be used for EDI transmissions. The ability to transmit complete or partial EDI standards or conventions.

Data contents of the Order Status Inquiry Transaction Set (869) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to request all pertinent information relative to an entire purchase order, selected line items on a purchase order, or selected products/ services on a purchase order. Inquiry can also be made for all or a selected portion of the customer's ordered items, all or a selected portion of the customer's unshipped items, or all or a selected portion of the customer's shipped items.

Data contents of the Order Status Report Transaction Set (870) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to report on the current status of a requirement forecast, an entire purchase order, selected line items on a purchase order, selected products/ services on a purchase order, or purchase orders for a specific customer in their entirety or on a selection basis. The transaction set can also be used to report on the current status of single or multiple requisitions. The report format allows for the inclusion of "reasons" relative to the status. This transaction set may also be used to update the supplier's scheduled shipment or delivery dates. This transaction set can result from either an inquiry or a prearranged schedule agreed to by the trading partners.

Data contents of the Component Parts Content Transaction Set (871) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set provides the ability to report the nondomestic contents of a product, or component part contained within a product, in accordance with governmental regulations.

Data contents of the Residential Mortgage Insurance Application Transaction Set (872) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by a mortgage originator to request mortgage insurance and provide supporting information needed to obtain a mortgage insurance commitment on one or several residential mortgage loans.

This X12 Transaction Set contains the format and establishes the data contents of the Commodity Movement Services Transaction Set (873) for use within the context of an Electronic Data Interchange (EDI) environment. This standard can be used to convey request and response information for commodity movement services. This transaction is not to be used for product sales or purchases. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

This X12 Transaction Set contains the format and establishes the data contents of the Commodity Movement Services Response Transaction Set (874) for use within the context of an Electronic Data Interchange (EDI) environment. This standard can be used to return validation information in response to the Commodity Movement Services Transaction Set (873). If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

Data contents of the Grocery Products Purchase Order Transaction Set (875) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to provide for customary and established grocery industry practice relative to the placement of purchase orders for finished goods in a retail or wholesale consumer market. This standard can be used by a retailer or wholesaler organization to request delivery of finished goods from a broker or supplier organization. This transaction set should not be used to convey purchase order changes or purchase order acknowledgement information.

Data contents of the Grocery Products Purchase Order Change Transaction Set (876) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to provide for customary and established grocery industry practice relative to the changing of purchase orders for finished goods in a retail or wholesale consumer market. This standard can be used by a retailer or wholesaler organization to request a change to a previously submitted purchase order. Changes are accomplished by restating the value of the data elements to be changed rather than indicating the difference between the old and new value. Deletions are handled by restating the values to zeros or blanks. If an item is to be deleted, the quantity ordered is restated to zero.

Data contents of the Manufacturer Coupon Family Code Structure Transaction Set (877) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by a manufacturer or third party agent to notify a distributor or third party agent relative to coupon family code structures and their associated product codes.

Data contents of the Product Authorization/Deauthorization Transaction Set (878) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to advise a Direct Store Delivery vendor of the authorization or deauthorization of products for a store or group of stores.

Data contents of the Price Information Transaction Set (879) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to enable a manufacturer, supplier, broker, or agent to provide a trading partner with pricing information.

Data contents of the Grocery Products Invoice Transaction Set (880) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to provide for customary and established grocery industry practice relative to billing details for finished goods in a retail or wholesale consumer market. The transaction set can be used by the supplier or broker organization to request payment from a retailer or wholesaler organization. This transaction set is to be used for standalone detail billing and cannot be used for statement billing or credit/debit adjustments.

Data contents of the Manufacturer Coupon Redemption Detail Transaction Set (881) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by a manufacturer or manufacturer's agent to communicate coupon redemption detail and the associated store tag detail necessary for reconciliation to a distributor's or distributor's clearinghouse invoice.

Data contents of the Direct Store Delivery Summary Information Transaction Set (882) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to summarize detailed delivery, return and adjustment information which was previously reconciled at time of delivery in a retail direct store delivery environment, and also to request payment for the products delivered. This transaction set will provide only a summary of direct store deliveries and adjustments without product detail.

Data contents of the Market Development Fund Allocation Transaction Set (883) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set is initiated by a manufacturer and provides for customary and established business and industry practice relative to informing a broker or retailer/wholesaler how funds should be allocated in a market development program.

Data contents of the Market Development Fund Settlement Transaction Set (884) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set provides for customary and established business and industry practice relative to communicating settlement information associated with a single market development fund event. This transaction set is multidirectional between trading partners.

Data contents of the Retail Account Characteristics Transaction Set (885) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set is used to enable a retailer, wholesaler or broker to provide detailed attributes of a retail store such as store number, size of store, class of trade, product category information, customer demographic information, or marketing, etc. to a trading partner.

Data contents of the Customer Call Reporting Transaction Set (886) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to enable a broker or manufacturer to communicate retail store level information such as condition of products, shelf space allocation, store conditions, marketing programs in effect, information on competitor products, selective pricing information, display information, etc.

Data contents of the Coupon Notification Transaction Set (887) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set is used by a manufacturer to notify a distributor, retail clearing house, manufacturer's agent or broker of the issuance of coupons and to provide information necessary for processing.

Data contents of the Item Maintenance Transaction Set (888) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set is used to enable a manufacturer, supplier, broker, or agent to provide detailed finished goods product information to a partner in a consumer goods market. This transaction set can be used to provide information about new products or changes in existing product specifications. Price changes will not be sent with this transaction set, but can be sent with the Price Change Transaction Set (879).

Data contents of the Promotion Announcement Transaction Set (889) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by a broker, distributor or manufacturer and provides for customary and established business and industry practice relative to the announcement of promotion allowance amounts, dates and performance conditions that may apply; the replacement of a previously transmitted promotion in its entirety; the cancellation of a previously transmitted promotion; changes to promotion dates; or acceptance of a promotion offered by a broker or supplier. This transaction set is multidirectional between trading partners.

Data contents of the Deduction Research Transaction Set (891) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by a seller to request information about a deduction from an invoice. It can also be used by a seller's agent or buyer to provide complete details needed to resolve deduction amounts.

Data contents of the Item Information Request Transaction Set (893) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by distributors and brokers to request complete item information from the manufacturers, suppliers, brokers, or agents. The item information will be returned using the Item Maintenance Transaction Set (888).

Data contents of the Delivery/Return Base Record Transaction Set (894) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to enable a Direct Store Delivery (DSD) vendor to communicate the details of a DSD delivery and is to be used during the checkin procedure.

Data contents of the Delivery/Return Acknowledgment or Adjustment Transaction Set (895) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to enable a distributor or Direct Store Delivery (DSD) vendor to communicate adjustments to a DSD delivery or to acknowledge the completion of a delivery. The transaction set contains changes to the Delivery/Return Base Record identified during the checkin procedure. A Delivery/Return Acknowledgement and/or Adjustment Transaction containing no changes is considered to be an acceptance of the preceding Base Record or Adjustment. The transaction set will contain only the detail data which is to be changed.

Data contents of the Product Dimension Maintenance Transaction Set (896) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide information about the physical characteristics of items for use in computerized shelf space management systems.

Data contents of the Loss or Damage Claim General Commodities Transaction Set (920) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to file a legal claim with a transportation carrier for loss or damage.

Data contents of the Loss or Damage Claim Motor Vehicle Transaction Set (924) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to file a legal claim with a carrier for loss or damage to a motor vehicle.

Data contents of the Claim Tracer Transaction Set (925) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by a claimant to request from a carrier the status of a loss or damage claim.

Data contents of the Claim Status Report and Tracer Reply Transaction Set (926) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by a carrier to report the status of a claim to the claimant or to reply to a claim tracer from the claimant.

Data contents of the Automotive Inspection Detail Transaction Set (928) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by automotive manufacturers, inspection agencies, or carriers to report motor vehicle inspection results to other interested parties.

Data contents of the Warehouse Shipping Order Transaction Set (940) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to enable the depositor to advise a warehouse to make a shipment, confirm a shipment, or modify or cancel a previously transmitted shipping order.

Data contents of the Warehouse Stock Transfer Shipment Advice Transaction Set (943) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by a depositor or an agent of the depositor to advise the recipient that a transfer shipment has been made. This transaction set provides a receiving location with detail information concerning product being shipped to that location.

Data contents of the Warehouse Stock Transfer Receipt Advice Transaction Set (944) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by a receiving location to advise a depositor or an agent of the depositor that a transfer shipment has been received. This transaction set provides the depositor or the depositor's agent with detail information concerning product that has been received.

Data contents of the Warehouse Shipping Advice Transaction Set (945) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by the warehouse to advise the depositor that shipment was made. It is used to reconcile order quantities with shipment quantities.

The transaction set can be used by a receiving location to advise a depositor or an agent of the depositor that a transfer shipment has been received. This transaction set provides the depositor or the depositor's agent with detail information concerning product that has been received. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

Data contents of the Warehouse Inventory Adjustment Advice Transaction Set (947) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to inform a warehouse/depositor of a quantity or status change to inventory records. This transaction set provides detail information concerning the internal adjustments which occur between a warehouse and a depositor.

Data contents of the Functional Group Totals Transaction Set (980) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to transmit selected totals and accumulated totals for each type of transaction set contained in a functional group.

Data contents of the Response to a Load Tender Transaction Set (990) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide general information relative to a specific shipment. The Response to a Load Tender is used as the response to a Motor Carrier Shipment Information Transaction Set (204) which has been used as a load tender.

This X12 Transaction Set contains the format and establishes the data contents of the Secured Receipt or Acknowledgment Transaction Set (993) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set provides three distinct security services: the 993 provides security protocol error reporting, non-repudiation of receipt for X12.58 authenticated transaction sets or functional groups, and transmission of authentication independent of the document for which the authentication is rendered. When the 993 is used to pass a dis-embodied signature (non-repudiation of origin), both the transaction set and the 993 with the assurance for the transaction set may be transmitted completely independent of each other. A 993 may be generated as a 'trusted receipt' for a 993 that contained a dis-embodied signature. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

Data contents of the File Transfer Transaction Set (996) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to transmit file information in formats agreed to by the sending and receiving parties. This transaction set is not intended to replace or bypass the use of existing X12 transaction sets to accommodate internal applications. The transaction set is solely intended for the exchange of formatted electronic accounting machine (EAM), 80 column card images.

Data contents of the Functional Acknowledgment Transaction Set (997) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to define the control structures for a set of acknowledgments to indicate the results of the syntactical analysis of the electronically encoded documents. The encoded documents are the transaction sets, which are grouped in functional groups, used in defining transactions for business data interchange. This standard does not cover the semantic meaning of the information encoded in the transaction sets.

The 998 transaction set can be used to request the deletion of a previously transmitted transaction set and will indicate the reason for this action, such as diversion or cancelled bill. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.

The EDI 999 transaction set is an Implementation Acknowledgement document, developed specifically to replace the 997 Functional Acknowledgement document for use in healthcare. Both the 997 and 999 are used to confirm that a file was received. However, the 999 includes additional information about whether the received transaction had errors. This includes whether the transaction is in compliance with HIPAA requirements. If you need help supporting this EDI document, please visit our signup page. We will contact you shortly after the information is received. Thank you.