products
in Anrok, that associate a tax configuration to each product that you sell in Orb. You’ll need the IDs for these products when configuring the Anrok integration in Orb.{sellerId}/{apiKeyId}
SalesInvoice
document to Avalara as a new transaction. When an invoice in Orb transitions to a status of paid
, Orb will commit
the transaction in Avalara. This marks the transaction to be reported to a tax authority in Avalara, for more information, see the Avalara docs here.
For each document, Orb will also specify the ShipTo
and ShipFrom
addresses in order to accurately compute tax based on your defined Nexus’ in Avalara. Avalara will compute the tax per invoice, returning the data to Orb, which Orb will use to enrich tax information for downstream use in executing external charges or external invoice syncs.
The document in Avalara will include the quantity, rate, and amount per line item, as well as the specified tax code to use for tax computation purposes. In the case that the Orb Invoice has a line item level minimum or discount, Orb will sync these as separate line items to Avalara. Line item discounts are always reflected in Avalara as negative line items.
ShipFrom
address in Avalara. This can be set from the Orb dashboard under Settings > Invoices.nexus
states you may be obligated to collect and remit taxes in.