Partner work on a separate spine, billed monthly by branch.
Status at ebf7cf0: Partial — LG order, job, billing and invoice-generation modules exist.
Production scheduler execution is not verifiable from the repository, and the RTMS import page is feature-flagged and uses mock data.
Partner work — currently LG — enters Encik Beku for dispatch, completion and billing.
LG uses a separate Partner Order spine with LG-specific details and shared Job Logs. Orders can be dispatched on Susun Trip, completed by Ops, approved for billing, and included in the monthly invoice process.
Technicians work the same way whether the job came from LG or from a walk-in.
invoiced, so nothing can be billed twice. The run is idempotent, so a repeated run is harmless.bill_status: unbilled or invoiced.LG-Melaka-202607-1.POST /api/v1/lg/invoices/generate, plus billable to preview and approve.Story. As partner operations, I want LG Orders kept separate from normal Sales Orders, so that partner billing and customer sales do not mix.
Acceptance. Explicit links may connect related records, but each keeps its own identity and lifecycle.
Story. As Account, I want completed LG work approved for monthly billing, so that only eligible partner jobs enter an invoice batch.
Acceptance. The batch lists its included jobs, billing month, approval and generated invoice reference.
Story. As the system, I want scheduled invoice generation observable in production, so that failures are detected rather than silently missed.
Acceptance. Each run records start, result, included records and error details.
LG order, job, billing and invoice-generation modules exist. The scheduled lg:generate-invoices command is defined, but production scheduler execution is not verifiable from the repository. The RTMS import page is feature-flagged and uses mock data. A generic LG/Khind CSV create-order importer and the partner-tier pricing flow described in the older document are not implemented.
routes/console.php registers:
Schedule::command('lg:generate-invoices')->monthlyOn(20, '02:00');
with a comment saying it "Requires a cron running php artisan schedule:run every minute (or an external cron hitting the generate endpoint)". Twenty lines below, a different note in the same file states plainly that "the production container runs no scheduler to fire it with anyway."
If that is still true, the 20 August billing run did not happen by itself. Either somebody pressed the button on the billing screen, or LG has not been invoiced for August.
This is money, and it fails silently. An invoice that is never generated produces no error, no alert and no empty screen. It just quietly does not exist.
One answer needed from Helmi: does anything run schedule:run in production, and were the August LG invoices generated? If the answer is "no scheduler", the fix is either a real cron or a calendar reminder for whoever clicks the button — but it must be written down, because right now the system's only safeguard is that somebody remembers. Q10.
New to these terms? See the Glossary.