Two dates instead of one. A rental order carries the day it goes out and the day it is due back. The return date sits in the same schedule as your stitching deliveries, so the piece that has not come back shows up beside the gown that has not been delivered — on one screen, before the next bride is promised the same lehenga.
The deposit stays attached to the order. Take the security deposit when the piece leaves and it stays on that order as money held, separate from the rental charge itself. When the outfit comes back clean and on time you release it; when there is damage or a late return you deduct against it. Either way the arithmetic is on the order, not in a second book, so the number you quote at the counter is the number that was agreed.
Part payments, the way rentals are actually paid. An advance at booking, the balance on collection, the deposit refunded after return — three separate movements on the same order, each dated. The outstanding figure is always current, which matters most on the day a family collects four outfits at once.
The piece comes back and needs work. A returned outfit usually needs cleaning, a repair or a re-fit before it can go out again. Raise that as a job against the same record and it enters the workroom queue like any other, so a lehenga is never promised to the next bride while it is still waiting on a seam.
What each outfit has actually earned. Because every rental is an order against the same piece, the history is already there: how many times it went out, what it brought in, what the repairs cost. That is the number that tells you which designs to buy more of next season, and which one has paid for itself twice over.