Skip to content

Channel

Granite City Electric (via Epicor Eclipse)

Plan a reliable EDI exchange for Granite City Electric (via Epicor Eclipse). Explore 10 document references, map them to your business records and test the complete workflow before launch.

Documents
10 transactions
Standards
X12
Implementation
Mapping and launch plan

Implementation guide

Granite City Electric (via Epicor Eclipse): EDI implementation plan

Build a reliable EDI workflow for Granite City Electric (via Epicor Eclipse). Use 10 document types to plan record mapping, prevent duplicate processing and reconcile results in your business systems.

The document list is based on the linked partner reference. Confirm the required messages, versions and directions for your account.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
X12 810 InvoiceListed for Granite City Electric (via Epicor Eclipse) accounts-receivable or accounts-payable invoice

invoice number, purchase order and invoice line

  • Reconcile line amounts, allowances, charges and tax to the invoice total.
  • Submit the same invoice twice and verify that it cannot create a second payable.
X12 820 Payment Order Remittance AdviceListed for Granite City Electric (via Epicor Eclipse) payment or remittance record

payment reference, invoice references and amounts applied

  • Allocate a partial payment across several invoices and preserve the remaining balances.
  • Keep receipt of remittance information distinct from confirmation that funds settled.
X12 844 Product Transfer Account AdjustmentListed for Granite City Electric (via Epicor Eclipse) product-transfer adjustment request

claim reference, product transfer and authorization

  • Test two claim lines against the same resale without paying the same adjustment twice.
  • Route an unknown price authorization to review instead of assuming eligibility.
X12 845 Price Authorization Acknowledgment StatusListed for Granite City Electric (via Epicor Eclipse) price authorization status

authorization reference, product and effective period

  • Test an authorization ending before a resale date.
  • Maintain separate eligibility for two customers buying the same product.
X12 849 Response To Product Transfer Account AdjustmentListed for Granite City Electric (via Epicor Eclipse) adjustment claim response

original claim, response line and authorized amount

  • Match partial approval to the submitted claim lines.
  • Test a repeated response and prevent a second credit from being posted.
X12 850 Purchase OrderListed for Granite City Electric (via Epicor Eclipse) purchase order or sales order

buyer purchase order, order line and trading-party identifiers

  • Map buyer item numbers to seller SKUs and explicitly convert case quantities to the agreed unit.
  • Resend one purchase order and confirm that only one sales order is created.
X12 852 Product Activity DataListed for Granite City Electric (via Epicor Eclipse) product activity report

item, location, activity type and reporting period

  • Keep sales, returns and stock movements in separate measures.
  • Replace a corrected reporting period without counting the original activity twice.
X12 855 Purchase Order AcknowledgmentListed for Granite City Electric (via Epicor Eclipse) purchase-order response

original purchase order, response revision and order line

  • Test a partially accepted order with a backordered line and retain both outcomes.
  • Do not treat a syntax acknowledgment as acceptance of price, quantity or delivery dates.
X12 856 Ship Notice ManifestListed for Granite City Electric (via Epicor Eclipse) shipment notice (ASN)

shipment, order, package and item references

  • Reconcile item quantities through shipment, order and packaging levels against the physical shipment.
  • Test split shipments for one purchase order and prevent the second ASN from replacing the first.
X12 867 Product Transfer And Resale ReportListed for Granite City Electric (via Epicor Eclipse) product transfer and resale record

product, transfer or resale reference and reporting period

  • Keep a transfer between locations separate from a sale to an end customer.
  • Deduplicate corrected resale reports before calculating rebates or channel demand.

Implementation steps

  1. Choose the trading account and channel

    Confirm the supplier or customer account, sender and receiver IDs, test environment and current guide for Granite City Electric (via Epicor Eclipse). Compare other Granite City Electric channels before reusing a mapping.

  2. Map records and assign owners

    Start with accounts-receivable or accounts-payable invoice, payment or remittance record, product-transfer adjustment request. For each document, assign the source system, destination record, stable identifiers and person responsible for exceptions. Agree whether a change updates an existing record or creates a new event.

  3. Test a complete exchange

    Run a successful exchange and the failure cases in the mapping table. Track delivery, document validation and processing in your business system separately. Agree on the Granite City Electric production handoff and save the results of each approved test.

  4. Check results after launch

    Match records between systems using invoice number, purchase order and invoice line. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries.

Go-live checklist

  • The required X12 documents, versions and sample files are agreed.
  • Sender and receiver IDs, test connections and production connections are agreed with the channel owner.
  • Delivery receipts, document validation and business responses have monitoring and a named owner.
  • Tests cover duplicates, partial processing and reconciliation with realistic business records.

Document flow on this channel

Document relationships on Granite City Electric (via Epicor Eclipse)

This channel lists all 10 document types in the Granite City Electric directory. Example relationships are shown below; confirm the required sequence in the channel guide.

Catalog & inventory

Some example steps listed
  1. 832 Price / Sales Catalog not listed on Granite City Electric (via Epicor Eclipse)
  2. 846 Inventory Inquiry / Advice not listed on Granite City Electric (via Epicor Eclipse)
  3. 852 Product Activity Data

Network onboarding

Plan the Epicor Eclipse connection

The directory associates Epicor Eclipse with 44 partner entries across 44 channels. Confirm transport, network enrollment, commercial terms and testing with the channel owner before implementation.

Most frequently listed documents on Epicor Eclipse
  • 810 44 ch
  • 850 44 ch
  • 855 42 ch
  • 856 42 ch
  • 844 3 ch
  • 849 3 ch

Granite City Electric (via Epicor Eclipse) questions

Which EDI documents are listed for Granite City Electric (via Epicor Eclipse)?

X12 810 Invoice; X12 820 Payment Order Remittance Advice; X12 844 Product Transfer Account Adjustment; X12 845 Price Authorization Acknowledgment Status; X12 849 Response To Product Transfer Account Adjustment; X12 850 Purchase Order; X12 852 Product Activity Data; additional documents are shown in the mapping plan. Confirm which documents, directions and versions apply to your account.

How should I choose the Granite City Electric EDI channel?

Granite City Electric (via Epicor Eclipse) lists 10 distinct document types. Match the channel to your business unit, account and delivery arrangement; compare the other channel links before choosing a connection. Confirm access and enrollment with the channel owner.

Which identifiers should the Granite City Electric mapping preserve?

For X12 810 Invoice, plan around invoice number, purchase order and invoice line. For X12 820 Payment Order Remittance Advice, use payment reference, invoice references and amounts applied. Use the partner guide to locate these values and check their allowed formats.

Does a successful EDI receipt mean Granite City Electric accepted the business document?

Track delivery, document validation and business processing separately. An AS2 message disposition notification (MDN) confirms transport receipt; an X12 997 or 999 reports technical validation. Use the agreed business response or reconciliation report to confirm that the order, shipment or invoice was processed.

What should be tested before launching Granite City Electric (via Epicor Eclipse) EDI?

Reconcile line amounts, allowances, charges and tax to the invoice total. Submit the same invoice twice and verify that it cannot create a second payable. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.

Connect Granite City Electric EDI to your business systems

See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.