Fuel tax

If you're a fuel industry ERP (with or without OMS/Logistics) or a retail (ecommerce) partner selling fuel, the tables below describes the options to include in your AvaTax Excise integration.

Fuel transactions - document level


Requirement	Use case	Endpoints/Models	Element type
Transaction effective date	Users must be able to specify the date when the tax rate should be applied to this transaction. This would typically be the bill of lading date.	RestTransaction	Required
Invoice number	Users must be able to specify the invoice number of a transaction.	RestTransaction	Required
Invoice date	Users must be able to specify the date of the invoice on a transaction.	RestTransaction	Required
Title transfer code	Users must be able to specify whether the title transfer takes place at the `ORIG` or `DEST`.	RestTransaction	Required
Transaction type	Users must be able to specify where the entire order is in the supply chain. For fuel tax, the available transaction types are: `ABOVE`: Above the rack `BELOW`: Below the rack `RACK`: At the rack	RestTransaction	Required
Seller	Users must be able to specify the unique seller ID.	RestTransaction	Required
Buyer	Users must be able to specify the unique buyer ID.	RestTransaction	Required
User transaction ID	Users must be able to specify the corresponding AvaTax transaction code that's used to commit a transaction in both environments. Every new transaction must have a new `UserTranId`.	RestTransaction	Required
Entity use code	For each transaction, users must be able to specify an entity use code for a sales/use tax exemption.	RestTransaction RestTransactionLine	Required
Custom strings and numerics	Users must have a way to enter strings and numeric values as a way to customize calculations based on their business rules.	RestTransaction RestTransactionLine	Required
Source system	Users must be able to specify a string that identifies the system that’s calling the application with this transaction.	RestTransaction	Required
Fuel use code	Users should be able to specify a code that describes how the fuel is used.	RestTransaction	Suggested
Transportation mode code	Users should be able to specify a code that describes the transportation mode. This code comes from the transportation mode code master data table.	RestTransaction	Suggested
User data	Users should be provided with a field for entering data about the user.	RestTransaction RestTransactionLine	Suggested
AvaTax transaction type	Users should be able to specify the corresponding AvaTax transaction type.	RestTransaction	Suggested
Discount amount	Users should be able to specify a discount amount at the header level. This discount will then be applied to all lines with `"Discounted": true`.	RestTransaction	Suggested

Fuel transactions - line level


Requirement	Use case	Endpoints/Models	Element type
Invoice line	Users must be able to specify multiple lines on a transaction.	RestTransactionLine	Required
Product code	Users must be able to specify a product code when creating an ATE transaction.	RestTransactionLine	Required
Unit price	Transactions must know the cost or amount of an item to perform a tax calculation. This is done by specifying either a unit price and/or a line amount.	RestTransactionLine	Conditional
Line amount	Transactions must know the cost or amount of an item to perform a tax calculation. This is done by specifying either a unit price and/or a line amount.	RestTransactionLine	Conditional
Currency	Users must be able to specify the currency that the unit price and/or line amount use.	RestTransactionLine	Required
Net units	Users must be able to specify the net unit volume when the item is at 60 degrees Fahrenheit.	RestTransactionLine	Required
Gross units	Users must be able to specify the gross unit volume at the time of delivery for an item.	RestTransactionLine	Required
Billed units	Users must be able to specify the unit volume that is used for billing. This value must match either the net units or gross units.	RestTransactionLine	Required
Unit of measure	Users must be able to specify the unit of measure that the net, gross, and billed units are defined in.	RestTransactionLine	Required
Origin address	Users must be able to specify the origination country code, jurisdiction (for example, the state), county, city, and postal code. In addition, including a street-level address will provide more accurate tax determination.	RestTransactionLine	Required
Origin code	Users must be able to specify a custom ID for a defined origination location rather than specifying the full origin address.	RestTransactionLine	Required
Origin type	Users should have an option to specify the type of facility where the product originated from (for example, pipeline, refinery, terminal, truck, and so on).	RestTransactionLine	Suggested
Destination address	Users must be able to specify the destination country code, jurisdiction (for example, the state), county, city, and postal code. In addition, including a street-level address will provide more accurate tax determination.	RestTransactionLine	Required
Destination code	Users must be able to specify a custom ID for a defined destination location rather than specifying the full destination address.	RestTransactionLine	Required
Destination type	Users should have an option to specify the type of facility receiving the product (for example, pipeline, refinery, terminal, truck, and so on).	RestTransactionLine	Suggested
Sale address	Users must be able to specify the sales country code, jurisdiction (for example, the state), county, city, and postal code. In addition, including a street-level address will provide more accurate tax determination.	RestTransactionLine	Required
Sale type	Users should have an option to specify the type of facility where the sale of the product took place (for example, pipeline, refinery, terminal, truck, and so on).	RestTransactionLine	Suggested
Movement start and end dates	For specialty tax configurations, users should be able to specify the start and end dates for when items are transported.	RestTransactionLine	Suggested
Bill of lading number	Users should have an option to specify a bill of lading number. This is useful for integrations that allow searching for transactions via the ATE UI.	RestTransactionLine	Suggested
Bill of lading date	Users should have an option to specify a bill of lading date. This is useful for integrations that allow searching for transactions via the ATE UI.	RestTransactionLine	Suggested
Tax included	Your integration should allow users to specify whether tax is already included in a transaction line's unit price and/or amount.	RestTransactionLine	Suggested
Discounted	Your integration should allow users to specify whether a transaction line's unit price and/or amount is a discounted value.	RestTransactionLine	Suggested