Travel Agent Docs

Journal

The Journal lets you enter bookings and then validate and post them. The Journal acts as a work log for bookings yet to be finalized and posted.

The Journal is used to prepare bookings before they are finalized. You create journal entries, add travelers and addon lines, validate for errors, and then post when everything is correct.

Open Journal from the sidebar.

The default view shows unposted journal entries. You can switch the view from Journal unposted to see posted journals and waiting-list journals.

Creating a New Journal Entry

From the Journal page, click New to create an entry.

A journal entry typically includes:

  • Description: A brief description of the entry.
  • Type: The type of entry (e.g., booking, waiting list).
  • Action Outcome: The outcome of the validation (e.g., confirmed, errors).
  • External Ref: An external reference number of the package to which the entry is related, if applicable.
  • Travel Package: The package connected to the entry. When changed, default values are refreshed on lines based on the selected package. This is especially important for offers and addons, because these are stock items that are consumed at posting.
  • Posted Date: The date when the entry was posted.
  • Journal Status: The status of the journal entry (e.g., Draft, Validated).

Managing Journal Entries

Open a journal entry from the list to edit its details.

This page has three tabs:

  • General: Contains the main details of the journal entry.
  • Booking Source: Displays the source data for the booking in JSON format.
  • Documents: Lists any documents associated with the journal entry.

Use the command bar to process the entry:

  1. Click Validate to check the journal and all lines for errors.
  2. Fix any errors shown on lines.
  3. Click Post to finalize the entry.

After posting, related bookings and stock consumption are finalized and available for downstream processes.

Journal lines

The Journal lines section contains all travelers included in the entry. Each line represents one traveler.

Add new lines from the grid using New Travel Journal Line.

When you click Validate, the system checks both the journal header and all journal lines. If errors exist, they appear in the Error field on each line and must be fixed before posting.

Open a line from the grid to update traveler details such as name, age, and passport information.

Important fields on journal lines:

  • SSN: Unique traveler identifier (typically social security number). After entry and save, traveler fields can be auto-populated from the traveler record based on previous bookings.
  • Price Band: Pricing category for the traveler. If changed, related offers and addons on the line are recalculated based on the new price band.
  • Price PP: Price per person, initialized from package prices. This value can be edited manually. To reset from package setup, clear the value and save the line.
  • Error: Displays any errors related to the line after validation.
  • Passport BirthDay: Traveler birth date used for passport details. Calculated from SSN when possible.
  • Payer: Indicates the traveler responsible for payment in the created booking.
  • Together Code: Indicates travelers who should be grouped together (for example, room allocation). The value is auto-generated from previous bookings and can be edited.

Journal Line Offers/Addons

Each journal line can include one or more offer or addon lines. These are stock-controlled items and must have available on-hand quantity for posting to succeed.

Key fields on addon lines:

  • Price Band: Price band used for the offer.
  • Price PP: Price per person for the offer. This cannot be edited in the journal before posting.
  • Include: If selected, the offer line is included when posting.
  • Description: Description from the related action or offer.
  • On Hand: Current available PAX for the offer.

If required offers are not visible, users can add addon lines directly on the journal line.

Common mistakes to avoid

  • Posting without running Validate first.
  • Ignoring line-level Error messages after validation.
  • Missing required addon lines when package setup expects them.
  • Posting when On Hand is insufficient for included offers.