The Alvys to Business Central integration exports, syncs, and posts customer invoices, carrier bills, and driver settlements from Alvys to Business Central (also called Microsoft Dynamics 365 Business Central or BC) and imports payment updates back into Alvys. After connecting, you configure which transaction types to export, how vendors are matched or created, and how subsidiaries and fleets map to Business Central dimensions.

Each Alvys subsidiary is connected to Business Central separately. Complete this process once per subsidiary.

Before connecting, confirm the following:

The companies shown are those that exist in your Business Central environment. To view or verify companies in Business Central: click the Search icon (magnifying glass) in the top-right of the BC header, search for "Companies," and select the related link.

Configure these settings to control how Alvys exports transactions to Business Central. Settings that interact with or conflict with each other are described in the Configuration Dependencies and Incompatible Settings section below.

[Heading 4 not supported]

Select the transaction types to export. Revenue exports customer invoices. Expense exports carrier bills and driver settlements. Your selection here takes precedence over all other configuration settings; if a transaction type is not selected, its associated settings have no effect.

[Heading 4 not supported]

When enabled, driver bills are excluded from export to Business Central. Use this when your operations do not require driver-level payroll entries in your accounting system.

[Heading 4 not supported]

When enabled, all line items on a driver's statement are consolidated into a single bill for export, rather than exporting each individual trip bill. This prevents Business Central from receiving hundreds of separate bills for high-volume drivers.

[Heading 4 not supported]

When enabled, a carrier bill is not exported to Business Central until the physical carrier invoice has been received and verified in Alvys. This prevents premature payouts and ensures expenses match documented carrier invoices.

[Heading 4 not supported]

When enabled, driver payments are separated by tax type when exported. Requires Single Bill for Driver Statement to also be enabled.

[Heading 4 not supported]

When enabled, billing responsibility shifts to a subsidiary carrier rather than the individual driver. This setting is incompatible with Single Bill for Driver Statement and other driver-based billing settings.

[Heading 4 not supported]

When enabled, transactions with a $0 value are excluded from export to Business Central.

[Heading 4 not supported]

When enabled, Alvys creates new vendors in Business Central using the driver's 1099 tax company information rather than the driver's individual profile. Requires Single Bill for Driver Statement to also be enabled.

[Heading 4 not supported]

When enabled, carrier statements are exported as a batch rather than as individual carrier bills. This is intended for specific carrier billing workflows; enable only when this export model is required for your operations.

[Heading 4 not supported]

When enabled, fuel costs that are deducted from driver pay are also exported as company overhead expense entries in Business Central.

[Heading 4 not supported]

When enabled, toll costs that are deducted from driver pay are also exported as company overhead expense entries in Business Central. If a driver was not previously configured for company fuel or toll expense export and this setting is later enabled, past transactions will not be exported automatically.

[Heading 4 not supported]

Enter a prefix to be added to all transaction reference numbers exported to Business Central. Use this to distinguish Alvys-originated transactions from those created directly in Business Central.

[Heading 4 not supported]

When enabled, Business Central sends an e-check to the carrier automatically when a carrier bill is generated in Alvys.

[Heading 4 not supported]

When enabled, asset-level Dimension values are added to transactions exported to Business Central.

[Heading 4 not supported]

When enabled, Alvys subsidiaries are mapped to Business Central Dimension values. After enabling this setting, a subsidiary mapping step appears.

You must choose between mapping by Subsidiary or by Fleet. These settings are mutually exclusive; the system does not support enabling both simultaneously.

Prerequisites for Successful Subsidiary Mapping

Each Alvys subsidiary must exist in both Alvys and Business Central before mapping. Confirm your Business Central environment has the corresponding entities configured.

How to Map Alvys Subsidiaries to Business Central

After enabling Subsidiaries, the mapping interface lists your Alvys subsidiaries. Select the corresponding Business Central Dimension value for each subsidiary.

[Heading 4 not supported]

When enabled, Alvys fleets are mapped to Business Central Dimension values. After enabling this setting, a fleet mapping step appears.

How to Map Alvys Fleets to Dimensions

After enabling Fleets, the mapping interface lists your Alvys fleets. Select the corresponding Business Central Dimension value for each fleet.

[Heading 4 not supported]

When enabled, intercompany transactions between subsidiaries are exported to Business Central. Shared Billing must be enabled on both subsidiaries involved in the intercompany transaction; without it, those transactions will not export correctly.

Some settings must be used together, while others must not be enabled at the same time. Review these rules before saving your configuration.

Revenue only: If only the Revenue transaction type is selected, do not enable any of the following: Single Bill for Driver Statement, Generate Carrier Invoice Separately, Process Statement by Tax Category, Pay Subsidiary Carrier, Create Vendor Using 1099 Tax Company, Ignore Driver Bills, Carrier Statements, Export Company Fuel Expense, Export Company Toll Expense. These settings depend on expense or driver bill data and have no effect without the Expense transaction type.

Single Bill for Driver Statement: Do not enable with Ignore Driver Bills or Pay Subsidiary Carrier. Single Bill assumes driver bills are being created and exported; Ignore Driver Bills removes them, and Pay Subsidiary Carrier redirects billing away from the driver entirely.

Process Statement by Tax Category: Requires Single Bill for Driver Statement to be enabled. Do not enable with Ignore Driver Bills or Pay Subsidiary Carrier. This setting depends on driver bill data separated by tax type; if driver bills are excluded or billing is redirected to a subsidiary carrier, tax-based filtering cannot function.

Pay Subsidiary Carrier: Do not enable with Single Bill for Driver Statement, Process Statement by Tax Category, Create Vendor Using 1099 Tax Company, or Ignore Driver Bills. When billing shifts to a subsidiary carrier, any configuration assuming driver-based billing or driver vendor creation becomes invalid.

Ignore Driver Bills: Do not enable with Single Bill for Driver Statement, Process Statement by Tax Category, or Create Vendor Using 1099 Tax Company. Each of these settings depends on driver bills being generated and exported; ignoring driver bills removes the underlying data they require.

Create Vendor Using 1099 Tax Company: Requires Single Bill for Driver Statement to be enabled. Do not enable with Pay Subsidiary Carrier or Ignore Driver Bills. This setting assumes driver-based billing by tax category; if billing redirects to a subsidiary carrier or driver bills are excluded, vendor creation using tax data is no longer applicable.

After saving your configuration, the Business Central integration becomes active for the selected subsidiary. Alvys will begin exporting transactions according to your settings on the next eligible transaction event.

Q: Can I configure the integration for multiple subsidiaries simultaneously?

A: No. The integration must be configured one subsidiary at a time. Return to Management > Integrations and repeat the connection steps for each additional subsidiary.

Q: What happens if I enable only the Revenue transaction type?

A: Only customer invoices are exported to Business Central. Carrier bills, driver settlements, and expense-related settings have no effect. Do not enable expense-specific settings when only Revenue is selected.

Q: What happens if I enable only the Expense transaction type?

A: Only carrier bills and driver settlements are exported to Business Central. Customer invoices are not exported.

Q: What does "Ignore Driver Bills" do?

A: It excludes driver-level bills from export entirely. Use this when you do not need individual driver payroll entries in Business Central, such as when drivers are paid through a separate payroll system.

Q: Can I enable "Single Bill for Driver Statement" with "Pay Subsidiary Carrier"?

A: No. These settings are incompatible. Single Bill consolidates driver-level billing, while Pay Subsidiary Carrier redirects billing away from drivers entirely. Enable only one or the other.

Q: How do I exclude W-2 driver payments from exporting to Business Central?

A: Enable Ignore Driver Bills. This excludes all driver bills from export. If you need to export only certain types of driver payments, review the Process Statement by Tax Category and Single Bill for Driver Statement settings for more targeted control.

Q: Why am I receiving a digit expectation error when exporting a previously $0 transaction?

A: This error can occur when a transaction that previously had a $0 value is updated and re-exported. Enabling Ignore Zero Valued Transactions prevents $0 transactions from being sent in the first place, which avoids this error on subsequent updates. If the error persists after enabling this setting, contact Alvys support.

Q: Can I enable both Ignore Driver Bills and Single Bill for Driver Statement?

A: No. These settings are incompatible. Single Bill depends on driver bills being exported; Ignore Driver Bills removes them before export.

Q: When do fuel and toll expenses sync to Business Central?

A: Fuel and toll expenses sync when the associated load transaction is exported. If Export Company Fuel Expense or Export Company Toll Expense was not enabled when past transactions were processed, those past transactions will not be retroactively exported after the setting is turned on.

Q: Do I need to manually map every individual driver and truck as a Dimension Value?

A: No. Subsidiaries and Fleets are mapped as groups, not as individual drivers or trucks. After enabling the Subsidiaries or Fleets setting, you map each Alvys subsidiary or fleet to its corresponding Business Central Dimension value.

Q: Can I map both Fleets and Subsidiaries to Business Central Dimensions?

A: No. These settings are mutually exclusive. You must choose to map by either Subsidiaries or Fleets, not both simultaneously.

Q: Why has a carrier bill not exported even though the load invoice was generated?

A: If Generate Carrier Invoice Separately is enabled, the carrier bill will not export until the physical carrier invoice has been received and verified in Alvys. Confirm that the carrier invoice has been marked as received on the load. If the invoice is marked received and the bill still has not exported, contact Alvys support.

Q: What happens if a vendor match is not found in Business Central during export?

A: If no matching vendor is found by name or External Accounting ID, Alvys automatically creates a new vendor in Business Central using the carrier or driver's profile information, along with the Default Payment Method you selected during setup.