Understand Courier accounting side effects
Trace customer sync, invoices, journals and payments through the accounting service.
Exact navigationTechnical reference → libraries/Clm_accounting_service.php
What this guide covers
Trace customer sync, invoices, journals and payments through the accounting service. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.
Exact step-by-step process
- Open Technical reference → libraries/Clm_accounting_service.php.
- Review the source record and choose the supported action.
- Save or submit once, then reopen the record and verify the result.
Fields, choices and supported possibilities
Customer syncsyncCustomerToCore and syncClientFromCore.
Driver syncsyncDriverToCore.
Job invoicecreateJobInvoice.
JournalspostJobJournal and postExpenseJournal.
ReconciliationreconcileInvoiceStatus and recordCorePayment.
Code-backed validations and workflow rules
- Core destination fields are filtered to the actual table schema.
Expected result and verification
- 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.