Payment receipts, advances and outstanding follow-up

Receipt entry — the step most businesses skip

Every business records that money arrived. Far fewer record what the money was for. Receipt entry is that discipline: each customer payment is recorded against the specific invoice or invoices it pays, so the system knows — invoice by invoice — what is paid, part-paid and open. The receipt then posts to your accounts as a receipt voucher, keeping the customer ledger in Tally identical to what billing shows.

Skip the allocation and you get the familiar SME condition: the bank statement says money came in, the customer says they have paid, and nobody can say which invoices are actually settled. Collection calls then chase totals instead of documents — and totals are exactly what customers dispute.

One payment, many invoices — allocation

In B2B trade the one-payment-one-invoice case is the exception. Customers pay against statements: one NEFT covering four invoices, less a transport deduction they dispute, plus a round figure "on account." Receipt entry has to handle that reality:

• Allocate across invoices — apply a single receipt to several invoices, oldest first or as the customer's advice directs.
• Record part-payments where they belong — a short payment sits against its invoice, visible, instead of vanishing into a customer-level total.
• Keep deductions explicit — a disputed freight deduction or agreed rebate is settled by a credit or debit note, not buried in a receipt difference.
• Park the remainder on account — anything unallocated becomes an explicit advance, tracked, not forgotten.

Allocation is five minutes of work per payment that buys a permanently true answer to "what does this customer owe, and on which bills?"

Advances and on-account money

An advance is money received before an invoice exists — with an order confirmation, as a project mobilisation payment, or simply a customer keeping a running balance with you. Advances are good cash flow and bad bookkeeping risk: money with no document attached is the easiest thing in a business to lose track of.

The right treatment is to record every advance explicitly against the party, dated and referenced to its order where there is one. Two consequences follow. First, the customer's true position is always net: invoices outstanding minus advances held. Second, tax stays clean — GST treatment differs between goods and services on advances, so an explicit advance record is what makes whichever treatment applies auditable. Confirm the current position for your case with your CA.

Advance adjustment — how it works

Advance adjustment is the moment the held money meets the invoice. When an invoice is raised for a customer holding an advance, the adjustment applies the advance to the invoice: the invoice's outstanding drops by the adjusted amount, the advance balance drops to match, and the remainder — on either side — stays visible.

The failure modes without disciplined adjustment are both expensive and common. Chase the full ₹1,60,000 from a customer who paid ₹1,00,000 up front, and you look careless and damage the relationship. Forget the advance entirely, and money sits on account for months while your outstanding report overstates what you are owed. Adjustment at the point of receipt entry — automatic, visible, against the invoice — removes both.

Reading the outstanding and ageing position

Once receipts allocate and advances adjust, the outstanding report becomes something it can never be on spreadsheets: true. Three views matter to an SME owner:

Party-wise outstanding. Who owes what, net of advances and credit notes. This is the collection worklist and the input to credit decisions — whether to release the next dispatch to a customer already over limit.

Ageing. The same money cut by how old it is — current, 30, 60, 90-plus days. Ageing converts a comfortable-looking total into an uncomfortable truth: the 90-plus bucket is where receivables go to become bad debts, and it should be nearly empty.

Invoice-level drill-down. Behind every party total, the open invoices with their part-payments and notes — because collection conversations are won at document level, where both sides can agree on facts.

Follow-up that actually collects

Collection is a rhythm, not an event. The businesses that get paid fastest are rarely the most aggressive — they are the most consistent: an invoice copy at billing, a statement at month-end, a reminder as the due date approaches, a firmer note when it passes, a call backed by exact numbers when it ages. Software contributes three things to that rhythm:

• Accurate ammunition — reminders quote real invoice-level balances, net of receipts, advances and notes, so no reminder is embarrassingly wrong.
• Automatic delivery — invoice copies, statements and overdue alerts go out over WhatsApp, email and SMS on schedule, whether or not anyone remembered.
• A worklist, not a mood — the ageing view ranks who to call today, so follow-up effort lands where the money is oldest and largest.

How Fast Billing Software runs receivables

In Fast Billing Software, the whole loop above is the Payments, Receipts & Follow-up module. Bill receipt entry records each customer payment against one or more invoices, with advance adjustment built into the same screen — on-account money is applied to invoices as they are raised, and the remainder stays tracked. The outstanding and ageing position updates live, party-wise and invoice-wise, feeding overdue alerts over WhatsApp, email and SMS.

Every receipt posts to Tally as a receipt voucher, so the book of record and the billing system never argue about a customer balance. And because receipts sit on the same linked document chain as invoices, credit and debit notes and dispatches, the number a collection call quotes is the number the customer's own records will confirm. For firms billing by project, the same receipt-and-advance mechanics apply to project and resource bills — mobilisation advances adjusted against progress bills is the everyday case.

Frequently asked questions