Skip to main content

AIR Setup (Table 51342)

The AIR Setup table is the central configuration for the entire AIR booking processing system. It is a singleton table (only one record exists).

Manual setup is often easier

Since this is a singleton table with a dedicated setup page, it is usually faster and less error-prone to configure it manually in the UI rather than via config package. Search for "AIR Setup" in Business Central to open the page directly.

Page​

Accessible via AIR Setup page (search for "AIR Setup" in Business Central).

Field Reference​

Markup Configuration​

Field IDField NameData TypeDescription
44NDC Markup % DomesticDecimalMarkup % for NDC (New Distribution Capability) tickets on domestic trips. Visible and VAT-carrying as its own line under the net revenue model
45NDC Markup % ForeignDecimalMarkup % for NDC tickets on foreign trips. Grouped into the booking line on the invoice printout under the net revenue model
42BSP Card Fee %DecimalCard transaction fee %, calculated on the Fare Gross Amount and added to the line's Markup Amount
46Include OB Fee in Markup BaseBooleanWhen Yes, NDC Markup % and BSP Card Fee % are calculated on Fare Gross Amount plus the airline's OB fee (the AIR file's ATF line — a charge the airline adds on top of the ticket, most often for card payment). Defaults to No: no percentage markup is taken on top of the airline's own fee. The fee itself is always included in the flight line amount regardless of this setting
43Currency Rate Markup %DecimalMarkup applied to the converted amount when converting foreign currency bookings. InitValue = 5, MinValue 0, MaxValue 100 — a new setup record starts at 5% unless you change it. Can be excluded per customer (see Customer field "Excl. Currency Rate Markup")
71Markup PresentationEnum Markup PresentationHow 0%-VAT (exempt) markup lines are shown on the printed invoice: printed as their own line (default), grouped into the booking line, or grouped into the same passenger's service fee line. Presentation only — posting, VAT entries and order lines are identical in all modes. See the enum reference for the full mode semantics
72Always Specify Service FeesBooleanForces itemized service fee lines on invoice printouts regardless of the customer's Specify Service Fees setting — the customer flag can only add itemization, never remove it. Enable in jurisdictions where the agency's remuneration must not be merged into disbursement (booking) lines, e.g. Norway (Bokføringsforskriften § 5-1-5). Presentation only — posting is unaffected

How the markup fields interact​

  • NDC markup applies only when the ticket is an NDC ticket and the booking carries no manual markup (RM*MA remark). A manual markup always wins; the NDC percentage is never added on top of it.
  • BSP Card Fee applies when the Form of Payment is not a UCCCF card charge and the booking's customer has a Credit Card Provider other than None. It is added to whatever markup already exists (manual or NDC).
  • Both are calculated per passenger, on the Fare Gross Amount — plus the airline's OB fee only when Include OB Fee in Markup Base = Yes.

Voucher Configuration​

Field IDField NameData TypeDescription
30Voucher No. SeriesCode[20]Number series used for generating voucher numbers. Must reference a valid No. Series record in Business Central

Supplier VAT Specification​

Only relevant together with the net revenue model, where booking lines are disbursements at 0% VAT.

Field IDField NameData TypeDescription
73Supplier VAT SpecificationEnumHow the supplier's VAT inside a disbursement line is shown on the invoice. None (default): nothing is printed. Amount Only: an informational row per line — "thereof 12 % VAT: 144.00 (base 1 200.00)". Name and Org. No.: the same row plus "issued on behalf of supplier, org.no number MVA", and posting is blocked when the attribution is incomplete
74Show Disbursement VAT NoteBooleanPrints a short explanatory line under the VAT summary stating that the 0% lines contain the supplier's VAT, specified per line, and that it is not part of the company's own VAT return

The amount is display only in every mode. It is never posted, never enters the VAT statement, and never changes a total — it exists so that a business customer can deduct the VAT the supplier charged.

Name and Org. No. has an operational consequence: every domestic supplier must exist as a vendor with an org.nr before an invoice containing its VAT can be posted. See Vendor.

Invoice Payment Info​

Controls the payment details block on the printed sales invoice.

Field IDField NameData TypeDescription
75Invoice Payment InfoEnumBankgiro (default): the invoice prints the Bankgiro number (Company Information → Giro No.) and the OCR payment reference. IBAN: the invoice prints IBAN and SWIFT/BIC from Company Information and asks the customer to state the invoice number as the payment reference — use for companies without a domestic giro or structured-reference (OCR/KID) agreement

In IBAN mode, Company Information must carry IBAN and SWIFT Code — verify both before the first invoice run.

Related, but driven by Company Information rather than this setting: the Swedish "Godkänd för F-skatt" footer text only prints when the company's Country/Region Code is SE (or blank), and a company with Country/Region Code NO instead prints "Foretaksregisteret" and appends "MVA" to the org.no when a VAT Registration No. is present.

Document Sending​

Field IDField NameData TypeDescription
76Auto Email Invoices EnabledBooleanMaster switch for the PDF email queue. Yes: posted invoices and credit memos for customers whose Document Sending Profile has E-Mail active are queued and emailed by codeunit 51722. No (default): posted documents are left at Not Applicable and the queue exits immediately. Customers whose profile has Electronic Document active are never emailed by this queue in either case

Leave it No until the email account, Report Selection, Document Sending Profiles and the job queue entry are in place — and when an external distribution service owns outbound distribution. Full setup: Document Email.

Credit Card Providers​

Field IDField NameData TypeDescription
52FirstCard EnabledBooleanEnables the FirstCard provider in this company. Defaults to Yes. When No: CCCA bookings stop in import validation with a clear error, and FirstCard cannot be selected as Credit Card Provider on customers
53Diners EnabledBooleanEnables the Diners provider in this company. Defaults to Yes. When No: CCDC bookings stop in import validation with a clear error, and Diners cannot be selected as Credit Card Provider on customers

Use these to switch off providers that do not exist in a company — e.g. the Norwegian company uses Diners only, so FirstCard Enabled should be set to No there (FirstCard is an SEB Sweden product). Disabling a provider does not affect customers that already have it selected — it blocks new selections and stops incoming bookings with that form of payment.

Credit Card Receivables​

Field IDField NameData TypeDescription
50FirstCard Receivables AccountCode[20]G/L Account for FirstCard receivables. Used when posting credit card settlement entries
51Diners Receivables AccountCode[20]G/L Account for Diners Club receivables. Used when posting credit card settlement entries

Revenue Model​

Field IDField Name (caption)Data TypeDescription
70Net Revenue Model (Disbursements)BooleanEnables the net revenue model for booking lines in this company. When Yes: the import keeps the gross supplier amount on booking lines (supplier VAT is never subtracted from flight fares, and domestic hotel/car/ground transport lines use Price Including VAT), and VAT validation expects 0 % VAT on booking lines instead of the source VAT. Defaults to No (gross model). (AL field name: Net Revenue Model)

See Revenue Model: Gross vs Net for what the models mean, the configuration that must accompany the switch, and how to choose — the choice follows from the agency's contractual setup and must be confirmed with its accountant. The Norwegian company runs the net model (see Norway setup); the Swedish baseline is gross.

The switch and the item VAT groups must agree: enabling it while booking items still have a non-zero VAT group produces a VAT validation error on every domestic booking (and vice versa — 0 % disbursement VAT groups without the switch underbill every domestic booking by the supplier VAT).

Web Bookings​

A booking counts as a web booking when any passenger's AIR Comment field contains the marker CYTRIC — the online booking tool is always Cytric via Amadeus, so the marker is built in and requires no configuration. (Field 65, Web Booking Identifier, briefly made it configurable; it no longer exists.)

Being a web booking has one effect: it selects the row with Is From Web = Yes in AIR Order Item Mapping (the key field — there is no naming convention such as a -W suffix; you may name the items anything). (It previously also selected the NDC Markup % — that rate now splits by trip region instead, fields 44/45.)

Item Defaults​

Defaults applied when a user presses New on the Item Card. The new item is always set to Type = Service; the three fields below are applied only when non-blank. Configure them with codes that exist in the company.

Field IDField Name (caption)Data TypeDescription
60Item Default Unit of MeasureCode[10]Default base unit of measure for new items (e.g. STYCK in Sweden, STK in Norway). Related to Unit of Measure
61Item Default Gen. Prod. Posting GroupCode[20]Default general product posting group for new items (e.g. FLY OTH). Related to Gen. Product Posting Group. (AL field name: Item Default Gen. Prod. Group)
62Item Default VAT Prod. Posting GroupCode[20]Default VAT product posting group for new items (e.g. MOMS25 in Sweden, MVA25 in Norway). Related to VAT Product Posting Group. (AL field name: Item Default VAT Prod. Group)

Test Mode (Optional)​

Field IDField Name (caption)Data TypeDescription
10Test Mode EnabledBooleanWhen enabled, AIR processing falls back to the test defaults below when real data is missing (e.g. no item mapping found), and bypasses some validations. Cannot be enabled unless fields 11–14 are all filled in
11Test Mode Default Booking ItemCode[20]Item No. used for booking lines when no item mapping matches. Must be a valid, non-blocked Item. (AL field name: Test Mode Booking Item)
12Test Mode Default Service ItemCode[20]Item No. used for service fee lines when no item mapping matches. Must be a valid, non-blocked Item. (AL field name: Test Mode Service Item)
13Test Mode Default CustomerCode[20]Customer No. used when the customer is not found. Must exist and not be blocked
14Test Mode Default SalespersonCode[20]Salesperson Code used when the salesperson is not found. Must be a valid Salesperson/Purchaser
20Test Mode WarningText[250]Read-only (Editable = false) warning text shown on the setup page. Initialised to "WARNING: Test mode bypasses critical validations and should only be used in test environments!" — not configurable, and there is nothing to enter for it in a config package

Config Package Notes​

This is a single-record table. In the config package:

  • The Primary Key field (field 1) should be blank (empty string)
  • Include the configurable fields listed above — but not field 20 (Test Mode Warning), which is read-only and self-initialising
  • Test Mode fields are optional — only include if the customer wants to start with test mode enabled
  • Set Currency Rate Markup % explicitly. Leaving it out of the package does not mean 0% — a freshly created record initialises to 5%

Setup Guidance​

Typical Values​

FieldTypical RangeNotes
NDC Markup % Domestic0–5%Depends on customer agreement. Only applies to NDC tickets with no RM*MA markup. Visible + VAT-carrying line under the net model
NDC Markup % Foreign0–10%May be set higher — grouped into the booking line on the printout under the net model. Same condition
BSP Card Fee %0–3%Depends on card provider agreement. Only for non-UCCCF bookings on card customers
Currency Rate Markup %0–5%Defaults to 5%. Applied to the converted amount

Dependencies​

  • Voucher No. Series must reference an existing No. Series. Create the No. Series first if it doesn't exist
  • Supplier VAT Specification = Name and Org. No. requires domestic travel vendors to carry an org.nr (Registration Number). Set the field before importing vendors, so the requirement is enforced as the vendor list is built rather than discovered at the first invoice
  • Receivables Accounts must reference existing G/L Accounts of type Posting that are not blocked
  • Item Defaults (60–62) must reference an existing Unit of Measure, Gen. Product Posting Group and VAT Product Posting Group
  • Test Mode items, customer, and salesperson must exist before enabling test mode
tip

Start with Test Mode enabled during initial setup — it lets you process test bookings before all master data is in place, by falling back to the test defaults. It is also the way to import AIR files that belong to another business (the usual test material early in a project): their customers and salespersons do not exist in this company, and Test Mode substitutes the defaults instead of failing. When testing like this, read the warnings in the AIR Import Log — customer/salesperson fallbacks are expected for foreign files, but an item mapping fallback on a combination this business also uses means a mapping row is missing.

Disable Test Mode once the configuration is complete, and run the final verification with Test Mode off: with it on, missing mappings and master data are silently masked by the defaults, so a passing test proves nothing about the real configuration.