How medmatix/accounting-system works
Project type and purpose
• This is a desktop, open-source accounting system written in Python 3.7 with a Tkinter GUI and an SQLite3 backend.
• Its purpose is to let users enter general-journal transactions, post them to a general ledger, maintain a chart of accounts, annotate entries, and produce standard GAAP reports (balance sheet, trial balance, etc.).
File structure
Top-level modules and directories:
• OpenAccounting.py – the main entry point that launches the splash screen and main UI
• splash.py – splash screen logic
• AccountDB.py – database connection and CRUD operations (Model)
• FormDialogs.py – dialog-based forms for Journal, Chart, Memo entry (Controller)
• ReportPreps.py – report-generation routines (Controller)
• Tooltips.py – UI helper for tooltips
• README.md, LICENSE, OpenAccounting.db (the SQLite file), OpenAccounting.sql
• .sln, .pyproj, .vs folders – Visual Studio solution/project files (for packaging or Windows deployment)
• testcode.py – exploratory/test scripts
Key patterns visible:
– MVC modular separation (Model=AccountDB, View=Tkinter widgets in OpenAccounting.py and FormDialogs.py, Controller=FormDialogs + ReportPreps)
– SQLite schema defined in .sql and created by AccountDB at runtime
README for additional insights
• Emphasizes bottom-up, data-driven design centered on four core tables: chart, journal, ledger, accountmemos
• Lists all Python and 3rd-party imports (tkinter submodules, sqlite3, pytz, numpy, etc.)
• Describes the user flows: enter transactions in Journal → post to Ledger → generate reports; manage Chart of Accounts; annotate entries; perform maintenance
Final advice
• Be very detailed: break the UI layer into splash, main window, tabs, and dialogs
• Every module and its relationship to the database
• Don’t overthink: enumerate each .py file as a component in the View or Controller