Branditify

Billing & Invoicing

An invoice is a claim. It is not a payment, and it is not your books.

A custom billing system built around one invoice — what it bills for, the review before it goes out, what has actually been recorded against it, the credit that corrects it without erasing it, and the balance that is left.

See how an invoice starts

Invoice fileNorthstar Studio Pvt LtdINV-2048Part recorded

Website build — milestone 2
₹1,50,000
Content structure and migration
₹50,000
Invoice total
₹2,00,000

Outstanding₹1,15,000of ₹2,00,000 claimed

  • ₹75,000received
  • ₹10,000credited
  • ₹1,15,000outstanding
  1. 15 SepInvoice issuedINV-2048
  2. 22 SepPayment recordedREF-8841 · recorded, not confirmed− ₹75,000
  3. 28 SepCredit note appliedCN-2048-01− ₹10,000

Next₹1,15,000 outstanding · payable by 30 Sep

The scope reduced, so a credit note is added against the invoice. The original claim still reads two lakh — a correction is a new line, never an edit.

ILLUSTRATIVE INTERFACE · SAMPLE DATA

Where the invoice starts

Something happened. Only then is there something to bill.

An invoice that begins as a blank form is an invoice somebody has to remember to raise. The useful version starts from the thing that actually became billable — an approved milestone, a delivered order, a completed job — carrying what it was for.

  1. Source recordWherever the work or the sale is already recorded.A CRM opportunity, an agency engagement, a retail transaction, an order, or an operational system built for the business.
  2. Billable itemThe moment it becomes chargeable.Milestone 2 approved by the client on 12 September.
  3. Invoice fileThe claim created from it.INV-2048, carrying what it bills for and why.

Which sources are connected is a scoping decision, not a feature list. We confirm what each existing system can expose before defining any connection.

What is billing and invoicing software?

Software that turns something billable into an invoice and then governs that invoice for the rest of its life: what it charges for, the tax fields it carries, the review before it goes out, its status once issued, what has been recorded against it, the credits or adjustments that correct it, and the balance that remains. It is the stretch between the work and the books.

What does invoice management software do?

It keeps every invoice and its history in one place — issued, due, part recorded, credited, resolved — so the current balance is derived from events rather than from somebody’s memory. The difference from a document generator is that the invoice is a record with a state, not a file.

Can billing connect to a CRM, an ecommerce store or a point of sale?

Where those systems can expose a billable event, yes — a won opportunity, an approved milestone, a completed order, a counter transaction. What we confirm first is what each system can actually expose and what the project is authorised to read, before defining the connection. No integration is included by default.

Draft and issued

The last moment anything can be changed for free

Before an invoice is issued, correcting it costs nothing. Afterwards, every correction is a document with a history. That is why the review gate exists — and why it is the single thing most off-the-shelf billing tools cannot bend to how a business actually works.

Before it goes out

Correcting anything costs nothing at all.

  1. Billable itemsWhat is being charged for, and where it came from.
  2. Customer detailsBilling entity, address and tax fields as configured.
  3. Tax treatmentThe rate and treatment set for this customer and these items.
  4. ApprovalRecorded by whoever the business requires — where it requires one.
Issue

After it goes out

Every correction becomes a document with a history.

  • INV-2048stops being editable
  • Credit notecarries the amount and the reason
  • Adjustmentrecorded against the invoice, never inside it

Plenty of businesses issue straight from draft, and that is a valid configuration. The gate is only worth building where somebody genuinely has to look — high-value invoices, a second pair of eyes, a client-specific rule.

What is the difference between a draft invoice and an issued invoice?

A draft is internal and freely editable — nothing has been claimed from anybody. An issued invoice is a document the customer has, so it stops being editable: from that point corrections happen through credit notes and adjustments that are recorded against it, which is what keeps the history honest.

Can invoice approvals be built into the workflow?

Yes, and this is usually the reason a business outgrows a standard invoicing tool. Approval can route by value, by customer, by team or by invoice type, and the approval is recorded against the invoice rather than living in somebody’s inbox. Whether a business needs a gate at all is its decision, not a default.

What is the difference between an invoice and a receipt?

An invoice is a claim — it says what is owed and by when. A receipt acknowledges that something was received against it. One invoice can attract several receipts, which is exactly why the balance has to be derived from what was recorded rather than assumed from the document.

Corrections

A correction adds a line. It never edits one.

Scope changes, a rate was wrong, a customer was over-billed. The tempting fix is to open the invoice and change the number. The honest fix is a credit note recorded against it, so six months later the invoice still says what was billed and the trail says what happened to it.

The silent edit

INV-2048₹2,00,000₹1,90,000

no second document

Nothing records that anything happened, and the customer’s copy no longer matches yours.

The recorded correction

INV-2048₹2,00,000

CN-2048-01₹10,000

The invoice still reads ₹2,00,000. The balance moves because the credit exists, not because the invoice was rewritten.

Does an issued invoice mean it has been paid?

No, and collapsing the two is the most common reason a billing record stops being trusted. Issued describes the document. Paid describes money, and money is described by what has actually been recorded against the invoice — which may be nothing, part of it, or all of it.

Can billing software track partial payments?

It has to. A part payment is recorded against the invoice with its reference and date, the outstanding balance becomes the total minus everything applied, and the invoice stays open until that difference is nil. The original invoice is never reduced to match what arrived.

Does a recorded payment mean the money has settled?

Not by itself. A payment entered by a person is a recorded payment; a payment matched from a bank feed, a payment provider or an accounting source is a confirmed one, and the record shows which it is. Billing does not move or settle money — it records what an authoritative source tells it.

Can credit notes and adjustments be tracked?

Yes, as documents in their own right, recorded against the invoice they correct and carrying the reason. The balance recalculates because the credit exists — the original invoice is left exactly as it was issued.

Is invoice history preserved after a correction?

That is the point of doing it this way. Issued, recorded, credited, resolved — each with its date and reference — so the invoice can be explained months later without anybody reconstructing it from email. Silently editing an issued invoice is the one thing a billing record must not do.

How is the outstanding balance calculated?

As the invoice total minus everything applied against it — payments recorded and credits raised. It is derived on the record rather than stored, so it cannot drift away from the events that are supposed to explain it.

GST-aware billing

GST-aware billing is not GST filing

An invoice in India carries tax fields, and getting them right on the document is a billing job. Working out what a business owes the government, and telling the government about it, is a different job with different professionals and different systems.

INV-2048GST 18% · inclusive

Taxable value
₹1,69,492
GST 18%
₹30,508
Invoice total
₹2,00,000

Configured per customer and per item. The breakdown is derived from the invoice total and the configured rate, so the fields printed on the invoice cannot disagree with the invoice.

This system

  • Tax fields on the invoice, configured per customer and per item.
  • Rate and treatment set against the billing record rather than typed each time.
  • A tax breakdown derived from the invoice, so the fields cannot disagree with the total.
  • Invoice history and exports for whoever prepares the return.

Somebody else’s

  • GST return preparation and filing.
  • The GST portal, the e-invoice IRP and e-way bill generation.
  • Tax positions, credits claimed and statutory advice.
  • The books, and what the numbers mean in them.

Where a business genuinely needs an e-invoice or e-way bill connection, that is a scoped piece of work against a confirmed provider interface — not something this Product claims by default.

Can GST fields be added to invoices?

Yes. Tax labels, rates and treatment are configured against customers and items rather than retyped, and the breakdown on the invoice is derived from the invoice total and the configured rate so the two cannot disagree.

Does GST billing software file GST returns?

This one does not. It produces GST-aware invoices and the history and exports that whoever prepares your returns will need. Return preparation, the GST portal and statutory advice belong to your accountant and to tax software — the market itself draws this line: billing software cannot file your taxes.

Can e-invoice or e-way bill systems connect?

They can be scoped, once the required provider or government interface and the business’s own obligations are confirmed. What we will not do is list them as included capability — an interface described on a page and one that actually exists for a given business are different things.

Where it sits

Between the work and the books

Billing owns the stretch from a billable event to a settled balance. The systems on either side of it are not competitors — they are where the invoice comes from and where its consequences go.

  1. BeforeThe work, the order or the sale, wherever it is already recorded.
  2. Billing & invoicingThe invoice, its review, its status, what is recorded against it, its corrections and its balance.
  3. AfterMoney moved by a payment provider or bank, and financial treatment recorded in the books.
Accounting
Owns the books — ledgers, journal entries, revenue recognition, the trial balance and what the numbers mean. Billing hands its figures over where that connection is scoped; it does not keep books.
Payment provider or bank
Moves and settles the money. Where connected, its confirmation comes back onto the invoice instead of being assumed.
Point of salePOS & retail management
Owns the counter transaction, where payment and document happen at once. Billing matters when the charge comes later, needs approval, or spans more than one source.
CRMCustom CRM
Owns the customer relationship and the commercial conversation. It can tell billing that something became chargeable.
Agency operationsAgency operations
Owns engagements, scope and approvals. An approved deliverable is one of the cleanest billable triggers there is.
Ecommerce storefrontEcommerce storefront
Owns catalogue, cart and checkout. A completed order can become an invoice where the business bills rather than charges at checkout.
DashboardsDashboards & reporting
Reads across billing once the record exists. Reporting is a view over invoice data, not the place invoices live.

What is the difference between billing software and accounting software?

Billing handles money you are about to collect; accounting handles money once it has already moved. Billing owns the invoice, its review, its status and its balance. Accounting owns the ledgers, the treatment and the reports. They connect at the handoff, and neither does the other’s job — accounting cannot run your approval workflow, and billing cannot file your taxes.

Is billing software the same as a payment gateway?

No. A gateway moves money. Billing says what is owed, records what came back and keeps the balance. Where a gateway or bank feed is connected, its confirmation lands on the invoice — which is how a recorded payment becomes a confirmed one.

How is billing different from a point of sale, or from order management?

A point of sale closes the charge at the counter, where document and payment are the same moment. Order management owns what happens to a confirmed order — allocation, fulfilment, shipment, returns. Billing owns the invoice: it can be raised from either of them, later, with its own approval and its own balance.

Coming off spreadsheets and old tools

A migrated balance is worth nothing until it reconciles

Invoice data moves easily and lies quietly. The work is proving that what the new system says is outstanding matches what the business has actually been chasing.

  1. 01What exists nowThe invoice sheet or old tool export, the customer list, the payment record, and the credits that were agreed by email.
  2. 02Sample checkA representative set — clean invoices, part-paid ones, credited ones, disputed ones, closed ones.
  3. 03Map the recordCustomer, invoice, line items, tax treatment, status and every event recorded against it.
  4. 04Reconcile balancesOutstanding recalculated from events and compared with what the business believes it is owed. Differences are examined, not averaged away.
  5. 05Load and verifyInvoices loaded with their history intact, and the ones that did not reconcile listed rather than quietly accepted.

Where a migrated balance and a legacy balance disagree, that difference is the most valuable thing the migration finds — usually a credit somebody agreed and never wrote down.

Can old invoices migrate from Excel or another system?

Customers, invoices, line items, statuses and payment history can be mapped and loaded, and balances rebuilt from events so they are reproducible. What we check first is what the current sources can actually export. We will not promise every historical invoice reconstructs perfectly — the ones that do not reconcile get listed, because a balance nobody can explain is worse than a gap everybody can see.

Can reminders and recurring invoices be supported?

Due and overdue reminders can be built where a communication channel is connected, and recurring invoices can be generated on a schedule for retainers or ongoing services. Both are scoped: which channel, whose provider, and what the business actually wants sent. Neither turns billing into a collections operation.

What it meets · what changes size

What is in every build, and what a project decides

The invoice lifecycle is the same everywhere. Billing models, approval rules and tax treatment are not, and those are the parts worth scoping honestly rather than promising as a feature list.

  • In every buildCustomers and billing basisWho is billed, on what basis, with the details and tax fields that belong to them.
  • In every buildInvoice and line itemsThe claim, summed from what it charges for, with the tax breakdown derived from it.
  • In every buildReview and issueWhatever check the business requires before an invoice becomes a document the customer holds.
  • In every buildStatus and balanceOpen, part recorded, resolved — with outstanding derived from events rather than stored.
  • In every buildCredits and adjustmentsCorrections recorded against the invoice, with history preserved.
  • In every buildInvoice historyEvery event with its date and reference, readable months later.
  • Scoped per projectApproval routingBy value, customer, team or invoice type, where a business needs more than one gate.
  • Scoped per projectRecurring billingRetainers and scheduled invoices where the business bills on a cycle.
  • Scoped per projectTax treatment depthMultiple rates, place-of-supply rules and per-item treatment where the products require them.
  • Scoped per projectPayment confirmation sourceA provider, bank feed or accounting source that can confirm what actually arrived.
  • Scoped per projectRemindersDue and overdue notices, through whichever channel the business already uses.
  • Scoped per projectAccounting handoffExports or a live connection into whatever keeps the books.
How many billing models really exist
Milestone, retainer, usage and one-off in the same business is four models, and it is usually the largest driver.
Whether approvals matter
Issuing straight from draft is a small build. Routing by value, customer and team is a different one.
How the invoice is shaped
One standard layout is straightforward. Per-customer formats, languages or purchase-order references are not.
Where payment truth comes from
Manual recording is simple. Matching a bank feed or provider against invoices is a project of its own.
How much history has to reconcile
Loading open invoices is not the same as reconciling a closed book going back years.

Does every business need custom billing software?

No, and most do not. If standard invoices, standard tax handling and standard integrations fit, an off-the-shelf billing or accounting tool is faster, cheaper and better supported — we would say so. There are a lot of good ones.

When is custom billing software actually worth it?

When the billing logic itself is unusual — several models running at once, approvals that route by value or customer, invoices originating from more than one internal system, adjustment workflows the standard tools cannot express, or a billing experience that has to sit inside a larger custom operation. The signal is a team spending real hours every week working around the tool they already pay for.

Who owns the system and the data?

You do. The customer and invoice records, the configuration, any code written for you and the accounts it runs on are handed over as agreed in scope, and the data is exportable.

What determines the cost and timeline of a billing project?

How many billing models genuinely exist, whether approvals route, how much the invoice document itself varies, where payment confirmation comes from, how much history must reconcile, who needs access, and what the business is obliged to keep. We would rather scope those with you than quote a range that ignores them.

Selected work

Records, states and the interfaces people operate them in

A billing record is a structured document with derived state and an operations interface on top of it. These are three builds where exactly that was the deliverable — a record given a structure, a product surface given real states, and a service given a flow somebody could follow.

Questions

Billing and invoicing, answered

What is a billing and invoicing system?
A system that owns the invoice from the moment something becomes billable to the moment its balance is resolved: what it charges for, its tax fields, the review before it goes out, its status, what has been recorded against it, the corrections raised against it, and the balance that remains.
Is billing software the same as accounting software?
No. Billing handles money you are about to collect; accounting handles money once it has already moved. Billing owns the invoice and its balance, accounting owns the books and the treatment, and they connect at the handoff.
Does this replace our accountant or our accounting software?
Neither. It produces the invoices and the history your accounting process needs, and hands them over where that connection is scoped. Ledgers, journal entries, revenue recognition, returns and statutory advice stay exactly where they are.
Can it handle GST invoices?
Yes — tax labels, rates and treatment configured per customer and per item, with the breakdown derived from the invoice so the fields cannot disagree with the total. It does not prepare or file GST returns, and it does not connect to the GST portal, the e-invoice IRP or e-way bill unless that is separately scoped against a confirmed interface.
Does the system collect payments?
No. It records what has been received against each invoice and, where a payment provider, bank feed or accounting source is connected, shows what that source has confirmed. Moving and settling money is done by those systems, not this one.
What happens when an invoice is wrong after it has gone out?
A credit note or adjustment is raised against it, carrying the amount and the reason, and the balance recalculates. The issued invoice is not edited — that is what lets somebody explain the account six months later.
Can invoices be raised from our existing systems?
Where those systems can expose a billable event — a won opportunity, an approved milestone, a completed order, a counter transaction — yes. We confirm what each one can actually expose and what the project is authorised to read before defining a connection.
Can it chase overdue invoices?
It can show what is overdue and send due or overdue reminders through a connected channel. It is not a collections or recovery system, and it does not manage disputes, agencies or legal action.
Should we build this or buy an existing tool?
Buy, if standard invoices, standard tax handling and standard integrations fit how you bill — that is most businesses, and the tools are good. Build when the billing logic is genuinely yours: several models at once, approvals that route, invoices from more than one internal system, or billing that has to live inside a larger custom operation.

Start

Bring one month of invoices and the one that caused an argument

The fastest way to scope a billing build is real invoices with real complications in them. Bring a month of what went out, and the account somebody had to explain.

  • How you bill — milestone, retainer, usage, one-off, or several of them at once.
  • Where the billable event is recorded today.
  • Who checks an invoice before it goes out, if anybody does.
  • How you know a payment arrived, and who tells you.
  • What happens when an invoice turns out to be wrong.
See how we build systems