Mission

Getting paid should be the easy part.

Independent businesses in India do the work, then lose evenings to the billing. Tax treatment that has to be right, a client who needs an obvious way to pay, and a running question of what has actually arrived. CloudInvoice exists to make that part boring, in the good sense.

The problem

Billing is where good work goes quiet

For a freelancer, a studio, or a two-person consultancy, an invoice is not paperwork. It is the moment a client decides how seriously to take you, and the moment your own cash flow is settled or deferred by a month.

The tools available tend to sit at two extremes. Either a spreadsheet and a manually typed GST figure, which works until it quietly does not. Or a full accounting platform built for a finance team, priced for one, and carrying a hundred features to navigate around.

CloudInvoice takes the narrow middle: get the tax right, give the client an unambiguous way to pay, and show the owner what has been billed against what has actually been collected. Nothing else has to be in the product for those three to be worth using.

Principles

Six positions the product actually holds

A principle that is not visible in the software is just copy. Each of these describes something already built, and each one is checkable by reading the product rather than trusting this page.

Tax treatment is not an afterthought

GST is calculated per line item, with CGST and SGST for intra-state supply and IGST for inter-state. Client GSTIN, state code, and HSN or SAC fields are part of the invoice record, not a note you attach afterwards.

Implemented in the invoice calculation and validation layer.

Payment state has to be earned

A browser landing on a success page proves nothing. A card payment is recorded only after the payment processor's signed webhook has been verified, and the same payment identifier can never be recorded twice.

Signature verification and idempotency in the webhook handler.

One workspace should never see another

Every read and every change resolves the current membership first, then scopes the query to that organization. A client list, an invoice, a payment record: all of it is bounded by the workspace that owns it.

Organization scoping on every authenticated query.

Say what the product does, not what it might

The security page refuses to claim certifications that have not happened. The status page publishes no uptime figure because none is measured. Pricing states plainly that paid checkout is not enabled yet. Where the product falls short, the site says so.

Visible across the security, status, and pricing pages.

Nothing gets charged by surprise

There is no subscription mechanism in the product today, which means no workspace can be moved onto a paid plan quietly. Any future paid plan will require an explicit action before it begins.

No billing or subscription implementation exists.

Small on purpose

An independent business does not need an accounting suite to bill a client. CloudInvoice stays deliberately compact so the workflow can be learned in one sitting, rather than growing features to fill a comparison chart.

A focused route surface and data model.

Commitments

Things we would rather not do, stated in advance

Not claim a certification we do not hold

No SOC 2, ISO 27001, PCI DSS, or HIPAA language will appear until an assessment has actually happened and can be produced on request.

Not publish an uptime number we do not measure

A status page with invented availability bars is worse than no status page. Ours shows component state and says plainly that it is maintained by hand.

Not treat a redirect as a payment

Confirming money moved is the one thing an invoicing tool cannot get wrong. Verified processor events only, and for methods we cannot verify we say the confirmation step is yours.

Not sell the roadmap as the product

Planned work is labelled as planned, with dates presented as estimates. If something is not built, the site should not imply that it is.

Honesty about the present

What this mission has not delivered yet

A mission page is easy to write and easy to fall short of. So here is the honest position: CloudInvoice does the core well and has real gaps around it.

Invoices are created accurately and shared cleanly. Payment collection through a card processor is implemented and verified properly. Revenue and outstanding balances are visible. That much works.

What is still missing is documented rather than hidden. The status page lists which components are operational and which are built but not configured. The changelog covers what shipped and what is planned. If something here reads as a promise the product does not keep, that is a defect worth reporting through contact.

Send one invoice and decide for yourself.

Create a workspace, add a client, and produce a GST-correct invoice with a private payment page. That is the whole promise, and it takes a few minutes to test.

Get started