Invoicing Software For Small Businesses
PlusInvoice gives your business one organised place for the people you invoice, the things you sell, and the documents you issue — with totals the server calculates and settings you configure once.
No payment details are requested. PlusInvoice does not process payments.
Verified Accounts
Registration confirms the email address before the workspace opens.
Separate Workspaces
Each business keeps its own customers, catalogue, and documents.
Decimal-Safe Totals
Amounts are calculated on the server in fixed precision, never a float.
Planned work is listed so the boundary is clear before you sign up. No dates are promised.
Your drafts, your issued invoices, and the customers behind them, on one screen. Status is written out in words, never signalled by colour alone.
Drafts In Progress
3
Not yet issued
Issued This Month
11
Numbered and locked
Active Customers
24
Across one business
| Number | Customer | Issued | Total | Status |
|---|---|---|---|---|
| INV-00024 | Apex Design Studio | — | 1,240.00 USD | Draft |
| INV-00023 | Northwind Fabrication | 12 Mar | 3,875.50 USD | Issued |
| INV-00022 | Bluepoint Consulting | 09 Mar | 640.00 USD | Sent |
| INV-00021 | Harbourline Logistics | 04 Mar | 2,110.25 USD | Sent |
| INV-00020 | Meridian Print Works | 01 Mar | 489.90 USD | Issued |
These are the kinds of business PlusInvoice is being built for. They are intended audiences, not a list of customers.
An invoice is a record a business stands behind. These are the guarantees the product is organised around.
Amounts are held and calculated in fixed decimal precision and recalculated on the server. Nothing money-related passes through a floating-point number, so a total never drifts by a hundredth.
Customers, catalogue items, settings, and documents belong to a business. Every request is checked against your membership of that business before any record is returned.
Tax rates, units, payment terms, number formats, and document defaults are set in business settings and then applied as you work, instead of being retyped on every document.
Issuing an invoice locks its number and its snapshot of the customer. Later corrections are recorded as further steps in the lifecycle, never as a quiet rewrite of what was already sent.
Five areas, each doing one job. Where a module is still being built, it says so.
Build an invoice from your catalogue and your customer record, then move it through a lifecycle that does not go backwards quietly.
The people you invoice, kept as records rather than as text retyped onto each document.
One catalogue for everything you sell, so a line item starts from a known price rather than from memory.
Configuration that flows into every document you create, changed in one place.
Access decided by the server on every request, not by which buttons the interface happens to render.
Three steps from an empty account to a document you can stand behind.
Register with your email address and confirm it from the verification message. Verification happens before the workspace opens, so an account is always attached to a reachable address.
Add your business profile, addresses, tax rates, formatting preferences, document defaults, bank details, and branding. These become the starting point for everything you create afterwards.
Add the customers you invoice and the products and services you sell, then draft an invoice from them. Lines, tax, and totals are calculated as you go and numbered when you issue.
Ready to start? Create Free Account
Every situation below is covered by a module that is already built.
Keep each client as a customer record with its own payment terms, then draft an invoice whose lines come from the services you already priced.
Hold labour as services and parts as products in one catalogue, each with its own unit and tax rate, and combine them on a single document.
Keep a second business in its own workspace, with separate customers, catalogue, numbering, and branding, under the same login.
Set a selling price, currency, and default tax rate per item once, so every document starts from the same number rather than from someone's memory.
Import your products and services from CSV, correct anything the file got wrong, and export the corrected list back out when you need it elsewhere.
Invite people into the business and let their role decide what they can change, with the server checking every request rather than trusting the screen.
Concrete mechanisms, described plainly. No certification is claimed and no grade of security is asserted.
An email address is confirmed before the workspace opens, so an account always belongs to someone who can receive mail at it.
Records belong to a business. An identifier on its own never reaches data — membership of that business has to prove the request first.
Roles decide what a person can do. Hiding a control is a courtesy for the interface; the decision that counts is made again on the server.
Every write is validated where it lands. Nothing is accepted because the form allowed it, and totals sent by a browser are never trusted.
Money is stored and computed in fixed decimal precision from end to end, including intermediate steps, so rounding is a decision rather than an accident.
Issued documents are added to, not rewritten. A correction becomes a further recorded step so the history of what was sent stays readable.
PlusInvoice has not published pricing. Creating an account today does not ask for payment details, because the product does not process payments.
Everything that is built, for a single business getting its invoicing in order.
A larger plan is intended once the modules it depends on exist. It is listed so the direction is visible, not so it can be bought.
Not available yet. No date is promised.
Including the ones where the answer is no.
No. Payment processing is not part of the product today. Nothing here takes a card, and nothing connects to a bank. You record the bank details you want shown as part of your business settings, and money moves outside the product.
Not yet. Email is used for account verification and account-related messages only; there is no document delivery. Marking an invoice as sent records that you sent it — it does not send anything.
Not yet. PDF generation is not built. Invoices live in the workspace, where you can view them and read their line detail and totals.
Recurring invoice automation is planned for a later product update. Today every invoice is created deliberately, one at a time.
Yes. Businesses are separate workspaces, each with its own customers, catalogue, settings, numbering, and documents, and you switch between the ones you are a member of.
On the server, in fixed decimal precision, including every intermediate step. Amounts a browser sends are never trusted as the answer — the server recalculates and the recalculated figure is what the document keeps.
The invoice takes its number under your configured format and freezes what the document says about the customer. From there it moves through sent, cancelled, or void as recorded steps. Issued history is added to rather than rewritten.
Yes. Every record belongs to a business, and every request is checked against your membership of that business before any data is returned. Knowing an identifier is never enough on its own.
PlusInvoice has not published pricing. Creating an account does not ask for payment details, and no plan can be purchased in the product today.
Set up your business, add your customers and your catalogue, and start drafting invoices with totals the server calculates for you.
No payment details are requested. PlusInvoice does not send documents or collect payments.