> ## 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.

# Submitting to a regulator

> What happens when you request submission, what blocks it, and how to track a submission through to acceptance.

You do not file directly with the regulator from Bumara. You prepare the filing, then **request
submission**, and the Bumara compliance team lodges it on your behalf and returns the
acknowledgement to your account.

This is deliberate. Regulator portals are inconsistent, go down, change formats, and reject
submissions for reasons that are not obvious. Having a trained team handle the lodgement means a
rejection is dealt with by someone who has seen it before.

## Before you can submit

Three gates are checked at the moment you press the button:

<CardGroup cols={3}>
  <Card title="Tasks" icon="list-check">
    Every **required** task must be Done or Skipped. **No** task may be Blocked — including
    optional ones.
  </Card>

  <Card title="Documents" icon="paperclip">
    Every **required** document must be uploaded and attached to its requirement.
  </Card>

  <Card title="Payment" icon="credit-card">
    If a fee applies, it must be paid and verified. If no fee applies, this gate is skipped.
  </Card>
</CardGroup>

If any gate fails, nothing is submitted and Bumara lists exactly what is missing — the specific
tasks, the specific documents, the payment status. You are never left guessing.

## Requesting submission

<Steps>
  <Step title="Confirm the filing is ready">
    The panel at the top of the filing or service request shows **Ready for submission** in green.
    If it shows an orange list instead, work through what it names.
  </Step>

  <Step title="Review the figures one last time">
    This is the last point at which you can change anything easily. Read the numbers being filed.
  </Step>

  <Step title="Press Request submission">
    Bumara re-checks the three gates, takes a permanent snapshot of the readiness state at that
    moment, and creates a submission job.
  </Step>

  <Step title="The status changes">
    The filing moves to **Submission in progress** and the panel changes to "Our team is
    processing this".
  </Step>
</Steps>

<Note>
  Pressing the button twice does nothing harmful. If a submission is already in progress for that
  filing, Bumara returns the existing one rather than creating a duplicate.
</Note>

## The readiness snapshot

At the moment you request submission, Bumara records exactly what the state was: which tasks were
done, which documents were present, what the payment status was.

This snapshot is permanent and cannot be edited. It is what proves that the filing genuinely was
complete when it was submitted, even if records are changed afterwards.

## What happens next

<Steps>
  <Step title="Your request enters the queue">
    Submission jobs are queued by regulator. Urgent items — anything near a deadline, and anything
    ZRA-related — are prioritised.
  </Step>

  <Step title="A team member claims it">
    One person takes responsibility for your submission. This is recorded in your timeline.
  </Step>

  <Step title="They prepare and lodge it">
    Your figures and documents are transferred to the regulator's format and lodged through their
    portal or process.
  </Step>

  <Step title="The acknowledgement is recorded">
    The regulator's reference number and acknowledgement document are attached to your filing.
    Status moves to **Submitted**.
  </Step>

  <Step title="Acceptance is confirmed">
    Some regulators confirm immediately; others take days. When confirmation arrives, the filing
    reaches **Accepted** and you are notified.
  </Step>
</Steps>

## Tracking a submission

| Where to look             | What it tells you                             |
| ------------------------- | --------------------------------------------- |
| The filing's status badge | The current stage                             |
| The submission panel      | Plain-language status, and who is handling it |
| The timeline              | Every step with a timestamp and a name        |
| Notifications             | Alerts at each significant change             |
| The documents panel       | The acknowledgement, once it exists           |

## If something goes wrong

### The regulator rejects it

The filing returns as **Needs correction** with the reason recorded.

<Steps>
  <Step title="Read the reason on the filing">
    Regulator rejection reasons are usually specific. Read the actual text rather than assuming.
  </Step>

  <Step title="Reopen the affected task">
    Correct the figure, replace the document, fix the detail.
  </Step>

  <Step title="Let the filing return to ready">
    It goes back to In progress, then to Ready for submission when the checklist is complete again.
  </Step>

  <Step title="Request submission again">
    The same route. The team's notes from the first attempt travel with it.
  </Step>
</Steps>

### The team needs something from you

You receive a **ticket** — a structured request attached to that filing. Common types are a
document request, a clarification, or a correction. Reply in the messages panel on the filing.
See [Messages and timeline](/compliance/messages-and-timeline).

Until you reply, the submission is on hold. Tickets are the most common cause of a submission
sitting still.

### The deadline is very close

Bumara prioritises by deadline, but nothing can be filed after a regulator's cut-off. If you are
requesting submission on the due date, say so in a message on the filing so it can be escalated.

<Warning>
  Requesting submission on the last day is not a safe habit. Regulator portals are slowest and
  least reliable at deadline. Aim to be ready several days early — that is what the reminder
  settings are for.
</Warning>

## After acceptance

Once a filing reaches **Accepted**:

* The acknowledgement is in your document vault, attached to the filing.
* The filing's documents are locked and cannot be changed.
* The next period's filing is created with its own due date.
* The filing stays permanently in your records as evidence of compliance.

## What is not checked at submission

For clarity, two things are **not** treated as blockers at the point of requesting submission:

* **Authorised representative** — an expired or missing authorisation does not stop you requesting
  submission, but it will stop the team lodging with regulators that require one. Keep it current.
* **Onward payment to the regulator** — where Bumara pays a fee onward on your behalf, that
  happens as part of processing, not as a gate on your request.

<Note>
  Related: [Paying fees](/compliance/paying-fees) and
  [Authorised representative](/compliance/authorised-representative).
</Note>