Requirements from a meeting (BRD)
Project → ERP implementation Workshop → Procure-to-Pay Status → Draft
Record a requirements workshop and StepReel fills this document: every requirement with an ID, priority and acceptance criteria, plus decisions, open questions and action items — so nothing said in the meeting is missed.
| ID | Requirement | Type | Priority | Raised by | Acceptance criteria |
|---|---|---|---|---|---|
| REQ-001 | Invoices above 50,000 need Finance manager approval | Functional | Must | Finance lead | Invoice over the limit routes to the Finance manager |
| REQ-002 | Block duplicate invoice numbers per supplier | Functional | Must | AP supervisor | Duplicate number gives an error |
| REQ-003 | Weekly report of invoices on hold | Report | Should | AP supervisor | Report lists hold name, amount and age |
3 requirements captured — 2 Must.
| # | Question | Owner | Needed by |
|---|---|---|---|
| 1 | Which bank file format is used? | Treasury | TBC |
| # | Action | Owner | Due |
|---|---|---|---|
| 1 | Send current approval matrix | Finance lead | TBC |
| Role | Name | Date | Signature |
|---|---|---|---|
| Business owner | |||
| Process owner | |||
| Functional consultant | |||
| Project manager |
| Version | Status | Approved by | Date |
|---|---|---|---|
| 0.1 | Draft | — | — |