Overview

The service's invoicing solution, known as Vertex Invoice IQ provides Marketplaces with the ability to send compliant invoices to their customers for confirmed (completed) transactions, as well as issuing compliant credit notes for refunds.

The service's Invoicing features enables Marketplaces to comply with international country-specific regulations which include:

• Sequential numbering.
• Displaying amounts in the local currency.
• Provide a signature of the supplier or the authorized representative.
• Displaying the accounting code of the service you are selling.

The response from the Confirm Transaction request includes a link to a HTML version of the invoice in the invoice_url field. You can also use the link to embed it in your store or you can specify the buyer's name and send it to them.

Invoices are created when a Confirm Transaction request is sent to the service. The information used in the invoice is based on what was returned in the response to a Store Transaction request.

See Store Transaction and Confirm Transaction

The final layout of the invoice can vary depending on settings and regulatory requirements. See Invoice Details and Variations.

Settings

Invoice processing and layout can be modified by your marketplace and seller settings. See Invoicing Settings.

Dashboard Customization Options

You can also customize your invoices in the Dashboard under Settings > Invoicing.

You can customize the following:

• Logo: Upload your own logo to appear on the invoice.
• Footnote: This area can be updated with any detail that you would like to add to the invoice, for example, terms and conditions.

Invoice Delivery Options

Invoices are created in HTML and can be sent to the buyer directly. The API response also contains an invoice URL that you can use to integrate it into your store or applications.

An invoice is sent to the liable party, this can be either the buyer or seller. If it is the buyer, it is sent to the email specified in the buyer_email field. If this is not specified, it is sent to the seller.

The HTML version of the invoice is included in the response that is returned by the Confirm Transaction request. You can hide this URL if you prefer. See Setting Invoice URL Privacy.

Invoice Processing

The following graphic describes an example process flow showing how an invoice is sent:

The process flow is as follows. This is a simplified example and steps can vary substantially in a real implementation.

1. Buyer places goods in basket. The buyer places some goods in their basket but do not go to the checkout yet.
2. Store Transaction request is sent to Vertex for Marketplaces. The Store transaction request is sent to the service and tax information and a transaction key is returned.
3. Buyer confirms the purchase. They complete checkout.
4. Confirm Transaction request sent to Vertex for Marketplaces. The Confirm Transaction request is sent (containing the Transaction Key created in the previous step.
5. Invoice sent per settings to the buyer or merchant. An invoice is sent to the liable party, this can be either the buyer or seller. If it is the buyer, it is sent to the email specified in the buyer_email field. If this is not specified, it is sent to the merchant.
6. Buyer receives invoice.

Post Transaction Processing

Refunds and Credit Notes

See Refunds and Credit Notes.