Sales/billing document integration

The following table lists the invoice and transaction-level requirements that your integration must support to ensure accurate tax calculation, reporting, and response handling.


Requirement	Use Case	Endpoint(s)/Model(s)	Required/Conditional/Suggested
Account reference	Users should be able to include their account reference number for reporting.	Invoice	Suggested
Document code	Users must be able to provide a method for specifying a unique document code used on transactions..	Invoice	Required
Customer reference	Users must be able to provide a unique ID that identifies the customer in a transaction.	Invoice	Required
Invoice number	Users must be able to include their invoice reference code in a transaction.	Invoice	Required
Invoice mode	In some cases, your integration should allow users to specify whether all line items in an invoice should be processed as a single invoice, where caps, thresholds, tax brackets, and tiers are applied per invoice as a whole.	Invoice	Conditional
Billing period	Users must be able to specify the billing period on the document.	BillingPeriod	Required
Bill-to location	Users must be able to specify the bill-to location for a transaction.	Invoice	Required
From/to locations	For Fact Pattern 1, allow users to specify the point of origin and the destination of an item at the level.	LineItem	Required
Transaction date	Users must be able to specify the calculation date in the header of invoice.	Invoice	Required
Charge amount	Users must be able to specify the amount being charged on a single line item.	LineItem	Required
Sale type	Users must be able to specify the type of sale associated with a line time.	LineItem	Required
Quantity	Users should be able to specify the quantity that should be applied to a line item so that, for example, instead of 100 lines of the same item, they can send a single line with a quantity of 100.	LineItem	Suggested
Bundles	Your integration must allow users to specify a custom profile ID and custom T/S pairs to trigger a bundle.	N/A	Required
Currency code	Users must be able to specify the currency code for all items on an invoice.	Invoice	Required
T/S pairs	Users must be able to specify and create T/S pairs.	TsPairData	Required
Transaction workflow considerations	Your integration must show that it can accurate send a transaction from a beginning order to a committed invoice.	N/A	Required
Response summary	Users must be able to specify whether summarized taxes for the invoice should be included in a response.	Invoice	Required
Response detail	Users must be able to specify whether individual line item taxes should be included in a response	Invoice	Required
Commit a transaction	Users must be able to commit transactions for accurate reporting.	Commit	Required