📋 Applies to: Users with "Billing" and "Invoice" permissions (AR invoices) · Users with "Billing" and "ViewCarrierRate" permissions (carrier settlements) · Users with "Billing" and "PayDriver" permissions (driver settlements)
Module: Accounting > Invoicing; Accounting > Carrier Settlements; Accounting > Driver Settlements
Last reviewed: 2026-06 · Owner: Support team
This article (covering Sage Intacct transaction export, record matching, and post-export modification) explains how Alvys exports AR invoices, AP bills, and settlement transactions to Sage Intacct, how customer and carrier records are matched in Sage, and how to modify transactions that have already been exported.
Overview
When Alvys exports transactions to Sage Intacct, it matches each AR transaction to a Sage customer record and each AP transaction to a Sage vendor record. If a match is not found, the transaction fails and appears in Accounting > Error Transactions. Once exported, the way Alvys handles a modification depends on the transaction's current state in Sage.
Where to Find It
Transaction exports are triggered from these sections:
AR invoices: Accounting > Invoicing
Carrier settlement bills: Accounting > Carrier Settlements
Driver settlement bills: Accounting > Driver Settlements
Failed and re-syncable transactions: Accounting > Error Transactions
Key Concepts
Customer and Carrier Matching
Alvys matches exported AR transactions to Sage customers in this order:
By Customer ID set on the Alvys customer record (if configured)
By exact customer name match in Sage
If no match is found: the transaction fails and appears in Error Transactions; the customer must be created or linked in Sage before re-syncing
For AP transactions, Alvys matches to Sage vendors in this order:
By Vendor ID set on the Alvys carrier record (if configured)
By exact carrier name match in Sage
By MC number
If no match is found: the transaction fails; the vendor must be created or linked in Sage before re-syncing
Dual Authority Carriers
If a carrier is designated as Dual Authority in Alvys, Alvys will create both a customer record (for AR invoices) and a vendor record (for AP bills) for that carrier in Sage.
Invoice As
The Invoice As field on an Alvys invoice controls whether the AR invoice exports as a single entity invoice or is split by subsidiary. This determines how the invoice appears in Sage when a load spans multiple Alvys subsidiaries.
Payment Terms
If a customer or carrier has Payment Terms configured in Alvys, those terms are included on exported AR invoices and AP bills in Sage. If no specific payment terms are set, the Default Payment Terms from Advanced Settings in the Sage Intacct connection apply.
Carrier Bill Export Combinations
The settings for carrier AP bill exports work in combination:
If both "Send carrier invoice upon upload" and "Export Carrier Statements" are disabled: no carrier AP bills export.
If only "Send carrier invoice upon upload" is enabled: an individual AP bill exports immediately when a carrier invoice is uploaded in Alvys.
If both are enabled: an individual AP bill exports on upload and a combined carrier statement AP bill is also exported.
How to Use It
Exporting AR Invoices
Go to Accounting > Invoicing. Select the invoice or invoices to export. Alvys validates the customer match and GL account mapping, then sends the transaction to Sage. Invoices that cannot be exported appear in Accounting > Error Transactions.
📷 Image placeholder — Screenshot showing Accounting > Invoicing with the export action button visible. Upload from IC:15333983.
Exporting Carrier Settlements
Go to Accounting > Carrier Settlements. Select the carrier settlement to export. Alvys matches the carrier to a Sage vendor record and exports the AP bill. If the carrier cannot be matched, the transaction appears in Accounting > Error Transactions.
📷 Image placeholder — Screenshot showing Accounting > Carrier Settlements with the export action. Upload from IC:15333983.
Exporting Driver Settlements
Go to Accounting > Driver Settlements. Driver settlements export as AP bills for driver payments. This section requires the DriverSettlement feature and the "PayDriver" permission.
📷 Image placeholder — Screenshot showing Accounting > Driver Settlements with the export action. Upload from IC:15333983.
Modifying an Exported Transaction
How Alvys handles a change to an exported transaction depends on its current state in Sage:
Draft: Alvys updates the transaction directly in Sage with the new values.
Posted: Alvys creates a reversal entry in Sage and posts a new corrected transaction automatically.
Paid or Partially Paid: Remove the payment from the transaction in Sage first. Once the payment is removed, Alvys can apply the reversal and post the corrected transaction.
Closed: This state is a Sage-side restriction; the transaction period has been closed and cannot be modified from Alvys. Contact Alvys support with the load number and the error message if a transaction is stuck in Closed state.
Selected: Alvys cannot automatically reverse a transaction in Selected state. Manually reverse the transaction in Sage Intacct, then re-sync it from Accounting > Error Transactions in Alvys.
📷 Image placeholder — Screenshot showing the transaction state options when modifying an exported transaction. Upload from IC:15333983.
Settings & Permissions
Access to transaction export pages is controlled by Alvys permissions:
Accounting > Invoicing requires "Billing" and "Invoice" permissions.
Accounting > Carrier Settlements requires "Billing" and "ViewCarrierRate" permissions.
Accounting > Driver Settlements requires the DriverSettlement feature flag plus "Billing" and "PayDriver" permissions.
Accounting > Error Transactions requires the "Billing" permission.
Limits & Behavior
Transactions in Closed state in Sage cannot be modified from Alvys; they require Alvys support to resolve.
Transactions in Selected state require a manual reversal in Sage before re-syncing from Alvys.
If a customer or carrier cannot be matched to a Sage record, the transaction fails and appears in Error Transactions.
The DriverSettlement feature must be enabled on your account for Accounting > Driver Settlements to be available.
Alvys does not automatically create Sage customer or vendor records; all matching is against existing records in Sage.
Troubleshooting
AR invoice did not export to Sage
Verify that the customer record in Alvys has a valid match in Sage by Customer ID or exact name. Verify that a GL account is mapped for the invoice line item types. Check Accounting > Error Transactions for the specific failure reason.
AP bill did not export to Sage
Verify that the carrier record in Alvys has a valid vendor match in Sage by Vendor ID, exact name, or MC number. Check Accounting > Error Transactions for the specific failure reason.
Payment terms are not appearing on exported invoices
Verify that Payment Terms are configured on the customer or carrier record in Alvys. If no record-level terms are set, verify that a Default Payment Terms value is configured in the Advanced Settings of the Sage Intacct connection.
Driver Settlements section is not visible
Accounting > Driver Settlements requires the DriverSettlement feature to be enabled on your account. Verify that your user has the "Billing" and "PayDriver" permissions in Alvys.
FAQs
Q: What happens if a customer in Alvys does not have a matching record in Sage?
A: The AR invoice will fail to export and appear in Accounting > Error Transactions. Create the customer in Sage or set the Sage Customer ID on the Alvys customer record, then re-sync the transaction from Error Transactions.
Q: Can Alvys automatically create Sage customer or vendor records?
A: No. Alvys matches to existing records in Sage. If a matching record does not exist, the transaction fails. You must create the customer or vendor in Sage manually.
Q: What is the difference between a Posted and a Closed transaction in Sage?
A: A Posted transaction has been journalized in Sage but can still be reversed by Alvys automatically. A Closed transaction has been closed for the accounting period and cannot be modified; Alvys support is required.
Q: What should I do if a transaction is in Selected state in Sage?
A: Manually reverse the Selected transaction in Sage Intacct, then return to Alvys and re-sync the transaction from Accounting > Error Transactions.
Q: Does Alvys export driver settlement transactions to Sage?
A: Yes, if the DriverSettlement feature is enabled on your account and the export driver settlements toggle is enabled in AP Settings.
Q: What controls whether an AR invoice is split by subsidiary in Sage?
A: The Invoice As field on the Alvys invoice determines whether it exports as a single entity invoice or is split by subsidiary.
Q: Can I re-sync a failed transaction after fixing the underlying issue?
A: Yes. After fixing the root cause, go to Accounting > Error Transactions and re-sync the transaction.
Q: What permissions are required to export AR invoices?
A: You need both the "Billing" and "Invoice" permissions in Alvys.
Q: When does Alvys export carrier AP bills — immediately on upload or on a schedule?
A: This depends on AP settings. If "Send carrier invoice upon upload" is enabled, the AP bill exports immediately when the carrier invoice is uploaded. If "Export Carrier Statements" is also enabled, a combined carrier statement AP bill is exported in addition to the individual bill.