Quote it, bill it, chase it, record it. On the same customer record as the deal it came from, with no per-invoice fee and no second subscription.
Unlimited invoices and unlimited users. MIT licensed, self-host it anywhere.
Set the cadence once. A task runs at midnight, finds what is due and raises it, with the line items already filled in.
Four steps, and the CRM does three of them for you.
Build the document from line items: quantity, unit price, per-line tax, discount as a percentage or a flat amount. Start from a blank estimate or from a deal, and turn a won deal into an invoice in one click. Every total is recomputed on the server on each save.
Email it to the customer. They get a link to a public page that needs no login, with your own template and your own terms on it. Once a document leaves Draft its lines and amounts are fixed, so the figures they saw are the figures you keep; the status, payments, notes and dates stay editable.
Reminders go out on a schedule you set, before the due date and after it. Overdue invoices are marked automatically each morning.
When the money arrives, record the payment against the invoice. Several partial payments can sit against one document, and the balance follows.
This page used to say Stripe was built in. It is not, it never was, and that is the most important thing on this page.
There is no Stripe integration, no PayPal, no Razorpay, and no gateway webhook. The app has never had one, and the public invoice page deliberately does not draw a "Pay now" button.
Bank transfer, card terminal, a payment link from your own processor, a cheque. Your payment terms appear on the public invoice page alongside the reference and the amount due.
A person enters the payment against the invoice: amount, date, method and reference. Partial payments stack, and the balance updates.
You lose one-click checkout. You keep an invoicing system with no per-invoice fee, no processor cut on top of your existing one, and no third party holding your customer list.
The same line-item model powers customer-facing estimates, one-off invoices and recurring schedules. Write an estimate from scratch or start it from a deal, convert an accepted estimate to an invoice in a single transaction, or turn a won deal straight into a draft invoice.
A tax rate per line for mixed jurisdictions, a document-level tax rate and discount, and shipping on an invoice. Every tax rate is held between 0 and 100 and shipping cannot be negative. The client never sends a total: the server derives subtotal, tax, discount and grand total on save. Both the web and the phone forms set the discount, tax and shipping.
Every estimate and invoice gets a tokenised URL. Customers open it, read it, and accept an estimate if they want to. No account, no password.
Weekly, monthly, quarterly, yearly or every so many days. A background task runs at midnight and generates the invoices that are due, inheriting the line items from the schedule. Auto-send needs at least one line, so nobody is mailed a blank invoice.
The invoice renders from an HTML template you edit per organisation: logo, colours, headings, footer terms. The default covers standard B2B layouts.
An accounts-receivable aging report showing what is owed and how long it has been owed, plus revenue reporting and a products catalogue behind the line items.
The invoice model, the recurring task and the public page are all in the open repository.
No. This is the honest answer and an earlier version of this page gave a dishonest one, so it is worth being blunt: BottleCRM has no payment processor. The public invoice page shows your terms, the reference and the amount due, and the customer pays you by whatever route you already use. When the money lands, someone records it against the invoice. If online checkout is a requirement for you, this is the feature to weigh before you adopt.
Any ISO-4217 currency code, set per document, so a customer in another market gets an invoice in their own currency. Tax is a single rate per line, which covers mixed rates across a document. Compound or stacked tax, where one tax is charged on top of another, is not supported.
A scheduled background task runs once a day at midnight, finds the schedules that are due and generates their invoices. Each one inherits the line items, the account and the contact from the schedule, and sends itself if you turned auto-send on. Auto-send needs at least one line on the schedule, so a customer is never emailed a blank invoice. Two other tasks run daily alongside it: one marks invoices overdue, another expires estimates past their date.
No. A deal that reaches a won stage has a Create invoice action on its page, on the web or the phone, which makes a draft invoice with the deal's line items, account, contact and currency already filled in, due in thirty days. Tax is left for you to set before you send it. Estimates can be started from a deal the same way, or written from a blank page when there is no deal behind them.
Yes. Invoices render from an HTML template you can edit per organisation, covering the logo, colours, headings and footer terms, and the same template drives the PDF. The default handles standard B2B layouts, and a fully custom template can be swapped in.
Unlimited documents, unlimited customers, on your own database. Host it yourself, or let MicroPyramid run it.
