upload-income-statements

To upload confirmed income statement CSVs into ReturnPro, run the upload command with an absolute file path and a month in YYYY-MM format. The Skill validates account codes against dim_account before writing the data as authoritative confirmed records.

Yes, you can append or replace confirmed month data when loading income statements. Use the optional replace flag during the CSV upload to fully overwrite existing confirmed records for that specific month or append new rows.

Yes, you need the RETURNPRO_SUPABASE_URL and RETURNPRO_SUPABASE_SERVICE_KEY environment variables configured. These credentials allow the Skill to connect to Supabase, validate account codes against the account dimension, and write to confirmed_income_statements.

The best way to compare staged versus confirmed income statement data is to run the upload command, which automatically performs a quick staged-versus-confirmed accuracy check and logs activity so analysts can act on data quality issues immediately.

If your NetSuite export contains invalid account codes, the validated ingestion process halts the CSV upload. The Skill parses rows and validates account codes against the account dimension to ensure confirmed GL rows are accurate before insertion.

You need to use the YYYY-MM format whenever you upload a confirmed income statement CSV. This month parameter directs the replace-or-upsert behavior, ensuring the validated data writes to the correct monthly partition in the confirmed_income_statements table.