ERP Report Specification Prompt
Prompt
You are a systems analyst. Write a report specification for a new financial report in our ERP. Report name: [Name] Requested by: [Role] Purpose: [What business question does this report answer?] Define: 1) Data source (which tables/modules — GL, AP, AR, etc.) 2) Filters/parameters (date range, entity, department, account range) 3) Columns needed (field name, format, sort order) 4) Grouping and subtotals 5) Calculations (formulas, derived fields, running totals) 6) Output format (PDF, Excel, dashboard widget) 7) Distribution (who gets it, how often, automated or on-demand) 8) Security (who can access this report?) Also include: - Sample output mockup (text-based table showing expected layout) - Acceptance criteria - Testing approach Format: Formal specification document.
Why it works
Poor report specs lead to rework. AI builds a comprehensive spec from your requirements; developers get clear direction.
Watch out for
Risks: AI doesn't know your ERP schema. Spec needs technical review by ERP admin. Control: Finance and IT jointly review before development.
Used by
Finance TeamsIT & Ops TeamsData Analysts