balaa System Requirements Document

Introduction

The purpose of this document is to outline the system requirements for the project "balaa," which aims to provide an affordable and efficient solution for Chartered Accountants (CAs) to match GSTR-2A/2B with purchase books, thereby saving significant manual effort and time.

System Overview

balaa is designed to address the needs of Chartered Accountants by offering a tool that automates the matching of GSTR-2A/2B with purchase books. This project targets CAs who require a cost-effective solution to streamline their workflow, reducing dependency on expensive enterprise tools. The system will incorporate API integration to further automate the GST ITC matching process.

Functional Requirements as Story Points

• As a Chartered Accountant, I should be able to match GSTR-2A/2B with purchase books to save time on manual Excel work.
• As a Chartered Accountant, I should be able to use API integration to automate the GST ITC matching process.
• As a Chartered Accountant, I should be able to perform fuzzy name matching to improve the accuracy of vendor matching.
• As a Chartered Accountant, I should be able to follow up with vendors via WhatsApp for unmatched entries.
• As a Chartered Accountant, I should be able to access metrics to evaluate the performance of the matching process.
• As a Chartered Accountant, I should be able to expand the tool to include TDS synchronization in the future.

User Personas

• Chartered Accountant: Primary user who needs to match GSTR-2A/2B with purchase books efficiently.
• Vendor: Secondary user who may receive follow-up communications regarding unmatched entries.

Core User Flows

1. Chartered Accountant logs into the system.
2. Uploads GSTR-2A/2B and purchase book files.
3. Initiates the matching process.
4. System performs fuzzy name matching and highlights discrepancies.
5. Chartered Accountant reviews results and uses API integration for automation.
6. Sends follow-up messages to vendors for unmatched entries via WhatsApp.
7. Reviews metrics to assess the process efficiency.

Visuals Colors and Theme

• primary: #1A73E8 (Deep Blue)
• primary_light: #E8F0FE (Light Blue)
• secondary: #FF6F61 (Coral)
• accent: #FFD700 (Gold)
• highlight: #FFA500 (Orange)
• bg: #FFFFFF (White)
• surface: rgba(240, 240, 240, 0.8)
• text: #333333 (Dark Gray)
• text_muted: #777777 (Light Gray)
• border: rgba(200, 200, 200, 0.5)

Signature Design Concept

Interactive Workflow Animation: The homepage will feature an animated workflow where documents representing GSTR-2A/2B and purchase books flow into a central processing hub. As they enter, the system visually matches them, highlighting discrepancies with animated markers. Users can interact by clicking on discrepancies to view details or initiate vendor follow-ups. This animation will be built using motion/react for smooth transitions and interactions.

LANDING HERO MOTION BRIEF

The landing hero will depict a dynamic illustration of documents flowing into a central hub, transforming through the matching process. The animation will loop every 10 seconds, showing documents being matched, discrepancies highlighted, and resolved. Users can hover over elements to pause the animation and click to explore details. The animation will be responsive, adjusting to different screen sizes while maintaining clarity and engagement.

Interaction Model & Motion Direction

• Interaction Model: Animated
• The landing page will feature moderate scroll-triggered reveals and hover transitions to enhance user engagement. Interactive elements will have spring physics for a polished experience.

Non-Functional Requirements

• The system should handle up to 350,000 users efficiently.
• The matching algorithm must maintain high accuracy and reliability.
• The system should be scalable to accommodate future expansions like TDS synchronization.

Tech Stack

• Frontend: React for Web
• Backend: Python, FastAPI
• Database: MySQL or MariaDB
• AI Models: GPT 5.4 for user-friendly responses
• AI Tools: Litellm for LLM Routing
• Local Orchestration: Docker, docker-compose
• Server-side Orchestration: Kubernetes

Assumptions and Constraints

• The system assumes users have basic knowledge of GST and purchase book reconciliation.
• The system will operate primarily in the Indian market, adhering to local GST regulations.
• Budget constraints limit the infrastructure cost to ₹2,000 per month.

Glossary

• GSTR-2A/2B: GST return forms used for matching input tax credit.
• ITC: Input Tax Credit, a mechanism to reduce tax liability.
• TDS: Tax Deducted at Source, a means of collecting tax at the source of income.
• CA: Chartered Accountant, a professional who provides financial advice and audit services.