1. Connecting to MongoDB (Crucial for Full Functionality)

For persistent storage, narration group rules, settings, and syncing across sessions, connect to a MongoDB database.

• Locate the "Data Management & MongoDB" section on the Home page.
• Enter your MongoDB connection URI.
• Click "Save URI & Fetch". This saves the URI and loads data, settings, and group rules.
• Transactions: TagMyTransaction collection.
• App Settings (N value, app name): app_settings collection.
• Narration Group Rules (incl. visibility): narration_group_rules collection.

2. Importing CSV Transactions

Import transaction data from a CSV file. Tags are not imported from CSV and are applied via group rules or manually.

• In "Data Management", click "Import CSV". New, unique transactions will be added. Existing data and N-value are preserved.

3. Narration Grouping & Auto-Tagging Rules (Debit/Credit Specific, Visibility Control)

Define rules to automatically apply a Tag and/or Parent Tag to transactions based on the initial characters of their narration. You can set different tags for DEBIT and CREDIT transactions that share the same narration prefix. Rules can also be hidden.

• Use the "Group by first N characters" slider to set how many characters of the narration form a prefix for grouping. Confirm changes. This setting is saved to MongoDB.
• Use the "Filter Narration Groups" dropdown to view groups based on their rule status (All, Visible, Hidden, Tagged Rules, Untagged Rules).
• In the "Narration Grouping & Auto-Tagging" accordion:
  • Each item shows a narration prefix (e.g., "upi-payment-"). A icon indicates a hidden rule.
  • Within each prefix, you'll find sections for "Tagging Rule for Debits" and "Tagging Rule for Credits".
  • Enter a "Primary Tag" and/or "Parent Tag" for debits, and separately for credits, that match this prefix. Suggestions for existing tags appear as you type.
  • Click "Save Rule Tags" to store these tag definitions in MongoDB. This rule will then auto-apply these tags to transactions matching the prefix and transaction type (debit/credit), unless the rule is hidden.
  • Click / "Hide Rule" / "Unhide Rule" to toggle the rule's visibility. Hidden rules are not auto-applied but their tag definitions are preserved. This action saves to MongoDB. This button is only active if a rule for the prefix already exists in the DB.
  • Click "Clear Rule from DB" to remove the rule (tags and visibility status) for this prefix from the database.
  • You can expand a "Show Transactions in this Group" foldout to see which transactions are affected by the current prefix, with options to filter by debit/credit.
• Auto-Tagging: When transactions are loaded or rules/N-value change, the app attempts to apply tags from VISIBLE group rules.
• Manual Override: If you manually edit a transaction's tags (see next section), those manual tags take precedence and won't be overwritten by group rules. Such transactions are visually indicated in the table by a blueish background and a icon.

4. Manual Tagging (Overrides Group Rules)

Manually set or change the Tag and Parent Tag for individual transactions. This marks the transaction as "manually tagged".

• In the main "Transactions" table, click the icon on any transaction row.
• A dialog opens to edit "Primary Tag" and "Parent/Category Tag". Suggestions appear as you type from existing tags in your dataset.
• Saving here sets the isManuallyTagged flag to true, so group rules won't affect this transaction's tags anymore.
• Transactions with manually set tags have a blueish background highlight in the table and a status icon.

5. Filtering Transactions

• Use the "Filter Transactions" card to filter by:
  • Primary Tag (multi-select dropdown with checkboxes)
  • Parent Tag (multi-select dropdown with checkboxes)
  • Transaction Type (All, Debit, Credit)
  • Min Amount / Max Amount
  • Date Range (Start and End dates)
• Click "Clear All Filters" to reset all transaction filters.
• Sort by clicking column headers (Date, Narration, Debit, Credit, Balance, Tag, Parent Tag).
• Use "Show Untagged Only" to view transactions where both `Tag` and `Parent Tag` are empty.
• Status icons indicate data source (DB/File), modification, and manual tag override.
• Pagination controls help navigate large datasets.

6. Tag Manager Page

Navigate to the Tag Manager page for a read-only overview of all unique tag values used as "Primary Tag" or "Parent Tag", and their financial impact. Tags are listed separately based on their role.

7. Importing/Exporting JSON Data

Save and load your dataset (including tags and `isManuallyTagged` status) using JSON.

• "Export JSON" saves current transactions.
• "Import JSON" loads them. See the JSON Format page for details on transaction and MongoDB collection structures.

8. Theme Customization

• Toggle Light/Dark mode (/ icon).
• Change accent color ( icon). Preferences saved in browser.