Orderful invoices (EDI 810) can be transferred to iPaaS.com as transactions, including their addresses, line items, and payment terms. The integration records the invoice header along with the Orderful EDI detail (currency, sender and receiver identifiers, terms of sale, dates, and message status).
ID Format
Manual Sync ID Format
On the iPaaS.com Manual Sync page, enter the Orderful transaction ID. Example: 1009.
External ID Format
iPaaS.com saves the Orderful transaction ID as the external ID on a dedicated external-ID record (the primary match for later updates). The invoice number is also stored in the transaction number field for visibility and fallback matching.
Deleted Record Support
Outbound delete is not supported. Deletions are not propagated to Orderful, and delete mappings are not included in the default templates.
Custom Field Support
The Orderful EDI detail is captured into iPaaS.com custom fields (business number, currency, sender/receiver identifiers, terms of sale, dates, and message status). No additional custom-field configuration is required.
Mapping Collection Status
Status: Enabled (filtered to invoice documents)
Trigger Events: Retrieved by polling from Dashboard / Integration Monitoring / Events.
Duplicate or Conflicting Mappings
Add Orderful Invoice FROM iPaaS.com transfers invoices in the opposite direction.
Review filters and Add/Update settings before enabling these together, and decide which system is the source of truth for invoice data.
Supported Child Collections
Add Orderful Invoice Address TO iPaaS.com — the addresses on the invoice.
Add Orderful Invoice Line TO iPaaS.com — the line items on the invoice.
Add Orderful Invoice Payment Terms TO iPaaS.com — the payment terms on the invoice.
System Caveats
Orderful Caveats
Orderful does not provide an email address in standard EDI fields, so a static placeholder email is used (replace if a real address is needed). Many Orderful EDI elements, including the terms of sale, are carried as custom fields.
iPaaS.com Caveats
Addresses, line items, and payment terms are recorded through the child collections. The transaction status is set from the Orderful status through a lookup translation.
Integration Flow
An invoice (810) is retrieved from Orderful by polling (or on demand via Manual Sync).
The integration creates the iPaaS.com transaction with the invoice header and the Orderful EDI detail.
The invoice's addresses, line items, and payment terms are recorded through the child collections.
The Orderful transaction ID is saved as the external ID.
Mappings
Add Orderful Invoice TO iPaaS.com
Mapping Filter: Type.Name == "810_INVOICE" — only transactions whose type is an 810 invoice are processed; transactions of any other type are skipped.
The invoice header, including the Orderful EDI identifiers, currency, terms of sale, dates, totals, and status.
Mapping Type | Source Field (Orderful) | Destination Field (iPaaS.com) | Description |
Static | EmailAddress | Placeholder — Orderful does not provide an email in EDI; replace before go-live. | |
Field | BusinessNumber | Orderful BusinessNumber | The trading-partner relationship the invoice belongs to. |
Field | Currency_CurrencyCode | Orderful Currency Code | The currency code for the invoice amounts, for example USD. |
Field | Currency_EntityIdentifierCode | Orderful Currency Entity Identifier Code | The entity identifier code for the currency segment. |
Field | BeginningSegmentForInvoice_Date | Orderful Date | The invoice date, in CCYYMMDD format. |
Field | Delivered_DateTimeReference_Date | Orderful Delivered DateTimeReference Date | The date corresponding to the delivered qualifier. |
Field | Delivered_DateTimeReference_DateTimeQualifier | Orderful Delivered DateTimeReference DateTimeQualifier | Type of date given (DTM02); 002 means Delivery Requested. |
Field | href | Orderful href | The Orderful API address of the transaction message, for reference. |
Field | AdministrativeCommunicationsContact_ContactFunctionCode | Orderful Invoice Administrative Communications Contact Function Code | The role of the administrative communications contact. |
Field | AdministrativeCommunicationsContact_Name | Orderful Invoice Administrative Communications Contact Name | The name of the administrative communications contact. |
Field | AcknowledgmentStatus | Orderful Message Acknowledgement Status | APPROVED or REJECTED. |
Field | DeliveryStatus | Orderful Message Delivery Status | DELIVERED or FAILED. |
Field | BeginningSegmentForInvoice_PurchaseOrderNumber | Orderful Purchase Order Number | The purchase order number related to this invoice. |
Field | Receiver_IsaId | Orderful Receiver IsaId | The receiver's ISA interchange ID. |
Field | Receiver_IsaIdQualifier | Orderful Receiver IsaIdQualifier | The qualifier for the receiver's ISA interchange ID. |
Field | Receiver_Name | Orderful Receiver Name | The name of the party receiving the invoice. |
Field | Sender_IsaId | Orderful Sender isaID | The sender's ISA interchange ID. |
Field | Sender_IsaIdQualifier | Orderful Sender IsaIdQualifier | The qualifier for the sender's ISA interchange ID. |
Field | Sender_Name | Orderful Sender Name | The name of the party sending the invoice. |
Field | Shipped_DateTimeReference_Date | Orderful Shipped DateTimeReference Date | The date corresponding to the shipped qualifier. |
Field | Shipped_DateTimeReference_DateTimeQualifier | Orderful Shipped DateTimeReference DateTimeQualifier | Type of date given (DTM02) for the shipped date reference. |
Field | Stream | Orderful Stream | The Orderful stream the transaction was received on, such as TEST or LIVE. |
Field | TermsOfSale_TermsBasisDateCode | Orderful Terms Basis Date Code | The code identifying the date the payment terms are calculated from. |
Field | TermsOfSale_Description | Orderful Terms Description | A description of the payment terms. |
Field | TermsOfSale_TermsNetDays | Orderful Terms Net Days | The number of days until the net amount is due. |
Field | TermsOfSale_TermsNetDueDate | Orderful Terms Net Due Date | The date the net amount is due. |
Field | TermsOfSale_TermsTypeCode | Orderful Terms Type Code | The code identifying the type of payment terms. |
Field | TransactionSetHeader_TransactionSetControlNumber | Orderful Transaction Set Control Number | A control number unique within the transaction set (length 4 to 9). |
Field | BeginningSegmentForInvoice_TransactionSetPurposeCode | Orderful Transaction Set Purpose Code | Purpose of the transaction; 00 means Original. |
Lookup | Lookup Translation: Orderful Transaction Status To iPaaS | Status | Converts the Orderful transaction status to the iPaaS.com transaction status. |
Dynamic Formula | Sum of line quantity times unit price | Subtotal | The invoice subtotal, computed across the line items. |
Dynamic Formula | iPaaS.com subscription | SystemId | The subscription that owns the transaction. |
Dynamic Formula | Sum of line quantity times unit price | Total | The invoice total, computed across the line items. |
Dynamic Formula | Sum of line quantity | TotalQty | The total quantity, computed across the line items. |
Field | BeginningSegmentForInvoice_InvoiceNumber | TransactionNumber | The invoice number, stored for visibility and fallback matching. The Orderful transaction ID is the external-ID link. |
Static | "Invoice" | Type | Sets the iPaaS.com transaction type to Invoice. |
The Orderful Transaction Status To iPaaS lookup translation maps each Orderful transaction status to the corresponding iPaaS.com transaction status; the value pairs are maintained in that translation collection.
Add Orderful Invoice Address TO iPaaS.com
The addresses on the invoice. Each address links to the parent transaction by a composite external ID made of the entity identifier code and the parent transaction ID (for example, ST then 4).
Mapping Type | Source Field (Orderful) | Destination Field (iPaaS.com) | Description |
Field | AddressInformation | Address1 | The first line of the address. |
Field | CityName | City | The city of the address. |
Field | Name | FirstName | The party name on the address. |
Dynamic Formula | Entity identifier code | IsPrimaryBilling | Marks the billing address; BT means Bill To. |
Dynamic Formula | Entity identifier code | IsPrimaryShipping | Marks the shipping address; ST means Ship To. |
Field | EntityIdentifierCode | Orderful Entity Identifier Code | The address role; for example BT, ST, BY. |
Field | PostalCode | PostalCode | The postal code of the address. |
Field | StateOrProvinceCode | Region | The two-character state or province code. |
Add Orderful Invoice Line TO iPaaS.com
The line items on the invoice. Each line links to the parent transaction by a composite external ID made of the line number and the parent transaction ID (for example, 1 then 4).
Mapping Type | Source Field (Orderful) | Destination Field (iPaaS.com) | Description |
Field | Description | Description | A free-form product description. |
Dynamic Formula | Quantity times unit price | ExtendedPrice | The extended price for the line. |
Field | AssignedIdentification | Orderful Assigned Identification | The line number of the item. |
Field | ItemDescriptionTypeCode | Orderful Item Description Code Type | Type of item description (PID05); F means Free-Form. |
Field | ProductServiceID | Orderful Product Service ID | The product/service identifier per the qualifier (PO105). |
Field | ProductServiceID1 | Orderful Product Service ID 1 | The second product/service identifier value (PO107). |
Field | ProductServiceIDQualifier | Orderful Product Service ID Qualifier | Type of item reference (PO106); UP means Universal Product Code. |
Field | ProductServiceIDQualifier1 | Orderful Product Service ID Qualifier 1 | The second item reference qualifier (PO108); VN means Vendor's Item Number. |
Field | UnitOrBasisForMeasurementCode | Orderful Unit | The unit of measure for the quantity (PO103); CA means Case. |
Field | Quantity | Qty | The quantity invoiced. |
Field | ProductServiceID | Sku | The product/service identifier used as the line SKU (PO105). |
Static | "Pending" | Status | Sets each line's status to Pending. |
Static | "Product" | Type | Sets each line's type to Product. |
Field | UnitPrice | UnitPrice | The price of the item for the unit of measure. |
Add Orderful Invoice Payment Terms TO iPaaS.com
The payment terms on the invoice. This is a parent-driven collection — the payment terms are derived from the parent invoice and processed only when the invoice carries a terms-of-sale description.
Mapping Type | Source Field (Orderful) | Destination Field (iPaaS.com) | Description |
Dynamic Formula | Invoice total monetary value summary | Amount | The payment amount. |
Dynamic Formula | Terms of sale | Method | A description of the payment terms. |
Dynamic Formula | Terms of sale description | Orderful Terms of Sale Description | A description of the payment terms. |
Dynamic Formula | Terms basis date code | Orderful Terms of Sale Terms Basis Date Code | The date the terms start from; 3 means Invoice date. |
Dynamic Formula | Terms net days | Orderful Terms of Sale Terms Net Days | The net number of days; 30 means due 30 days after the basis date. |
Dynamic Formula | Terms type code | Orderful Terms of Sale Terms Type Code | The type of payment terms; 01 means Basic. |
Error Handling
See the Orderful Error Messages article for the full catalog. This inbound flow surfaces "The Transaction Type is not valid" when the returned transaction is empty or unsupported — resolution: confirm the type is supported and the transaction ID exists in Orderful.
Testing & Validation
Test Scenarios
Sync an Orderful invoice by its transaction ID and verify the iPaaS.com transaction is created with its addresses, line items, and payment terms.
Sync an invoice that carries no terms of sale and confirm no payment-terms record is created.
Re-sync an updated invoice and verify children match by their composite keys rather than duplicating.
Validation Checklist
The invoice header, addresses, line items, and payment terms transfer.
The invoice number appears as the transaction number and the Orderful transaction ID is the external ID.
Payment terms are recorded only when the invoice carries terms of sale.
Related Documents