upload-netsuite

Upload NetSuite XLSM and CSV financial exports into ReturnPro staging tables.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/clenisa/optimal-cli --skill upload-netsuite
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upload-netsuite
Source: https://github.com/clenisa/optimal-cli/tree/main/skills/upload-netsuite
Command: npx skills add https://github.com/clenisa/optimal-cli --skill upload-netsuite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates ingestion of NetSuite financial exports into ReturnPro staging to eliminate manual parsing, mapping, and inconsistent staging data that slow FP&A workflows.

Core Features & Use Cases

  • Format detection: Auto-detects XLSM/XLSX versus CSV and handles multi-sheet XLSM workbooks with monthly tabs.
  • Parsing & validation: Converts rows to account_code, account_name, amount, period, and source_file, and validates account codes against dim_account.
  • Safe staging: Batch upserts into stg_financials_raw with optional dry-run and activity logging for traceability.
  • Use Case: Ingest a quarterly multi-tab NetSuite workbook or a single-month CSV to prepare data for budget projections and anomaly detection.

Quick Start

Run optimal upload-netsuite with the --file path and optional --month to parse and load a NetSuite XLSM or CSV into ReturnPro staging, using --dry-run to validate without writing.

Frequently Asked Questions about upload-netsuite

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upload NetSuite XLSM exports into staging tables?

You can upload NetSuite XLSM exports by running the tool with your file path, which auto-detects multi-sheet workbooks with monthly tabs and batch-upserts parsed rows into staging tables.

What is the best way to parse NetSuite CSV financial exports for FP&A workflows?

The best way to parse NetSuite CSV financial exports is using automated format detection that extracts account codes, names, amounts, and periods, then validates account codes against dim_account before loading.

Can I validate NetSuite financial data before writing it to the staging database?

Yes, you can validate NetSuite financial data before writing by using the dry-run flag, which checks account codes against dim_account and parses rows without executing the batch upsert into stg_financials_raw.

Does this tool support multi-sheet XLSM workbooks with monthly tabs?

Yes, it supports multi-sheet XLSM workbooks with monthly tabs by auto-detecting the file format and parsing each sheet to extract account_code, account_name, amount, period, and source_file data.

How does account code validation work during NetSuite financial ingestion?

Account code validation works by checking parsed NetSuite export rows against the dim_account table during ingestion, ensuring only valid codes are batch-upserted into stg_financials_raw.