BigCommerce B2B Edition invoices and their payments transfer into iPaaS.com. An invoice is captured onto the Transaction that represents its originating order — adding the invoice's external ID, due date, open balance, and status — and the payments applied to the invoice are captured as Transaction Payments on that Transaction. 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 is recorded on the same Transaction as its originating order — it does not create a separate record. 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's BigCommerce external ID is recorded on the Transaction (through the BC B2B Invoice External ID field), and each payment's BigCommerce identifier is recorded on its Transaction Payment, so invoices and 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 collection updates the same Transaction that the order collections create. It runs as an Update and carries the order's existing header values forward, so it layers invoice detail onto an existing order rather than creating a competing record. Confirm the originating order has already transferred so the Transaction exists before the invoice update runs.

The invoice is matched to its originating order Transaction through the parent-order link, resolved from the invoice's order number. It does not create a new Transaction. 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. 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 the BigCommerce Installation Instructions for the poll-event setup steps.

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 originating order's Transaction. It runs as an Update: the identity and financial header fields are carried forward from the existing Transaction, while the invoice-specific fields (external ID, 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's Transaction. This is a child of the invoice collection.

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.