> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bumara.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Authorised representative

> Naming someone to act for your business with a regulator, and keeping that authorisation valid.

Some regulators — PACRA in particular — require a named person authorised to act on behalf of your
business. Without a valid authorisation, Bumara cannot lodge submissions with that regulator for you.

## Who it should be

Someone with the standing to bind the business:

* A director
* The company secretary
* The owner, for a business name or sole trader
* A partner, for a partnership

It should be someone reachable. If the regulator queries a submission, they will contact this
person.

## Setting one up

<Steps>
  <Step title="Open the regulator workspace">
    Go to the regulator, then **Authorisation**.
  </Step>

  <Step title="Enter the representative's details">
    Full name as it appears on their identification, their role at your business, email address
    and phone number.
  </Step>

  <Step title="Upload the letter of authority">
    A signed letter on your letterhead authorising that person to act for the business with that
    regulator. Some regulators have their own prescribed form — the page tells you if so.
  </Step>

  <Step title="Set the validity period">
    A start date and an end date. Keep the period sensible — a year is common. An open-ended
    authorisation is harder to control if the person leaves.
  </Step>

  <Step title="Save and wait for approval">
    The authorisation is created as **Pending** and reviewed. Once approved it becomes active.
  </Step>
</Steps>

## Authorisation statuses

| Status       | Meaning                  | Can Bumara submit? |
| ------------ | ------------------------ | ------------------ |
| **Pending**  | Created, awaiting review | No                 |
| **Approved** | Active and valid         | Yes                |
| **Expired**  | Past its end date        | No                 |
| **Revoked**  | Cancelled by you         | No                 |

## Keeping it valid

Bumara warns you before an authorisation expires. Renew it before the date, not after — an expired
authorisation discovered on a deadline day is a bad afternoon.

<Warning>
  If your authorised representative leaves the business, replace the authorisation immediately.
  Removing someone from your Bumara team does **not** revoke their regulator authorisation — these
  are separate things. A regulator acting on a letter naming someone who has left is a problem you
  do not want.
</Warning>

## Changing your representative

<Steps>
  <Step title="Revoke the existing authorisation">
    Open it and choose **Revoke**. It stops being valid immediately.
  </Step>

  <Step title="Create a new one">
    Enter the new person's details and upload a new letter of authority naming them.
  </Step>

  <Step title="Check for in-flight submissions">
    Anything already with the Bumara team may need to wait for the new authorisation to be
    approved. Raise a message on the affected filing if a deadline is close.
  </Step>
</Steps>

## Which regulators require it

| Regulator | Authorisation required                               |
| --------- | ---------------------------------------------------- |
| **PACRA** | Yes — for most filings and services                  |
| **ZRA**   | Varies by service; your workspace tells you          |
| **NAPSA** | Generally handled through your employer registration |
| **NHIMA** | Generally handled through your employer registration |

Where a regulator does not require one, the Authorisation page still exists but is optional.

## What it does not do

An authorisation is about the **regulator**, not about Bumara. It does not:

* Give that person any additional access inside Bumara — that is controlled by their
  [role](/account/team-and-roles)
* Allow them to approve payments or run payroll
* Replace the need for proper director resolutions where the regulator requires those separately

## If a submission is blocked by authorisation

You can still request submission with a missing or expired authorisation — that gate is not
checked at request time. The block happens later, when the team goes to lodge with the regulator,
and you receive a message telling you so.

This costs days. Check your authorisation status at the start of any period where you expect to
file, rather than discovering the problem mid-submission.

<Note>
  Related: [Submitting to a regulator](/compliance/submitting-to-a-regulator) and
  [Team and roles](/account/team-and-roles).
</Note>