Reconcile job payment from invoice status changes | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/reconcile-job-payment-from-invoice-status-changes Publisher: Pixie Technologies LLC Jobs, stops, dispatch and status control Reconcile job payment from invoice status changes Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Allow the core invoice hook to update the job payment state. Audience: Courier operations staff; Permission: Courier: Manage finance; Module v2.0.0; Where to goAdmin Area → Sales → Invoices → Open linked invoice What this guide helps you do Allow the core invoice hook to update the job payment state. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects. Follow these steps - Change/send/update the linked invoice through the core CRM workflow. - Allow the invoice_status_changed hook to run. - Return to the Courier job. - Check payment status reflects the core invoice. Fields and options This action uses the values already stored on the selected source record. Review that record before continuing. Rules and limits - The hook reconciles by linked invoice ID. - The invoice remains the authoritative source for its core status. Check it worked - The source record, status/history and any downstream notification, provider, POD or finance record should agree after the action. Security, audit and operational checks - Use the exact record and least-privilege role before changing any state. - Verify the saved record after every action; a browser message alone is not evidence that every downstream step completed. - Use protected document and image routes rather than exposing server filesystem paths. - Keep customer, driver, provider, financial and credential data within the authorised workflow. - For provider, finance, employment, transport and compliance decisions, follow the organisation’s authorised professional process. Do not bypass the code flowDo not force database values, invent a status, mark a job completed without signed POD evidence, or expose encrypted credentials to make a screen appear successful. Related guides Create a courier job (https://pixiecrm.com/help-centre/create-a-courier-job)Edit a draft or pre-dispatch job (https://pixiecrm.com/help-centre/edit-a-draft-or-pre-dispatch-job)Understand job sources and external references (https://pixiecrm.com/help-centre/understand-job-sources-and-external-references)Enter collection and delivery addresses (https://pixiecrm.com/help-centre/enter-collection-and-delivery-addresses)