Skip to main content
Require a specific field on a specific form so records can’t be saved until that field is filled in.

​
Business Value

  • Enforces key fields on the forms you choose before records can be saved.
  • Prevents incomplete records by requiring fields such as Usage Department.
  • Configures each form’s required fields independently from one screen.
  • Removes a rule anytime to make the field optional again.
  • Captures cost-allocation data at the point of entry.

​
Use Cases

  • Finance manager requires Usage Department on Receiving Orders so every receipt carries a cost center.
  • Operations supervisor requires Usage Department on Store Usages to keep consumption data complete.
  • Administrator removes a mandatory-field rule when a form no longer needs it.

​
How It Works

  • Go to Front Office → Settings → General and open the Mandatory Fields screen. It lists the existing rules, each showing the form (Model) and the Field that is required on it.
  • Click Add New to create a rule.
  • Choose the Model — the form the rule applies to, such as Receiving Order or Store Usage.
  • Select the Field to make mandatory, such as Usage Department.
  • Click Save. A Settings saved successfully confirmation appears, and the new rule is added to the list.

​
Managing Rules

  • Use the Search Model box to filter the list by form.
  • Each rule has a delete icon — removing it makes that field optional on the form again.

​
Behavior When a Field Is Mandatory

  • The field is marked required on the selected form; saving without it is blocked with a validation message.
  • Validation applies on both create and edit.

​
Update: July, 2026

​
Channel & Company E-Invoicing Fields

The Mandatory Fields screen now includes two more models: Channel and Company. You can require their e-invoicing address and tax fields before a record is saved.

​
What’s New?

E-invoicing details on channels and companies are used for ETA in Egypt and ZTCA in Saudi Arabia. They were previously only checked when an invoice was generated, so an incomplete profile was caught late. You can now make these fields mandatory at data-entry time, the same way you already do for inventory documents.

​
How It Works

  • Add a rule and choose Channel or Company as the Model.
  • Select the Field to require. The available fields are the e-invoicing address and tax fields:
    • VAT Number
    • Registration Number
    • Country
    • City / Governorate
    • District
    • Address / Street
    • Building Number
    • Postal Code
    • Email
  • Click Save. The selected field is then required when creating or editing that channel or company.
Each property chooses which fields to enforce. As a guide:
  • ETA (Egypt): registration number and full address (governorate/city, street, postal code, country).
  • ZTCA (Saudi Arabia): building number, postal code, and district.

​
Update: August 30, 2026

​
Guest Profile Model — Enforced at Check-In

Mandatory Fields now has a Guest Profile model. Its rules are checked at check-in, not when the profile is saved.

​
What’s New?

Staff create the profile and reservation before the guest arrives. Identity and contact details come later, at the desk. So the profile still saves with fields missing. The data is checked at check-in instead.

​
How It Works

Add a rule, choose Guest Profile as the Model, then pick the Field to require. Each field is independent and all are off by default:
  • Guest details: Date of Birth, Language, Gender, Nationality, Document Type, Version Number, Issue Place, Issue Date, Expiry Date, Email, Mobile, Telephone, Work Phone
  • Contact information: Address, City, Country, Zip Code, PO Box, Contact Type

​
Enforcement at check-in

At check-in, the fields are checked on every guest profile on the reservation, not just the primary guest.
  • If any guest is missing a field, check-in is blocked. A warning appears: Profile/s data incomplete. The reservation does not change state.
  • This covers every action ending in Checked In: single check-in, bulk check-in, cancel-no-show, and undo-check-out.
  • Bulk actions are all-or-nothing. If one guest fails, no reservation is checked in.
  • Once every guest has the required fields, check-in works normally.

​
Help text on the guest profile

A banner at the top of the guest profile names the fields needed for check-in: The following fields are required to check in this guest: {list of mandatory fields}. The list comes from your own Guest Profile settings, using the same labels. With nothing configured, the banner does not appear. The banner is only a hint. The profile still saves with those fields empty.

​
Permissions

Any user who can edit a guest profile can also read the Mandatory Fields settings, so the banner works. They do not need the full settings permission.

​
What is not affected

  • Saving is never blocked. Only check-in is blocked.
  • Guests already checked in are not re-checked. There is no data migration.
  • Profiles from Online Booking, channels and OTAs, and from profile import, are not blocked.