Invoices that iPaaS.com created in BigCommerce B2B Edition come back into iPaaS.com, with their payments. The supported flow is a round trip: an iPaaS.com Invoice Transaction (typically created by your ERP once an order ships) creates the invoice in B2B Edition, and later changes to that invoice — its due date, open balance, status, and the payments applied to it — are captured back onto the same Invoice Transaction, with payments recorded as Transaction Payments. Invoices created directly in B2B Edition are not imported. Because BigCommerce B2B Edition does not emit invoice webhooks, invoices are captured through scheduled polling, or on demand from the iPaaS.com Manual Sync page.

This article is the field-level companion to BigCommerce B2B Edition Support. B2B handling is off by default and only applies when B2B support is enabled on the subscription. Creating invoices in BigCommerce from iPaaS.com is covered by the companion iPaaS.com to BigCommerce B2B Invoice Mapping Documentation.

This article documents the following mapping collections and the iPaaS.com data type each one operates on. Every collection here transfers BigCommerce to iPaaS.com.

The invoice updates the Invoice Transaction that created it, which is linked to its originating order as a child (ParentId). It never creates a Transaction. The payment collection is a child of the invoice collection.

Invoice payments have no independent Manual Sync entry point; they transfer as part of the parent invoice.

The Invoice Transaction's external ID is {invoice ID}_INVOICE. It is saved when Add BigCommerce B2B Invoice FROM iPaaS.com creates the invoice, and the inbound invoice collection uses it to find the Invoice Transaction. Each payment's BigCommerce identifier is recorded on its Transaction Payment, so payments are matched and updated in place on later transfers.

Inbound delete is not supported for these collections. Removing an invoice or payment in BigCommerce does not remove the corresponding record in iPaaS.com.

The invoice-specific values (external ID, due date, open balance) and the invoice-payment reference values are carried on iPaaS.com custom fields on the Transaction and Transaction Payment. These custom fields are part of the default configuration and require no manual creation.

Both collections ship Enabled. BigCommerce B2B Edition does not send invoice webhooks, so invoices transfer through a scheduled poll event configured under Inbound Data Flows; the payment child transfers as part of the invoice. The invoice collection processes only records that carry an invoice number, and the payment collection processes only completed payments whose payment method already exists in iPaaS.com (see the Mappings section). Automatic transfers do not run until the poll event is configured — see Setup Requirements.

The invoice poll returns invoices as order-type records, so Add BigCommerce Order TO iPaaS.com and Update BigCommerce Order TO iPaaS.com must skip records that carry an invoice number; their filters include that condition. Only the invoice collection then applies to an invoice. It runs as an Update and keeps the Invoice Transaction's existing header values, so it never creates a competing record.

The invoice is matched to its Invoice Transaction through the {invoice ID}_INVOICE external ID. An invoice without that link (one created directly in B2B Edition) is skipped. Each payment is matched by its BigCommerce payment identifier so it is recorded once and updated in place.

The payment collection is a child of the invoice collection and transfers as part of the invoice.

Automatic transfers do not run until the invoice poll event is configured. Under Inbound Data Flows in the subscription configuration, add a poll event for B2B invoices, and confirm B2B Edition is enabled. Create invoices through Add BigCommerce B2B Invoice FROM iPaaS.com (see the companion iPaaS.com to BigCommerce article). Before enabling the payment collection, run the Initialize Data feature for Payment Methods so the methods referenced by invoice payments exist in iPaaS.com. See BigCommerce B2B Edition Support for the poll-event setup (scope store/order/poll, filters B2B_Invoice and B2B_Invoice_Payment).

Invoice and its payments:

Each collection below lists its Mapping Filter, the iPaaS.com data type it operates on, and its field mapping table. The Description column carries the required/recommended classification and behavior for each field.

iPaaS.com data type: Transaction

Captures a BigCommerce B2B invoice onto the Invoice Transaction that created it. It runs as an Update: the identity and financial header fields keep the Invoice Transaction's values, while the invoice-specific fields (external reference, due date, open balance), the parent-order link, the type, and the status are set from the invoice.

Mapping Filter: processes a record only when the invoice number is present — that is, when the incoming record is an invoice rather than a plain order.

iPaaS.com data type: Transaction Payment

Captures the payments applied to a BigCommerce B2B invoice as Transaction Payments on the Invoice Transaction. This is a child of the invoice collection, so it applies only to invoices created from iPaaS.com.

Mapping Filter: resolves the payment method (the payment gateway when present, otherwise the payer name), searches for a matching payment method in iPaaS.com, and processes the payment only if the method exists and the payment is in a completed processing state. When no matching payment method exists, the transfer stops and asks you to run the Initialize Data feature for Payment Methods so the method exists beforehand.

Related Mapping Documentation