> ## 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. # Automatic Reporting > Use the Rules page to create and manage reporting rules. Rules setup ## Overview Automatic reporting lets you save recurring reporting checks as rules. If your team reviews the same reporting scenarios often, you can publish a rule once and manage it from the **Rules** page instead of repeating the setup each time. Rules are created from a guided setup page. You choose a reporting body, choose a supported report type, select one or more predefined rule instructions, and publish the rule. This makes automatic reporting useful for repeatable compliance scenarios where your team wants consistent handling instead of rebuilding the same reporting logic each time. ## Before you start * Set up your reporting agents and entities in **Reporting → Preferences** * Decide which report type you want to configure * Check the default currency before publishing * Make sure the rule instructions you want are available for the selected report type Automatic reporting works best when your team already understands which filing scenarios should recur often enough to justify a saved rule. ## Create a rule 1. Go to **Reporting → Rules** 2. Click **Create new rule** 3. Choose the **Reporting body** 4. Choose the **Report type** 5. Select the rule instructions that match what you want to monitor 6. Review the default currency shown for the rule 7. Use **Change default currency** if needed 8. Click **Publish rule** Sigma names the rule automatically from the reporting body and report type, then adds it to your rules list. This setup is intentionally guided. Instead of defining raw field logic from scratch, you select from the available rule instructions presented for the chosen report type. ### What you choose during setup The rule setup asks for: * **Reporting body** * **Report type** * One or more **rule instructions** from the predefined list * **Default currency** for the transactions the rule should evaluate Each rule instruction appears as a selectable checklist item. You can publish a rule only after selecting at least one instruction. These instructions let your team work from approved reporting scenarios while keeping setup simple and consistent. ### Supported rule types Rule creation is available for **NFIU** reporting with: * **Currency Transaction Report (CTR)** * **Funds Transfer Report (FTR)** Other reporting-body tabs may appear on the Rules page, but new-rule setup supports the NFIU CTR and FTR flows. ### Default currency The rule setup page shows the currency the rule applies to. If the currency is not correct: 1. Click **Change default currency** 2. Select the correct currency 3. Save the change This setting helps keep transaction validation and rule matching consistent. ### Publish the rule When everything is set, click **Publish rule** and confirm the action. Once published, the rule is added to your rules list. From there, the rule becomes part of your ongoing rule management workflow. ## Manage rules From the Rules page, you can review your rules and manage them as needed. * Review the rule name, type, creator, status, and date created * Pause or resume a rule * Delete a rule * Open **Logs** to see rule activity * Use **Create case** when a rule needs escalation or investigation The Rules page groups rules by reporting body and gives you quick actions from the menu on each row. ### Rule lifecycle * **Active** rules are in use * **Paused** rules remain saved but are temporarily disabled * **Inactive** rules are effectively removed from active use after deletion This lets your team keep a rule available without fully removing it whenever you need to temporarily stop it. ### Logs and case management The **Logs** action helps you inspect activity tied to a rule. Use **Create case** when a rule result needs a more formal investigation or case workflow outside the rule list itself. This separation is useful because not every rule event should immediately become a report or enforcement action. Sometimes it first needs analyst review. ## How automatic reporting fits into the workflow In practice, automatic reporting supports the front end of the workflow: 1. Your team publishes a rule for a recurring scenario 2. The rule remains available on the Rules page for ongoing management 3. Teams use logs and case creation to monitor and investigate rule outcomes 4. Reporting operations remain connected to the broader report review process ## Tips * Start with a small number of rules and expand gradually * Keep the default currency aligned with the transactions you expect to review * Review logs regularly to confirm the rule is behaving as expected * Revisit your selected instructions when reporting expectations change