Different types of financial transaction documents need different types of information on them. For that reason the different document types are discussed separately, although some of the Sections are common to more than one transaction document.
Debtors invoices can as simple or as complex as necessary, and most companies have at least two invoice layouts - one showing individual service costs and a total, one showing just the booking total and possibly one specific to deposit invoices which could have different terms and conditions on it.
Section Tags
The most common section (used in all transaction documents) is the <<LINES>> section (this is the equivalent of the <<SERVICES>> section in Booking/PCM message templates) and the implication is that areas of the template before and after the <<LINES>> section are the Header and the Tail.
If different line detail is required (based on Message Type Format Codes), then these can be incorporated into the template.
| Section Tags | Data Source | |
|---|---|---|
| <<LINES:START>> | ||
| <<DEFAULT>> | Default message line type format | |
| Transaction substitution codes for Default message line type | ||
| <<AC>> | Accommodation message line type format | |
| Transaction substitution codes for accommodation message line type, including Room quantities and types. | ||
| <<LINES:END>> | ||
An example Invoice Message template is below.
The header has billing name/address details as well as booking name, booking reference, payment due date etc.
The Lines section has three Line Format types - <<DEFAULT>>, <<AC>> and <<FL>>. All services, except those with an AC or FL line format type attached, will be in the DEFAULT format.
This example will outputting the unit price (<TRNPRICE>) and the extended total price (<TRNEXT>) per service.
Example Invoice Message Template
An example of the output generated from the above template is below.
Example Invoice Message Output
Tax Summary
It is not uncommon in some countries for a breakdown of taxes to be shown on invoice documents. There is some setup at Product Level to achieve this and the local Tourplan office will be able to assist. The formatting of Tax Summary from the above template is shown in detail below.
| Section Tags | Substitution / Data Source | ||
|---|---|---|---|
| <<TRANSUMMARY:START:DBA6>> | The start of the Tax summary, and the Product DB Analysis Code being used. | ||
| <SUMCODEDESC> = DBA6 Description | <TRNEXCLTAX> = Tax exclusive amount | <TRNTAX> = Tax amount | <TRNTOT> = Total amount |
| <<TRANSUMMARY:END>> | End of the Tax summary | ||