> ## 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.
# Request a service
> One-off regulator jobs — registrations, name changes, restorations — and how to raise and track them.
A **service request** is a one-off job with a regulator, as opposed to a recurring filing.
Registering a company. Clearing a name. Changing directors. Restoring a company from strike-off.
It works exactly like a filing — checklist, documents, fee, submission — but it happens once
rather than every period.
## What you can request
What appears in your catalogue depends on your entity type, which regulators you are connected to,
and your plan. A business name will not be offered company-only services; a business not connected
to ZRA will not be offered ZRA services.
| Regulator | Typical services |
| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **PACRA** | Name clearance, name reservation, company registration, business name registration, change of directors, change of registered address, share transfer, annual return catch-up, restoration from strike-off |
| **ZRA** | TPIN application, VAT registration, tax type additions, tax clearance certificate |
| **NAPSA** | Employer registration, employee registration |
| **NHIMA** | Employer registration |
## Raising a request
Go to the regulator, then **Service requests**.
Each service card explains what it is, why it matters, and what happens if you delay. Popular
services are shown first.
Check the expected turnaround and the fee. Some services have prerequisites — you cannot
register a company before its name has been cleared.
Each service asks for what it specifically needs. The form validates as you type, so an
incorrectly formatted TPIN or registration number is caught immediately rather than by the
regulator two weeks later.
Bumara creates the request, generates its checklist and document requirements, and calculates
the fee.
Exactly as for a filing. See [Working a task](/compliance/working-a-task).
## Services with a guided wizard
Some services are complex enough to have their own step-by-step wizard rather than a single form.
PACRA name clearance and company registration are the main examples.
A wizard typically runs:
1. **Details** — the information the regulator needs
2. **Checks** — live validation, such as checking a proposed name against the register
3. **Review** — a summary of everything entered, with the fee
4. **Submit** — creates the request and takes you to its detail page
You can leave a wizard part-way through and come back to it. Your progress is saved against the
request.
See [Name clearance](/regulators/pacra/name-clearance) and
[Company registration](/regulators/pacra/company-registration) for the detailed walkthroughs.
## The service request page
| Section | What is there |
| ------------- | ------------------------------------------------------------- |
| **Header** | What was requested, when, current status, expected completion |
| **Blockers** | What is stopping submission, or confirmation that nothing is |
| **Progress** | Tasks done out of total, documents provided out of required |
| **Tasks** | The checklist |
| **Details** | What you entered on the intake form |
| **Documents** | Required and supporting documents |
| **Payment** | The fee and its status |
| **Timeline** | Everything that has happened, with names and times |
| **Messages** | Tickets raised by the Bumara team about this request |
## Service request statuses
| Status | Meaning |
| -------------------------- | ---------------------------------------------------------- |
| **Pending data** | Created; the checklist has not been started |
| **In progress** | Work has begun |
| **Ready for submission** | Everything required is complete |
| **Awaiting payment** | The fee must be settled before it can go |
| **Submission in progress** | With the Bumara team |
| **Submitted** | Lodged with the regulator |
| **Accepted** | Approved. The certificate or confirmation is in your vault |
| **Needs correction** | The regulator wants something changed |
| **Waived** | No longer required |
| **Cancelled** | Withdrawn |
## Fees
Most service requests carry a fee made up of two parts:
| Part | What it covers |
| ----------------- | -------------------------------------------------------------- |
| **Regulator fee** | What the regulator itself charges — set by them, not by Bumara |
| **Handling fee** | Bumara's charge for preparing and lodging the submission |
Both are shown separately before you commit, so you always know what is going where. See
[Paying fees](/compliance/paying-fees).
## If a request is rejected
Regulators reject things. A name is already taken; a form is incomplete; a document is not
certified.
You are notified, and the reason is recorded on the request.
It is on the request page and in the timeline. Do not guess — regulator rejections are usually
precise.
Reopen the relevant task, correct the detail, replace the document.
The request goes back through the same route.
A rejection does not usually mean paying the regulator fee twice, but this depends on the
regulator and the reason. If a second fee applies, it is shown before you resubmit.
## Cancelling a request
You can cancel a request that has not yet been submitted. Once it is with the regulator it cannot
be pulled back through Bumara — raise a message on the request and the team will advise.
Fees already paid to a regulator are subject to that regulator's refund rules, which are generally
unforgiving.
## Requests created from your health check
If you completed a [compliance health check](/start/compliance-health-check), some of your service
requests will have been created from its recommendations rather than raised by you. They behave
identically, and carry a note showing which finding they came from.
Related: [Submitting to a regulator](/compliance/submitting-to-a-regulator) for what happens
after you press Request submission.