BizBytes Collection Agent

What was sold in this period, taken from the bills imported against each salesman. Every other report here answers what is still owed; this one answers what went out. The date used is the bill date, so a month here matches the sales figure on the Targets screen.

Which shops are called on which day, and how much is owed on each round. The day comes from the Visit Day column loaded with the opening balances, and can be changed per customer under Masters → Customers.

How the app sends reminders and reports. Without this, WhatsApp buttons open the app with the message ready and you press send — which works, but cannot attach a file.

An SMTP mailbox the server sends from, so a report can go out with the Excel or PDF attached. For Gmail use an app password, not the account password.

Used to explain a report in plain words and to draft reminder messages. Only figures are sent — totals and counts, never customer names or phone numbers.

Load what this business is already owed on the day it starts using the app, straight from the Bills Receivable report its old software prints. Upload the sheet as it comes — the title block, the per-customer Total lines and the blank rows are all ignored, and the account name only has to appear on each customer's first line.

Columns are matched by their headings, not by position, so extra or reordered columns are fine. Recognised: Account, Salesman, Visit Day, Dated, Ref. No., Group, Ref. Amt., Pending Amt., Last Rcpt Dt., Last Rcpt Amt. Due Days is ignored — the app works ageing out itself from the bill date.

Template: Customer Name | Bill No | Amount

Send a shop a WhatsApp reminder for the money they owe. Overdue accounts are listed first.

How much of your outstanding is fresh versus old. Buckets are by days since the bill date.

Each salesman's two goals for this month. Collection is the money brought back from customers. Sales is the value of the bills imported against him — so every sales import that names a salesman counts towards his sales figure automatically.

Today's collections at a glance. Tap Share to send this to yourself or a group on WhatsApp.

The shops a salesman needs to cover, and which ones have paid today. Not-visited shops are listed first.

When a shop says it will pay, put it here. A promise is against the account, not a particular bill — which bills it settles is decided when the money actually arrives. Nothing here changes a balance.

Log cheques you receive — including post-dated ones — and track whether they clear or bounce.

Tick each cheque you are physically handing to the owner. UPI is not listed — it is already in the bank and nothing changes hands.

Added up from the breakdowns entered against individual cash payments.

Report only. UPI collections are entered in Cash Flow → Receive Payment by choosing UPI as the payment method.

Beats are the territories customers belong to. The salesman is picked per brand at import time, not here.

Customers are also created automatically when bills are imported.

Vendors are also created automatically when purchase bills are imported.

Template: Vendor Name | Invoice No | Amount

—

Selfie *

Opens the front camera on a phone.

Odometer reading (km)

📍 Getting your location…

Save Cancel

Payable = monthly salary ÷ days in month × (present days + paid holidays). Allowance = travel km × that person's per-km rate, from their check-out odometer readings. Balance = Payable + Allowance − Advance − Paid, where Paid and Advance come from Cash Book entries for the month.

Every cash book entry for the chosen period. New entries are added in Cash Flow → Cash Book.

Check-in selfies are files on the server, while the record naming them lives in the database. If the server has no permanent storage attached, every update wipes the photos and leaves the records pointing at nothing.