Skip Navigation

Taxes

Tax Breakdown per Passenger Type

In the service that returns a detailed price breakdown of all products and passenger details in the itinerary, all fares, taxes, and fuel surcharges split by the passenger type code PTC (except fees and discounts).

This feature applies to the following flows:

  • The Revenue (B2C) Flow
  • The Redemption (RBE) Flow
  • Manage Your Booking – Change Itinerary (MYB:CI) Flow
  • Manage Your Booking – Modify Trip Options (MYB:MTO) Flow
  • Book Now Pay Later (BNPL) Manage Your Booking – Book Now Pay Later (MYB:BNPL) Flows.

Specific behaviour for The Redemption (RBE) Flow:

  • /products, /products/cart, /products/air/search services– responses will be able to provide taxes split by tax codes
  • /purchase, /pnr – as the only information stored in payfields are regarding total, there is no way to display by certain tax code, providing exact information on each code.

Special handling for Manage Your Booking – Change Itinerary (MYB:CI) Flow:

  • /pnr/exchange/products – split by PTC will be only in part for new booking summary, old booking summary remain with no changes.

Highlights

Following are examples which include some simple scenarios:

The Revenue (B2C) and the Redemption (RBE) Flows

  1. The Airline calls /products/air/search POST to obtain the list of available flights to the passenger. The Airline can format the information for display to the passenger.
  2. The passenger selects a flight.
  3. The Airline submits /products/air POST to add selected flight to the itinerary.
  4. The Airline uses a /products GET operation to obtain a current list, with prices of products that the passenger has added to the itinerary. Prices will be divided by Passenger Type (PTC).
  5. The Airline prompts passenger for passenger’s details e.g. passport information.
  6. The Airline uses /passengers POST to add a passenger to the itinerary.
  7. The passenger can continue shopping by selecting seats and ancillaries, according to the Airline’s shopping sequence. Product cart is updated.
  8. When the passenger indicates that shopping is complete the Airline obtains available payment options for the current itinerary by calling /paymentOptions GET. The Airline can format the information for display to the passenger.
  9. When the passenger selects the form of payment, completes the payment and decides to purchase, the Airline initiates the purchase and ticketing process by calling /purchase POST; if authorization is successful, the /purchase service will create a PNR, EMD(s), etc.
  10. The response indicates whether the purchase is successful. The Airline formats this information for display to the passenger.
  11. The passenger specifies a PNR for review.
  12. The Airline submits a /pnr GET request. The Airline can format the information for display to the passenger.

Manage Your Booking – Change Itinerary (MYB:CI) Flow

  1. The passenger retrieves a booking either by supplying basic PNR information or by logging in to a Frequent Flyer account. If the passenger is logged in, all their reservations are visible. The /pnr service GET operation returns information for the PNR specified in the parameters. Airlines can prompt passengers for information that identifies a PNR, retrieve the information and format it to display to the passenger.
  2. After the passenger selects one or more flights to be exchanged, the Airline calls pnr/exchange request, GET operation to initialize Exchange process.
  3. The Airline calls /pnr/exchange /products/air/search POST to obtain the list of available flights to the passenger. The Airline can format the information for display to the passenger.
  4. The passenger selects a flight.
  5. The Airline submits /pnr/exchange /products/air POST to add selected flight to the itinerary.
  6. The Airline uses a /pnr/exchange /products GET operation to obtain a current list, with prices of products that the passenger has added to the itinerary.
  7. The Airline prompts passenger for passenger’s details e.g. passport information.
  8. The Airline uses /pnr/exchange /passengers POST to add a passenger to the itinerary.
  9. The passenger can continue shopping by selecting seats and ancillaries, according to the Airline’s shopping sequence. Product cart is updated.
  10. When the passenger indicates that shopping is complete the Airline obtains available payment options for the current itinerary by calling /pnr/exchange /paymentOptions GET. The Airline can format the information for display to the passenger.
  11. When the passenger selects the form of payment, completes the payment and decides to purchase, the Airline initiates the purchase and ticketing process by calling /pnr/exchange /purchase POST; if authorization is successful, the /pnr/exchange /purchase service will create a PNR, EMD(s), etc.
  12. The response indicates whether the purchase is successful. The Airline formats this information for display to the passenger.
  13. The passenger specifies a PNR for review.
  14. The Airline submits a /pnr GET request. The Airline can format the information for display to the passenger.

Custom Tax Breakdown for Loyalty

Digital Connect includes the following tax breakdown options:

  • The Airline can display total sum tax for all passengers and total tax for each passenger without tax code breakdown.
  • Taxes are shown as a single line item during booking and for PNR retrieval.
  • This feature is introduced to secure any rounding issues which might happen after converting taxes.
  • The tax breakdown is lined in the following way:
    • Sum of taxes
      • Taxes for passenger 1
      • Taxes for passenger 2

Custom tax breakdown impacts only the Redemption bookings.

Prerequisites

This feature cannot be used in case the tax code breakdown is needed.

Highlights

  1. The Airline calls /products/air/search POST to obtain the list of available flights to the passenger.
  2. The passenger selects a flight.
  3. The Airline submits /products/air POST to add selected flight to the itinerary.
  4. The Airline prompts passenger for passenger details e.g. passport information.
  5. The Airline uses /passengers POST to add a passenger to the itinerary.
  6. The passenger can continue shopping by selecting seats and ancillaries, according to the Airline’s shopping sequence.
  7. The Airline can call /products GET operation to obtain a current list, with prices of products that the passenger has already added to the itinerary and use this information to build and display a shopping cart. The response for seats will include breakdown of the original amount, discount and discount amount.
    • If Custom tax breakdown configuration is turned on, the response will be displayed in the described way.
  8. When the passenger is ready to purchase the itinerary, the Airline adds field values for all applicable remarks, SSRs, and OSIs to the /purchase POST request.
    • If Custom tax breakdown configuration is turned on, the response will be displayed in the described way.
  9. The Airlines submits a /pnr GET request; the results will include remarks.
    • If Custom tax breakdown configuration is turned on, the response will be displayed in the described way. The Airline can format the information for display to the passenger.

Indian Goods and Service Tax

Digital Connect addresses a mandate to support the new General Sales Tax (GST) in India that applies to State Goods and Services. For any tickets issued worldwide where travel originates in India, regardless of point of sale, the Airline must send a GST invoice within 30 days of the date of ticket issuance regardless of the form of payment.

This tax impacts all Airlines issuing tickets within India and Ex-India, hence Airlines need to apply the tax at time of pricing and adhere to this Indian tax mandate to avoid any penalties for Non-Compliance. Digital Connect requires from passengers to supply their Indian tax registration details (GST number, Company name, Address of business, phone number and email), these are added as SSR’s to the PNR. The purpose of these SSRs is to store and transmit (if applicable) the GST Number, Name and Address of the business entity registered for GST. These differ from the passenger's own name and address.

This feature is activated by default if the application identifies that K3 tax is returned in shopping response then Digital Connect requests UI to provide Indian tax details if applicable for Business persons (passengers possessing an Indian tax registration number).

This functionality applies to the following flows:

  • The Revenue Flow (B2C);
  • Book Now Pay Later Flow (B2C: BNPL);
  • The Redemption Flow (RBE);
  • The Change Passenger Details Flow (MYB: CPD).

Limitations

  • General sales tax data can only be provided if a configured tax is present in the pricing response.
  • If the Airline tries to change passenger’s GST data in response they will receive an error with all details about data that was changed, therefore Airline should not even try to change the data. UI should be responsible for blocking modification general sales tax in post-booking paths.
  • If the passenger does not provide Indian tax registration number and other mandatory details then they can only add the Indian tax data in the change passenger details path.
  • Passenger are not able to remove or modify Indian tax data once it is provided.
  • This functionality does not apply to the post-booking paths:
    • Manage Your Booking – Change Itinerary Flow (MYB: CI);
    • Manage Your Booking – Modify Trip Options Flow (MYB: MTO);
    • Upgrade Flow (MYB:FFU, MYB:FQTU)

may not rectify the validation for each field as this GST data will not be accepted in the service /pnr/exchange/passengers.

Error Handling

  • In the post-booking flows, general sales tax data can only be provided in /pnr/passengers service Change Passenger Details Flow. If Digital Connect receives a request to add Indian tax details an error message will be returned.
  • If passenger provides Indian tax registration number for infant then Digital Connect will return an error. This functionality is configurable, the Airline can decide which passenger type(s) they want to exclude.

Highlights

  1. IATA has introduced 4 new IATA Standard SSR codes to communicate GST data to the validating carrier when required. These SSRs are:
    • GSTN - Goods and Services Tax Number
    • GSTA - Goods and Services Tax Business Address
    • GSTP - Goods and Services Tax Business Phone Number(s)
    • GSTE - Goods and Services Tax Business Email

      The SSRs are name number associated and once added to the PNR looks as follows:
       

      Taxes - GST

  2. In /pnr service response a special message is provided if the tax is present ("General Sales Tax Code found in the reservation.").
  3. A rule has been created (GST_DATA) which is used to inform if the configured tax is present (before /passengers service).

The Revenue Flow (B2C)

  1. The Airline calls /products/air/search POST to obtain the list of available flights to the passenger.
  2. The passenger selects a flight.
  3. The Airline submits /products/air POST to add selected flight to the itinerary.
  4. The Airline fills shopping cart data /products.
  5. The Airline prompts passenger for passenger details e.g. passport information.
    1. New feature - SSR of Indian tax details If applicable will be added in POST /passengers.
  6. The passenger can continue shopping by selecting seats and ancillaries, according to the Airline’s shopping sequence.
  7. Product cart is updated.
    1. New feature - SSRs for Indian are shown in the shopping cart - GET /products.
  8. When the passenger indicates that shopping is complete the Airline obtains available payment options for the current itinerary by calling GET /paymentOptions. The Airline can format the information for display to the passenger.
  9. When the passenger selects a form of payment, completes the payment and decides to purchase, the Airline initiates the purchase and ticketing process by calling /purchase POST.
    1. New feature - SSRs for Indian tax can be added in POST /purchase or POST /products/bnpl/purchase.
  10. The response indicates whether the purchase is successful. The Airline formats this information for display to the passenger.
  11. The passenger specifies a PNR for review.
  12. The Airlines submit a /pnr GET request. The Airline can format the information for display to the passenger. The response will now contain:
  13. SSRs for Indian tax.

The Change Passenger Details Flow (MYB: CPD)

  1. The Airline displays profile information to the passenger.
  2. The passenger clicks a link to Change Passenger Details. The Airline calls /pnr GET to obtain SSR data.
  3. The Airline displays the PNR information to the passenger.
  4. The passenger updates the passenger data (e.g. passport number).
    1. New feature – the passenger can add SSR’s of Indian tax details but only if no SSR details are returned for this passenger during PNR retrieval in addition they cannot delete or modify SSR data related to General Sales Tax (GST) data.
    2. If 1st passenger already provided GST data, the 2nd passenger still can add it in the Change Passenger Details Flow.
  5. The Airline updates the passenger's PNR with a /pnr/passengers POST request.

Ticket Field Expansion

Digital Connect v3.4 enhances Ticketing by changing background handling of the fare value. Ticketing currently has limitations of 8 characters for base, equivalent, and total amounts and 7 characters for tax amounts. The decline of currency values is causing carriers to experience errors at the time of ticketing because of the digit limitation. New enhancement to Ticketing provides an accurate display of large value currencies in Digital Connect and assures their proper handling in processing. Form of Payment (FOP) is now changed to allow both forms of payment to be 9 characters in length.

This enhancement affects below paths:

  • The Revenue Flow (B2C);
  • Manage Your Booking – Change Itinerary Flow (MYB: CI);
  • Manage Your Booking – Book Now Pay Later Flow (MYB: BNPL);
  • Business to Business (B2B).

The proper error message will be provided in the case of Multiple Form of Payment (MFOP).

No special setup is required for this enhancement it will be activated automatically.

Limitations

This feature will only be available in conjunction with a “normal” fare. What is meant by a “normal” fare is one which is not CAT35 (of any type) or contains any “net” data.

Pricing Breakdown of Loyalty Fares and Taxes by Fare

The conversion of taxes in the redemption space is problematic due to the various taxes that can be applied at any level within the fare structure. Redemption for fixed fares works at the fare component level and when some taxes cross the itinerary it is difficult to determine the conversion and refund strategies for these taxes. Redemption fares and taxes on those fares may or may not be converted to points per the carrier’s business direction.

Digital Connect clearly defines each tax in the pricing response and provides points breakdown of taxes and surcharges that apply to each fare component in an itinerary.

The taxes will be returned in the response at the following levels:

  • The complete itinerary;
  • Inbound or outbound;
  • The fare component;
  • Segment;
  • Part of the base fare.

This feature allows the taxes to be returned at the fare component level regardless of how the Airline filed the taxes and surcharges.

Dynamic fares (in fully dynamic and mixed awards scenarios) are also adjusted to make sure that the summation of the fare component pricing matches itinerary part pricing.

This functionality applies to The Redemption Flow (RBE).

Prerequisites

  • Tax compensation logic and surcharge compensation must be activated in IntelliSell.
  • Configuration to use fare breakdown enabled.
  • Configuration to use this functionality or to keep the existing logic.

Limitations

This functionality only applies to fixed awards.