Sales Orders

eMessaging receives electronic orders from your customers and creates Sales Orders in your Business Central. Orders can arrive via PEPPOL or EDI networks (EDIFACT, X12).

Your customer sends an order → eMessaging receives it → Sales Order appears in your BC

Inbound order sources

Source	Format	How it arrives
PEPPOL network	PEPPOL BIS Order 3.0	Via CentaraIQ Access Point
EDI — EDIFACT	EDIFACT ORDERS	Via SFTP, AS2, or API
EDI — X12	X12 850 (Purchase Order)	Via SFTP, AS2, or API
EDI — BASDA	BASDA eBIS-XML Order	Via API

PEPPOL and EDI orders

How it works

1. The customer’s system sends an electronic purchase order to your PEPPOL or EDI endpoint.
2. The Receive job queue downloads the order from CentaraIQ to eMessaging.
3. eMessaging validates the order structure, customer identification, and line items.
4. A Sales Order is created in Business Central with all relevant fields mapped.
5. You review and process the Sales Order as you normally would — pick, ship, and invoice.

Order mapping

Source field	BC Sales Order field
Buyer’s identifier (VAT number)	Customer No. (looked up by VAT Registration No.)
Order lines	Sales Order Lines (items mapped by cross-reference or item number)
Requested delivery date	Requested Delivery Date
Customer’s PO number	External Document No.
Delivery address	Ship-to Address
Payment terms	Payment Terms Code (mapped via payment method mapping)
Currency	Currency Code
References	Order header references

Item mapping

Items on incoming orders are matched to your BC item catalog using:

1. Cross-Reference — the customer’s item number is looked up in Item Cross References
2. GTIN / EAN — if a GTIN is provided, it is matched against your item’s GTIN field
3. Item Number — direct match on your item number
4. Description — if no code match is found, the item description is used for manual matching

If an item cannot be matched, the Sales Order line is created with a description but no item number. You can then manually assign the item.

Intercompany transactions

eMessaging supports intercompany transactions when both companies use Business Central with eMessaging:

1. Company A releases a Purchase Order → eMessaging sends it electronically.
2. Company B receives it as a Sales Order → processes, ships, and invoices.
3. Company B’s Sales Invoice is sent electronically → Company A receives it as a Purchase Invoice.
4. Company A matches the invoice to the original PO, approves, and posts.

This eliminates manual re-keying between related companies and ensures complete document consistency throughout the procurement-to-payment cycle.

Review incoming orders

1. Open Sales Orders in Business Central.
2. Orders created from electronic documents are marked with the electronic document reference.
3. Review the order details, verify items and quantities.
4. Check the Original Document to see the raw PEPPOL/EDI order.
5. Process the order through your normal sales workflow.

Next steps

• Sending Documents — send the invoice back after fulfillment
• Sales Documents Overview — full sales document flow
• Preview & Resend — track delivery status