A security deposit is usually the largest single amount a PG tenant ever hands over — often two months' rent, frequently in cash, at the moment they're least inclined to ask for paperwork. It's also, in most PGs, the least documented transaction in the business.
Quick answer (for the impatient)
A deposit was collectable and completely unprovable. That's now fixed — the collection produces a real record.
Proof protects both sides, and the owner more than they expect.
The deposit ledger tracks it as a liability, which is what it actually is until the tenant leaves.
Why "unprovable" is the owner's problem too
The intuition is that documentation protects the tenant. It does. But the owner's exposure is arguably larger, because the owner is the party who has to demonstrate what was collected and what was deducted, potentially fourteen months later, to someone who has left and is unhappy.
Without a record: the tenant says three months, you say two. The tenant says nothing was ever agreed about damages. You deducted for a broken cupboard and can't show what was collected in the first place. Every one of those arguments is one the owner loses by default, because the party who should have documented it is the party running the business.
Treating a deposit as what it is
A security deposit isn't revenue. It's money you're holding that belongs to someone else and will mostly go back. Recording it as a liability — which is what the deposit ledger does — has two effects worth having.
First, it stops deposits being quietly consumed as working capital. Many PGs do this without deciding to, and discover the problem when three tenants leave in the same month. Second, it means the outstanding deposit obligation is a number you can see rather than a total nobody has ever added up.
That figure is worth knowing. For a 40-bed PG holding two months' deposit per tenant, it's a substantial liability sitting invisibly in the business.
What the record should capture
Amount and date collected, with the mode of payment.
Who collected it — which matters when cash and staff turnover are both involved.
A receipt the tenant actually gets. The receipt is the point; an internal record the tenant never sees solves half the problem.
Deductions, itemised, when they happen — not a lump-sum reduction at exit.
The refund, with its date and amount.
Itemising deductions at the time rather than at exit is the single practice that prevents most deposit disputes. A tenant told in month four that a repair cost ₹1,200 and will come off their deposit rarely argues. The same tenant told at exit, as part of a total, always does.
A practical operating workflow for this PG
The useful way to apply A Deposit You Collected and Couldn't Prove You Collected is to turn the idea into a repeatable operating rhythm. Start with the current process, not the software screen. Write down who begins the task, what information they need, where the record is kept, who checks an exception, and what the resident is told. That prevents a common PG mistake: digitising an unclear process and discovering that the same argument now happens faster.
Step 1 — establish the starting record. A deposit was collectable and completely unprovable. That's now fixed — the collection produces a real record. The owner or warden should decide which field, document or confirmation is the source of truth. Existing residents, rooms, balances or requests should be checked before a new workflow is switched on. If the starting record is incomplete, note the gap openly instead of filling it with an assumption.
Step 2 — define responsibility. Proof protects both sides , and the owner more than they expect. Name the person who enters the record, the person who can approve a change, and the person who follows up when something is overdue. In a small PG those roles may belong to one person, but writing them down still matters. It stops a cook, caretaker, accountant and owner from each believing that somebody else handled the same exception.
Step 3 — test one real case end to end. The deposit ledger tracks it as a liability , which is what it actually is until the tenant leaves. Use one room, one resident or one billing cycle first. Follow the record from the first action to the final acknowledgement. Check the owner view, staff view and resident-facing result separately. A backend record or internal screen is not enough if the person expected to act cannot reach it.
Step 4 — keep an exception path. Decide what happens when information is late, a resident disputes the record, a staff member lacks permission, or the usual approver is absent. Record the reason for any manual correction. Do not quietly overwrite history simply to make a dashboard look tidy.
What the weekly review should cover
Fifteen focused minutes is enough when the team brings the same evidence each week. Review what was completed, what remains open, which cases needed manual intervention, and whether residents received the message or document they were meant to receive. The objective is not a perfect-looking count. It is to find repeated friction while it is still small enough to fix.
Review question Evidence to check Action if it fails
Did the process start with a complete record? The original entry, document or resident confirmation Correct the source and note who verified it
Did the right person act? User, timestamp and permission trail where available Clarify responsibility or access before the next cycle
Did the resident receive a clear outcome? Receipt, message, portal view or signed acknowledgement Send the missing confirmation and repair the template
Did an exception repeat? Open cases and manual corrections from the week Change the process; do not keep relying on memory
For Why "unprovable" is the owner's problem too, ask whether staff explain the process consistently. For Treating a deposit as what it is, compare the operating record with what the resident experienced. For What the record should capture, look for cases handled outside the agreed path. These checks do not assume an automated report, alert or capability that the article has not established.
A safe rollout checklist
Confirm the property, room and resident scope before changing any record.
Check that only the intended role can create, approve, reverse or view the relevant information.
Run a real test with the people who perform the work, not only an administrator.
Keep the previous record available until the new result has been checked.
Tell residents what changes, what does not, and where they can raise a dispute.
Review the first week and document every manual workaround.
This checklist protects both sides. Residents get a process they can understand and question. Owners get a record that can be checked later instead of an argument reconstructed from memory. It also respects the boundary between guidance and capability: use only screens, permissions and resident surfaces actually reachable in your Hotel/Hospitality tenant.
One more question operators ask
Should we move every existing case into the new process at once?
No. Start with a controlled group or the next clean cycle, reconcile the result, and then expand. A staged rollout is slower for a few days and far safer than correcting every resident record after a rushed migration.
Where AXOIX is honest about its limits
A record is not a legal instrument. Your rent agreement is what sets the deposit terms; this documents what happened under them.
Nothing enforces a refund timeline. If your agreement or local rules set a period for returning deposits, meeting it is your process.
Deposits moving the wrong way was a real defect, since fixed. If you've had unexplained deposit ledger oddities, reconcile rather than assume it was entry error.
FAQ
Should I keep deposits in a separate account?
Not required in most cases, but it's the practice that prevents accidentally spending money you owe back. Worth discussing with your accountant.
Can I deduct for normal wear?
That depends on your agreement and applicable law. Deducting for ordinary wear is where most disputes originate and most owners are on weak ground.
What if a tenant leaves without notice?
Your agreement should specify the consequence. See deposit refund rules for the general shape of this.
The bottom line
The largest transaction in a PG tenancy was, in a lot of properties, the one with the least paper behind it. Producing a real receipt at collection is a small operational change that removes the argument you're most likely to lose.
See how rent and deposit billing works, how corrections are handled, or pricing.
Prove what you collected. Start free →
Comments