Use this guide to connect Avalara Exemption Certificate Management to Nuvo, test the connection, send customers and certificates to Avalara, and troubleshoot common issues.
Before you start, reach out to your Avalara account manager and let them know that you want to connect to Nuvo, or reach out to sara.webster@avalara.com if you don't know your representative.
Prerequisites
Before you begin, make sure you have:
An Avalara account with Exemption Certificate Management enabled
Your API credentials:
Username or Account ID
Password or License Key
Admin access in Nuvo, since only admins can manage integrations
Connect Avalara to Nuvo
To connect Avalara in Nuvo:
Go to Settings > Integrations in the Nuvo dashboard.
Scroll to the Services section.
Click Connect on the Avalara row.
Enter your Username/Account ID and Password/License Key.
Click Connect.
Nuvo automatically validates your credentials against the Avalara API. If the connection is successful, you’ll see a confirmation message and the Avalara integration will show as connected with your username.
Test the Connection
You can verify the connection at any time.
Click the options menu (⋮) on the Avalara row.
Select Test Connection.
You’ll see one of the following messages:
Success: “Connection verified successfully”
Failure: “Connection test failed. Please check your credentials.”
How Company Code Configuration Works
When you connect Avalara, Nuvo automatically resolves and stores the Avalara company ID tied to your credentials. No manual company code entry is required.
Here’s how it works:
Nuvo first reads the
authenticatedCompanyIdreturned by the Avalara ping endpoint.If no company ID is returned from ping, Nuvo falls back to the default company using the Avalara Companies API.
That resolved company ID is then used for all future Avalara actions, including customer creation and certificate uploads.
To link a different Avalara company, disconnect the integration and reconnect using credentials associated with the correct company.
Send a Customer to Avalara
You can send a customer to Avalara directly from the credit application.
Open the customer’s credit application.
Click More.
Select Send to Avalara.
If the customer has tax exemption certificates, Nuvo will:
Create a customer record in Avalara using an auto-generated customer code in the format
NUVO_{uuid}Upload all tax exemption certificate PDFs to the Avalara customer record
Link those certificates to the customer
If the customer has already been sent to Avalara, Nuvo shows the existing Avalara customer code and only sends any new certificates.
If the customer does not have tax exemption certificates, Nuvo prompts you to request them using Request Info.
Send a Customer During Approval
When working through a customer approval flow, Nuvo automatically shows a Send Customer to Avalara toggle if Avalara is connected.
This toggle is enabled by default when the customer has uploaded tax exemption certificates.
Existing Customers
If you would like to add your existing customer's Avalara IDs to Nuvo, reach out to your Nuvo contact and ask about importing your existing customers into Nuvo.
How Customers Are Identified in Avalara
Each customer sent from Nuvo to Avalara gets a unique customer code in this format:
NUVO_{uuid}
This code is:
Automatically generated by Nuvo
Not entered manually
Shown in the credit application sidebar under Avalara ID
Sending the same customer more than once does not create duplicates.
How Customer Exemptions Are Identified
Once certificates are synced to Avalara, each certificate in the Compliance & Tax Documents section displays a status badge.
Certificate status badges
Valid (green): The certificate is current and valid
Invalid (red): The certificate has expired or is not valid
Missing (gray): Nuvo could not determine certificate status
Hover over a badge to view more detail, including:
Exempt state
Exemption reason
Expiration date
How exemption tracking works
Each certificate uploaded to Avalara is linked to the customer through the NUVO_ customer code. The status shown in Nuvo reflects Avalara’s stored status for that certificate.
View and Download Certificates
To view or download a certificate:
Click the certificate name to open a preview
Click Download to save it locally
Disconnect Avalara
To disconnect the integration:
Click the options menu (⋮) on the Avalara row
Click Disconnect
This removes the saved Avalara credentials. You’ll need to reconnect before using the integration again.
Troubleshooting
Here are the most common Avalara integration errors and how to resolve them.
Error reference
INVALID_CREDENTIALS
Your username or password is incorrect.
Resolution: Re-enter your credentials using Reconnect/Update Credentials.
UNABLE_TO_CONNECT
Nuvo cannot reach the Avalara API.
Resolution: Check network connectivity and try again after a few minutes.
CREDENTIALS_NOT_CONFIGURED
No Avalara credentials are currently saved.
Resolution: Connect Avalara in Settings > Integrations.
AUTHENTICATION_FAILED
Avalara rejected the credentials.
Resolution: Verify the credentials in your Avalara account portal.
COMPANY_MISMATCH
You are attempting to send a customer under a different company than the one linked to the integration.
Resolution: Confirm you are operating under the correct company.
NO_CERTIFICATES_FOUND
The customer has no tax exemption certificates on file.
Resolution: Request certificates from the customer using Request Info.
CUSTOMER_CREATION_FAILED
Nuvo could not create the customer record in Avalara.
Resolution: Retry the action and check for Avalara account limits.
CERTIFICATE_UPLOAD_FAILED
Nuvo could not upload the certificate to Avalara.
Resolution: Retry and confirm the certificate files are valid PDFs.
UNKNOWN_ERROR
An unexpected error occurred.
Resolution: Retry the operation. Contact support if the issue continues.
General Troubleshooting Steps
If you run into issues:
Use Test Connection to confirm the saved credentials still work.
If the test fails, click Reconnect/Update Credentials and re-enter your credentials.
Check the Avalara status page for active service issues.
Contact Nuvo support if the problem continues after reconnecting and retesting.
If you want, I can also turn this into a tighter Intercom-style help center article with cleaner headings, a short intro, and callout-ready troubleshooting sections.