All projects
Web AppLive2025–2026

Web-Based Accounting System

Production-style accounting engine with GAAP-minded double-entry.

Web-Based Accounting System preview
Domain
ERP · Accounting · SMB operations
Category
Web App
Stack focus
Python · Flask · SQLAlchemy
Links
Live site · GitHub

Overview

Accounting Pro is a robust web accounting system designed to mirror high-end ERP capabilities in a streamlined dark-themed interface. It enforces double-entry discipline so journal entries cannot save unless debits and credits balance within a strict tolerance.

The product covers the full operational lifecycle: chart of accounts, accounts payable/receivable, tax mapping, FIFO inventory layers, payroll, fixed asset depreciation, and multi-currency translation into a base currency for a clean trial balance.

It ships with role-based access (Admin, Accountant, Viewer), invitation-only onboarding, rate-limited auth, audit logging, and a live demo deployment for hands-on evaluation.

Key features

  • Mathematically enforced double-entry journal entries
  • Chart of accounts, invoices, bills, customers, and vendors
  • FIFO / moving-average inventory valuation
  • Payroll, fixed assets, and depreciation workflows
  • Tax groups, cost centers, stock, and warehouses
  • Multi-currency invoices mapped into base currency
  • RBAC: Admin, Accountant, Viewer
  • Invitation-only onboarding with JWT email invites
  • Audit service logging create / update / delete mutations
  • Live demo deployment on Render

Real-world usage

Where this kind of system shows up outside a portfolio context.

  • Small businesses needing structured books without enterprise ERP cost
  • Accountants managing AP/AR, payroll, and inventory in one system
  • Startups validating multi-currency and inventory costing rules
  • Teaching double-entry, trial balance, and year-end close mechanics

Challenges

  • Keeping every posting balanced while supporting complex documents
  • Implementing true FIFO cost layers that survive partial withdrawals
  • Hardening auth, invites, and rate limits for a multi-user system

What I learned

  • Accounting rules are product requirements, not optional polish
  • RBAC and audit logs are essential once more than one role exists
  • Multi-currency forces careful separation of document currency vs base currency

Related projects

More work in a similar space or stack.

Want something like this built?

I'm open to internships, collaborations, and product work across backend, AI/ML, and full-stack apps.