The Error Transactions page in Alvys presents a centralized overview of transactions that failed to sync with external accounting systems. It allows users to quickly identify failed exports, examine error messages, and take the necessary corrective actions. The page is accessible from the accounting menu by selecting Error Transactions within Alvys.
The Error Transactions page includes the following columns:
Entity Type: The type of Alvys transaction that failed to export, showing where the transaction originated. Examples include Load, Trip, Paystub, Deduction, Accessorial Revenue, Toll, Fuel, Escrow, E-check, and Accounting Invoice.
Transaction Type: How the record is classified in the external accounting system, such as Invoice, Bill, Credit Memo, Vendor Credit, or Journal Entry.
Class: The subsidiary associated with the transaction.
Error Message: The message returned by the external accounting system explaining why the transaction failed.
Status: The current state of the transaction, such as Failed or Resolved.
Reference: Additional identifiers to link the transaction, such as load number, summary invoice number, or trip number.
Transaction Total: The total amount of the transaction.
Date Created: The date the transaction was first attempted to be exported.
Supported Transaction Types That Can Be Re-Synced from Error Transactions
Not all transactions can be automatically re-synced from this page. Currently, only the following entity types can be re-synced:
Load
Trip
E-check
Paystub
Before re-syncing, ensure that any necessary corrections have been made to the transaction. To re-sync:
Select one or more transactions from the Error Transactions page.
Right-click to reveal the context menu options “Sync Transaction” or “Sync All Transactions.”
Click Sync Transaction and confirm the action in the prompt.
Use Sync All Transactions only if all transactions in the Error Transactions list are ready for export. Any transactions that still require corrections will be skipped.
The following entity types cannot be re-synced from the Error Transactions page:
Deduction
Accessorial Revenue
Fuel
Toll
Accounting Invoice (same as a summary invoice)
Escrow
Carrier Statement
Driver Statement
For carrier settlements, summary invoices, and driver pay, corrections and re-syncs must be performed directly from their respective pages rather than from the general Error Transactions page.
Clearing an Error Transaction Manually Fixed in the External System
If a transaction has been manually corrected in the external accounting system and no longer requires action in Alvys, it can be cleared from the Error Transactions page:
Select one or more transactions from the Error Transactions page.
Right-click to reveal the context menu option “Mark as Synced.”
Click Mark as Synced and confirm the action in the prompt.
Only mark a transaction as synced if it has been fully resolved, as this action cannot be undone.
⚠️ Contact Alvys Support if a transaction fails repeatedly and cannot be re-synced, or if there are complex errors that cannot be understood from the Error Transactions page.
Common Business Central Errors and Resolution Steps
This section provides an overview of the most frequently encountered errors when exporting transactions between Alvys and Business Central. It explains why these errors occur, how to identify them, and the recommended steps to resolve or prevent them.
Resource Not Found (Purchase or Sales Invoice)
Error Shown in Error Transactions:
Resource not found for the segment 'purchaseInvoice' OR 'salesInvoice’
This error occurs when Alvys attempts to update a Purchase Invoice or Sales Invoice in Microsoft Dynamics 365 Business Central, but the invoice has been manually deleted from the system.
When a financial change is made to a load in Alvys, the system attempts to sync that update back to the corresponding invoice in Business Central. If the original unposted invoice was manually removed, Business Central cannot locate the record. Because the document no longer exists in the database, the system returns a “Resource Not Found” error.
This issue is specifically caused by the manual deletion of the invoice. Since the original record has been removed, Alvys has nothing to update.
Resolution Steps:
Step 1: Confirm the Deletion in Business Central
Search Business Central for the Purchase Invoice or Sales Invoice.
If the record is not found in the unposted list, it has been deleted.
Step 2: Contact Alvys Support This error cannot be fixed manually. Because the unique identifier between the two systems has been destroyed by the deletion, Alvys Support must resend the transaction.
Contact Alvys Support with:
Load Number
Error Message and Error ID (Found in the Transaction Log)
Record Already Exists (Purchase & Sales Invoices)
Error Shown in Error Transaction:
The record in table Sales Header already exists. Identification fields and values: Document Type='Invoice',No.='[Invoice Number]’
This error indicates that a Purchase Invoice or Sales Invoice already exists in Business Central with the same transaction number, preventing Alvys from creating a new record. Business Central requires unique numbers for all unposted documents.
Resolution Steps:
Step 1: Search for the duplicate transaction in Business Central
For Customer Invoices: Navigate to the Sales Invoices list using the Sales tab in the main navigation menu.
For Carrier/Driver Bills: Navigate to the Purchase Invoices list using the Purchasing tab in the main navigation menu.
Search the list by the No. provided in the error message to identify the existing unposted record.
Step 2: Resolve the conflict
If the existing invoice in Business Central is valid and should remain; Mark the transaction as Synced in Alvys to skip the re-export process.
If the existing invoice in Business Central is incorrect, a duplicate, or a test: Delete the unposted record from Business Central.
Step 3: Retry the transaction in Alvys
Go to Alvys Error Transactions page.
Locate the transaction that failed.
Right-click and select Sync or Retry to export it again.
Step 4: Confirm success
Verify in Business Central that the Purchase Invoice or Sales Invoice is now present.
⚠️ If the error persists after completing these steps, please contact Alvys Support for further assistance.
Duplicate Dimension Set
Error Shown in Error Transaction:
“The dimension set line already exists. Check existing dimension set lines and the default dimension set lines on the parent.”
This error indicates a conflict between Business Central default settings and the Alvys integration export. Business Central automatically generates dimension lines (such as Truck, Driver, or Subsidiary) based on the Default Dimensions saved on a Vendor or Customer card. When Alvys attempts to export a Purchase Invoice or Sales Invoice containing those same dimensions, Business Central rejects the transaction because it cannot create a second entry for a dimension that already exists on the invoice header.
Resolution Steps:
Step 1: Identify the conflicting Dimension in Business Central
For Customer Invoices: Navigate to the Sales tab > Customers and open the specific Customer Card.
For Carrier/Driver Bills: Navigate to the Purchasing tab > Vendors and open the specific Vendor Card.
Go to Related > Dimensions. Identify which Dimension Code (e.g., Truck, Driver, or Subsidiary) is set as a default.
Step 2: Remove the default dimension
Select the conflicting dimension line on the Customer or Vendor card.
Click Delete to remove the default dimension.
Note: Removing the default here allows Alvys to provide the specific, dimension data during the sync without causing a collision.
Step 3: Trigger a new sync from the Alvys Load Once the conflict is cleared in Business Central, you can re-trigger the sync directly from the load:
For Customer Invoices: Locate the load in Alvys and Regenerate the Sales Invoice.
For Carrier/Driver Bills: Locate the load in Alvys and Re-upload the carrier invoice.
Step 4: Confirm success
Verify in Business Central that the Purchase Invoice or Sales Invoice has been created with the correct dimensions applied.
Failed Export of Updated Zero-Valued Transaction
Error Shown in Error Transaction:
"A digit was expected at position 3 in '(ID)'.”
This error occurs when a transaction that was originally zero-valued (for example, a customer invoice with a total of $0) is later updated to a value greater than $0, and Alvys attempts to export it to Business Central. If the Ignore Zero Valued Transactions setting was previously enabled: Alvys may have skipped exporting the original $0 transaction.
When the transaction is updated to a non-zero value, Business Central may generate an error related to the transaction’s internal ID. This prevents the updated transaction from exporting successfully.
Resolution Steps
Step 1: Identify the affected transaction
In Alvys, locate the transaction that was originally $0 and has since been updated.
Step 2: Contact Alvys Support
This error cannot be fixed manually.
Email Alvys Support with:
Load Number
Error message and Error ID
Manual Numbering Required (Purchase & Sales Invoices)
Error Shown in Error Transaction:
“You may not enter numbers manually. If you want to enter numbers manually, please activate Manual Nos. in No. Series. CorrelationId: [Unique ID]”
This error indicates that Alvys is trying to assign its own document number to a Sales or Purchase Invoice, but the No. Series configuration in Business Central is currently "Locked" to only allow BC to generate numbers. To allow the Alvys-generated number to pass through the API, the "Manual Nos." setting must be enabled for the corresponding numbering sequence.
Resolution Steps
Step 1: Search for No. Series: In Business Central, use the magnifying glass to search for No. Series.
Step 2: Enable Manual Numbers for Invoices
In the No. Series list, find the code for your Sales Invoices and Purchase Invoices.
Locate the Manual Nos. column.
Check the box for the relevant invoice types.
Step 3: Resync in Alvys
Go back to the Alvys Error Transactions page.
Locate the failed invoice.
Right-click and select Sync or Retry.
FAQs
Q: Where can I see a list of all transactions that failed to export to Business Central? A: You can find these in the Error Transactions page. In Alvys, navigate to the Accounting menu and select Error Transactions. This page provides a centralized view of all failed exports, including error messages and transaction totals.
Q: Which Alvys transactions can I re-sync directly from the Error Transactions page? A: Currently, the following entity types support direct re-syncing: Loads, Trips, E-checks, and Paystubs.
Q: How do I fix errors for Driver or Carrier Statements? A: Entity types like Driver Statements, Carrier Statements, Fuel, and Tolls cannot be re-synced from the general Error Transactions page. To resolve these, you must go directly to their respective pages (such as the specific Driver Pay or Carrier Settlement screen), make the necessary corrections, and trigger the sync from there.
Q: What should I do if I manually fixed the invoice inside Business Central? A: If you have already corrected the data in Business Central and do not want Alvys to attempt another export, find the record on the Error Transactions page, right-click it, and select Mark as Synced. This removes it from the error list without sending new data.
Q: What does "Resource not found for the segment 'purchaseInvoice'" mean? A: This happens if an unposted invoice was manually deleted in Business Central. Because the link between Alvys and the BC record has been broken, you must contact Alvys Support to reset the transaction ID so a new record can be generated.
Q: Why am I getting an error saying, "The record in table Sales Header already exists"? A: Business Central prevents the creation of a document if an unposted invoice with that exact number already exists. If the BC record is correct, mark the transaction as Synced in Alvys. If the BC record is wrong, delete the unposted invoice in Business Central and then click Sync in Alvys to try again.
Q: How do I fix the "Duplicate Dimension Set" error? A: This occurs when both Business Central (via the Vendor/Customer card) and Alvys try to assign the same dimension (like "Department" or "Truck"). To fix this, go to the Customer or Vendor card in BC, navigate to Related > Dimensions, and remove the conflicting default dimension. Then, re-trigger the sync from the load in Alvys.
Q: What does "Manual Nos." mean in the error message? A: Alvys often sends its own document numbers to Business Central. If BC is configured to only allow system-generated numbers, it will reject the Alvys export. In Business Central, search for No. Series and ensure the Manual Nos. checkbox is enabled for your Sales and Purchase invoice sequences.
Q: Why did my updated invoice fail with a "Digit was expected" error? A: This usually happens if a transaction was originally $0.00 (and skipped by the integration) but was later updated to a non-zero value. This error requires Alvys Support to manually intervene and push the updated record.
Return to Collection
📁 Need to see the full list of articles? Return to the Business Central Integration Collection.