Invoice

An invoice is normally a document you would send to a customer in order ask for money (and as an official record of the transaction)

We suggest that the basics of an invoice should include:

Your company information
The booking reference, invoice date etc
An invoice number
The detail on what has been purchased (%itinerary_table_cust%)
... and at what price (%summary_sale_table%)

At a very minimum, your invoice would therefore look like this:


Date				%inv_date_display%
Booking ID			%b_id%
Invoice number			%inv_seq%
Lead customer name		%primary_contact_name%

%primary_contact_full_address%
%primary_contact_telephone%

%itinerary_table_cust%

%summary_sale_table%

Sequential invoice numbers without gaps
In some countries the booking reference (%b_id%) is acceptable to be used as a legal tax reference number. It will be unique in your account. However there are gaps in the sequence (caused by temporary bookings not completed at the end of the booking process).

As a result of these gaps in the booking reference sequence, this means that the booking number is non-compliant with European tax law.

Therefore use the invoice sequence token (%inv_seq%) in conjunction with the booking reference (%b_id%). Each time a document containing the invoice sequence token is generated (for RTF documents only) the sequence is incremented by 1.

Below the document table (within an individual booking) you can see which invoice references have been used on that particular booking - and reissue the invoice (Note that when you reissue this uses the product, prices and invoice template as currently configured - not how was at time of initial generation). The %inv_date_display% token will recall the date from the initial date of issue.

Default invoice format (pre-configured in TourCMS)