Maintenance Service Order (650) is an EDI transaction used to communicate the details of a maintenance service order between a service provider and a service recipient. Typically, a service provider sends this transaction to a customer or to an internal maintenance management system to establish or confirm the scope of work, location details, and service requirements. The transaction is built on a hierarchical structure using the HL (Hierarchical Level) segment to organize service components and line items. Key segments include the BGN (Beginning Segment) to establish the order context, the HL (Hierarchical Level) segment to structure service layers, and the LIN (Item Identification) segment to identify specific maintenance items or tasks to be performed.

Consider a facility management company, BuildCare Services, that sends a 650 transaction to Acme Manufacturing to initiate a quarterly HVAC maintenance service order. The BGN segment establishes the order date and purpose, while the N1 loop identifies Acme Manufacturing as the service location and includes a contact person via the PER segment. Within the HL loop structure, BuildCare details the specific maintenance tasks—such as filter replacement and system inspection—using LIN segments, assigns quantities and costs through QTY and AMT segments, and includes any special instructions or safety requirements through the MTX (Text) loop. This structured information allows Acme to assign technicians, prepare parts, and schedule the work efficiently before the service team arrives on-site.