Global Advice Network | Borgergade 111 | DK - 1300 Copenhagen K
E-Mail: info@business-anti-corruption.org | Phone: (+45) 60 88 10 44

A practical anti-corruption policy for employees in the field

How to write an anti-corruption policy that is practical for employees in the field, not just legal jargon comes down to whether employees can make a sound decision when it matters. A policy packed with definitions may look rigorous while leaving a sales representative unsure whether a meal is permitted or what to do when a supplier offers cash. A better document turns risk into observable actions: pause, check, record and escalate.

That matters in Australia, where field staff may move between a Sydney office, a Melbourne warehouse and a regional site near Brisbane, often using phones, email and messaging apps to secure approvals. The policy should fit this environment and acknowledge that many transactions are already digital, from contactless payments and mobile banking to electronic invoices. Clear rules reduce confusion without treating every awkward request as criminal conduct.

Begin with the work employees actually do

Start with tasks, not abstract exposure. Ask managers to identify where employees handle cash or cash equivalents, influence purchasing, meet government or state officials, engage agents, award contracts, or submit claims for money paid to third parties. A regional construction supervisor and a procurement officer in Melbourne may have different duties, but both need a route for handling an unusual request.

Convert that inventory into a short risk profile based on country, sector and relationship. Prioritise activities with high value, little transparency or a government connection, including permits, customs, licensing and tenders. Include lower-risk office work only where necessary. A useful policy states which activities require pre-approval, which are prohibited and where employees can obtain help. Broad statements about “high-risk areas” are too abstract for someone standing in a car park with a contractor.

Turn legal duties into plain workplace rules

Australia’s legal setting needs careful translation. There is no single general anti-bribery statute covering every private-sector payment. The Criminal Code Act 1999 (Cth) deals with bribery of foreign public officials and misleading conduct involving foreign officials, while the Corporations Act 2001 (Cth) imposes governance and record-keeping obligations on companies. State and territory integrity laws also affect dealings with public agencies.

Do not reproduce those laws without context. Instead, state company rules that prevent employees from causing or concealing improper payments: no unauthorised benefit, no misleading records, no payment for an improper purpose and prompt reporting of conflicting instructions. Explain that a payment may be legal yet unacceptable under company policy, while misconduct can also involve fraud, conflicts of interest or breach of contract. State that violations may lead to refusal of the transaction, contract termination, disciplinary action or reporting where required.

Set clear rules for gifts, hospitality and payments

Gifts and hospitality need thresholds employees can apply. Say what counts, including meals, travel, event tickets, merchandise, donations and gift cards; name who must approve; set value and frequency limits; and require a record. Avoid relying on the phrase “modest hospitality,” because different employees interpret it differently. A $60 meal may be routine, while a $60 cash payment or repeated gifts to one person create a different risk.

Prohibit the categories most likely to undermine trust: cash and cash equivalents, undeclared personal benefits, luxury or travel paid without a genuine business purpose, charitable donations made at another party’s request, and facilitation payments intended to speed up a routine action. Local custom never turns a bribe into a legitimate fee. Where payment is genuinely required for a lawful service, require proof of entitlement, an invoice and approval from an authorised manager.

Use a decision test that works in plain English. Employees should ask whether the benefit has a genuine business purpose, whether it could influence a decision, whether it meets the stated limit and whether it can be disclosed and recorded. If any answer is unclear, they should not offer it and should seek approval first. Written examples make the test more reliable than a long list of exceptions.

Make third-party due diligence routine

Third-party due diligence should be proportionate and documented. Agents, brokers, contractors, suppliers and joint-venture partners can channel improper value even when the company makes no direct payment. This is particularly important for Australian small and medium-sized businesses that rely on franchise networks, consultants and subcontractors. Before engagement, identify the entity and its directors, check ownership and sanctions exposure, understand government connections, verify capability and references, and confirm that each payment matches the contracted service.

Focus on facts that change the risk rather than nationality alone. Warning signs include an unusually large success fee, refusal to provide invoices, a request to pay an unrelated or overseas account, vague deliverables, recent ownership changes, or pressure to bypass a tender. Contracts should state scope, fees, records and audit rights. After onboarding, retain evidence, review performance and refresh checks when ownership, banking details, scope or risk changes.

Give employees tools they can use on the job

Field usefulness depends on brevity and visible steps. A policy supported by checklists, examples and approval records will outperform a long document that employees rarely consult. The tools should be available through the company intranet, a mobile-friendly intranet application and the manager’s usual communication channels.

A one-page checklist should include:

  • The activities requiring prior approval, expressed as clear job actions.
  • Gift and hospitality limits, exclusions and authorised approvers.
  • The information employees must record about a payment or benefit.
  • Reporting channels for concerns, conflicts and unusual requests.

A field decision sequence can be:

  • Pause the transaction or benefit until the requirement is confirmed.
  • Check the policy, approval limits and documented business purpose.
  • Record the request, decision, supporting documents and final payment details.
  • Escalate uncertainty, pressure or conflicting instructions promptly.

Deliver training through short, realistic scenarios involving a supplier, customer or public official. Employees should practise deciding what to record and whom to contact, rather than memorising legal definitions. Accessibility matters too: materials should use plain English, accommodate different roles and remain usable by remote crews and shift workers. Additional implementation advice is available through the portal’s compliance support service.

Handle reports, investigations and audit findings

Provide several reporting routes, including a manager, a compliance officer, a confidential hotline and a web form. Explain what happens after a report, whether anonymity is available and how confidentiality will be protected. A strong policy prohibits retaliation against anyone who raises a concern in good faith or participates in an investigation. Sensitive matters should be capable of being raised outside the employee’s direct reporting line.

An investigation is not an excuse for an uncontrolled internal inquiry. Assign an independent or suitably qualified investigator, preserve relevant documents and electronic messages, restrict information to those with a legitimate need to know, and give the person subject to the allegation a fair opportunity to respond. Employment contracts, workplace policies, privacy obligations and Fair Work requirements may affect the process. The policy should promise a consistent procedure rather than absolute secrecy.

When an audit reveals a control gap, teams can use corrective action planning to assign an owner, deadline, action and evidence of completion, rather than changing the policy and assuming the weakness has been solved. The audit should test whether employees understand the rules, whether approvals happen before value is provided, and whether third-party payments match actual services.

Keep the policy current, useful and supported

Review the policy at least annually and after a significant incident, legal change, new market, acquisition or change in business model. Owners should be named for each section, with a clear process for proposing amendments. Oversight should consider overdue due diligence, unusual payment routes, gift-register exceptions, training completion and the time taken to escalate concerns. A fall in the number of reports may reflect trust, but it may also indicate that employees do not know where to report.

For organisations seeking a formal management framework, the portal’s ISO 37001 implementation guide outlines the policy, controls, training, monitoring and review cycle. Certification can demonstrate structure, but it cannot replace judgement, leadership or the quality of day-to-day decisions.

A practical policy ultimately gives employees permission to pause, authority to ask questions, a process for recording decisions and reassurance that speaking up will not trigger retaliation. The standard is simple: a procurement supervisor in Melbourne and a sales representative in regional Australia should be able to explain what to stop, what to document and where to seek help without first consulting a lawyer.

copyright © Global Advice Network