AvaTax for Excise
Avalara.Excise.Determination.Engine.RestTransactionResponse
Represents the response data for a REST transaction, containing calculated results and processed transaction information.
Line-level results and inputs echoed for each item in the calculated transaction.
Exchange rates applied when converting amounts across currencies on this transaction.
The system-assigned identifier for this calculated transaction.
The company context under which tax was calculated.
How the engine treated this run (for example estimate, commit, or reverse).
The date tax rules and rates are evaluated against for this transaction.
The invoice or document number associated with this transaction.
The invoice date supplied for this transaction.
The intended end use of fuel when fuel-specific excise rules apply.
When title to the goods transfers for purposes of excise sourcing rules.
The business nature of the transaction (for example sale, purchase, or transfer).
The primary mode used to move the product (for example truck, rail, or pipeline).
A secondary or override transportation mode when multiple modes apply.
The seller party identifier in the host system when party-based rules apply.
The buyer party identifier in the host system when party-based rules apply.
The upstream seller in a multi-leg supply chain, when modeled.
The downstream buyer in a multi-leg supply chain, when modeled.
An intermediary party in the chain when middleman rules apply.
Customs or cross-border status affecting duty and excise treatment.
Whether Form A or equivalent documentation was indicated for duty treatment.
Whether a simplified customs procedure applies to this movement.
Incoterms governing risk, cost, and delivery for international trade context.
The reporting or filing perspective used when determining tax (for example seller vs buyer).
Identifies the position of this movement in a multi-hop supply chain.
The commercial order type influencing tax or exemption logic.
Total quantity of dyed fuel units across the transaction when dyed-fuel rules apply.
The total calculated tax amount for the whole transaction.
The currency in which total tax is expressed.
Total tax restated in the reporting currency for compliance or GL posting.
The currency used for reporting totals and related figures.
The unit of measure used for reporting quantity on the transaction.
Opaque client data echoed on the transaction for integration or audit.
The client-supplied transaction identifier echoed in the response.
A value returned with the transaction for client-side correlation or downstream use.
The originating system name or code when transactions are federated.
First client-defined string extension echoed on the transaction header.
Second client-defined string extension echoed on the transaction header.
Third client-defined string extension echoed on the transaction header.
Fourth client-defined string extension echoed on the transaction header.
Fifth client-defined string extension echoed on the transaction header.
Sixth client-defined string extension echoed on the transaction header.
Seventh client-defined string extension echoed on the transaction header.
Eighth client-defined string extension echoed on the transaction header.
Ninth client-defined string extension echoed on the transaction header.
Tenth client-defined string extension echoed on the transaction header.
First client-defined numeric extension echoed on the transaction header.
Second client-defined numeric extension echoed on the transaction header.
Third client-defined numeric extension echoed on the transaction header.
Fourth client-defined numeric extension echoed on the transaction header.
Fifth client-defined numeric extension echoed on the transaction header.
Sixth client-defined numeric extension echoed on the transaction header.
Seventh client-defined numeric extension echoed on the transaction header.
Eighth client-defined numeric extension echoed on the transaction header.
Ninth client-defined numeric extension echoed on the transaction header.
Tenth client-defined numeric extension echoed on the transaction header.
Whether this transaction is committed, estimated, or in another lifecycle state in the host.
The mapped AvaTax document type when results are bridged to AvaTax.
The aggregate discount applied at the transaction level before or after tax, per product rules.