Manual Reporting

Manual Reporting:

Manual report generation with API integration

Overview

Manual reporting allows you to create compliance reports by uploading CSV files or selecting transactions from Transaction Monitoring. You can generate reports for specific transactions without setting up automated rules, making it ideal for ad-hoc reporting needs.

Prerequisites

Before you begin with manual reporting, ensure you have:

Active Sigma Account: A registered and verified Sigma account with reporting permissions
Business Profile Setup: Your business profile must be configured with:
- Valid business information and regulatory licenses
- Compliance officer details and contact information
- Regulatory reporting requirements for your jurisdiction
Reporting Configuration: Set up your reporting entities and agents in Reporting → Preferences

Two Methods Available: You can create manual reports by uploading CSV files or by selecting transactions from Transaction Monitoring (if enabled).

Report Creation Methods

Method 1: Upload CSV File

Navigate to Reports: Go to Reporting → All Reports
Create New Report: Click Create New Rule → NFIU Report → Manual Transaction Report (CTR, FTR, STR) → Upload CSV
Choose Report Type: Select CTR, FTR, or STR based on your requirements
Upload Transaction Data: Upload your CSV file with transaction details
Configure Report: Set filing name, reporting agent, and entity
Review and Generate: Verify details and create the report

Method 2: Select from Transaction Monitoring

Navigate to Reports: Go to Reporting → All Reports
Create New Report: Click Create New Rule → NFIU Report → Manual Transaction Report (CTR, FTR, STR) → Select Transactions
Choose Transactions: Select specific transactions from your Transaction Monitoring data
Configure Report: Set filing name, reporting agent, and entity
Review and Generate: Verify details and create the report

Method 3: Create SAR Report

Navigate to Reports: Go to Reporting → All Reports
Create SAR Report: Click Create New Rule → NFIU Report → Suspicious Activity Report (SAR)
Enter Activity Details: Provide suspicious activity information and parties involved
Configure Report: Set filing name, reporting agent, and entity
Review and Generate: Verify details and create the report

Data Format Requirements

CSV Upload Format

For bulk transaction uploads, use this CSV structure:

transactionNumber,transactionDate,transactionMode,type,amount,narration,senderCountry,senderFundsCode,senderInstitution,senderAccount,receiverCountry,receiverFundsCode,receiverInstitution,receiverAccount
TXN-001,2025-01-15T14:30:00.000Z,C,TRANS,5750000,personal,NG,K,Access Bank Plc,012345,NG,K,Bank PHB Plc,067890

Field Descriptions:

transactionMode: A (In-branch), B (ATM), C (Electronic), O (Other)
type: DEPS (Deposit), WTHD (Withdrawal), TRANS (Transfer)
fundsCode: K (Cash), C (Currency exchange), E (Bank draft), etc.

Optional: API Integration for CSV Data Enrichment

If you’re uploading CSV files and want Sigma to automatically fetch additional transaction details from your system, you can configure API integration:

Setup API Connection

Navigate to Configuration: Go to Reporting → Preferences
Configure API Connection: Set up your endpoint details:
- Base URL: Your API endpoint base URL
- Authentication: Bearer token or API key
- Headers: Additional headers if required

API Response Format

When Sigma processes your CSV, it will call your API to get detailed transaction information:

// Sigma will call your endpoint like this:
GET https://api.example.com/transactions?transactionId=12345,67890,54321

// Your API should respond with:
{
  "data": [
    {
      "transactionNumber": "TXN-001",
      "transactionDate": "2025-01-15T14:30:00.000Z",
      "transactionMode": "Electronic transaction",
      "type": "TRANS",
      "amount": 5750000,
      "narration": "Business transfer",
      "sender": {
        "country": "NG",
        "fundsCode": "cash",
        "account": {
          "institutionName": "Access Bank Plc",
          "institutionCode": 21222,
          "accountNumber": "0123456789"
        }
      },
      "receiver": {
        "country": "NG", 
        "fundsCode": "cash",
        "account": {
          "institutionName": "Bank PHB Plc",
          "institutionCode": 129393,
          "accountNumber": "0987654321"
        }
      }
    }
  ]
}

Data Format Requirements

Transaction Data Structure

{
  "transactionNumber": "string",
  "transactionDate": "ISO 8601 datetime",
  "transactionMode": "string", // A (In-branch), B (ATM), C (Electronic), O (Other)
  "type": "string", // DEPS (Deposit), WTHD (Withdrawal), TRANS (Transfer)
  "amount": "number",
  "narration": "string",
  "senderCountry": "string", // ISO country code
  "senderFundsCode": "string", // K (Cash), C (Currency exchange), E (Bank draft)
  "senderInstitution": "string",
  "senderAccount": "string",
  "receiverCountry": "string",
  "receiverFundsCode": "string",
  "receiverInstitution": "string",
  "receiverAccount": "string"
}

Authentication

API Key Setup

Navigate to Account → API & Webhooks in your Sigma dashboard
Click Generate New API Key
Select Reporting Permissions
Copy and securely store your API key

Request Headers

Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

Best Practices

Data Accuracy: Ensure all transaction data is accurate and complete before submission. Incorrect data can lead to regulatory compliance issues.

Batch Processing: Use batch submission for multiple transactions to improve efficiency and maintain data consistency.

Validate Data: Always validate transaction data before creating reports
Document Process: Maintain detailed records of manual reporting activities
Regular Backups: Keep backups of transaction data and generated reports
Access Control: Limit manual reporting access to authorized personnel only
Audit Trail: Maintain complete audit trails for all manual reporting activities

Error Handling

Common Error Codes

400 Bad Request: Invalid request format or missing required fields
401 Unauthorized: Invalid or missing API key
403 Forbidden: Insufficient permissions
422 Unprocessable Entity: Validation errors in submitted data

Error Response Format

{
  "status": "error",
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "Invalid transaction data",
    "details": [
      {
        "field": "amount",
        "message": "Amount must be a positive number"
      }
    ]
  }
}

Testing

Use the staging environment for testing:

BASE_URL=https://api-staging.sigma.pastel.africa

Start with Test Data: Always begin with test or sample data to familiarize yourself with the manual reporting process before processing live transactions.

Get Started

Products

Account