Customer — Custom Fields
The extension adds 14 fields to the standard Customer table. These fields control how the system handles bookings, invoices, and credit card settlements for each customer.
Field Reference
| Field ID | Field Name | Data Type | Description |
|---|---|---|---|
| 51309 | Require Department | Boolean | When enabled, warns if Department is empty on AIR sales order lines — and blocks posting |
| 51310 | Require Project Number | Boolean | When enabled, warns if Customer Project is empty on sales order lines — and blocks posting |
| 51311 | Require Cost Place | Boolean | When enabled, warns if Cost Center is empty on sales order lines — and blocks posting |
| 51312 | Require Employee Number | Boolean | When enabled, warns if Employee ID is empty on sales order lines — and blocks posting |
| 51322 | Require Requisition No | Boolean | When enabled, warns if Requisition No is empty on sales order lines — and blocks posting |
| 51323 | Require Requester | Boolean | When enabled, warns if Requester Name is empty on sales order lines — and blocks posting |
| 51313 | Credit Card Provider | Enum | Which credit card provider handles this customer's payments. Values: None (caption "None (Invoice)" — default), FirstCard, Diners |
| 51314 | Credit Card No. | Text[16] | The customer's corporate credit card number. Not enforced by the table — checked during booking validation for UCCCF bookings. Displayed masked on the Customer Card |
| 51316 | Specify Service Fees | Boolean | When enabled, service fees are itemized separately on the invoice report instead of being grouped. Overridden by Always Specify Service Fees in AIR Setup (field 72) — when that company flag is on, fees are always itemized regardless of this value |
| 51317 | Hotel Voucher Option | Enum | Controls hotel voucher type for web bookings only. Values: Manual (goes to the Voucher Decision queue), Yes (Voucher Type = Voucher), No (Voucher Type = Confirmation) |
| 51318 | Car Rental Voucher Option | Enum | Same as Hotel Voucher Option, for car rentals. Web bookings only |
| 51319 | Hotel Voucher Dismissed | Boolean | Internal flag — suppresses the voucher decision prompt after user has dismissed it. Not for manual configuration |
| 51320 | Car Rental Voucher Dismissed | Boolean | Internal flag — same as above for car rentals. Not for manual configuration |
| 51321 | Excl. Currency Rate Markup | Boolean | When enabled, the currency rate markup percentage (from AIR Setup) is not applied to this customer's bookings |
Config Package Mapping
When building a config package, include these fields from the Customer table (table ID 18):
| Include in Package | Field ID | Typical Source |
|---|---|---|
| Yes | 51309–51312, 51322–51323 | Customer requirements document — which reference fields are mandatory per customer |
| Yes | 51313 | Contract with Diners/FirstCard — which provider, if any |
| Yes | 51314 | Customer's corporate card number |
| Yes | 51316 | Customer preference — itemized service fees or not |
| Yes | 51317–51318 | Customer preference — voucher behavior for web bookings (ignored for non-web bookings) |
| No | 51319–51320 | Internal flags, leave as default (false) |
| Yes | 51321 | Customer agreement — currency markup exclusion |
Behavior Details
Required Field Warnings — soft at import, hard at posting
The "Require" flags (Department, Project Number, Cost Place, Employee Number, Requisition No, Requester) behave differently at the two stages:
- At order creation they do not block anything. They generate warnings (visible in the Order Reference Warning table) when the corresponding field is empty on a sales line, so the booking is processed while the missing information is flagged for follow-up.
- At posting they are hard blockers.
Sales-Postre-evaluates the warnings and raises an error listing every offending line, so the document cannot be posted until each required field is filled in.
Turning on a Require flag for a customer whose AIR files do not carry that remark will stop their invoices from being posted. Confirm with the customer that the corresponding RM* remark is actually present in their bookings before enabling the flag.
The data for these fields comes from RM remarks in the AIR booking file:
- Department → from
RM*ADremark - Customer Project → from
RM*PRremark - Cost Center → from
RM*COremark - Employee ID → from
RM*EMremark - Requisition No → from
RM*REremark - Requester Name → from
RM*YRremark
Credit Card Provider
When a Credit Card Provider is set on a customer:
- Sales orders created for this customer are automatically tagged with the provider
- The credit card status tracking is enabled on the order
- Settlement files can be generated for the provider
- The Credit Card Provider field on the sales order is locked (cannot be changed manually) for AIR-created orders
Credit Card No.
The field is not validated at table level — a customer record can be saved with a provider and no card number. It is checked during booking validation: for a UCCCF booking (Form of Payment CCDC/CCCA) the system verifies that the customer's Credit Card Provider matches the Form of Payment and that Credit Card No. is non-blank; otherwise an error is written to the AIR Import Log and the import fails.
On the Customer Card the value is displayed masked (************ plus the last 4 digits). When verifying a config-package import, do not read the card number off the Customer Card — check it against the source data or via the config package worksheet instead.
Voucher Options
The customer's voucher option is consulted only for web bookings (bookings whose passenger comments contain the marker CYTRIC — the online booking tool). For non-web bookings the system takes the voucher flag straight from the AIR file and ignores this setting entirely.
For web bookings, the option controls what happens when a hotel or car rental booking is processed:
- Manual: No automatic decision. The segment goes to the Voucher Decision queue and a user picks the type per booking
- Yes: Voucher Type = Voucher (agency pays the vendor; a voucher is sent)
- No: Voucher Type = Confirmation (vendor invoices the traveller/customer; a confirmation is sent). Note this is not "no voucher document at all" — it selects the Confirmation variant, which drives the Confirmation rows in AIR Product Posting Setup