Subledger-to-GL Reconciliation Copy link

🚨 Blitz data = Excel worksheet UDFs, not MCP tools/connectors. Extract data only by writing =br_...() into a cell (via execute_office_js) and reading the spill — never tool_search for br_*, never refresh_mcp_connectors, and never conclude "no Oracle EBS / Blitz connector is set up" (the Blitz Report add-in is an Excel add-in, not an MCP connector, so it never appears in the connector list — its absence there is expected). Load the extraction mechanism first: read_skill("br-run-reports").

Performance: Read br-analytics-standards at the start of every run (read_skill("br-analytics-standards")). All pipeline steps must follow those rules. Target runtime: under 7 minutes for single-module, under 20 minutes for orchestrations.

Tie each subledger to its GL control account in one workbook and surface the variances. You own orchestration, the tie-out, and the verdict; br-run-reports does extraction and br-data-dashboard the build. Run steps in order, keeping intermediate sheets.

Requires: br-run-reports, br-data-dashboard.

Division of responsibility — READ FIRST

You do NOT run Blitz reports yourself. All extraction is done by br-run-reports (connection, auth, async run, completion, cell population). Never call br_* functions, and never rename/read/sum the result sheet or start analysis until extraction is confirmed complete. This skill is read-only: it reconciles and reports; it changes nothing.

When to use

"Reconcile AP/AR/INV/FA to GL", subledger-to-GL tie-out, control-account differences, period-end recon.

Inputs

• Ledger (required); Period; optional: which subledgers to include (default AP, AR, INV, FA).

Reports used (authoritative names — do NOT broad-search for them)

These exact report names are known. When you ask br-run-reports to run one, pass the documented name directly — do NOT run a br_report_list_external discovery search first. Inspect parameters only if you need an exact LOV spelling. Fallback: only if a run returns #BLITZ_REPORT_NOT_FOUND (the instance renamed it, or the module isn't installed) do a name search.

CONFIG

Subledger → source report → GL control account

Materiality / RAG

• Green — every included subledger ties within the materiality threshold (ask the user; default 0).
• Amber — a variance within a small tolerance the user accepts.
• Red — any variance over materiality.

Output sheets & tab order (left to right)

Subledger_GL_Recon (first), then one sheet per subledger (AP_TB, AR_GL, INV_Value, FA_Reserve), GL balance sheet last.

Pipeline

1. Extract — DELEGATE. For each included subledger, br-run-reports runs its source report (CONFIG) for the Ledger+Period, plus "GL Trial Balance Detail" for the GL control balances. Wait for each; do nothing mid-run.
2. Anchor & tie-out (single execute_office_js call). In one call: read each subledger's ending balance and the matching GL control balance (the reconciliation anchor for the final step), compute variance = subledger − GL per subledger, and classify per CONFIG materiality. Trust formula_results from the write call. No re-read needed here.
3. Scorecard (single execute_office_js call) (delegate to br-data-dashboard if it fires; else build inline). Write all sections to Subledger_GL_Recon in one call: the tie-out table (subledger, subledger balance, GL balance, variance, status), the RAG banner, and the worst-variance highlight.
   • Build mechanics (learned on a real run): build on a NEW sheet at position 0 (first tab); leave each report on the sheet br-run-reports created (its report name) — do NOT rename it, the dashboard links to it. Do NOT use a multi-row copyToRange to fill formula rows (it can latch onto the wrong source box and duplicate headers into the data) — write each row's formula explicitly. After building, scan beyond the dashboard's column range, clear any stray cells, and widen amount columns so values don't render as ######.
4. Narrative (single set_cell_range call). Write all ≤5 bullets in one call: which subledgers tie, which don't, the largest variance and where to look.
5. Arrange tabs + final validation (single execute_office_js call + one read). In one call: reorder tabs per CONFIG and make Subledger_GL_Recon active. Only after the scorecard. Then do the one permitted verification read: confirm each scorecard subledger/GL balance equals the Step-2 anchor.

Validation

Each variance = its subledger balance − its GL balance; Red only if a variance exceeds materiality. If a subledger's control account mapping is unknown on the instance, say so rather than reporting a false tie.