Record an invoice payment — Contracts, invoices, payments and PDFs
Enter amount, payment mode, transaction ID and note. 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.
Where to goBroker Portal → Invoices → open invoice → Record Payment
Before you start
- Use an account with Authenticated broker user with payment 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
Enter amount, payment mode, transaction ID and note. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Follow these steps
- Go to Broker Portal → Invoices → open invoice → Record Payment.
- Select the New, Add, Create or Start action exposed on that screen.
- Complete the required fields described below and review any linked record, currency, tax, approval or recipient selection.
- Save or submit the form once; correct any validation message rather than bypassing it.
- Go to the resulting record and verify its number, status, totals, files, activity and downstream links.
Fields and options to review
Exact actionRecord an invoice payment
Exact navigationBroker Portal → Invoices → open invoice → Record Payment
Module version1.0.0
Access ruleAuthenticated broker user with payment access
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
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.
Rules the system enforces
- Verify outstanding amount and whether a receipt email should be suppressed.
- 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.
How to confirm it worked
- The supported record an invoice payment 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.