No description
Find a file
padreug 33c294de7f Removes parent-only accounts
Removes parent accounts from the database to simplify account management.

Since the application exports to Beancount and doesn't directly interface with it, parent accounts for organizational hierarchy aren't necessary. The hierarchy is implicitly derived from the colon-separated account names.

This change cleans the database and prevents accidental postings to parent accounts. Specifically removes "Assets:Bitcoin" and "Equity" accounts.
2025-11-07 23:24:11 +01:00
core Completes core logic refactoring (Phase 3) 2025-10-23 02:45:50 +02:00
docs add dev docs 2025-11-04 01:19:30 +01:00
static Enables user selection for permissions 2025-11-07 23:06:24 +01:00
templates/castle Enables user selection for permissions 2025-11-07 23:06:24 +01:00
.gitignore initial commit 2025-10-22 12:33:45 +02:00
__init__.py Adds task cleanup on extension shutdown 2025-11-02 01:41:34 +01:00
account_utils.py Removes parent-only accounts 2025-11-07 23:24:11 +01:00
CLAUDE.md Adds CLAUDE.md to guide Claude Code 2025-11-01 23:22:25 +01:00
config.json initial commit 2025-10-22 12:33:45 +02:00
crud.py Auto-creates equity account for eligible users 2025-11-07 22:37:45 +01:00
description.md initial commit 2025-10-22 12:33:45 +02:00
manifest.json initial commit 2025-10-22 12:33:45 +02:00
migrations.py Removes parent-only accounts 2025-11-07 23:24:11 +01:00
models.py Clarifies equity account name generation 2025-11-07 22:37:45 +01:00
README.md initial commit 2025-10-22 12:33:45 +02:00
services.py Adds per-user wallet configuration 2025-10-22 14:54:25 +02:00
tasks.py Adds fiat currency metadata to payments 2025-11-02 02:52:41 +01:00
views.py Adds admin permissions management page 2025-11-07 18:05:30 +01:00
views_api.py Refactors Castle user retrieval 2025-11-07 23:06:37 +01:00

Castle Accounting Extension for LNbits

A full-featured double-entry accounting system for collective projects, integrated with LNbits Lightning payments.

Overview

Castle Accounting enables collectives like co-living spaces, makerspaces, and community projects to:

  • Track expenses and revenue with proper accounting
  • Manage individual member balances
  • Record contributions as equity or reimbursable expenses
  • Track accounts receivable (what members owe)
  • Generate Lightning invoices for settlements

Installation

This extension is designed to be installed in the lnbits/extensions/ directory.

cd lnbits/extensions/
# Copy or clone the castle directory here

Enable the extension through the LNbits admin interface or by adding it to your configuration.

Usage

For Members

  1. Add an Expense: Record money you spent on behalf of the collective

    • Choose "Liability" if you want reimbursement
    • Choose "Equity" if it's a contribution
  2. View Your Balance: See if the Castle owes you money or vice versa

  3. Pay Outstanding Balance: Generate a Lightning invoice to settle what you owe

For Admins

  1. Create Accounts Receivable: Record when someone owes the collective money

  2. Record Revenue: Track income received by the collective

  3. View All Transactions: See complete accounting history

  4. Make Payments: Record payments to members

Architecture

Data Models

  • Account: Individual accounts in the chart of accounts
  • JournalEntry: Transaction header with description and date
  • EntryLine: Individual debit/credit lines (always balanced)

Account Types

  • Assets: Things the Castle owns (Cash, Bank, Accounts Receivable)
  • Liabilities: What the Castle owes (Accounts Payable to members)
  • Equity: Member contributions and retained earnings
  • Revenue: Income streams
  • Expenses: Operating costs

Database Schema

The extension creates three tables:

  • castle.accounts - Chart of accounts
  • castle.journal_entries - Transaction headers
  • castle.entry_lines - Debit/credit lines

API Reference

See description.md for full API documentation.

Development

To modify this extension:

  1. Edit models in models.py
  2. Add database migrations in migrations.py
  3. Implement business logic in crud.py
  4. Create API endpoints in views_api.py
  5. Update UI in templates/castle/index.html

Contributing

Contributions welcome! Please ensure:

  • Journal entries always balance
  • User permissions are properly checked
  • Database transactions are atomic

License

MIT License - feel free to use and modify for your collective!