Troubleshooting, limitations and technical reference

Troubleshoot supplier invoice payment

Check invoice/job/status, final amount, payment mode, transaction ID and permissions. 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: Authorised finance staffModule v1.0.0
Jump to steps
Where to goAdmin supplier invoice → Mark Paid
Before you start
  • Use an account with Authorised finance staff 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

Check invoice/job/status, final amount, payment mode, transaction ID and permissions. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Follow these steps

  1. Go to Admin supplier invoice → Mark Paid.
  2. Select the relevant record, filter, report, model or configuration described below.
  3. Use the displayed action or read the current values without altering unrelated data.
  4. Compare the output with the code-backed rules and expected result in this guide.
  5. Record or correct any mismatch before relying on the output in production.

Fields and options to review

Exact actionTroubleshoot supplier invoice payment
Exact navigationAdmin supplier invoice → Mark Paid
Module version1.0.0
Access ruleAuthorised finance staff
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Maintenance requestProperty, tenant, subject/issue, priority, status, supplier, assignee, cost and administrative note.
Supplier work orderJob title/description, property/manual address, allocated amount, supplier notes, photos and completion evidence.
Financial linkSupplier invoice status, amount/final amount, payment mode, transaction ID and payment comments.
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

  • Reconcile maintenance cost after final_amount changes.
  • Maintenance hub visibility is tied to customer-view access in the registered menu.
  • Supplier completion can create a Pending supplier invoice when one does not already exist.
  • 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 troubleshoot supplier 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.