Business brokers and broker portal

Convert a broker request to invoice

Follow this guide to create a CRM invoice from an eligible request. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: CRM staffPermission: Authenticated broker user with request edit/conversion accessModule v1.0.0
Jump to steps
Where to goBroker Portal → Requests → open request → Convert to Invoice
Before you start
  • Use an account with Authenticated broker user with request edit/conversion access and confirm the intended record or setting before making a change.
  • Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
  • Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.

What you’ll accomplish

Create a CRM invoice from an eligible request. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Follow these steps

  1. Go to Broker Portal → Requests → open request → Convert to Invoice.
  2. Select the exact record or option described in this guide.
  3. Complete the displayed fields or action using the rules below.
  4. Save or submit once and resolve any validation response.
  5. Check the resulting record, status, file, notification or integration effect.

Fields and options to review

Exact actionConvert a broker request to invoice
Exact navigationBroker Portal → Requests → open request → Convert to Invoice
Module version1.0.0
Access ruleAuthenticated broker user with request edit/conversion access
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Request recordCode, client, property/item, request type, currency, property price, term and inspection choice.
Notes and billingClient note, admin note and billing/shipping data where the form exposes them.
ConversionCheck status and linked customer/property before converting to a contract or invoice.
Financial recordClient/vendor/landlord, linked property/request/contract, date/due date, currency, items, taxes, discounts, totals and status.
Payment evidencePayment mode, amount, transaction ID, note/comments, date paid and email/PDF choices where exposed.
Organisation/personName, code, email, phone, website, tax/VAT, address, status and profile image where exposed.
Access and structurePlan, role, administrator flag, departments, staff type/company link, approval-manager and public flags where applicable.

Rules the system enforces

  • Check customer billing, currency, taxes and price before conversion.
  • Buy and rent requests use separate real_buy_request and real_rent_request capability groups.
  • Status changes and conversion actions validate the current request and linked record IDs.
  • Verify linked CRM invoice/payment records before changing a real-estate payment or payout status.
  • The module hooks after_payment_added to write property-related activity when the payment is linked.
  • Company, owner, broker and staff records use different capability groups and ownership checks.
  • Email-exists checks prevent duplicate staff/company identities in supported forms.

How to confirm it worked

  • The supported convert a broker request to invoice flow completes without bypassing permission or validation checks.
  • The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
  • Unexpected validation, provider or linked-record errors are investigated before retrying.

Security, privacy and operational checks

  • Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
  • Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
  • Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
  • Test settings and automated jobs with controlled records before production-wide use.