Summary
iPaaS.com creates BigCommerce B2B Edition invoices from orders. When an iPaaS.com Transaction of type Invoice is transferred, this flow instructs BigCommerce to generate the invoice from the corresponding BigCommerce B2B order. Transfers run automatically from subscribed iPaaS.com triggers 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. Capturing invoices and their payments from BigCommerce into iPaaS.com is covered by the companion BigCommerce to iPaaS.com B2B Invoice Mapping Documentation.
Contents
Data Types and Direction
This article documents the following mapping collection and the iPaaS.com data type it operates on. It transfers iPaaS.com to BigCommerce.
Collection | iPaaS.com data type | Direction |
Add BigCommerce B2B Invoice FROM iPaaS.com | Transaction | iPaaS.com to BigCommerce |
ID Format
Manual Sync ID Format
Invoice: enter the iPaaS.com Transaction ID of the invoice transaction.
External ID Format
After the invoice is created, BigCommerce returns the new invoice identifier, which iPaaS.com records as the external ID on the Transaction.
Deleted Record Support
Outbound delete is not supported for this collection. It creates invoices only.
Custom Field Support
The order-resolution logic reads a custom field on the source transaction to identify the originating order. The specific custom field depends on the source system — see the Mappings section.
Mapping Collection Status
The collection ships Enabled. Its filter processes iPaaS.com transactions of type Invoice and excludes deposit-ticket and gift-card-ticket clones. Automatic transfers do not run until the iPaaS.com invoice triggers are enabled — see Setup Requirements.
Duplicate or Conflicting Mappings
This collection creates invoices in BigCommerce; capturing invoices back from BigCommerce is handled by the companion inbound collections. Coordinate the two so an invoice is created once and later changes are captured through the inbound flow.
Collision Handling
Invoices are generated from their originating BigCommerce B2B order. Confirm the order exists in BigCommerce and is resolvable from the source transaction before the invoice is created.
Supported Child Collections
None.
System Caveats
BigCommerce Caveats
B2B Edition required. Invoice creation is available only when the store runs BigCommerce B2B Edition and B2B support is enabled on the subscription.
Order must exist. The invoice is generated from an existing BigCommerce B2B order; the order must exist and be resolvable before the invoice can be created.
Rate limiting. When BigCommerce rate-limits requests, the transfer is automatically rescheduled to resume after the limit window resets — no subscriber action is required.
iPaaS.com Caveats
Invoice-type transactions only. Only transactions of type Invoice are processed; the filter excludes ticket clones.
Order resolution is configuration-specific. The originating order is resolved from a custom field on the source transaction; the resolution logic must match how your environment records the source order (see the Mappings section).
Setup Requirements
Automatic transfers do not run until the iPaaS.com invoice triggers are enabled under Outbound Data Flows in the subscription configuration. Confirm B2B Edition is enabled, and adapt the order-resolution logic to your source system before enabling this collection.
Integration Flow
Invoice creation:
An iPaaS.com invoice trigger fires, or an invoice transaction is manually synced by its iPaaS.com Transaction ID.
The filter processes the transaction only when its type is Invoice and it is not a ticket clone.
The originating BigCommerce B2B order is resolved from a custom field on the source transaction.
BigCommerce generates the invoice from that order, and the new invoice identifier is recorded on the Transaction as its external ID.
Mappings
Add BigCommerce B2B Invoice FROM iPaaS.com
iPaaS.com data type: Transaction
Creates a BigCommerce B2B invoice from its originating order.
Mapping Filter: processes a transaction only when its type is Invoice and its transaction number does not end in -D (deposit-ticket clone) or -GC (gift-card-ticket clone).
Mapping Type | Source Field (iPaaS.com) | Destination Field (BigCommerce) | Description |
Static |
| CreateInvoiceFromOrder | Required. A fixed value that instructs BigCommerce to generate the invoice from its B2B order. |
Dynamic Formula | resolves the BigCommerce B2B order from the source transaction | B2B_OrderId | Required. The BigCommerce B2B order the invoice is generated from. See the placeholder note below. |
Placeholder value — replace during implementation: the order-resolution logic that supplies B2B_OrderId is an example specific to a source system. As configured, it reads a NetSuite Sales Order ID custom field, resolves the iPaaS.com transaction from a specific source subscription, then resolves the BigCommerce order and its B2B order ID. Replace this logic with the resolution that matches your source system and remove the hardcoded source-subscription reference before enabling this collection. Validate the invoice-creation flow end to end in a staging environment first.
Testing and Validation
Test Scenarios
Invoice creation. Manually sync an iPaaS.com invoice transaction whose originating order exists in BigCommerce, and confirm BigCommerce generates the invoice and the new invoice identifier is recorded as the Transaction's external ID.
Filter. Confirm a non-invoice transaction, and a ticket-clone transaction (-D / -GC), are skipped.
Order resolution. With the order-resolution logic adapted to your source system, confirm the correct BigCommerce B2B order is resolved; confirm a transaction whose order cannot be resolved raises a clear error.
Validation Checklist
B2B Edition is enabled and the iPaaS.com invoice triggers are configured before expecting automatic transfers.
The order-resolution logic has been adapted to your source system and the hardcoded source-subscription reference removed.
The originating BigCommerce B2B order exists and is resolvable before the invoice is created.
Additional Notes
Order-resolution logic is subscriber-specific. The supplied logic resolves the order through a source-system (NetSuite) custom field and a hardcoded source subscription; adapt it to your environment before enabling this collection.
Inbound direction. Capturing invoices and their payments from BigCommerce into iPaaS.com is documented separately in the companion BigCommerce to iPaaS.com B2B Invoice Mapping Documentation.