
Travento
Internal Django travel-accounting app covering 10+ workflows: firms, clients, passengers, ledger entries, period locks, audit recovery, and reports.
- Type
- Web app
- Domain
- Travel accounts
- Project
- Internal build
Highlights
- Firm, client, passenger, and debit/credit transaction modules
- Entry locking, restore/delete flows, audit history, and verification
- Daily activity, interest, profit/loss, user work, and travel calendar reports
Project screenshots
Scroll
01
02
03Engineering narrative
From problem to outcome, in eight focused steps.
Business Problem
Travel businesses need to manage passenger details, client ledgers, debit/credit entries, reports, and accounting periods without relying on disconnected spreadsheets.
Project Understanding
Travento was scoped around the actual accounting flow: create firms and clients, attach passenger records, post debit or credit entries, lock closed periods, and generate reports without breaking ledger accuracy.
Solution
Travento brings travel ledger operations into one browser interface with authentication, permission-based menus, transaction verification, ledgers, email/print flows, and reports.
Technology Stack
Python and Django power the application, MySQL stores ledger records, and Bootstrap, jQuery, and DataTables support the interface.
Development Process
The build is split into authentication, ledger, report, templates, static assets, media uploads, and Django settings so each workflow remains maintainable.
Key Features
Custom users, firms, clients, passenger documents, debit/credit entries, locks, audit history, restore/delete flows, ledgers, reports, admin support, and local email output.
Outcome
This internal web app brings 10+ travel-accounting workflows into one Django system, including ledger posting, passenger records, period locking, and reporting. It is positioned as a self-built operations tool rather than a client deployment, and the screenshots show the dashboard, ledger, and report views already working.
Lessons Learned
Closing-period controls cannot be added as an afterthought in accounting software; the data model and permission layer need to treat entry locks, restore flows, and audit history as first-class features from day one.
























