Based on the property PurchaseMessageType value, a tax calculation is performed and may or may not be saved for reporting and tax remittance.
Purchase Order call / message
A Purchase Order is used to estimate the tax on intended purchases for a Buyer. The intended purchase of goods or services, including tax, is used as input to generate the purchase order. The ultimate use of the goods or services typically dictates the taxability of the purchase. Purchase Order transactions are not stored for reporting or used in tax remittance.
Accrual call / message
The Accrual Request initiates a self-accrual calculation. This situation occurs when the buyer must remit tax on tangible personal property or services (used or consumed) when tax due on the transaction has not been paid. Accrual transactions are stored and used for reporting and remittance.
Invoice Verification call / message
The Invoice Verification is used to verify tax on incoming invoices to the buyer for tangible personal property, rentals, and leases. The invoice is recreated from the seller's perspective to validate that the appropriate tax has been applied. The Invoice Verification compares the total vendor-charged or supplier-charged tax amount from the original invoice to the Vertex-calculated tax amount. If any user-defined verification thresholds are set up, the engine validates for tolerances at the transaction level, and returns an indicator to the host system for undercharges and overcharges outside of the settings. The invoice may display no tax if the buyer has filed a direct pay permit with the vendor or supplier. Invoice Verification transactions are not stored for reporting or used in tax remittance.
Distribute Tax call / message
The Distribute Tax Procurement accepts a combined total tax amount for a purchase and distributes that tax to the appropriate jurisdictions. The engine uses the total tax amount with the combined rates for the taxing jurisdictions to determine the taxable base, and then redistributes the calculated taxes to each level for remittance. Use this request for a tax-only adjustment (debit or credit) to reconcile a tax underpayment or overpayment. The engine uses Vertex taxability rules that are effective on the date specified in the documentDate attribute. The engine processes records for jurisdiction registration, product exception or customer exception, or customer exemption if they are dated on or before that date. A Distribute Tax Procurement transaction impacts revenue unless you designate it as a tax-only adjustment. Distribute Tax Procurement transactions are stored for reporting.
Evaluated Receipts Settlement (ERS) call / message
Initiates an ERS calculation. Use the ERS request to calculate tax when a formalized agreement between the buyer and seller places the tax calculation burden on the buyer. In these situations, the seller does not issue an invoice. Instead, the buyer relies on pre-established terms (represented in a purchase order or other agreement) to calculate the tax due and remit payment directly to the seller. You must have a current knowledge of the seller's tax status (for example, where the seller is registered or has nexus) to assess tax at the appropriate rate. In instances where the seller is not registered or does not have nexus in a taxing jurisdiction, the buyer determines the tax due and remits this Consumer Use Tax directly to the jurisdiction.
APInvoice Sync call / message
The Accounts Payable Invoice Synchronization Request message. This request initiates the reconciliation of Accounts Payable invoices between Vertex O Series and your host system.
Accrual Sync call / message
The Accrual Synchronization Response message. This response returns the calculation results for the reconciliation process for Accrual transactions between Vertex O Series and your host system.
Conditional Procurement
The Conditional Procurement message. This request enables invoice verification and tax reconciliation via procure-to-pay workflows by comparing Vendor Charged Tax (VCT) against O Series Calculated Tax (OCT). Based on the comparison, the API applies configured Conditional Procurement rules to determine the appropriate action, such as accruing additional tax, paying vendor charged tax, or holding the invoice for review if discrepancies exceed configured thresholds.