Exemption Certificate Management

CertCapture RESTful APIs

MultiDocumentModel

A MultiDocument transaction represents a sale or purchase that occurred between more than two companies.

A traditional transaction requires exactly two parties: a seller and a buyer. MultiDocument transactions can involve a marketplace of vendors, each of which contributes some portion of the final transaction. Within a MultiDocument transaction, each individual buyer and seller pair are matched up and converted to a separate document. This separation of documents allows each seller to file their taxes separately.

This model is used in the following APIs:

Parameters
idOptional
integer

The unique ID number of this MultiDocument object.

accountIdOptional
integer

The unique ID number of the AvaTax customer account that created this MultiDocument object.

codeOptional
string

The transaction code of the MultiDocument transaction.

All individual transactions within this MultiDocument object will have this code as a prefix.

typeOptional
string

Indicates the type of MultiDocument transaction. Common values are:

  • SalesOrder - An estimate that is not permanently recorded
  • SalesInvoice - An invoice that can be reported on a tax return

For more information about document types, see DocumentType

Enum: SalesOrder, SalesInvoice, PurchaseOrder, PurchaseInvoice, ReturnOrder, ReturnInvoice, InventoryTransferOrder, InventoryTransferInvoice, ReverseChargeOrder, ReverseChargeInvoice, CustomsInvoice, CustomsOrder, InventoryTransferOutboundInvoice, InventoryTransferOutboundOrder, Any
createdUserIdOptional
integer

The user ID of the user who created this record.

createdDateOptional
string

The date/time when this record was created.

modifiedDateOptional
string

The date/time when this record was last modified.

modifiedUserIdOptional
integer

The user ID of the user who last modified this record.

documentsOptional
array

A separate document will exist for each unique combination of buyer and seller in this MultiDocument transaction.