Accounting Remarks

Accounting Remarks are optional remarks that are added to the PNR and typically used by an agency's back office system in some way. The remarks can include ticket numbers, customer or account numbers, fares offered to the customer but refused, and canned remarks that document fare rules.

Note: Accounting Remarks can be added for the Galileo (1G) and Apollo (1V) providers.

Accounting Remarks are supported in:

Request

Include one or more AccountingRemark element in the Create Reservation request to add an accounting remark to a reservation.

Include TypeInGds to define the type of accounting remark. Any accounting remark type that does not have a specific TypeInGds should be sent as TypeInGds="Other", and a Category should be included. See the Exceptions section for a list of valid entries for TypeInGds and Categories for each Host.

Use BookingTravelerRef to link an accounting remark to a specific traveler.

Set @UseProviderNativeMode="true" to add Accounting Remarks which are not feasible through regular channels to Galileo (1G) and Apollo (1V).

Adding, Updating, and Deleting Accounting Remarks

Accounting Remarks can be added, updated, and deleted using UniversalRecordModifyReq/UniversalModifyCmd and:

Multiple Accounting Remarks can be added and updated in one request. To delete multiple remarks, send multiple UniversalModifyCmd elements in the request.

Encode/Decode for Accounting Remark Type Codes

Reference Data is available for Accounting Remark Type codes. To obtain the Type code values, send ReferenceDataRetrieveReq TypeCode="AccountingRemarkType".

Response

The accounting remark is returned in the response:

The Category in AccountingRemark is sent in the request as a 2- to 3-character alpha field, but it returns in the response as a 4-character numeric. See the Exceptions section for a list of categories and codes for the Host.

When a Universal Record request is submitted, if a change in Accounting Remark is detected, the change is stored in the UR History.

Exceptions

  • In Galileo, accounting remarks are called Document Itinerary Remarks and are displayed in a PNR with the format *DI.
  • The Category in AccountingRemark is sent in the request as a 2- to 3-character alpha field, but it returns in the response as a 4-character numeric.

The following table shows accepted values for AccountingRemark when sent to Galileo.

TypeInGds & Related Host Keyword () Category Request Format Response Keyword

Fare saver (FS)

None

Special characters allowed, but no decimal allowed. If the Host sends an @, replace is it replaced in Universal API by a dot for sync/store/history etc.

3002

Canned (CR)

None

Up to 43 characters. Numeric values separated by ".", E.g., 1.33.65.2.14.64

3003

Ticket number (TK)

None

Up to 10 numeric characters, in two formats: 10 digits or 10 digits-3 digits for conjunctive ticket, e.g., 1234567890 or 1111222234-235

3006

Customer number (AC)

 

Up to 34 alpha numeric characters, including special characters. Currently, Universal API does not accept DOTS but the Host does. If the Host sends an @, it is saved/compared/synched as a dot in the Universal Record (UR).

3009

Back office accounting field (X*)

X*

Up to 89 characters (including the DI.X* entry). For example:

Copy 
<com:AccountingRemark Key="13" TypeInGds="Other" Category="X*" >
<com:RemarkData>X*AG-S1W1-example</com:RemarkData>
</com:AccountingRemark>

3000

AgentSign (AR)

None

Up to 10 alpha numeric characters, e.g., T-FA-SN

3018

Other
  • Free text (FT)
  • Design your own (DYO)
  • Payment Calculator (CM)
  • Free text (T): Up to 90 characters (including the DI.FT- entry). Although Universal API allows all special characters, the Host has limitations on certain characters.

  • Design your own (DYO): Exactly 2 numeric characters.

3010 (FT)

3001 (DYO)

3000 (CM)

  • Apollo does not support Category X*. Instead, use T-.

  • The Category in AccountingRemark is sent in the request as a 2- to 3-character alpha field (Keyword), but it returns in the response as a 4-character numeric.

    • Notes:

    • These remarks are supported for Apollo (1V) only.
    • If the request contains TypeInGDS as “Other” and Remarks starts with any new category (e.g., “*MK-Test Remarks”), the response converts the category to “*MK” and the remarks to “Test Remarks”.

The following table shows all the accepted values for AccountingRemark TypeInGDS= when sent to Apollo.

TypeInGds & Related Host Keyword () Category Request Format Response Keyword

Fare (DS)

None

Up to 9 characters. [0-9]{1,7}+ single @ {0,1} + [A-Z]{0,1}

If @ is present, then single alpha has to exist, e.g., DS-80002@Y

3002

Canned (CR)

None

Up to 58 characters. Numbers, hyphens, and @, with two formats accepted:

  1. Numbers and any number of @ signs, e.g., CR-12@34@121212@12 2

  2. [0-9]{1,2} @ [ [0-9]{1,2} single hyphen [0-9]{1,2} ]

    and this pattern repeats, for example: 

    CR-22@45-26 or 22@45-66@34

    or

    CR- 34@22-90@34-76 or 1-2@4-5@8

3003

Ticket (TK)

None

[0-9]{8,10} + single hyphen {0,1} + [0-9]{3}. If hyphen is present then 3 digits after hyphen should be present, e.g., TK-1276121821-825

3006

Account (CA)
  • SA
  • SD
  • CD

If Category is not included, the default is CA. Up to 61 alpha numeric characters, with any number of @.

E.g., CA-127A@12G

Important: @ in remark content is replaced with the pillow character (¤) in Apollo. Therefore, sending:

<com:AccountingRemark TypeInGds="Account">

 <com:RemarkData>01@400</com:RemarkData>

</com:AccountingRemark>

Results in the following Accounting Remark in the PNR:

TRMK-BACK OFFICE BRANCH & ACCOUNT NO-01¤400

3007 (CA)

3014 (SA)

3015 (SD)

3016 (CD)

AgentSign (FA)

None

E.g., T-FA-SN

3018

ServiceFee (SF)

None

E.g., T-SF-45.00

3013

InvoiceLayout (DEF)

None

E.g., T-DEF11

3011

MarketCode (MK)

*MK

*MK – Market code

3000

BranchLocationOverride (BL)

*BL

*BL – Branch location override

3000

BranchAgentOverride (BA)

*BA

*BA – Booking agent override

3000

SellingAgentOverride (SA)

*SA

*SA – Selling agent override

3000

TicketingAgent (TA)

*TA

*TA – Ticketing agent

*TA-TEST REMARK

3000

PurchaseOrder (PO)

PO

PO – Purchase order

3000

ItineraryWithFare (IO)

IO

IO – Itin with Fare/No Invoice Nbr

ITIN ONLY-TEST REMARK

3000

ItineraryWithoutFare (IN)

IN

IN – Itinerary without Fare

ITIN NO$-TEST REMARK

3000

ItineraryWithAmount (ID)

ID

ID – Itinerary with Amount

ITIN W/$-TEST REMARK

3000

Product Type Override (PT)

*PT

*PT- Product Type Override

*PT-TEST REMARKS

3000

Sort (S1 - S99)

S<n>

S1 thru S99 - Sort <n> for S1-S9 and S<n> for S10-S99

If it is s1-09, then in Apollo, it converts to SORT ‘n’ spelled out, whereas, if it’s S10-S99, it displays as shown:

SORT 1-2323

2 SORT 2-23424

3 S10-ABAB

4 S99-3232/2323

3000

Other
  • Free text (T)
  • Design your own (DYO)
  • PTA number (PT)
  • Override agency phone field (PH)
  • Waive PTA Fee/No PTA Fee (NP)
  • Add PTA Fee (PF)
  • Add Routing Code (RC)
  • Free text (T): Up to 64 alpha numeric characters, including special characters - *, hyphen and dot. E.g., T-TEST*12-34.REMARK

  • Design your own (DYO): 2 numeric characters, no hyphen, e.g., DYO05

  • PTA number (PT): E.g., T-PT-72838283
  • Override agency phone field (PH): E.g., T-PH-303200534
  • Waive PTA Fee/No PTA Fee (NP): E.g., T-NP-16.00
  • Add PTA Fee (PF): E.g., T-PF-45.00
  • Add Routing Code (RC): Required for Canadian Market in Apollo. E.g., T-G*RC/44

3000 (T)

3001 (DYO)

3012 (PT)

3019 (PH)

3005 (NP)

3004 (PF)

3017 (RC)

 

Worldspan supports TypeIndGds="Account", "Other", and "DividerCard".

See Divider Card Remarks for more details.

TypeInGds="DividerCard"

A maximum of 40 characters is allowed in a Divider Card Remark. If the entry exceeds the limit, a warning is returned: "Divider Card Remark can be maximum 40 characters for the requested Provider and this Divider Card Remark is not applied".

TypeInGds="Account"
  • Worldspan only supports one remark with TypeInGds="Account". If multiples are submitted, only the first remark with TypeInGds="Account" is mapped to the host and saved in the Universal Record, and a warning is returned: "Provider supports only one AccountingRemark of TypeInGDS = Account".
  • If the PNR already has a AccountingRemark with TypeInGDS="Account", a warning is returned: "Only one AccountingRemark with TypeInGDS = Account is supported by provider. The reservation already has an existing AccountingRemark with TypeInGDS = Account".
  • PNRA.XS.CA (text) is mapped to AccountingRemark (text).
  • PNRA.XS.CA allows a maximum of 30 characters. If more than 30 characters are sent in the request, the request is truncated and submitted to the Host and a warning is returned: "Provider supports a max of 30 characters for AccountingRemark with TypeInGDS = Account. Text truncated while submitting to provider."
TypeInGds="Other" with Category=FT (Free form Text)
  • Mapped to PNRA.GRA.GR.
  • Allows a maximum of 66 characters per remark.If more than 66 characters are sent in the request, the request is truncated and submitted to the Host and a warning is returned: "Provider supports a max of 66 characters per AccountingRemark. Text truncated while submitting to provider."
TypeInGds="Other" with other Categories
  • A warning is returned: "Provider only supports Category of FT for AccountingRemark with TypeInGDS = Other"."

"TAN" (Traveler Account Number) is an acceptable entry in the TypeInGds field.

  • Universal API sends the TAN details to ACH and retains the same information in the AirCreatereReservationRsp. If no booking traveler reference is indicated in an Accounting remark with TypeIndGds=TAN, then the first respective Accounting remark will be mapped to the first booking traveler in the ACH book request.

  • If a request with TAN data for any carrier other than Air Canada is sent, Universal API ignores it and does not send it to ACH (thus it will not be in the Universal Record).
  • All bookings that have accounting remarks with TAN details are now available whenever a Universal Record Retrieve or Universal Record History is requested.
  • In the request, at minimum, the TAN number must be sent with the SupplierCode ( (T20098776DAC/AC)TAN Number and SupplierCode separated by a “/”). Acceptable formats are:

    • T20098776DAC/AC

    • T20098776DAC/AC/IATA

    • T20098776DAC/AC/IATA/Govt of Canada

    • T20098776DAC/AC//IATA/Govt of Canada/Add