I have an export error. What do I do?
Here’s how to figure out what went wrong, fix the most common issues, and get your data into your accounting system. One thing to keep in mind: once an invoice hits an error, Garde won’t automatically try to send it again — even after you fix the underlying problem. After resolving the issue, head to Accounting > Export, select the invoice in error, and press Send to retry the export.This article covers invoice export errors specifically. For payment-related errors, see How to Troubleshoot Common Payment Export Errors.
Uncovering the Error
On the accounting export page, you can filter to show only exports in error. Click the Filter button next to the date selector and choose the Error status. To see what’s causing an export error, click the word “Error” in red. That pulls up an audit trail of the export history for your invoice, including the last response from your accounting system describing the error.Common Invoice Export Errors
Duplicate Document Error
This means the invoice you’re trying to export already exists in your accounting system — same invoice number, same vendor. Example Messages- “org.apache.http.client.HttpResponseException: Unexpected response status: 400 {“Fault”:{“Error”:[{“Message”:“Duplicate Document Number Error”,“Detail”:“Duplicate Document Number Error : You must specify a different number. This number has already been used. DocNumber=#### is assigned to TxnType=Bill with TxnId=###”,“code”:“6140”,“element”:""}],“type”:“ValidationFault”},“time”:”####”
Missing Category Mapping
One of the categories on your invoice hasn’t been mapped to a corresponding account in your accounting system. Example Messages- Category is not mapped to a Quickbooks Account: ####
- Accounting code is not mapped: ####
- Category is not mapped to an InfoSync category.
Go to Accounting > Categories and map any missing categories. For step-by-step instructions, check out the guide on General Ledger Accounts, Categories, and Category Types.
The Period is Closed — Invoice Cannot Be Exported
Most accounting systems won’t allow invoices to be exported to closed accounting periods or periods outside the current one. Example Messages- `org.apache.http.client.HttpResponseException: Unexpected response status: 400 {“Fault”:{“Error”:[{“Message”:“Account Period Closed…”
- ”..An attempt was made to modify a General Journal transaction with a date that is on or before the closing date of the company. If you are sure you really want to do this, please ask a user with Admin privileges to remove the password for editing transactions on or before to closing…”
- ”…An attempt was made to modify a Bill with a date that is on or before the closing date of the company. If you are sure you really want to do this, please ask a user with Admin privileges to remove the password for editing transactions on or before to closing date…”
Vendor ID Should be a Valid Number, Supplied Value: null
This happens when you try to export an invoice for a vendor that hasn’t been mapped to a vendor in your accounting system. The accounting system rejects the export because a required value (the vendor) is null — meaning it isn’t mapped. Example Messages- org.apache.http.client.HttpResponseException: Unexpected response status: 400 {“Fault”:{“Error”:[{“Message”:“Invalid ID”,“Detail”:“Id should be a valid number. Supplied value:null”,“code”:”####”,“element”:“Id”}],“type”:“ValidationFault”}}
Payment Account is Not Mapped
If an invoice is closed to a payment account that hasn’t been mapped to the corresponding balance sheet account in your accounting system, the invoice won’t export. Example Messages- Payment Account (Payment Account Name) is not mapped to an accounting system account. Map this account on Accounting > Payment Accounts.