Software & Backend / Data science
Private local-first finance application combining double-entry accounting, reviewable document imports, payment planning and encrypted backup support.
Original code-generated category illustration; not a product screenshot.
Private codebase; this page shares a general technical summary. Source files, real records and organization-specific information remain private.
Finansım brings accounts, cards, payment plans and document imports into a local application. Its double-entry ledger prioritizes consistency, while import previews keep users in control of suggested records. This overview describes the application and data-integrity approach without sharing personal financial information, banking documents or private source code.
Tracking transactions and payment plans across separate tools makes duplicate records and inconsistent categorization harder to detect. Importing extracted document data without review can turn extraction mistakes into permanent accounting errors. The project explores a local workspace that preserves user oversight while applying explicit record-integrity rules.
Local application development, focusing on accounting rules, document-import workflows and testable data management.
A local web interface brings account tracking, planning and document imports over a shared persistence layer. Monetary amounts use integer minor units. Balanced ledger entries, reversals and period locks support consistent records. PDF, CSV and spreadsheet imports produce reviewable suggestions. Backup handling uses integrity checks and a separate restore destination, with encryption available for configured backup archives.
I treated document import as a reviewable workflow rather than immediately turning every extracted row into a final ledger entry. The user checks the transaction, account and classification before proceeding. This places a control point between PDF extraction and accounting. The separation matters when working with different document layouts, repeated imports and incorrect matches: extracting text and accepting a financial record are different operations.
Amounts are stored in integer minor units to limit rounding differences associated with floating-point arithmetic. Balanced transaction lines form the core rule of the double-entry approach. Reversals handle corrections without silently rewriting history, making the relationship between an original entry and its correction traceable. Period locks and audit records support the same focus on data integrity.
Running locally does not automatically encrypt the application files. I considered encrypted backups separately from the live SQLite database: backup protection, restore targets and integrity validation are distinct responsibilities. Checking a restore at a separate destination protects existing records. Access control and disk security on the device remain relevant for the live database and imported documents.
Local browser interface for accounts and payment planning
Application rules for accounting and reviewable document imports
SQLite persistence with coordinated transaction and audit records
Backup workflow with integrity checks and a separate restore target
Conceptual flow derived from project descriptions; not an application screenshot.
A Streamlit prototype combining Turkish tender PDF extraction, AI-assisted risk review, retrieval-based questions, comparison and reporting components.
A desktop document-preparation tool arranging front/back badge PDFs into A4 Word documents with previews, ordering and configurable printing layout settings.