Python Finance Statement Builder and Tally Integration
Budget: ₹75,000 – ₹150,000 INR
Job Title
Python Desktop Application – Financial Statement Builder (ICAI & Schedule III) + License Key Protection + Tally Integration
Project Description
I am looking for an experienced Python desktop application developer with strong knowledge of financial reporting to build a Financial Statement Builder.
The application should generate both:
Non-Corporate Financials – as per ICAI guidelines (Firms, LLPs, Proprietorships).
Corporate Financials – as per Schedule III, Companies Act, 2013 (Division I/II/III).
Additionally, the application must support:
Tally Integration to auto-fetch Trial Balance and ledgers.
Manual Import of Trial Balance for non-Tally users (Excel/CSV).
Auto-Mapping of ledgers to Schedule III and ICAI heads (including sub-schedules), with a review/override screen.
Core Features
Trial Balance Importer
Tally Auto-Fetch: Connect to Tally (ERP 9/Prime) via ODBC/XML-HTTP to pull Trial Balance, Ledger Masters, and Groups for a selected company and period.
Non-Tally Import: Excel/CSV import wizard with column mapper and validation (debit=credit, missing accounts, duplicates).
Mapping Manager
Rule-based and AI-assisted Auto-Mapping to Schedule III/ICAI heads and sub-schedules.
Uses name patterns, group hierarchy, and past user confirmations to improve accuracy.
Review grid with confidence score, one-click approve, and bulk reclassify; persistent mapping dictionary per client.
Adjusting Entries Module
Journal entries (reversals, provisions, depreciation), period lock, and full audit log.
Automated Statements
Balance Sheet, Profit & Loss, Cash Flow (Indirect), Notes to Accounts (Receivables ageing, Payables ageing, PPE roll-forward, Equity, Borrowings, Contingencies).
Switch Mode: Generate Corporate (Schedule III) or Non-Corporate (ICAI) formats.
Audit Trail / Linkage
End-to-end traceability from TB → mapping → statement line → note/schedule. Difference checks and ties (Assets = Equity+Liabilities; PL→Reserves bridge; CF reconciliation).
Export Options
Excel and PDF packs with professional formatting, page setup, and sign blocks.
License Key System
Hardware-locked keys (Windows Machine ID), offline RSA-signed license file, optional online activation/revocation, and an admin tool to generate/manage keys.
Technical Details (Required)
Tally Connectivity: Implement using Tally ODBC and/or XML over HTTP (default port 9000), with company selection and date range. Handle multi-company, multi-FY, and exchange rate cases.
Auto-Mapping Engine:
Deterministic rules: keyword patterns, Tally group lineage, sign, and usage (e.g., balances vs turnovers).
Fuzzy matching for unknown ledgers; maintain client-specific mapping dictionary that learns from user approvals.
Sub-schedule assignment (e.g., Current Assets → Trade Receivables → Ageing buckets).
Confidence scoring and exception queue for unclassified items.
Validation: TB debits=credits; mapping completeness; rounding and materiality thresholds; unit tests for mapping and cash flow math.
Tech Stack (Recommended)
Frontend/UI: PySide6 (Qt) or Tkinter
Data Processing: pandas, numpy
Storage: SQLite with SQLAlchemy
Exports: openpyxl/xlsxwriter (Excel), Jinja2 + WeasyPrint/ReportLab (PDF)
Packaging: PyInstaller (single EXE), Inno Setup (installer)
Licensing: RSA-signed license files, hardware ID check
Tally Integration: ODBC and/or XML-HTTP requests
Deliverables
Windows desktop application (.exe installer) with Tally auto-fetch and non-Tally import wizard.
Auto-mapping engine (rules + fuzzy), review UI, and persistent mapping dictionary.
Statements (BS/PL/CF) and Notes with Schedule III/ICAI switch, sub-schedules, and audit trail.
License management system (admin tool + user activation flow).
Source code with documentation and tests; user guide and training material.
Initial configuration templates for Schedule III and ICAI charting (groups/sub-groups) to jump-start mapping.
Ideal Candidate
Strong Python desktop app development experience
Prior work on finance/accounting applications
Hands-on with Tally integration (ODBC/XML)
Familiarity with Indian reporting (ICAI & Schedule III)
Experience with software licensing and application security
Timeline & Budget
Preferred Timeline: 3–6 weeks
Budget: Open (based on expertise and proposal quality)
What to Include in Your Proposal
Examples of similar work (desktop apps, Tally integrations, financial tools)
Your approach for: Tally auto-fetch, non-Tally import wizard, and auto-mapping logic
Implementation plan with milestones and test strategy
Rough timeline and cost estimate
Python Desktop Application – Financial Statement Builder (ICAI & Schedule III) + License Key Protection + Tally Integration
Project Description
I am looking for an experienced Python desktop application developer with strong knowledge of financial reporting to build a Financial Statement Builder.
The application should generate both:
Non-Corporate Financials – as per ICAI guidelines (Firms, LLPs, Proprietorships).
Corporate Financials – as per Schedule III, Companies Act, 2013 (Division I/II/III).
Additionally, the application must support:
Tally Integration to auto-fetch Trial Balance and ledgers.
Manual Import of Trial Balance for non-Tally users (Excel/CSV).
Auto-Mapping of ledgers to Schedule III and ICAI heads (including sub-schedules), with a review/override screen.
Core Features
Trial Balance Importer
Tally Auto-Fetch: Connect to Tally (ERP 9/Prime) via ODBC/XML-HTTP to pull Trial Balance, Ledger Masters, and Groups for a selected company and period.
Non-Tally Import: Excel/CSV import wizard with column mapper and validation (debit=credit, missing accounts, duplicates).
Mapping Manager
Rule-based and AI-assisted Auto-Mapping to Schedule III/ICAI heads and sub-schedules.
Uses name patterns, group hierarchy, and past user confirmations to improve accuracy.
Review grid with confidence score, one-click approve, and bulk reclassify; persistent mapping dictionary per client.
Adjusting Entries Module
Journal entries (reversals, provisions, depreciation), period lock, and full audit log.
Automated Statements
Balance Sheet, Profit & Loss, Cash Flow (Indirect), Notes to Accounts (Receivables ageing, Payables ageing, PPE roll-forward, Equity, Borrowings, Contingencies).
Switch Mode: Generate Corporate (Schedule III) or Non-Corporate (ICAI) formats.
Audit Trail / Linkage
End-to-end traceability from TB → mapping → statement line → note/schedule. Difference checks and ties (Assets = Equity+Liabilities; PL→Reserves bridge; CF reconciliation).
Export Options
Excel and PDF packs with professional formatting, page setup, and sign blocks.
License Key System
Hardware-locked keys (Windows Machine ID), offline RSA-signed license file, optional online activation/revocation, and an admin tool to generate/manage keys.
Technical Details (Required)
Tally Connectivity: Implement using Tally ODBC and/or XML over HTTP (default port 9000), with company selection and date range. Handle multi-company, multi-FY, and exchange rate cases.
Auto-Mapping Engine:
Deterministic rules: keyword patterns, Tally group lineage, sign, and usage (e.g., balances vs turnovers).
Fuzzy matching for unknown ledgers; maintain client-specific mapping dictionary that learns from user approvals.
Sub-schedule assignment (e.g., Current Assets → Trade Receivables → Ageing buckets).
Confidence scoring and exception queue for unclassified items.
Validation: TB debits=credits; mapping completeness; rounding and materiality thresholds; unit tests for mapping and cash flow math.
Tech Stack (Recommended)
Frontend/UI: PySide6 (Qt) or Tkinter
Data Processing: pandas, numpy
Storage: SQLite with SQLAlchemy
Exports: openpyxl/xlsxwriter (Excel), Jinja2 + WeasyPrint/ReportLab (PDF)
Packaging: PyInstaller (single EXE), Inno Setup (installer)
Licensing: RSA-signed license files, hardware ID check
Tally Integration: ODBC and/or XML-HTTP requests
Deliverables
Windows desktop application (.exe installer) with Tally auto-fetch and non-Tally import wizard.
Auto-mapping engine (rules + fuzzy), review UI, and persistent mapping dictionary.
Statements (BS/PL/CF) and Notes with Schedule III/ICAI switch, sub-schedules, and audit trail.
License management system (admin tool + user activation flow).
Source code with documentation and tests; user guide and training material.
Initial configuration templates for Schedule III and ICAI charting (groups/sub-groups) to jump-start mapping.
Ideal Candidate
Strong Python desktop app development experience
Prior work on finance/accounting applications
Hands-on with Tally integration (ODBC/XML)
Familiarity with Indian reporting (ICAI & Schedule III)
Experience with software licensing and application security
Timeline & Budget
Preferred Timeline: 3–6 weeks
Budget: Open (based on expertise and proposal quality)
What to Include in Your Proposal
Examples of similar work (desktop apps, Tally integrations, financial tools)
Your approach for: Tally auto-fetch, non-Tally import wizard, and auto-mapping logic
Implementation plan with milestones and test strategy
Rough timeline and cost estimate