Finance & post-sales

The client portal: what booked clients see and do

How a buyer signs in, what the portal shows (schedule, demand letters, receipts, ledger, construction, help), how they report a payment, and what your team does with it.

Signing in

A buyer signs in at your company's BMexa address with their Company ID, Username and Password, the same sign-in page as staff; the username decides that the client portal opens. The login is created from the booking (see Booking documents): BMexa makes a username from the client's name and emails a first password, and the buyer chooses their own password at first sign-in. Forgot username? and Forgot password? work for buyers too. There is no self sign-up and no OTP login for buyers.

What the buyer sees

  • Dashboard: Booked value, Paid, Outstanding to us, TDS to deposit, Next due and any Late-payment interest, then one card per booking with its stages and a link to the full schedule.
  • Demand letters: every letter issued, with its PDF, and the Full payment schedule showing basic, GST, the 1% TDS the buyer deposits, what to pay the builder and what was received.
  • Ledger: demanded, received and the balance, the running Statement, Download statement, Welcome letter (PDF) and any credit and debit notes.
  • Payments: verified receipts with PDFs, the Report a payment form and Payments you reported.
  • Construction: the project's updates with photos and stage badges.
  • Help: raise a request and read the replies. The bell carries every notification: demand issued, receipt verified, due date moved, ticket replies.
  • Profile: name, email, mobile, builder, bookings, username and company ID, read-only, with a change-password card.

Reporting a payment (with proof)

  1. The buyer opens Payments and fills Report a payment: Amount paid (₹), How (NEFT, RTGS, UPI, Cheque, Demand draft, Cash at office, TDS deposited (1%, Form 26QB) or Other), Date of payment, the UTR / transaction reference (required except for cash and other), Your bank, For which demand (or "Not sure — adjust in order"), an optional Proof screenshot or challan (required for TDS) and a note, then clicks Report payment.
  2. The report shows under Payments you reported as "Reported · with your relationship team". The rep and the CRM desk are notified.
  3. CRM opens ERP › Receipts & payments › Reported by buyers, checks the Proof, and clicks Record receipt (pre-filled) or rejects it with a reason the buyer reads. The buyer's report moves to "Recorded · with accounts for verification".
  4. Accounts verifies the receipt; the report becomes "Verified · receipt issued" and the receipt appears with its PDF. A bounced or cancelled receipt updates the report's wording too.

On the phone

On a phone the portal becomes an app-style layout with the tabs Home, Payments, Documents, Help and Me. Home shows the booking, a Pay now card with what is due, the latest construction update and the relationship manager; Payments holds the schedule, receipts and I've paid (the payment report); Documents groups the statement, welcome letter, demand letters, late-fee invoices, receipts, credit and debit notes and the papers on file; Me has the login details, Sign out and Sign out everywhere.

Updated on 29 October 2026