By InvoiceShelf

InvoiceShelf

What it does

InvoiceShelf is an open-source invoicing app that a business installs on its own server. It follows work from an estimate through an invoice and a recorded customer payment, with expenses and reports alongside that billing record. The operator controls the installation and must also manage its setup and upkeep.

Last updated
Oct 19, 2026
InvoiceShelf · Editorial illustration
Conceptual editorial illustration of an estimate becoming an invoice and a recorded payment in a self-hosted ledger.

Work at InvoiceShelf?

Help customers find accurate information about your software.

Manage this listing →

Find your fit

Who it is for

It is a fit for a freelancer, small service firm or agency that wants estimate and invoice records together and is comfortable running a web app. A bookkeeper can see invoice status, payment entries and categorized expenses in one place, while a customer can receive a document by email or use an enabled portal to retrieve an invoice PDF.

Several companies can share one installation with separate branding, currency and tax settings. That is useful for an operator managing more than one business, but the business should pilot its own tax, currency and reporting needs before relying on the combined setup.

Back to sections

The work it supports

Core capabilities

Build an estimate with a customer, item lines, expiry date and notes, then send or mark it sent. InvoiceShelf tracks estimate states including viewed, expired, accepted and rejected. Converting an estimate to an invoice marks it accepted automatically, so check the commercial meaning of that status before using conversion as your approval record.

The invoice editor supports due dates, item lines, taxes, notes and discounts on individual items or the invoice total. The documented lifecycle runs from draft and sent through viewed, overdue and completed; use a sample invoice to check how your team moves between those states.

Record money received as a payment entry with date, customer and amount. The invoice link and payment mode are optional, and the features page describes partial as well as full payments. This is a recordkeeping workflow; it does not establish that the customer portal can collect an online card payment.

For regular billing, a recurring invoice can generate documents on a schedule with a count or end-date limit, and can be put on hold. Automatic generation depends on a running server scheduler, so test one harmless cycle and email delivery before using it for real retainers.

Enter an expense with category, date and amount, optionally attaching a receipt. Reports cover sales by customer or item, profit and loss, expenses and taxes. These figures depend on the completeness and categorization of entries, so reconcile a representative period against your accounting records.

A customer portal can show an invoice list, status and PDF download. The operator enables access and sets a password for each customer; test that invitation and sign-in flow with a sample customer before promising self-service access.

Invoices, estimates, payment receipts and statements can be sent through a configured mail transport. The server has default mail settings and a company can use its own configuration, so verify sender identity and delivery before relying on the app for customer notices.

Back to sections

Understand the offer

Pricing and getting started

The vendor currently presents the self-hosted product as free under AGPL-3.0, with no seat or SaaS subscription bill. That is software pricing, not a promise of zero operating cost: you still need a server, database setup, mail transport and someone to maintain the installation.

At research time the official download page labels 2.4.6 stable and 3.0.0-alpha.10 an early-access insider build. Use the stable channel for a production evaluation and recheck the release page before installing, since version labels can change.

Deployment choices include the official production Docker Compose examples with SQLite, MariaDB or PostgreSQL, and a manual ZIP installation route. Choose one path your team can back up and restore, and validate server and mail configuration before exposing customer data.

Back to sections

Look a little closer

Before you choose

Run a low-risk example from estimate to invoice to a manually recorded partial payment. Verify that conversion marks the estimate accepted, that the resulting balance and status make sense, and that your customer-facing document uses the intended taxes and discounts.

The homepage discusses online card checkout, while the official customer-portal guide says online payments are unsupported. Treat collection inside the portal as unresolved for your selected release; test the exact payment route or confirm it with the project before promising customers they can pay there.

For recurring work, test the server scheduler, the hold state and a real mail transport with a harmless internal recipient. For financial reporting, compare a small set of invoices, payments and expenses with known totals before migrating the full ledger.

Back to sections

12 distinct sources behind this profile. Research observed Oct 19, 2026. Features and offers can change.
View sources and research →

Help keep this profile useful

Spotted an outdated detail? Send the correction with a supporting source. A verified account is needed to submit.

Suggest a correction ↗