Migrate from Edicom EDI to Acumatica

Edicom stores every trading partner with ISA/GS envelope qualifiers, connection protocol (AS2/SFTP/VAN), acknowledgment requirements, and per-document mapping rules. Acumatica EDI Settings requires each partner to be re-entered manually. FlitStack exports the partner list with connection metadata so Acumatica admins have a complete rebuild reference.

Edicom EDI 850s map to Acumatica Sales Orders (if your company is the seller receiving POs from buyers) or Purchase Orders (if you are the buyer). The document header fields (PO number, date, buyer/seller IDs) map to Acumatica's Order Nbr., Date, CustomerID, and VendorID. Line items map with SKU, quantity, unit price, and UOM from the PO1/P4 segments.

Edicom EDI 855s confirm or change PO lines. In Acumatica, these are reflected by updating the Sales Order line statuses or creating Sales Order Confirmation documents. Acumatica does not have a native 855 equivalent — the acknowledgement is an internal status update on the Sales Order rather than a separate document type.

Edicom EDI 856 Advance Shipment Notices carry the ASN number, ship date, carrier details, and line-item quantities shipped. In Acumatica, these map to the Shipment record linked to the original Sales Order. Carrier and tracking information populates Acumatica's Shipping Settings on the shipment.

Edicom EDI 810 invoices migrate directly to Acumatica AR Invoices. The invoice number, date, bill-to address, line items with amounts, and tax information map from Edicom's ITA/IT1 segments to Acumatica's AR Invoice document fields. FlitStack matches the customer/vendor by the EDI qualifier + ID against Acumatica's party records.

Edicom EDI 820 payment orders carry remittance advice — amounts applied to specific invoices. Acumatica's APPaymentEntry records the payment and links it to the original AP Bill using the payment amount and reference from the 820's RMR segment. Unapplied amounts surface as on-account credits in Acumatica.

Edicom EDI 824 Application Advice documents report errors or warnings on received EDI documents. Acumatica has no native EDI 824 object — these are surfaced as Notes or Activity Log entries attached to the relevant AR/AP document, preserving the original 824 rejection code and description for audit purposes.

Edicom EDI 830 planning schedules convey forecasted demand from buyers to suppliers. In Acumatica, these map to Demand Forecast records or Purchase Requisitions depending on your configured workflow. FlitStack maps the SCH segment quantities and dates; your Acumatica admin configures how the system consumes the forecast.

Edicom EDI 940 warehouse shipping orders direct outbound fulfillment. Acumatica maps these to the INShipping module's Shipment Order records, triggering the pick-list and warehouse confirmation workflow. Line-item quantities and item IDs from the Edicom W05 segment populate Acumatica's inventory allocation.

Edicom maintains a full EDI transmission log showing ISA/GS envelope timestamps, functional acknowledgment (997/999) status, and document error history per partner. Acumatica does not replicate this as a native EDI log — FlitStack writes the transmission reference number and timestamp as a Note on each migrated AR/AP or Sales Order document for traceability.

Edicom stores AS2 certificate configurations, SFTP credential pairs, and VAN mailbox IDs per partner. These protocol-level connection settings are not portable to Acumatica's EDI Settings, which require the certificates and credentials to be re-entered. FlitStack exports a structured summary of every partner's connection type, endpoint URL, and certificate fingerprint for re-entry.

Edicom supports custom segment mappings and transformation logic per partner or document type. Acumatica handles equivalent transformations via Generic Inquiries and Import/Export Scenarios, which must be built from scratch. FlitStack documents each Edicom mapping rule (source segment, condition, transformation) in a spreadsheet so Acumatica developers can rebuild the logic in the correct Acumatica artifact.

Edicom handles e-invoicing compliance for Italy (SDI), Spain (FACe), Brazil (NF-e), and other country-specific mandates. Acumatica's e-invoicing compliance requires country-specific add-ons or third-party integrations. FlitStack migrates the underlying invoice transaction data; compliance records and legal archive references must be handled by your e-invoicing add-on in Acumatica.

Edicom user accounts tied to trading partner admin or operations staff map to Acumatica Contact records if the individuals correspond to customer or vendor contacts. Edicom internal operator accounts do not have a direct Acumatica equivalent — they are referenced in the transaction migration documentation but do not create Acumatica users unless they represent actual business contacts.