@ -16,7 +16,7 @@ OTB Billing is a contractor-focused billing system designed to be:
- deployable on fresh Linux systems
- deployable on fresh Linux systems
- suitable for managed hosting or client-installed deployments
- suitable for managed hosting or client-installed deployments
The system is being built as a practical alternative to overly restrictive SaaS billing tools, with emphasis on ownership, simplicity, and contractor workflow.
The system is being built as a practical alternative to restrictive SaaS billing tools, with emphasis on ownership, simplicity, portability, and contractor/operator workflow.
Tagline direction:
Tagline direction:
@ -86,7 +86,6 @@ This remains a core project rule.
- invoice lock after payment activity
- invoice lock after payment activity
- invoice statuses
- invoice statuses
- invoice email sending with PDF attachment
- invoice email sending with PDF attachment
- latest invoice email activity display
Current invoice statuses:
Current invoice statuses:
- draft
- draft
@ -122,7 +121,7 @@ Current payment statuses:
- PDF invoice generation
- PDF invoice generation
- client details on invoice
- client details on invoice
- status badge on invoice
- status badge on invoice
- totals, paid, remaining display
- totals / paid / remaining display
- branding/logo support on HTML and PDF
- branding/logo support on HTML and PDF
## Exports
## Exports
@ -131,7 +130,7 @@ Current payment statuses:
- payments CSV export
- payments CSV export
- filtered invoice CSV export
- filtered invoice CSV export
- filtered invoice PDF ZIP export
- filtered invoice PDF ZIP export
- monthly/quarterly/yearly accounting package ZIP export
- accounting package ZIP export
- revenue report JSON export
- revenue report JSON export
## Batch / Print
## Batch / Print
@ -185,6 +184,11 @@ app_settings
- SSL flag
- SSL flag
- report delivery email
- report delivery email
## Email Delivery
- invoice email with PDF attachment
- revenue report JSON email
- accounting package email
## Email Logging
## Email Logging
Stored in:
Stored in:
email_log
email_log
@ -216,7 +220,6 @@ Confirmed working:
- invoice view
- invoice view
- invoice PDF generation
- invoice PDF generation
- invoice email with PDF attachment
- invoice email with PDF attachment
- invoice email log display
- payment entry
- payment entry
- payment overpayment prevention
- payment overpayment prevention
- payment reversal / void
- payment reversal / void
@ -233,6 +236,7 @@ Confirmed working:
- revenue report email
- revenue report email
- accounting package ZIP export
- accounting package ZIP export
- accounting package email
- accounting package email
- email audit logging
---
---
@ -251,14 +255,14 @@ This file must remain complete so installer-driven deployment works in one shot.
# Business / Product Direction
# Business / Product Direction
This system is intended to grow into a deployable billing product for small contractors and related service businesses.
This system is intended to grow into a deployable billing product for small operators, hosting providers, and service businesses.
Target strengths versus typical SaaS billing tools:
Target strengths versus typical SaaS billing tools:
- simpler workflow
- simpler workflow
- data ownership
- data ownership
- exportability
- exportability
- portability
- portability
- contractor-first design
- operator-first design
- no hostage-style software design
- no hostage-style software design
Long-term success goal:
Long-term success goal:
@ -286,7 +290,7 @@ build something users are happy to use and proud to own.
- client portal
- client portal
- role-based access
- role-based access
- accountant/export workflows
- accountant/export workflows
- job-tracking integration with related contractor platform modules
- integration paths for vertical forks such as HVAC/customer-service variants
---
---
@ -324,23 +328,3 @@ python3 backend/app.py
During active development, run in a visible terminal so logs stay visible.
During active development, run in a visible terminal so logs stay visible.
Do not rely on hidden/background launch during normal debug workflow.
Do not rely on hidden/background launch during normal debug workflow.