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

# Getting Started

> Set up Sigma's reporting system for regulatory compliance with NFIU, CBN, and EFCC.

<Card title="Quick Setup:" img="https://mintcdn.com/pastelafrica/WpP9Ug8qrORoId-I/images/reporting/configuration.png?fit=max&auto=format&n=WpP9Ug8qrORoId-I&q=85&s=7975d6fe3aaa630341ab8d90f9354b91" width="2310" height="1321" data-path="images/reporting/configuration.png">
  Reporting configuration dashboard
</Card>

## Before You Begin

Regulatory reports filed through Sigma must identify:

* The **Reporting Entity** (your organisation)
* The **Reporting Agent** (authorised individual)

Both must be configured before generating any report.

This is a **one-time setup**. Once configured, you can reuse your saved entities and agents when creating new reports.

Think of these as your filing profiles. The reporting entity identifies the
institution submitting the report, while the reporting agent identifies the
person authorised to file on behalf of that institution.

***

## Initial Setup

Set up the following before generating reports:

### 1. Reporting Entity

A **Reporting Entity** is your organisation's regulatory profile. It stores the institution details that appear on reports created in Sigma.

1. Navigate to **Reporting → Preferences**
2. Switch to **Entities** tab
3. Click **Add New Entity**
4. Provide:
   * **Reporting entity ID**
   * **Reporting entity branch**
   * **Entity reference**
   * **Local currency code**
   * **Address type**
   * **Address**
   * **City**
   * **Country**
5. Save and optionally set as default

Use a separate entity when different branches file independently or use different regulatory identifiers.

### Entity field breakdown

| Field                        | What it is used for                                         |
| ---------------------------- | ----------------------------------------------------------- |
| **Reporting entity ID**      | Your institution's regulatory or reporting identifier       |
| **Reporting entity branch**  | The branch or reporting location associated with the filing |
| **Entity reference**         | An internal or regulatory reference used for identification |
| **Local currency code**      | The primary currency code used for the reporting entity     |
| **Address type**             | The type of address being stored for the entity             |
| **Address / City / Country** | The entity's location details used in the reporting profile |

<Note>
  If your institution has multiple branches that file independently, create a
  separate entity for each branch.
</Note>

***

### 2. Reporting Agent

A **Reporting Agent** is the person authorised to submit reports on behalf of your institution. In most teams, this is your compliance officer or MLRO.

1. Navigate to **Reporting → Preferences**
2. Switch to **Agents** tab
3. Click **Add New Agent**
4. Provide:
   * **First name** and **last name**
   * **Email**
   * **Date of birth**
   * **Gender**
   * **Passport number** or **ID number**
   * **Nationality**
   * **Occupation**
   * **Comment**
5. Save and optionally set as default

### Agent field breakdown

| Field                           | What it is used for                                |
| ------------------------------- | -------------------------------------------------- |
| **First name / Last name**      | The reporting officer's identity                   |
| **Email**                       | Contact address tied to the reporting officer      |
| **Date of birth**               | Identity detail used in the agent profile          |
| **Gender**                      | Agent profile detail used in the reporting profile |
| **Passport number / ID number** | Identity reference for the reporting officer       |
| **Nationality**                 | Country of nationality for the agent               |
| **Occupation**                  | The officer's role or profession                   |
| **Comment**                     | Extra internal context where needed                |

<Tip>
  The reporting agent is typically your compliance officer or MLRO. Sigma's
  agent form is designed around that role.
</Tip>

***

### 3. Optional: Manual API connection

If you want Sigma to retrieve transaction details from your server, configure the **Manual API Connection** in Preferences.

1. Go to **Reporting → Preferences → General**
2. Open **API connection settings**
3. Enter your:
   * **Endpoint URL**
   * **HTTP Method** (`GET`)
   * **Authorization** type (`None`, `Bearer Token`, or `Basic Auth`)
   * Optional **Headers**
4. Use **Test connection** with a sample transaction ID
5. Save the connection once the test succeeds

This connection is used for the **Retrieve from your server** flow and for any CSV enhancement flow that depends on your saved API settings.

### Why this connection matters

If your team keeps the full transaction payload in an internal system, this
connection allows Sigma to fetch that data during manual report creation instead
of requiring you to upload the full transaction detail in every case.

***

## What Happens After Setup

Once at least one entity and agent are configured, you can:

* Generate reports
* Manage reporting rules
* Reuse your default entity and agent during report creation
* Create a new entity or agent directly from the report page if needed

You can also maintain multiple entities and agents and choose the right
combination for each filing, which is useful for teams supporting multiple
branches, subsidiaries, or reporting officers.

***

## Report Generation Methods

<CardGroup cols={2}>
  <Card title="Manual Reporting" icon="pencil" href="manual-reporting">
    Create reports by selecting transactions, uploading CSV files, or retrieving
    transaction details from your own server.
  </Card>

  <Card title="Automatic Reporting" icon="robot" href="automatic-reporting">
    Save recurring reporting checks as rules and manage them from the Rules
    page.
  </Card>
</CardGroup>