AvaTax for VAT integration guide
Build
- Authentication in AvaTax
- Sandbox vs Production environments
- Authentication methods
- Ping the server
- Certification requirements
- Test authentication
- Authentication Q-and-A
- Can I use my credentials in both Sandbox and Production environments?
- How do I verify that the service is up?
- How do I add users?
- How do I identify a firewall or proxy server?
- How do I reset my license key?
- How do I reset my password?
- I’m using .NET NugetAvaTaxpackage to connect to AvaTax. Are account ID and license code enough for AvaTaxAPI authentication?
- Is TLS required?
- What authentication methods are supported?
- What is the production URL?
- What is the sandbox URL?
- What ports are used for communication?
- Where can I get the SDK?
- Where do I input the client ID?
- Whom do I contact if my sandbox is expired?
- AvaTax error messages
- Design considerations
- Invoice messages
- Display and store the VAT code in responses
- Display and store the AvaTax user's VAT code in responses
- Display and store the deemed supplier in responses
- Document code
- Customer code
- Document date
- Document type
- Ship-to address (header and line levels)
- Ship-from address (header and line levels)
- Point-of-order origin address (header and line levels)
- Goods place or service address (header and line levels)
- Import address (header and line levels)
- Line number
- Item code
- Item description
- Quantity
- Amount
- Include tax in line amounts
- Tax code
- Merchant seller identifier
- Merchant name
- Merchant VAT ID
- Merchant establishment country
- Verify that the transaction uses the Avalara-calculated tax amount
- Shipping/freight handling
- Sales order/sales invoice workflow
- Discount transactions
- Commit transactions
- Business identification number
- Country code
- Transport
- Void/delete a document
- Currency code
- Exchange rate
- Exchange rate currency code
- Exchange rate effective date
- The user is the importer of record
- Delivery terms
- Second-hand goods
- Location code
- Reporting location code
- Customer supplier name
- Marketplace liability type
- Origination site
- The counterparty is registered through a fiscal representative
- The Avalara client is registered through a fiscal representative
Authentication
Troubleshooting
Q-and-A
Error handling
Certification requirements
AvaTax for VAT transaction concepts
Design the user experience
Sales/billing document integration
Server audit clarity and installation
Triangulation integration for ERP
Design the user experience Q-and-A
Design the transaction workflow
Test
- Understand the transactions
Test transactions
Core examples
Examples for ERP and Ecom integrations
Examples for Marketplace integrations
Triangulation examples for ERP integrations
