Gifts and hospitality from clients
How staff should handle a gift or hospitality from a client, why a firm's own policy is the standard, and what to record in the independence register.
By Achekam · · 4 min read · For Accountants & audit firms in South Africa, Nigeria, Kenya
A client sends a hamper in December. A financial director invites the audit senior to a rugby final in the company's suite. A grateful owner insists on buying the team lunch the day the statements are signed. Each feels like courtesy, and refusing can feel rude. Each is also a small test of the firm's independence.
For staff, the question is rarely "is this allowed?" in the abstract. It is "what do I do now, with the client standing in front of me, and what do I write down afterwards?"
Why a gift is a threat at all
The IESBA Code's conceptual framework groups threats into self-interest, self-review, advocacy, familiarity and intimidation. Gifts and hospitality touch two of them:
- Self-interest. The person receiving something of value has a reason, however small, to keep the giver content.
- Familiarity. Repeated hospitality builds a personal closeness that can soften professional scepticism over time.
Both bear on the fundamental principles. The IESBA Code's five principles are integrity, objectivity, professional competence and due care, confidentiality, and professional behaviour, and the IESBA describes professional behaviour as including avoiding conduct that discredits the profession. A gift that a client later mentions in a dispute ("we always looked after your people") discredits the firm in exactly that way.
Trivial gifts, or a firm-wide ban
Firms tend to take one of two approaches. Some allow gifts and hospitality that are clearly trivial and require anything else to be declined or approved. Others ban gifts from clients altogether.
ACCA explains that ISQM 1 requires a firm's own ethical policies that go beyond the IESBA Code and local regulation to be captured by its system of quality management. It gives the example of firms or jurisdictions that prohibit accepting gifts, even of trivial value. The consequence is important. If the firm's policy is stricter than the Code, a staff member who breaks the firm's policy has caused a failure of the firm's quality management system, even where the Code itself was not breached.
So the firm's written policy, not the Code's minimum, is the standard staff are held to. Whatever it says, it must be clear enough to apply on the spot, in a client's boardroom, without phoning anyone. How firm policies relate to the Code is explored in firm ethics policies beyond the Code.
The third-party view
When an offer falls in a grey area, apply the IESBA Code's reasonable and informed third-party test: would a knowledgeable, objective outsider, aware of all the facts, conclude that compliance with the fundamental principles and with independence is maintained at an acceptable level?
Some facts that shift the answer:
- Timing. A gift during fieldwork, or just before the opinion is signed, looks very different from a desk calendar at the start of the year.
- Who receives it. A gift to the engagement partner weighs more than a tin of biscuits for the whole office.
- Frequency. One lunch is courtesy. A standing monthly lunch is a relationship.
- What the client wants at the time. A gift that arrives while the client is disputing an adjustment needs no further analysis.
Recording a gift against the client in Achekam
A declined gift is worth recording as much as an accepted one, because it shows the policy working. In Achekam, under Quality & Governance, then Independence & Conflicts, staff record annual independence declarations and any interest, relationship or gift involving a client. Anyone can check whether a person has an active independence exception for a client, which is worth doing before assigning them to an engagement.
A useful gift entry records who offered it, to whom, what it was and its nature and approximate value, when it was offered, whether it was accepted or declined, and who approved any acceptance. The annual declaration then summarises a register that already exists rather than testing anyone's memory. The declaration routine itself is covered in independence declarations today.
Breaches as quality incidents
When a staff member accepts something the policy forbids, treat it as what ISQM 1 says it is: a failure in the firm's system, not a private embarrassment to be smoothed over.
Achekam keeps the firm's quality registers, such as professional judgements, quality incidents, complaints and inspection progress, on the server with every version and the name of whoever changed it. Log the breach as a quality incident: what happened, how it came to light, what was done about the gift and the engagement, and what changed in training or policy afterwards. Over time the incident register shows whether the policy is actually understood, which is the question an inspector will ask.
A one-line policy staff can remember
Long policies are not read at the moment a client hands over a gift. Give staff a rule they can carry with them:
Decline anything you would be uncomfortable seeing listed in the client's file, and record every offer either way.
Then back it with the detail: what counts as trivial, if anything does; who may approve an exception; and how to decline gracefully without offending a good client. A short, kind refusal ("our firm's rules don't allow it, but thank you, it's a lovely thought") preserves the relationship and the independence.
ACCA's technical article on ISQM 1 explains the components of a firm's system of quality management, including how a firm's own ethics policies sit within it.
The aim is not suspicion of every kindness. It is a firm where every gift, accepted or declined, is visible, and where nobody ever has to wonder what a client thought it was buying.
General guidance only, not advice on your own circumstances. Tax and payroll rules change: check the current position with the authority or your adviser.
