Contents
Summary
A completed order transaction in iPaaS.com can be written into Microsoft Dynamics 365 Business Central as a posted sales invoice through the Add/Update Dynamics 365 Business Central Invoice FROM iPaaS.com family. The parent collection maps the invoice header — it resolves the Business Central customer from the iPaaS.com customer (or company), sets the bill-to customer, the invoice and posting dates, the sell-to address drawn from the transaction's primary shipping address, the email, currency, salesperson, and payment terms, and flags the record so the integration posts it as an invoice rather than an open sales order. Four child collections add the rest of the document within the same transfer: the item lines, a shipping charge line, tax lines, and customer payments applied to the posted invoice.
This invoice family exists so the integration can capture the invoice stage of a completed iPaaS.com order. Once an order is completed it is no longer an open sales order, and this family writes it into Business Central as a posted invoice with its line items, shipping, taxes, and customer payments. Because a posted invoice cannot be edited in Business Central, the first transfer creates and posts the invoice, and later transfers of the same transaction add only new customer payments to the existing posted invoice rather than re-posting it. This invoice flow is mutually exclusive with the open sales order flow: the open sales order collections handle transactions whose status is pending, and this family handles transactions whose status is complete.
ID Format
Manual Sync ID Format
When transferring a completed order from the iPaaS.com Manual Sync page, enter the iPaaS.com transaction (order) record ID of the order to transfer.
External ID Format
After a successful transfer, iPaaS.com saves an external ID that links the iPaaS.com transaction to the posted invoice created in Business Central, so later updates route to the same posted invoice rather than creating a duplicate. The posted invoice external ID combines a fixed prefix with the Business Central posted-invoice identifier.
Example: invoice|7b3e4f3b-1234-4567-89ab-0c1d2e3f4a5b
Each invoice line is identified in Business Central by its line identifier. Customer payments use a composite identifier that combines the invoice the payment applies to with the payment itself, which lets the integration add new payments to the existing posted invoice without disturbing the header or lines.
Customer payment composite example: 7b3e4f3b-1234-4567-89ab-0c1d2e3f4a5b|9d2c1b7a-9876-4321-aaaa-bbbbccccdddd
Deleted Record Support
Outbound delete is not supported for the posted invoice or for any of its child records (lines, shipping line, tax lines, and customer payments). This family creates and posts invoices into Business Central and adds payments to them; it does not delete Business Central records, and deleting a transaction in iPaaS.com does not remove the corresponding posted invoice or any child record in Business Central. Posted invoices and posted payments are not editable in Business Central by design, so they also cannot be removed through this integration. Subscribers who need to reverse or correct a posted invoice should manage that on the Business Central side using its standard reversal and correction processes.
Custom Field Support
Custom fields are supported on the parent invoice collection and on the item, shipping, and tax line collections. To set a Business Central invoice or invoice-line field that is not already in the standard mapping list:
In Business Central, customize the relevant Web Service so it accepts the field on the invoice or invoice-line request. Subscribers or their MiSP can contact iPaaS.com Support for assistance customizing Business Central Web Services.
In iPaaS.com, create a custom field whose name matches the Business Central field name you want to populate.
Map the new custom field to a static or dynamic source.
Each such custom field name and value is included in the invoice record sent to Business Central as-is. The name must be a valid field in your Business Central environment, or Business Central rejects the request.
Mapping Collection Status
Status: Enabled
Trigger Events: Transaction Create, Transaction Update. These collections use the transaction scope set. In this direction, transfers dispatch automatically once subscribers or their MiSP subscribe to the iPaaS.com transaction outbound triggers — enable them in the subscription configuration's Outbound Data Flows section by subscribing to the transaction create and update events. Until those subscriptions are enabled, no automatic transfers occur. This family is not driven by polling and does not use webhooks from Business Central. A Manual Sync can be run at any time. Whether a transferred transaction creates a new posted invoice or adds to an existing one depends on whether the transaction is already linked to a posted invoice in Business Central, not on which event fired — see ID Format.
Duplicate or Conflicting Mappings
Other collections also read the same iPaaS.com transaction entity and may write the same kind of record:
Dynamics Sales Order Add/Update FROM iPaaS.com and its child create or update open sales orders in Business Central from transactions whose status is Pending. This invoice family and the open sales order flow are mutually exclusive by transaction status — the open sales order flow handles pending transactions, and this family handles completed ones, posting them as invoices. A completed transaction follows the invoice path; a pending one follows the open sales order path.
Dynamics Sales Order Add/Update TO iPaaS.com captures orders from Business Central into iPaaS.com — the opposite direction.
Before enabling these collections together, review their status filters and Add/Update settings and decide which system is the source of truth, so the same transaction is not written in conflicting directions or processed by more than one flow.
Collision Handling
This integration does not provide configurable collision-handling methods for the invoice collections. There is no subscriber-selectable conflict-resolution option (such as Error, Remap and Link, or Update and No Link) on these collections. Transactions are instead matched to their posted invoice by the saved external ID — see Duplicate Matching.
Duplicate Matching
Before creating a posted invoice, the integration checks whether the transaction is already linked to a Business Central sales document by its transaction number and links to the existing record instead of creating a duplicate. After the invoice is posted, subsequent transfers of the same transaction add only new customer payments to the existing posted invoice; the header and lines are not re-posted. For customer payments, the integration checks whether a payment with the same amount already applies to the same posted invoice and creates a new payment only when no match is found, so re-sending a transaction does not duplicate a payment. Payments are posted only when the invoice is not already marked paid; when the invoice is already paid, the payment is skipped.
This family does not auto-transfer a related record as a prerequisite except for the customer or company — see Setup Requirements and the parent collection note on customer resolution.
Supported Child Collections
The parent Add/Update Dynamics 365 Business Central Invoice FROM iPaaS.com collection maps the invoice header. Four child collections add the rest of the invoice within the same transfer:
Child Collection | Purpose |
Add/Update Dynamics 365 Business Central Invoice Line FROM iPaaS.com | Maps each transaction line item to an item line on the posted invoice. |
Add/Update Dynamics 365 Business Central Invoice Shipping Line FROM iPaaS.com | Adds the transaction's shipping charge as a general-ledger account line when the transaction has a shipping amount. |
Add/Update Dynamics 365 Business Central Invoice Tax Line FROM iPaaS.com | Adds each transaction tax record as a general-ledger account line. |
Add/Update Dynamics 365 Business Central Invoice Customer Payment FROM iPaaS.com | Creates customer payments applied to the posted invoice. |
Each child collection runs as part of the parent invoice's transfer; the children are not triggered or synced on their own.
System Caveats
Microsoft Dynamics 365 Business Central Caveats
Payment terms must already exist: the payment terms code resolved for the invoice must already exist in Business Central, or the value cannot be resolved. The match is by name and is exact and case-sensitive. Confirm the configured payment terms code exists in your company before the first transfer.
Customer payment journal must exist: the customer payment journal resolved for a payment must already exist in Business Central under Cash Management, Cash Receipt Journals, or the value cannot be resolved and the transfer fails. The match is by name and is exact and case-sensitive.
General-ledger accounts must exist: the general-ledger account numbers used for the shipping line and the tax lines must exist in your Business Central chart of accounts, or those lines are rejected. To find a general-ledger account number, open Search in Business Central, type Chart of Accounts, open it, and read the value in the No. column.
Payment method balancing account: do not configure a balancing account type or number on the payment methods used by this integration. When a balancing account is set, Business Central automatically creates a balancing entry during posting, which auto-applies and closes the payment and prevents the integration from linking it to the invoice correctly.
Payment amount must be negative: Business Central requires a negative amount to post a customer payment; the integration converts a positive payment amount to negative automatically before sending it.
Bin-mandatory locations: if a Business Central location has bin-mandatory enabled, every item line must have a bin defined, or invoice posting fails. Assign a default bin to the items, or use a location that does not require bins.
Customer location code: if a line does not specify a location, Business Central uses the customer's default location code.
Items must exist: the SKU on each transaction line must match an item number in your Business Central company, or the line is rejected.
Posted records are not editable: posted invoices and posted payments cannot be changed in Business Central; this integration is designed to add new payments to a posted invoice, not to edit a posted invoice or a previously posted payment.
Tax configuration: the template mappings transfer tax as general-ledger account lines on the invoice. For invoice totals to match, customers, items, and shipping should be configured not to collect tax in Business Central, so tax is reflected only through these lines. If totals are mismatched because only the subtotal is mapped, configure tax in Business Central — enable tax-liable and assign the tax area code on the customer, assign a tax group code on items, set the shipping general-ledger account as nontaxable, and define the tax area, tax group, and percentage mappings. Subscribers or their MiSP should confirm this with their tax setup.
iPaaS.com Caveats
Customer or company must exist or be created first: the Business Central customer or company referenced by the transaction must already exist in iPaaS.com with a Business Central external ID, or the integration creates the customer or company as part of this transfer before posting the invoice. If the customer or company cannot be created, the invoice transfer fails.
Sell-to address requires a primary shipping address: the sell-to address fields populate only when the transaction has an address flagged as the primary shipping address. Without one, those fields are left unset.
Shipping line requires a shipping amount: the shipping line is added only when the transaction has a shipping amount; transactions without one get no shipping line.
Tax lines require tax records: a tax line is added only when the transaction has tax records; transactions without tax get no tax line.
Custom fields must exist first: a mapped custom field stores a value only when a custom field of a matching name exists; otherwise the value is not stored.
Integration-Specific Caveats
Completed orders only become invoices: only transactions whose type is order and whose status is complete are posted as invoices through this family. Pending transactions are handled by the open sales order flow instead.
Updates add payments only: after the first transfer posts the invoice, later transfers of the same transaction add only new customer payments to the existing posted invoice, because a posted invoice cannot be edited. The header and lines are not re-posted.
Currency, salesperson, location, journal, payment terms, and general-ledger accounts ship with example values: these are placeholder values that must be reviewed and replaced to match your Business Central setup before the first transfer.
Setup Requirements
Microsoft Dynamics 365 Business Central Configuration
Configure records the mappings resolve by name or number so they already exist before the first transfer: the Payment Terms code, the Customer Payment Journal (under Cash Management, Cash Receipt Journals), the general-ledger accounts used for shipping and tax charges, and any location codes referenced by the line mappings.
Ensure the items referenced by the transaction SKUs exist in your company, and that any bin-mandatory locations have default bins assigned to those items.
Confirm the payment methods used by this integration do not have a balancing account configured.
Confirm tax setup matches how tax is transferred (as general-ledger account lines) so invoice totals reconcile.
Enable the Web Services the integration needs to read and write sales invoices, customer payments, and journals. If custom fields are mapped, customize the relevant Web Service to accept them.
Authentication uses Business Central API credentials; ensure credentials are stored securely in the iPaaS.com credential manager.
For the full installation walkthrough, see the Installation Instructions.
iPaaS.com Configuration
In the subscription configuration's Outbound Data Flows section, subscribe to the transaction create and update events to enable automatic transfers.
Ensure the Business Central customer or company referenced by each transaction exists in iPaaS.com with a Business Central external ID, or rely on the prerequisite handling that creates it before posting.
Replace the shipped example static values (currency, salesperson, location code, payment terms name, customer payment journal name, and the shipping and tax general-ledger account numbers) with values configured in your Business Central company.
Create custom fields whose names match the Business Central field names for any custom-field mappings in use.
Subscribers or their MiSP can contact iPaaS.com Support for assistance configuring Business Central Web Services.
Because Business Central enforces invoice, line, payment, and posting requirements through your company configuration rather than a public API specification, validate this family in a staging environment before relying on it in production.
Integration Flow
An order is completed in iPaaS.com (type order, status complete), and the corresponding transaction outbound trigger fires, or a subscriber runs a Manual Sync using the iPaaS.com transaction record ID.
The parent mapping filter confirms the transaction is a completed order; pending transactions follow the open sales order path instead.
The integration ensures the customer exists in Business Central. If the iPaaS.com customer has no Business Central external ID, the integration transfers the customer (or, when the transaction is tied to a company, the company) to Business Central first; if it cannot be created, the invoice transfer fails.
iPaaS.com authenticates with Business Central.
The parent collection maps the invoice header — customer, bill-to customer, invoice and posting dates, payment terms, currency, salesperson, email, and sell-to address — and a draft sales invoice is created in the Business Central company.
The item line child collection adds each transaction line as an item line on the draft invoice.
The shipping line child collection adds a general-ledger account line for the shipping charge when the transaction has a shipping amount.
The tax line child collection adds a general-ledger account line for each transaction tax record.
The draft invoice is posted to a posted sales invoice and given its external ID.
The customer payment child collection creates and posts customer payments applied to the posted invoice, each amount converted to negative as Business Central requires.
On a later transfer of the same transaction, the integration matches the existing posted invoice by external ID and adds only new customer payments; the header and lines are unchanged.
Transfer status and any errors are recorded in the iPaaS.com Dashboard under Integration Monitoring and the Error Logs.
Mappings
Add/Update Dynamics 365 Business Central Invoice FROM iPaaS.com (Parent)
iPaaS.com data type: Transaction
Mapping Filter
Type == "Order" && Status == "Complete"
Filter Description. Only iPaaS.com transactions whose type is Order and whose status is Complete pass this filter. Drafts, pending orders, and non-completed transactions are ignored, so only financially ready orders become posted invoices in Business Central. Pending transactions are handled by the open sales order flow.
This collection maps the invoice header and is the parent of the four child collections below.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Microsoft Dynamics 365 Business Central) | Description |
Dynamic Formula |
| CustomerId | Required. Resolves the Business Central customer number for the invoice. It first looks for the iPaaS.com customer's Business Central external ID; if there is none, it falls back to the company's external ID. The customer or company must already exist in Business Central, or the integration creates it as part of this transfer before posting the invoice. |
Dynamic Formula |
| IsInvoice | Required. Flags this record so the integration posts a sales invoice in Business Central rather than creating an open sales order. Without it the transaction would be handled as an open sales order. |
Dynamic Formula |
| PostedInvoice_BillToCustomerId | Recommended. Sets the bill-to customer number on the invoice, using the same logic as the customer field — the iPaaS.com customer's Business Central external ID first, then the company's external ID. |
Dynamic Formula |
| PostedInvoice_InvoiceDate | Recommended. Sets the invoice date from the transaction's creation date, formatted as a year-month-day string. Left unset when the transaction has no creation date. |
Dynamic Formula |
| PostedInvoice_PostingDate | Recommended. Sets the posting date from the transaction's creation date, formatted as a year-month-day string. Left unset when the transaction has no creation date. |
Dynamic Formula |
| PostedInvoice_PaymentTermsId | Recommended. Resolves the Business Central payment terms by matching the payment terms name exactly to a payment terms code in your company. |
Static |
| PostedInvoice_CurrencyCode | Optional. Sets the currency code on the invoice. |
Static |
| PostedInvoice_Salesperson | Optional. Sets the salesperson code on the invoice. |
Field |
| PostedInvoice_Email | Optional. Sets the email on the invoice from the iPaaS.com transaction email address. |
Dynamic Formula |
| PostedInvoice_SellToAddressLine1 | Optional. Sets the sell-to address line from the transaction's primary shipping address. Left unset if the transaction has no primary shipping address. |
Dynamic Formula |
| PostedInvoice_SellToCity | Optional. Sets the sell-to city from the transaction's primary shipping address. Left unset if the transaction has no primary shipping address. |
Dynamic Formula |
| PostedInvoice_SellToCountry | Optional. Sets the sell-to country from the transaction's primary shipping address. The country value must match an existing country/region code in your Business Central company. Left unset if the transaction has no primary shipping address. |
Dynamic Formula |
| PostedInvoice_SellToState | Optional. Sets the sell-to state or region from the region on the transaction's primary shipping address. Left unset if the transaction has no primary shipping address. |
Dynamic Formula |
| PostedInvoice_SellToPostCode | Optional. Sets the sell-to postal code from the transaction's primary shipping address. Left unset if the transaction has no primary shipping address. |
Note on payment posting. In Business Central, when a payment method such as cash has a balancing account configured, the system automatically uses that account as the offset entry and can auto-post and auto-apply the payment against invoices, so payments may not appear as separate records. When the balancing account is removed from the payment method, invoices and payments follow the standard posting pattern and are stored as distinct documents the integration can process normally.
Add/Update Dynamics 365 Business Central Invoice Line FROM iPaaS.com (Child)
iPaaS.com data type: Transaction Line
This collection is a child of the invoice parent. It has no mapping filter, so every line item on a qualifying transaction is processed. It maps each transaction line to an item line on the posted invoice and supports custom fields.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Microsoft Dynamics 365 Business Central) | Description |
Field |
| LineObjectNumber | Required. Links the invoice line to a Business Central item using the transaction line's SKU. The SKU must match an item number in your Business Central company, or the line is rejected. |
Field |
| Quantity | Required. Sets the quantity for the invoice line from the transaction line quantity. |
Field |
| PostedInvoiceItem_UnitPrice | Required. Sets the unit price for the invoice line from the transaction line unit price. |
Dynamic Formula |
| PostedInvoiceItem_LineType | Required (designed constant). Sets the line type to item so the line is treated as an inventory item line on the invoice. |
Dynamic Formula |
| PostedInvoiceItem_LocationId | Recommended. Resolves an inventory location code to its Business Central location and sets it on the invoice line. |
Field |
| Description | Optional. Sets the invoice line description from the transaction line description. |
Add/Update Dynamics 365 Business Central Invoice Shipping Line FROM iPaaS.com (Child)
iPaaS.com data type: Transaction Line
This collection is a child of the invoice parent. It adds the transaction's shipping charge to the posted invoice as a general-ledger account line and supports custom fields.
Mapping Filter
SourceTypeName== "ParentOnly" && Parent.ShippingAmount != null
Filter Description. A shipping line is added only when the source is the parent transaction (SourceTypeName is ParentOnly) and the parent transaction has a shipping amount. Transactions without a shipping amount do not get a shipping line.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Microsoft Dynamics 365 Business Central) | Description |
Static |
| LineObjectNumber | Required. Sets the general-ledger account number used for the shipping line. |
Dynamic Formula |
| PostedInvoiceItem_LineType | Required (designed constant). Sets the line type so the shipping charge is posted to a general-ledger account rather than an inventory item. |
Dynamic Formula |
| PostedInvoiceItem_UnitPrice | Required. Sets the shipping line amount from the parent transaction's shipping amount. The shipping line is added only when the parent transaction has a shipping amount. |
Static |
| Quantity | Required (designed constant). Sets the shipping line quantity to one. |
Static |
| Description | Optional. Sets the description shown on the shipping line. Adjust it if you want a different label. |
Add/Update Dynamics 365 Business Central Invoice Tax Line FROM iPaaS.com (Child)
iPaaS.com data type: Transaction Tax
This collection is a child of the invoice parent. It has no mapping filter, so each transaction tax record on a qualifying transaction produces a tax line. It adds the transaction's tax to the posted invoice as a general-ledger account line.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Microsoft Dynamics 365 Business Central) | Description |
Static |
| PostedInvoiceItem_lineObjectNumber | Required. Sets the general-ledger account number used for the tax line. |
Static |
| PostedInvoiceItem_LineType | Required (designed constant). Sets the line type so the tax is posted to a general-ledger account rather than an inventory item. |
Field |
| PostedInvoiceItem_UnitPrice | Required. Sets the tax line amount from the transaction tax record amount. |
Static |
| PostedInvoiceItem_Quantity | Required (designed constant). Sets the tax line quantity to one. |
Static |
| PostedInvoiceItem_Description | Optional. Sets the description shown on the tax line. Adjust it if you want a different label. |
Only the description, line type, unit price, quantity, and the general-ledger account number are supported for transfer through this collection.
Add/Update Dynamics 365 Business Central Invoice Customer Payment FROM iPaaS.com (Child)
iPaaS.com data type: Transaction Payment
This collection is a child of the invoice parent. It has no mapping filter, so each payment on a qualifying transaction is processed. It creates a posted customer payment in Business Central and applies it to the posted invoice.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Microsoft Dynamics 365 Business Central) | Description |
Dynamic Formula |
| CustomerId | Required. Resolves the Business Central customer number for the payment from the parent transaction's customer. It first looks for the parent transaction customer's Business Central external ID; if there is none, it falls back to the parent company's external ID. |
Dynamic Formula |
| JournalId | Required. Resolves the Business Central customer payment journal by matching the journal name exactly to a journal code in your company. |
Dynamic Formula |
| Amount | Required. Sets the payment amount and converts it to a negative value. Business Central requires a negative amount to post a customer payment, so a positive payment amount is negated before it is sent. |
Dynamic Formula |
| PostingDate | Recommended. Sets the payment posting date from the parent transaction's creation date, formatted as a year-month-day string. Left unset when the parent transaction has no creation date. |
Field |
| Description | Optional. Sets the payment description from the transaction payment description. |
Error Handling
For the complete catalog of error messages this integration can produce, see the Error Messages article. The conditions most relevant to the invoice transfer are:
Invalid tax code or general-ledger account number: Business Central rejects an invalid or non-existent general-ledger account on a shipping or tax line. Resolution: replace the example account number with a valid account configured in your Business Central chart of accounts.
Inventory account missing in inventory posting setup: Business Central cannot find an inventory account for the line's location code and posting group when posting an item line. Resolution: configure a valid inventory account in Inventory Posting Setup for that location and posting group combination.
Location code cannot be converted: the Business Central API expects a location identifier but the supplied location code does not resolve. Resolution: ensure the location code maps to a location that exists in Business Central, or leave it to the customer's default location.
Missing journal: Business Central requires a valid customer payment journal to post a payment. Resolution: ensure the journal named in the payment mapping exists under Cash Management, Cash Receipt Journals.
Payment amount must be negative: Business Central expects a negative customer payment amount. The integration negates positive amounts automatically; if a payment still fails on amount sign, verify the source amount is not already negated upstream.
Customer posting group missing on the customer: the Business Central customer record is missing a required customer posting group. Resolution: assign a valid customer posting group to the customer record.
Unbalanced general-ledger entry: a posting is not balanced. Resolution: review the posting setup (customer posting group, general posting setup) so debits and credits balance.
Errors and transfer status for every invoice transfer are recorded in the iPaaS.com Dashboard under Integration Monitoring and the Error Logs.
Validation Rules
Transaction qualification: only transactions whose type is order and whose status is complete are posted as invoices; pending transactions follow the open sales order path.
Customer resolution: the customer or bill-to customer must resolve to a Business Central customer (by customer external ID, then company external ID) before the invoice is created; the customer or company is created first if it does not yet exist.
Invoice flag: the invoice flag must be set so the record is posted as an invoice rather than an open sales order.
Line requirements: each item line requires a SKU that matches a Business Central item, a quantity, a unit price, and the item line type.
Shipping line condition: a shipping line is added only when the source is the parent transaction and the parent transaction has a shipping amount.
Tax line requirements: each tax line requires a valid general-ledger account, the general-ledger account line type, the tax amount, and a quantity.
Payment requirements: a customer payment requires a resolved customer, a valid customer payment journal, and a negative amount; it is skipped when the invoice is already paid.
General-ledger accounts: the static general-ledger account numbers used for shipping and tax must exist in Business Central.
Testing and Validation
Test Scenarios
Basic invoice creation. Send a completed order transaction with a valid customer external ID and at least one transaction line. Confirm a posted invoice is created in Business Central with the matching header and item lines, and no payment when none is provided.
Invoice with payment. Send the same transaction with a transaction payment record. Confirm the posted invoice is created and a posted customer payment is applied to it with the correct negative amount.
Update adds a payment only. Re-send the same transaction with an additional payment. Confirm a new customer payment is created and linked to the existing posted invoice, while the header and lines are unchanged.
Invoice without shipping. Send a transaction with item lines but no shipping amount. Confirm the posted invoice has item lines only, with no shipping general-ledger line, and the payment is created normally.
Invoice with multiple tax rows. Send a transaction with multiple tax records. Confirm each tax record creates a separate general-ledger account line on the invoice.
Required record validation. Transfer while the shipped example payment terms, customer payment journal, location code, or general-ledger account values are still in place and do not exist in your company. Confirm the relevant transfer fails, then replace the values with existing ones and confirm the transfer succeeds.
Mutual exclusivity. Confirm that a pending transaction is handled by the open sales order flow and a completed transaction is handled by this invoice flow, so the same transaction is not posted twice.
Validation Checklist
Customer and company external IDs resolve to Business Central customers before invoice creation.
The payment terms name in the parent mapping matches a Business Central payment terms code.
The customer payment journal name in the payment mapping matches a journal under Cash Management, Cash Receipt Journals.
Location codes and any required bins are configured in Business Central for the items being invoiced.
The static currency, salesperson, and shipping and tax general-ledger account values are valid in your Business Central company.
Payment methods used by this integration have no balancing account configured.
Shipping and tax amounts on the posted invoice match the source transaction totals.
Payments on the posted invoice reflect the correct negative amounts and reference the correct invoice.
Web Services are enabled for sales invoices, customer payments, and journals; custom fields exist with matching names for any custom-field mappings in use, and the relevant Web Service is customized to accept them.
The transaction outbound triggers are subscribed in Outbound Data Flows if automatic transfers are wanted.
Additional Notes
This invoice family and the open sales order family are mutually exclusive by transaction status: pending transactions become open sales orders, and completed transactions become posted invoices. Review the status filters on both before enabling them together.
At the time this documentation was written, after the first transfer posts the invoice, later transfers of the same transaction add only new customer payments to the existing posted invoice, because a posted invoice cannot be edited in Business Central.
At the time this documentation was written, the payment amount is always posted as a negative value, and a payment is skipped when the invoice is already marked paid.
The shipping and tax lines transfer tax and freight as general-ledger account lines; for invoice totals to reconcile, customers, items, and shipping should be configured not to collect tax in Business Central.
Outbound delete is not supported; deleting a transaction in iPaaS.com does not remove the posted invoice or any child record in Business Central.
Related Documents
Connections and Settings (pending publication)
Known Limitations (pending publication)