Transactions

Learn about the commonly used transactions in CIS.

The Customer life cycle starts with enrollment and then as the Customer starts using the services as provided in form of gas and electricity, he starts getting billed based on the usage inclusive of special charges like disconnect charges, late payment fee, promotional credit, and others. At some stage, the Customer may decide to stop availing services and close his account or the Supplier may decide to close his account due to bad payment history. All these stages in a life cycle are managed by transactions.

The commonly used transactions in CIS are:

Transactions Type Transaction Set Description Flow
867 Product Transfer and Resale Report

Used to communicate energy usage (gas or electric):

  • Metered (non-interval and interval)
  • Unmetered
  • Historical usage
 Utility to Supplier
810 Invoice Used to communicate invoice transactions.
Note: Outbound 810s: transactions include Supplier charges to be sent to the utility, to bill to Customers in a Bill Ready model.

Inbound 810s: transactions include utility charges or delivery charges, to be billed to Customer, by Supplier (in Supplier Consolidated model) or to shadow bill (in Rate Ready model) respectively.

To learn more about billing models, see Supported Billing Models.

 Both ways
814 General Request, Response or Confirmation

Used to request enrollments or communicate changes to a Customer account.

  • Enrollments – enrolling a new Customer.
  • Changes – changing Customer account information (address, billing type, rate, etc.)
  • Drops – Customer dropped by marketer or switches to a different Supplier.
  • Historical Usage – request historical usage for a Customer.
  • Reinstatement – a Customer rescinds a switch request and is reinstated to previous Supplier.
  • Move-ins and Move-outs.
 Both ways
650 Service Order

Used to request or communicate changes in service:

  • Disconnect and Reconnect for Non Pay.
  • Meter Maintenance
  • Switch Holds
  • Switch Hold removal
  • Outage notifications (for ERCOT only)
 Both ways
820 Payment Order/Remittance Advice Used to communicate details about remittance/payment to LDC or Marketer. Both ways
824 Application Advice

Used to communicate acceptance and rejection of various transactions to the sending party.

  • 810 accept / reject
  • 867 reject
  • 820 reject
  • 568 reject
  • 248 reject
Note: The sender of an 810 receives an 824 acceptance or rejection. 824 is designed to either request a resend (reject), or serve as an acceptance notification only.
 Both ways
248 Account Assignment Used to communicate a write-off in consolidated billing models. Utility to Supplier
568 Accounts Receivable Advice Used to communicate A/R balances in consolidated billing models. Utility to Supplier
997 Functional Acknowledgement Used to acknowledge receipt of other transactions. It serves as a response or electronic receipt between EDI transactions.
Note: It is an important function for establishing timely delivery of EDI transactions. Suppliers gain valuable insights if their transactions are submitted to utilities and vice versa, on time.
 Both ways