> For the complete documentation index, see [llms.txt](https://documentation.opencrvs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencrvs.org/v1.6/setup/4.-functional-configuration/4.2-configure-registration-periods-and-fees.md).

# 5.2 Configure registration periods and fees

### Before you start

* Only a National System Admin can configure application settings
* You can make changes to the registration rates and fees whenever you like
* Refer to our [Intro to Farajaland](/v1.6/default-configuration/intro-to-farajaland.md) configuration for recommendation on what the registration periods and fees should be. 

![](https://content.gitbook.com/content/YTKQAa9NKqMdS5tq1TB3/blobs/qaNqp3qMOXhONn4vt3Zi/app-config-birth.png)

### Steps

1. **Set the legally specified registration time period**\
   Click change and enter the number of days legally specified in law for when a birth must be registered. <br>
2. **Set the delayed registration time period**\
   Click change and enter the number of days deemed a delayed registration. \
   Note: The late registration time period is automatically calculated based on the legally specified and delayed registration time periods. <br>
3. **Set the registration fees**\
   Click change and enter the fee for a registration within legally specified, late and delayed. This amount will be requested as part of printing a certificate and contributes to the total fees collected metric in Performance. <br>
4. **Complete the same steps for death**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.opencrvs.org/v1.6/setup/4.-functional-configuration/4.2-configure-registration-periods-and-fees.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.