Reporting and Audit - Distributor

Quick Checklist

Always save audit output as a timestamped JSON file.
Use counts + samples to decide next actions (no guessing).
Routing can be derived via join (no schema changes required).

Run audits (recommended workflow)

From project root /idsahome/:

Branch-Partner-CSC audit

C:\\xampp\\php\\php.exe scripts\\audit_branch_partner_csc.php

Store output with timestamp (evidence artifact):

$ts = Get-Date -Format \"yyyy-MM-dd_HH-mm-ss\"

C:\\xampp\\php\\php.exe scripts\\audit_branch_partner_csc.php | Out-File -Encoding utf8 \"reports\\audit_branch_partner_csc_$ts.json\"

How to read the JSON

summary.counts: high-level counts per issue group.
orphaned_*: missing/invalid links (branch, partner, CSC).
status_mismatches: active/suspended inconsistencies.
commission_issues: missing mapping and aged pending items.
routing_issues: missing or inconsistent routing fields; may be derived from CSC data.

Derived routing (no schema change)

If a Partner table lacks routing columns, routing can be derived from CSC centers linked to that partner. The audit may report missing or inconsistent derived values (example: multiple branches for a single partner).