Department Anomaly Scan — GL Miscoding Cleanup
Scans your workspace for GL-to-department coding anomalies — expenses hitting the wrong cost center, vendors consistently miscoded, accounts landing in unexpected departments. Surfaces patterns and generates a NetSuite reclass CSV journal entry to fix them.
Scans your workspace for GL-to-department coding anomalies — expenses hitting the wrong cost center, vendors consistently miscoded, accounts landing in unexpected departments. Surfaces patterns and generates a NetSuite reclass CSV journal entry to fix them.
Before You Begin
- Numeric MCP connected.
- Numeric Toolkit installed.
- An income statement report with a department pivot (or access to build one ad-hoc).
- Access to transaction-line drill-down.
Default anomaly rules are tuned to a hardware/software company (80xxxx = R&D, 70xxxx = S&M, 670xxx = G&A). Claude adapts to your actual department structure based on the report data.
How It Works
- Ask Claude to scan. Example prompts:
- "Scan for department anomalies."
- "Find GL miscodings."
- "Anything miscoded this period?"
- "Run a department audit."
- Claude lists available IS reports; you pick one (or choose ad-hoc).
- Claude validates the report has department data; if not, asks for a different report.
- Claude applies anomaly rules — GL ranges vs expected departments, new large items ($0 last month → >$10K this month), extreme variance (>500% MoM), round-number manual JEs.
- Claude drills into transaction lines on flagged rows to confirm root cause (card default, accrual template, manual JE).
- Claude generates a balanced NetSuite CSV with debit-correct-dept, credit-wrong-dept entries.
What You Get
- Anomaly table in chat — flagged account × department combinations with drill-down notes
- NetSuite CSV file: External IDs
RECLASS-YYYY-MM-NNN, one JE per anomaly - Verification: programmatic DR = CR balance check per JE with PASS/FAIL status
- Entries flagged
[REVIEW W/ MGMT]where intent is ambiguous (e.g. PR spend under CEO)
Default anomaly rules:
Troubleshooting
FAQ
- Does this skill work on any company? Yes — the skill reads department names from your report and adapts, but you should review the flags with domain context. Update the skill with your adjustments.
- Can I scope to one account or department? Yes — "scan 70xxxx accounts only" or "Marketing department only."
- Does it post the JE? No — CSV only. Import via NetSuite's JE Import Assistant.
- Vendor-level analysis? Yes — ad-hoc mode with
pivots: ["Department", "Vendor"]. - Audit trail? Line memos reference the original JE number when the anomaly traces to a specific entry.
- What period does it scan? The most recent closed period by default. You can point it at another period if needed.
Download & Install
Download the full Numeric Toolkit (15 community skills, including this one):
Install via Claude Code CLI:
/plugin marketplace add geoff-lew/numeric-toolkit
/plugin install numeric-mcp-toolkit
Or drop the .skill directory into ~/.claude/skills/ manually. Once installed, just describe what you need — the skill activates automatically.
Need help? Reach out to support@numeric.io.
Related use cases
.png)
Computes standard financial ratios from Numeric report data and layers them inline on your source statement. Covers profitability, covenant/liquidity/solvency, and operational/working-capital metrics — margins, EBITDA, current ratio, DSO, DPO, DIO, and more.
.png)
Pulls outstanding journal entry tasks from your Numeric close checklist, reads the supporting workbook or documentation, generates balanced journal entries, marks the task complete in Numeric, and posts directly to NetSuite. From checklist task to posted entry — no manual steps in between.
.png)
Scans your workspace for GL-to-department coding anomalies — expenses hitting the wrong cost center, vendors consistently miscoded, accounts landing in unexpected departments. Surfaces patterns and generates a NetSuite reclass CSV journal entry to fix them.