What is udhaar when you leave paper?
Udhaar means customer credit — the builder who takes cement today and pays Thursday, the contractor with a running khata, the account that never quite zeroes before the next load.
On paper it lives in a notebook, a head, and three reminder chats. The owner knows the real balance; the salesman guesses; the diary at home has a different total. For shops where someone else bills, that scatter is how balances go wrong.
Solo freemium khata apps track party balances for one person on one phone. A staffed or family counter needs the limit at billing — before the bag leaves — not a balance you reconcile next week when the customer denies the number.
MaterialOS treats udhaar as part of the same ledger as stock and invoices. You are not maintaining a separate "credit app" that might disagree with what was actually billed.
Hard stop at billing versus party balance later
A party balance after the fact tells you what already happened. It is useful for the owner Sunday review — "Ram babu owes 1.2L" — but useless while the gate is open and another truck is loading.
A credit limit at billing stops the overshoot while the customer is still at the counter. Staff raise a bill; the system knows open invoices plus this cart; if the limit breaks, the sale stops or seeks an override on Growth/Pro before cement leaves.
That is the difference between khata as memory and khata as control. Memory apps congratulate you on recording debt. Control stops new debt when policy says stop.
In MaterialOS you set a limit on the customer record. Sales staff see headroom, not your purchase margins. Owner and manager see full outstanding across shops when multi-location applies. See udhaar and credit limits for the feature path.
FIFO when they pay in parts
Builders rarely clear one invoice cleanly. They pay 50k against three open bills. Without allocation rules, partial payments leave the ledger guessing which invoice closed.
FIFO payment allocation ties collections to open invoices in order — oldest first unless you adjust. Staff record a payment; the system applies it; outstanding on the customer record matches what you would defend on a call.
That is ops discipline, not a WhatsApp reminder pack. Reminders do not fix wrong balances; allocation does. Your CA's outstanding view and your counter's credit headroom stay aligned because they read the same ledger.
Combine FIFO with the billing hard stop: new sales respect remaining headroom after partial pays, not a notebook page that still shows last month's guess.
Example: builder owes ₹2L across two open bills, limit ₹3L, cart today ₹1.1L — system allows. Same builder, same limit, cart ₹1.2L — hard stop or approval path before load. Party balance alone would only tell you ₹3.1L after the truck left.
When staff make udhaar worse
The failure mode is familiar: owner sets a limit in head; salesman wants the sale; notebook gets a new line without updating the shared total. By month-end three versions of the same builder exist.
Role separation helps. Sales staff bill within limits; managers approve exceptions; owner sets policy and heavy accounts. Five roles ship on every plan — you grow into invites when someone else touches the counter.
Multi-shop adds another fracture: builder buys from yard A Monday and yard B Wednesday. One ledger, one customer outstanding — filter by shop when you need counter view, rollup when you call at 10 PM. Read multi-shop ledger if that is your shape.
When to leave a freemium billing app
Leave when staff can oversell credit, when udhaar lives in three places, or when you want stock and credit on one ledger. Stay on freemium if one person owns every bill on one phone and permanent free is the only requirement.
Honest peers sit on Vyapar alternatives. Building-materials dealers with heavy credit days often hit the limit first — building materials is the beachhead vertical we ship signup for today.
We will not market a permanent free plan. We will not claim MaterialOS submits GST returns. We will not invent customer testimonials. Public proof is the Kolkata two-shop origin plus product facts: 14 reports, five roles, multi-shop from day one.
Trial: 30 days of full Pro, no card, on MaterialOS pricing. After trial, data stays readable and exportable; new sales pause until you choose Starter (₹799/mo), Growth (₹1,799/mo), or Pro (₹3,499/mo) — prices exclude GST (+ 18% GST at checkout).
Credit limits in practice
Set limits on the accounts that actually move volume — not all 200 notebook names on day one. Owner knows which builders test every salesman; start there.
When a limit trips, Growth and Pro can route to manager approval instead of a silent override. Starter hard-stops the bill — still better than notebook honour system.
Outstanding reports and customer ledger exports give the owner Sunday review without opening the sales app. Same numbers the hard stop used on Tuesday — no second truth.
Udhaar without billing discipline is just a prettier notebook. The leave-paper move is: invoice every load, limit at bill, allocate every collection. Khata apps that skip billing still leave stock and revenue guessing.
Growth and Pro add approval when a limit breaks — manager or owner can allow a load with eyes open. Starter stops the bill; that alone beats honour system at a staffed gate.
Notebook khata often mixes personal and business debt on one page. On the ledger, keep builder accounts clean — opening balance once, then every load is a bill. Mixing types breaks both the hard stop and the CA export.
Payment collection staff can use accountant role or owner/manager depending how you split duties — either way FIFO allocation is the same button, not a separate khata notebook.
Udhaar is fine. Untracked udhaar across three places is how shops bleed. One ledger with a hard stop beats another reminder WhatsApp.