The Django Ledger Project is led and maintained by Miguel Sanda aiming to provide an open source financial engine to power financially driven applications using Python and the Django Framework. Unfortunately due to its complexity we cannot offer a stable release until all features on the Roadmap has been implemented.
Finance and Accounting is a complicated subject. Django Ledger is different from other Django projects as it aims to provide a developer-friendly accounting engine while providing a reliable and extensible API. This project in particular, not only requires Python AND Django programming experience, but also finance and accounting experience.
Due to time limitations, the developer is focusing on the development of new features.
This project can greatly benefit from contributions towards Documentation and Unit Tests.
Django Ledger supports:
- Chart of Accounts.
- Financial Statements (Income Statement & Balance Sheets).
- Automatic financial ratio & insight calculations.
- Multi tenancy (multiple users/clients).
- Hierarchical entity management (for consolidated financial statements - v0.9).
- Self-contained Ledgers, Journal Entries & Transactions.
- Basic OFX & QFX file import.
- Bills & Invoices with optional accruable functionality.
- Basic navigational templates.
- Entity administration & entity manager support.
- Items, lists & inventory management.
- Bank Accounts.
WARNING: Currently this project is under active development, it is not stable and is not recommended for production environments. Due to its high complexity, breaking changes may occur in future releases and migration backwards compatibility may not be preserved until the first stable release. The author is actively working to provide a stable release as soon as possible and to incorporate the following functionality:
- 0.4.0: Items, resources and & lists for bills & invoices itemization:
- 0.4.0: Enhance and optimize Django Ledger the random data generation functionality to properly populate relevant random data for testing.
- 0.4.1: Entity internal organizations, department, branches, etc.
- 0.4.2: Custom Accounting Periods.
- 0.4.3: Purchase Order Model implementation.
- Bugfixes & UI/UX Enhancements.
More details available in the Django Ledger v0.5 Page.
- 0.5.0: Inventory tracking.
- Average Cost.
- 0.5.1: Customer estimates & contract tracking.
- Link Estimate/PO/Bill/Invoice workflow.
- Journal Entry (or trial balance) import.
- 0.5.2: Cash flow statement.
- 0.5.3: Closing entries, snapshots & trial balance import.
- 0.5.4: Testing framework implementation that will include:
- Unit tests using the Built-in Django unit test modules.
- Behavioral Driven Testing using the behave library.
- Need help!!!! If you want to contribute PLEASE ADD UNIT TESTS!!!
- Start creating basic package documentation via Sphinx
- Document code and functions within code base.
- Generate HTML documentation.
- Work with Accountants, Subject Experts and Developers to define an initial list of Unit Tests to validate output ( help needed!).
- Update package and code documentation.
- Bugfixes & UI/UX Enhancements.
- Credit Line Models.
- Time tracking.
- Transaction tagging.
- Update package and code documentation.
- Bugfixes & UI/UX Enhancements.
- Currency Models implementation as a way to define EntityModel default currency.
- Produce financial statements in different currencies.
- Update package and code documentation.
- Bugfixes & UI/UX Enhancements.
- User roles and permissions on views to support read/write permissions for assigned managers to entities.
- Customer jobs & job tracking.
- Client proposals & estimates.
- User preferences and settings & account creation views.
- Update package and code documentation.
- Enable Hierarchical Entity structures via MPTT.
- Consolidated financial statements.
- Intercompany transactions.
- Update package and code documentation.
- Complete Internationalization of all user-related fields.
*** Roadmap subject to change based on user feedback and backlog priorities.
This project is actively looking for contributors. Any financial and/or accounting experience is a big plus. If you have prior accounting experience and want to contribute, don't hesitate to contact me. See contribution guidelines.
- GraphQL API - See details here.
Django Ledger comes with a default CoA ready to use or you could use your own. Make sure to select the appropriate option when creating new entities.
- Install Django Ledger
pip install git+https://github.com/arrobalytics/django-ledger.gitTo install Django Virtual Environment
pip install pipenv
- Or with pipenv:
pipenv install git+https://github.com/arrobalytics/django-ledger.git- Add django_ledger to INSTALLED_APPS
INSTALLED_APPS = [
...,
'django_ledger',
...,
]- Add URLs to your project:
from django.urls import include, path
urlpatterns = [
...,
path('ledger/', include('django_ledger.urls', namespace='django_ledger')),
...,
]Django Ledger comes with a basic development environment already configured under dev_env/ folder not to be used for production environments. If you want to contribute to the project perform the following steps:
- Navigate to your projects directory.
- Clone the repo from github and CD into project.
git clone https://github.com/arrobalytics/django-ledger.git && cd django-ledger- Install PipEnv, if not already installed:
pip install -U pipenv- Create virtual environment.
pipenv installIf using a specific version of Python you may specify the path.
pipenv install --python PATH_TO_INTERPRETER- Activate environment.
pipenv shell- Apply migrations.
python manage.py migrate- Create a Development Django user.
python manage.py createsuperuser- Run development server.
python manage.py runserverAfter setting up your development environment you may run tests.
python manage.py test django_ledger
