Category: Anti-Bribery and Corruption

Gift and Hospitality Register

Also known as: Gifts and Hospitality Register, Gifts Register

Simply put

A gift and hospitality register is a record in which an organisation logs gifts and hospitality that its staff, board members, or officials receive, and in some cases those they give. It is used to promote transparency and to help the organisation spot situations where a gift might create a conflict of interest or an ethical concern. Some organisations publish their register, for example on an annual basis.

Formal definition

A gift and hospitality register is a compliance and transparency control through which an entity captures details of gifts and hospitality offered to or received by members, staff, or board members, and in some cases items given by the business, so that potential conflicts of interest and integrity risks can be monitored. Typical entries require full and accurate reporting of the nature, source, and value of each item, supporting anti-bribery and conflict-of-interest management; the register may also be used to track red flags and risk areas arising from gifts sent from the business. Ownership of the register and the disclosure threshold vary by organisation, sector, and jurisdiction, and public bodies such as government departments and prosecuting authorities may publish registers of items received by board members on a periodic basis. The specific scope, reporting obligations, valuation thresholds, and whether disclosure is mandatory or a matter of internal policy depend on the entity's own rules and applicable requirements, and are out of scope of this general definition.

Why it matters

Gifts and hospitality are a recognised area of integrity risk because an item of value, whether a meal, an event invitation, or a physical gift, can create, or appear to create, a conflict of interest or an obligation that influences a decision. A gift and hospitality register addresses this by making such exchanges visible rather than leaving them to individual judgement and memory. Under certain frameworks and internal policies, full and accurate reporting of the nature, source, and value of each item supports both conflict-of-interest management and broader anti-bribery objectives, allowing an organisation to identify patterns that a single isolated disclosure would not reveal.

The register is also a transparency mechanism, particularly in the public sector. Some bodies publish records of items received by board members on a periodic basis; for example, the Crown Prosecution Service publishes details of gifts and hospitality received by its Board members over the reporting year on an annual basis, and New Zealand's Treasury periodically releases material relating to its register of corporate hospitality and gifts received. Publication of this kind serves accountability to external stakeholders, whereas an internal-only register serves monitoring and control within the organisation. Whether a register is published, and what threshold triggers a disclosure obligation, varies by entity, sector, and jurisdiction.

It is important not to overstate what a register achieves on its own. A register is a record and a control point; it does not by itself prevent improper conduct, and its value depends on whether entries are made accurately and completely and whether the resulting information is reviewed. It also does not replace substantive anti-bribery, conflict-of-interest, or ethics policies, and it is not, in itself, a legal requirement in all contexts, whether one is mandatory, and on what terms, depends on applicable requirements and the organisation's own rules.

Who it's relevant to

Board members and senior officials

Board members and officials are frequently the subjects of register entries, and in published registers, such as those maintained by some public bodies for items received by board members, their disclosures may be visible externally. They are typically expected to report fully and accurately the gifts and hospitality offered to them, and to understand how an accepted item could bear on actual or perceived conflicts of interest.

Chief compliance and ethics officers

Compliance and ethics functions generally design and administer the register, set reporting thresholds within the organisation's policy, and review entries for red flags. They are typically responsible for connecting the register to broader anti-bribery and conflict-of-interest management rather than treating it as a standalone log.

Staff and members

Employees and members who receive, or in some organisations give, gifts and hospitality are the primary reporters into the register. Their obligation to record the nature, source, and value of items, and the threshold at which a disclosure is required, depend on the organisation's own policy and applicable requirements.

Internal audit and assurance functions

Assurance functions may examine whether the register is being used as intended, that is, whether entries are complete and accurate and whether they are reviewed, as part of assessing the operating effectiveness of gifts, hospitality, and anti-bribery controls. Reviewing the register is distinct from owning it; assurance evaluates the control rather than administering it.

Public bodies and their stakeholders

Government departments, prosecuting authorities, and similar public entities may publish registers of items received by board members on a periodic basis, supporting external accountability. Citizens, oversight bodies, and other stakeholders relying on that transparency are relevant users of published register information.

Inside Gift and Hospitality Register

Recipient and Giver Details

Typically records who received or offered the gift or hospitality and the counterparty involved, including the organization and, where relevant, the individual's role or relationship to the business (for example, a supplier, customer, or public official).

Description and Nature of the Benefit

Captures what was given or received (a physical gift, meal, event, travel, or entertainment) so that the entry can be assessed against policy thresholds and prohibitions.

Estimated Value

Generally includes a monetary estimate of the benefit, which supports comparison against pre-set de minimis limits and approval thresholds set out in the organization's gifts and hospitality policy.

Date and Context

Records when the item was given or received and the surrounding circumstances, such as whether a tender, contract negotiation, or regulatory decision was pending at the time.

Approval and Disposition Status

Notes whether the gift or hospitality was accepted, declined, returned, retained, or escalated for approval, and identifies who authorized any exception.

Ownership and Maintenance

The register is typically owned and maintained by the compliance function as a first-line-supported control, though the underlying duty to declare usually rests with individual employees and managers.

Common questions

Answers to the questions practitioners most commonly ask about Gift and Hospitality Register.

Does maintaining a gift and hospitality register mean gifts and hospitality are prohibited?

No. A register is a monitoring and transparency tool, not a prohibition. It records offers, receipts, and sometimes the giving of gifts and hospitality so that patterns can be reviewed and conflicts identified. Whether particular gifts or hospitality are permitted, capped, or barred is determined by the organisation's underlying gifts and hospitality policy and by any applicable anti-bribery laws, which vary by jurisdiction, sector, and counterparty (for example, dealings with public officials are often treated more strictly). The register evidences compliance with those rules; it does not itself set them.

If something is entered in the register, does that make it automatically acceptable?

Not necessarily. Recording an item creates a documented trail but does not, on its own, confer approval or legitimise conduct that breaches policy or law. Under many programs, entries above a defined threshold require separate review or sign-off, and a properly logged item may still be declined, returned, or escalated. Treating registration as a substitute for judgment is a common misconception; the register supports oversight rather than replacing the policy assessment and, where relevant, the approval workflow.

Who typically owns and maintains the gift and hospitality register?

Ownership arrangements vary by organisation. In many programs the compliance function owns the policy, the register's design, and periodic review, while individual employees and managers are responsible for making accurate and timely entries as a first-line activity. Assurance functions such as internal audit generally do not maintain the register but may test whether it operates as intended. Boards or audit/risk committees typically receive summary reporting rather than administering the register directly. Organisations should confirm accountability in their own policy.

What information is commonly captured in a register entry?

Fields vary by organisation, but entries commonly capture the individuals or entities involved (giver and recipient), the nature and estimated value of the gift or hospitality, the date, the business context or relationship, whether it was offered, received, given, accepted, or declined, and any approval obtained. Some organisations also flag whether a public official or a party in an active tender or negotiation is involved. The precise fields should reflect the organisation's policy, risk profile, and reporting needs.

How are monetary thresholds generally used with a register?

Many programs set thresholds that determine the required action rather than whether an item is logged. A common approach is to require recording of items above a de minimis amount and to require pre-approval or escalation above a higher threshold; some organisations require all items to be recorded regardless of value. Thresholds and their treatment differ across organisations and may be stricter for public officials or during sensitive activities such as procurement. The applicable amounts and rules should be set out in the organisation's own policy.

How can an organisation check that the register is operating effectively?

Effectiveness generally depends on both design and operation. Design considerations include clear policy definitions, accessible logging mechanisms, defined thresholds, and an escalation path; operating considerations include whether entries are made completely, accurately, and promptly, and whether required approvals actually occur. Periodic review may look for under-reporting, clustering of items around thresholds, or entries linked to counterparties in active decisions. Independent testing by an assurance function can assess these points, but any review approach should be tailored to the organisation and is a matter of professional judgment rather than a fixed standard.

Common misconceptions

A gift and hospitality register is a legal requirement for all organizations.

Maintaining a register is generally a control adopted as good practice and is often expected under anti-bribery and corruption frameworks, but whether it is required, and in what form, depends on jurisdiction, sector, and the applicable laws or regulations to which the entity is subject. It is frequently a policy-driven or best-practice measure rather than a universal statutory mandate.

Recording a gift in the register makes it acceptable.

A register is a transparency and monitoring tool, not an authorization mechanism. Logging an item does not by itself render it compliant; the benefit must still meet the organization's policy thresholds and any applicable legal restrictions, and improper benefits may remain prohibited regardless of whether they are disclosed.

The register alone demonstrates an effective anti-bribery control.

The existence of a register evidences control design, but it does not demonstrate operating effectiveness. Whether the control works depends on employees actually declaring items, timely review, and consistent enforcement, which typically require assurance testing to confirm rather than assume.

Best practices

Define clear value thresholds and approval requirements in policy, and align the register's fields so each entry can be assessed against those limits and any relevant prohibitions.

Assign clear ownership, with the compliance function typically maintaining the register while making the individual declaration obligation explicit for all employees and managers.

Require timely and prospective declaration where feasible, capturing context such as whether a tender or decision was pending, to support meaningful risk assessment rather than after-the-fact recording.

Periodically review register entries for patterns, concentrations, or trends and escalate items that approach thresholds or involve heightened-risk counterparties such as public officials.

Subject the register to independent assurance testing to confirm it operates effectively, not merely that it exists, and address gaps between policy and practice.

Provide targeted training and reminders so employees understand what must be declared, treating entries as educational compliance measures rather than legal or audit conclusions.