Invoice APIs

Invoices allow companies to exchange billing amounts and payment terms with upstream and downstream supply chain trade partners for finished goods and services without giving these trade partners access to their serialization system of record.

Type = API Reference,; Topic = Multienterprise Information Network Tower,;Persona = TraceLink Administrator, User, Orchestration Architect,; Orchestration = Manufacturing, Logistics, Procurement,; Function = Supply Chain, IT,

Invoice (IDoc)

The Invoice IDoc message sends a request for payment from the seller to the buyer and details information such as the full amount due and payment terms. When sending an invoice IDoc message from your company inbound to TraceLink, TraceLink requires that the values for the following elements in the message header control settings must be present for TraceLink to correctly process the B2B message:

Companies can communicate using the standard IDoc format they normally use to communicate with Partners from their ERP to communicate asynchronously with the Multienterprise Process Connect app. While TraceLink supports this message format, companies must follow some TraceLink specific requirements for the message header control settings in all asynchronous IDoc message communications sent inbound to TraceLink.
  • Message Type: MPC_INVOICE (Invoice)
  • IDoc Format: INVOIC.INVOIC02
  • Transform Names:
    • B2B_IDoc_INVOIC02_Invoice_IB_V1
    • B2B_IDoc_INVOIC02_Invoice_OB_V1

When sending an Invoice IDoc message from your company inbound to TraceLink the following hierarchy must be adhered to for TraceLink to correctly process the B2B message.

Tag end

Type = API Reference,; Topic = Multienterprise Information Network Tower,;Persona = TraceLink Administrator, User, Orchestration Architect,; Orchestration = Manufacturing, Logistics, Procurement,; Function = Supply Chain, IT,

Invoice (EDIFACT)

The Invoice EDIFACT message sends a request for payment from the seller to the buyer and details information such as the full amount due and payment terms. When sending an invoice EDIFACT message from your company inbound to TraceLink, TraceLink requires that the values for the following elements in the message header control settings must be present for TraceLink to correctly process the B2B message:

Companies can communicate using the standard EDIFACT format they normally use to communicate with Partners from their SAP to communicate asynchronously with the Multienterprise Process Connect app. While TraceLink supports this message format, TraceLink only processes some of the elements included in the standard EDIFACT message. TraceLink will not process elements that are included in the message but not present in message hierarchy provided.
  • Message Type: MPC_INVOICE (Invoice)
  • EDIFACT Format: INVOICE
  • Transform Names:
    • B2B_EDI_EDIFACT_INVOIC_Invoice_IB_V1
    • B2B_EDI_EDIFACT_INVOIC_Invoice_OB_V1

When sending an EDIFACT INVOICE message from your company inbound to TraceLink, the following hierarchy must be adhered to for TraceLink to correctly process the B2B message:

Tag end

Type = API Reference,; Topic = Multienterprise Information Network Tower,;Persona = TraceLink Administrator, User, Orchestration Architect,; Orchestration = Manufacturing, Logistics, Procurement,; Function = Supply Chain, IT,

Invoice (X12)

The Invoice X12 message sends a request for payment from the seller to the buyer and details information such as the full amount due and payment terms. When sending an invoice X12 message from your company inbound to TraceLink, TraceLink requires that the values for the following elements in the message header control settings must be present for TraceLink to correctly process the B2B message:

Companies can communicate using the standard X12 format they normally use to communicate with Partners from their SAP to communicate asynchronously with the Multienterprise Process Connect app. While TraceLink supports this message format, TraceLink only processes some of the elements included in the standard X12 message. TraceLink will not process elements that are included in the message but not present in message hierarchy provided.
  • Message Type: MPC_INVOICE (Invoice)
  • X12 Format: 810
  • Transform Names:
    • B2B_EDI_X12_810_Invoice_IB_V3
    • B2B_EDI_X12_810_Invoice_OB_V1

When sending an Invoice X12 810 message from your company inbound to TraceLink, the following hierarchy must be adhered to for TraceLink to correctly process the B2B message:

Tag end