Troubleshoot incorrect job margin | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/troubleshoot-incorrect-job-margin Publisher: Pixie Technologies LLC Troubleshooting and operational controls Troubleshoot incorrect job margin Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Reconcile revenue, assignment pay and linked expenses. Audience: Courier operations staff; Permission: Courier: Manage finance; Module v2.0.0; Where to goAdmin Area → Courier & Logistics → Jobs → Open job What this guide helps you do Reconcile revenue, assignment pay and linked expenses. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects. Follow these steps - Check agreed revenue. - Check assignment/manual driver cost. - List all linked expenses/other costs. - Recalculate revenue minus driver cost minus other costs. - Correct the source item. Fields and options This action uses the values already stored on the selected source record. Review that record before continuing. Rules and limits - Use the supported screen and permission; do not bypass validation or edit database records directly. 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 Troubleshoot a dispatch rejection (https://pixiecrm.com/help-centre/troubleshoot-a-dispatch-rejection)Troubleshoot an invalid job status change (https://pixiecrm.com/help-centre/troubleshoot-an-invalid-job-status-change)Troubleshoot a failed core invoice creation (https://pixiecrm.com/help-centre/troubleshoot-a-failed-core-invoice-creation)Troubleshoot a provider connection failure (https://pixiecrm.com/help-centre/troubleshoot-a-provider-connection-failure)