Event creation with AP Invoice Automation connector

Aptean APIA  •  Article  •  3/25/2026  • 

The Aptean AP Invoice Automation connector synchronizes vendor and financial master data between Business Central and the Aptean Integration Platform (AIP) connector through different types of events. These events ensure that changes in Business Central are automatically communicated to AIP according to the predefined event mappings used for AP Invoice Automation processing.

Vendor synchronization

The Aptean AP Invoice Automation connector supports publishing events when vendor information is created or modified in Business Central. These events ensure that vendor master data and remit address details are synchronized with AIP so that invoices can be validated and processed correctly.

When vendor information is created or updated in Business Central, the connector generates an outbound vendor-createdormodified-v1 event.

The event is triggered in the following scenarios:

  • When a vendor record is created
  • When a vendor record is modified
  • When a vendor remit address is created
  • When a vendor remit address is modified
  • When a vendor remit address is deleted
  • When the Use as Default checkbox is selected for a vendor remit address

This ensures that any changes related to vendor information or default remit address details are synchronized with AIP.

To create or modify vendor information that triggers the vendor event, follow these steps.

  1. Open the Vendor Card page.
  2. Create a new vendor or open an existing vendor record.

  3. Enter or update the required vendor details such as:

    • Vendor No.
    • Name
    • Address information
    • Registration Number
    • VAT Registration Number
    • AP Invoice GL Account

  4. Select the Use as Default checkbox if the remit address should be used as the default remit address.

Vendor remit address synchronization

Vendor remit address information is included in the vendor event payload to ensure correct invoice payment processing.

When a default Vendor Remit Address field value exists, the system uses the remit address information in the event payload.

If no default remit address is found, the system uses the corresponding address information from the Vendor Card page.

If neither the vendor card nor the default remit address contains values, the field values remain blank in the payload.

Event generation

When vendor data is created or updated, an event is created on the AIP Events page.

The Event Type field value displays the event type, vendor-createdormodified-v1.

This event contains the vendor master data and remit address details in the JSON payload and is published to AIP for AP Invoice Automation processing.

Vendor GL Account Synchronization

The APIA GL Account field is available on the Vendor Card to define the G/L account used for AP Invoice Automation.

When a vendor record is created or modified:

  • The APIA GL Account field value is included in the event payload if it is provided.
  • If the field value is left blank, the event is still triggered and the apiaGlAccount field is included with an empty value.

This ensures that the vendor record is synchronized successfully even when the field is not populated.

Vendor deletion synchronization

The Aptean AP Invoice Automation connector supports publishing an event when a vendor record is deleted in Business Central. This ensures that vendor information removed from Business Central is also reflected in AIP to maintain data consistency for AP Invoice Automation processing.

When a vendor record is deleted in Business Central, the connector generates an outbound vendor-deleted-v1 event.

This event includes the essential vendor identification details required by AIP.

To delete a vendor and trigger the vendor deletion event, follow these steps.

  1. Open the Vendor Card page.
  2. Open the vendor record that needs to be deleted.
  3. Verify the vendor details such as:
    • Vendor No.
    • Vendor Name
    • SystemId (unique identifier of the vendor record).
  4. On the action bar, select Delete.
  5. Confirm the deletion by selecting Yes in the confirmation dialog.

Event generation

When the vendor record is deleted, an event is created on the AIP Events page.

The Event Type field displays vendor-deleted-v1. This event sends the vendor identification information required for synchronization with the Aptean Integration Platform (AIP) connector.

This ensures that vendor records deleted in Business Central are also removed from AIP for AP Invoice Automation processing.

G/L Account Synchronization

The Aptean AP Invoice Automation connector supports publishing events when G/L Accounts are created or modified in Business Central. In APIA, G/L Accounts are referred to as Nominals.

When a G/L Account is created or updated in Business Central, the connector generates an outbound glAccount-createdormodified-v1 event.

This event ensures that financial account information required for invoice posting and validation is synchronized with AIP.

To create or modify a G/L account and trigger the synchronization event, follow these steps.

  1. Open the G/L Account Card page.
  2. Create a new G/L Account or open an existing G/L Account record.
  3. Enter or update the required information such as:
    • Account Number
    • Name
    • Search Name
    • Account Type
    • Account Category
    • Account Subcategory
    • Reconciliation Account
    • Direct Posting
    • General Posting Groups
    • VAT Posting Groups
    • Balance
  4. Save the record.

Event generation

When the G/L Account record is created or updated, an event is created on the AIP Events page.

The Event Type field value displays glAccount-createdormodified-v1.
This event sends G/L account information to AIP so that the corresponding nominal accounts are available for invoice validation and posting during AP Invoice Automation processing.

G/L Account deletion synchronization

The Aptean AP Invoice Automation connector synchronizes the deletion of G/L Accounts from Business Central to the Aptean Integration Platform (AIP) connector through event-based integration.

When a G/L Account is deleted in Business Central, the system automatically publishes the glAccount-deleted-v1 event. This event ensures that AIP is notified that the corresponding financial account has been removed from Business Central and should no longer be used for AP Invoice Automation processing.

The event includes the key identifiers required to recognize the deleted account in AIP.

G/L Account deleted event

The glAccount-deleted-v1 event is triggered whenever a G/L Account record is deleted in Business Central.

Event generation

When a G/L Account is deleted, the system automatically creates an event on the AIP Events page.

The Event Type field displays glAccount-deleted-v1. The event is then published to AIP to ensure that the deletion of the financial account is synchronized between Business Central and the AP Invoice Automation system.

Purchase order release synchronization

The Aptean AP Invoice Automation connector synchronizes purchase order release information between Business Central and the Aptean Integration Platform (AIP) connector through event-based integration.

When a purchase order is released in Business Central, the system automatically publishes an event to AIP with all the required information for AP Invoice Automation processing. This ensures that AIP receives the complete purchase order details before invoices are matched against the order.

Purchase order released event

When a purchase order is released, the system creates an event on the AIP Events page.

The Event Type field displays purchaseOrder-released-v1, and the event is published to AIP for invoice matching and validation.

Posted purchase receipt synchronization

The Aptean AP Invoice Automation connector also synchronizes posted purchase receipt information between Business Central and AIP.

When a posted purchase receipt document is created, an event is automatically generated to inform AIP that goods have been received for the corresponding purchase order. This information is used during the three-way matching process between invoice, purchase order, and receipt.

Posted purchase receipt created event

When a posted purchase receipt is created, the system publishes the postedPurchaseReceipt-created-v1 event.

This event ensures that AIP receives the goods receipt information required for accurate invoice matching and validation.