# Gap Analysis

## Summary

The application already implements the core automated reconciliation and InitialBalances transfer capabilities. The main gaps are operational rather than purely technical: governance, ownership, metrics, post-import validation, and documented control procedures.

| Area | Current state | Target state | Gap | Priority |
| --- | --- | --- | --- | --- |
| Reconciliation automation | Implemented with profiles, exceptions, audits, and manifests. | Use as standard operating workflow. | Need formal SOP and staff training materials. | High |
| Manual exception review | Candidate reports, checklists, proposed transfer creation, and delta audit exist. | Every manual edit is traceable and approved. | Approval owner and review threshold are undefined. | High |
| InitialBalances readiness | Clean imports generated only when control checks pass. | Imports are also verified after Lunchtab upload. | Post-import acceptance check is outside current process. | Medium |
| Profile governance | Profiles can be created, duplicated, imported, exported, and validated. | Profiles have owners, naming conventions, review cycles, and test evidence. | Governance process is not documented. | High |
| Data retention and privacy | Source files are unchanged; manifests avoid row-level data; generated CSVs contain sensitive data. | Outputs stored and disposed according to approved policy. | Retention, approved storage, and sharing rules are open. | High |
| Metrics and reporting | Per-run counts and summaries exist. | Ongoing trend reporting across runs and venues. | No aggregate metrics repository or dashboard is implemented. | Medium |
| Release management | Build script, installer script, checksum guidance, and release checklist exist. | Repeatable release with upgrade and rollback documentation. | Rollback/support procedure is not explicit. | Medium |
| Direct system integration | File-based import/export. | Optional integration if business wants less manual export/import. | No Odin or Lunchtab API integration is implemented. | Low |
| Operational support | Tests and diagnostics exist. | Clear triage path for blocked runs and app errors. | Support ownership and escalation path are open. | Medium |

## Capability Gaps

1. SOP gap: README is user guidance, but it is not a role-based operational procedure with approvals and retention steps.
2. Governance gap: Matching profile changes can materially affect financial outputs, so they need business ownership.
3. Measurement gap: The project has run summaries but no longitudinal business performance record.
4. Control gap: Application control totals stop unsafe files, but final human approval and post-import verification are outside the code.
5. Privacy gap: The application limits log and manifest exposure, but generated operational artifacts still require storage controls.

## Recommended Closure Actions

| Gap | Recommended action |
| --- | --- |
| SOP | Create a one-page runbook for reconciliation, manual review, InitialBalances, and final import. |
| Profile governance | Define profile owner, approval process, test pack requirement, and change log. |
| Manual approval | Require reviewer sign-off for high-severity manual reconciliation deltas. |
| Metrics | Capture run date, profile, total rows, accepted matches, manual-review exceptions, blocked reasons, operator handling time, and post-import corrections. |
| Privacy | Define approved storage location, retention period, and sharing rules for generated artifacts and crosswalk exports. |
| Support | Document common blocked reasons and escalation path. |