ERP HRM · WORD DOCUMENT VIEW · V1.0c

عرض الـUser Stories بنفس ملف الـWord

طريقة عرض إضافية لا تستبدل التحليل الحالي: اختر الإدارة ثم الـEpic، وستظهر كل القصص تحته بنفس ترتيب الصفوف وألوان المصدر.

العودة للتحليل الفني

171 Story معتمدة في V1.0c2 إضافة نظام خارج الملف1 · 3 · 5 Epics مذكورة في سجل تحديث V1.0c

الإدارةEpic / Module

EPIC DOCUMENT · كل القصص في صفحة واحدة

Payees

0 من المصدر المعتمد

User StoryDescriptionAcceptance CriteriaField ValidationJourneyScenarios

SAME DOCUMENT LAYOUT

· As a Finance User, I want to bulk-add payees to the chart of accounts, so that accounting linkage is efficient.

Payees

Payee-BulkToTree-006Canonical SRS Graph

· As a Finance User, I want to bulk-add payees to the chart of accounts, so that accounting linkage is efficient.

User Story

· As a Finance User, I want to bulk-add payees to the chart of accounts, so that accounting linkage is efficient.

طبقًا للمصدر الأساسي ERP_SRS: · As a Finance User, I want to bulk-add payees to the chart of accounts, so that accounting linkage is efficient.

Description

طبقًا للمصدر الأساسي ERP_SRS: · As a Finance User, I want to bulk-add payees to the chart of accounts, so that accounting linkage is efficient.

Acceptance Criteria

· Route: GET /payees/add-payees-to-tree?ids[]={id}. Permission: payeesToTree_Payee.
· Triggered by Add To Tree button on index; collects checked row-checkbox payee ids.
· Requires FinanceCategory for App\Payee entity; warns if category missing.
· Calls Helper::addToTree for each selected payee.

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Requester	User Reference	Yes	Active user and immutable from client
Item or Service	Reference	Yes	Active, branch-enabled and purchasable
Quantity	Decimal(18,4)	Yes	Positive, valid UOM precision and within request limits
Unit of Measure	Reference	Yes	Linked to item with a valid conversion
Needed By	Date	Yes	Not in the past and respects lead time
Budget or Cost Center	Reference	Yes	Active, in scope and has available budget or explicit override

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Finance User سيناريو Bulk Add Payees to Chart of Accounts ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: · Route: GET /payees/add-payees-to-tree?ids[]={id}. Permission: payeesToTree_Payee.
ERP_SRS acceptance test: · Triggered by Add To Tree button on index; collects checked row-checkbox payee ids.
ERP_SRS acceptance test: · Requires FinanceCategory for App\Payee entity; warns if category missing.
ERP_SRS acceptance test: · Calls Helper::addToTree for each selected payee.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

· As a Procurement Officer, I want a calendar of payee contract payments, so that payment dates are visible.

Payees

Payee-Calendar-007Canonical SRS Graph

· As a Procurement Officer, I want a calendar of payee contract payments, so that payment dates are visible.

User Story

· As a Procurement Officer, I want a calendar of payee contract payments, so that payment dates are visible.

طبقًا للمصدر الأساسي ERP_SRS: · As a Procurement Officer, I want a calendar of payee contract payments, so that payment dates are visible.

Description

طبقًا للمصدر الأساسي ERP_SRS: · As a Procurement Officer, I want a calendar of payee contract payments, so that payment dates are visible.

Acceptance Criteria

· Route: GET /payees/calender. Permission: calender_Payee.
· AJAX returns ContractPaymentResource for payee contracts between start/end dates.
· View: payees.contractcalender.
· Accessible from Options menu on payees index.

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Requester	User Reference	Yes	Active user and immutable from client
Item or Service	Reference	Yes	Active, branch-enabled and purchasable
Quantity	Decimal(18,4)	Yes	Positive, valid UOM precision and within request limits
Unit of Measure	Reference	Yes	Linked to item with a valid conversion
Needed By	Date	Yes	Not in the past and respects lead time
Budget or Cost Center	Reference	Yes	Active, in scope and has available budget or explicit override

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Procurement Officer سيناريو View Payee Contract Payment Calendar ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: · Route: GET /payees/calender. Permission: calender_Payee.
ERP_SRS acceptance test: · AJAX returns ContractPaymentResource for payee contracts between start/end dates.
ERP_SRS acceptance test: · View: payees.contractcalender.
ERP_SRS acceptance test: · Accessible from Options menu on payees index.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

· As a Procurement Officer, I want to create a payee, so that I can register a new supplier.

Payees

Payee-Create-002Canonical SRS Graph

· As a Procurement Officer, I want to create a payee, so that I can register a new supplier.

User Story

· As a Procurement Officer, I want to create a payee, so that I can register a new supplier.

طبقًا للمصدر الأساسي ERP_SRS: · As a Procurement Officer, I want to create a payee, so that I can register a new supplier.

Description

طبقًا للمصدر الأساسي ERP_SRS: · As a Procurement Officer, I want to create a payee, so that I can register a new supplier.

Acceptance Criteria

· Route: GET /payees/create (create_Payee), POST /payees/store (store_Payee).
· Form uses StorePayeeRequest validation; phones formatted E164 via libphonenumber.
· Expense items loaded dynamically by type via GET api/payee/getExpenseItems.
· Optional add_to_tree triggers Helper::addAccountToTree; expense items attached via payeeRelatedExpenseItems.
· Contacts created as ContactPerson rows when provided.
· On success redirects to payees.index with success message.
Create Payee - field dictionary

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Requester	User Reference	Yes	Active user and immutable from client
Item or Service	Reference	Yes	Active, branch-enabled and purchasable
Quantity	Decimal(18,4)	Yes	Positive, valid UOM precision and within request limits
Unit of Measure	Reference	Yes	Linked to item with a valid conversion
Needed By	Date	Yes	Not in the past and respects lead time
Budget or Cost Center	Reference	Yes	Active, in scope and has available budget or explicit override

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Procurement Officer سيناريو Create Payee ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: · Route: GET /payees/create (create_Payee), POST /payees/store (store_Payee).
ERP_SRS acceptance test: · Form uses StorePayeeRequest validation; phones formatted E164 via libphonenumber.
ERP_SRS acceptance test: · Expense items loaded dynamically by type via GET api/payee/getExpenseItems.
ERP_SRS acceptance test: · Optional add_to_tree triggers Helper::addAccountToTree; expense items attached via payeeRelatedExpenseItems.
ERP_SRS acceptance test: · Contacts created as ContactPerson rows when provided.
ERP_SRS acceptance test: · On success redirects to payees.index with success message.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

· As a Procurement Officer, I want to delete a payee, so that obsolete suppliers are removed.

Payees

Payee-Delete-005Canonical SRS Graph

· As a Procurement Officer, I want to delete a payee, so that obsolete suppliers are removed.

User Story

· As a Procurement Officer, I want to delete a payee, so that obsolete suppliers are removed.

طبقًا للمصدر الأساسي ERP_SRS: · As a Procurement Officer, I want to delete a payee, so that obsolete suppliers are removed.

Description

طبقًا للمصدر الأساسي ERP_SRS: · As a Procurement Officer, I want to delete a payee, so that obsolete suppliers are removed.

Acceptance Criteria

· Route: DELETE /payees/destroy/{id}. Permission: destroy_Payee.
· Authorizes destroy_Payee policy; soft deletes payee.
· Blocked when FutureBill exists for payee (has_related_bill message).
· Delete action hidden in dropdown when payee.has_financial_transactions is true.

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Requester	User Reference	Yes	Active user and immutable from client
Item or Service	Reference	Yes	Active, branch-enabled and purchasable
Quantity	Decimal(18,4)	Yes	Positive, valid UOM precision and within request limits
Unit of Measure	Reference	Yes	Linked to item with a valid conversion
Needed By	Date	Yes	Not in the past and respects lead time
Budget or Cost Center	Reference	Yes	Active, in scope and has available budget or explicit override

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Procurement Officer سيناريو Delete Payee ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: · Route: DELETE /payees/destroy/{id}. Permission: destroy_Payee.
ERP_SRS acceptance test: · Authorizes destroy_Payee policy; soft deletes payee.
ERP_SRS acceptance test: · Blocked when FutureBill exists for payee (has_related_bill message).
ERP_SRS acceptance test: · Delete action hidden in dropdown when payee.has_financial_transactions is true.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

· As a Finance User, I want an extended payee export from Quick Control Panel, so that full payee fields are available.

Payees

Payee-ExportExtended-013Canonical SRS Graph

· As a Finance User, I want an extended payee export from Quick Control Panel, so that full payee fields are available.

User Story

· As a Finance User, I want an extended payee export from Quick Control Panel, so that full payee fields are available.

طبقًا للمصدر الأساسي ERP_SRS: · As a Finance User, I want an extended payee export from Quick Control Panel, so that full payee fields are available.

Description

طبقًا للمصدر الأساسي ERP_SRS: · As a Finance User, I want an extended payee export from Quick Control Panel, so that full payee fields are available.

Acceptance Criteria

· Route: GET /quick-control-panel/payees-export. Permission: payeesExport_Quick.
· QuickController@payeesExport exports all payees via FastExcel.
· Includes bilingual names and extended contact/address fields.
Extended export - column dictionary

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Requester	User Reference	Yes	Active user and immutable from client
Item or Service	Reference	Yes	Active, branch-enabled and purchasable
Quantity	Decimal(18,4)	Yes	Positive, valid UOM precision and within request limits
Unit of Measure	Reference	Yes	Linked to item with a valid conversion
Needed By	Date	Yes	Not in the past and respects lead time
Budget or Cost Center	Reference	Yes	Active, in scope and has available budget or explicit override

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Finance User سيناريو Extended Payee Export (Quick Panel) ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: · Route: GET /quick-control-panel/payees-export. Permission: payeesExport_Quick.
ERP_SRS acceptance test: · QuickController@payeesExport exports all payees via FastExcel.
ERP_SRS acceptance test: · Includes bilingual names and extended contact/address fields.
ERP_SRS acceptance test: Extended export - column dictionary

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

· As a Procurement Officer, I want a simple Excel export, so that I can share basic payee data.

Payees

Payee-ExportSimple-012Canonical SRS Graph

· As a Procurement Officer, I want a simple Excel export, so that I can share basic payee data.

User Story

· As a Procurement Officer, I want a simple Excel export, so that I can share basic payee data.

طبقًا للمصدر الأساسي ERP_SRS: · As a Procurement Officer, I want a simple Excel export, so that I can share basic payee data.

Description

طبقًا للمصدر الأساسي ERP_SRS: · As a Procurement Officer, I want a simple Excel export, so that I can share basic payee data.

Acceptance Criteria

· Route: GET /payees/export with current filter query params. Permission: export_Payee.
· Uses Payee::filter(request)->get(); exports via SelectTemplateExport.
· Respects active index filters from request.
Simple export - column dictionary

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Requester	User Reference	Yes	Active user and immutable from client
Item or Service	Reference	Yes	Active, branch-enabled and purchasable
Quantity	Decimal(18,4)	Yes	Positive, valid UOM precision and within request limits
Unit of Measure	Reference	Yes	Linked to item with a valid conversion
Needed By	Date	Yes	Not in the past and respects lead time
Budget or Cost Center	Reference	Yes	Active, in scope and has available budget or explicit override

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Procurement Officer سيناريو Simple Payee Excel Export ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: · Route: GET /payees/export with current filter query params. Permission: export_Payee.
ERP_SRS acceptance test: · Uses Payee::filter(request)->get(); exports via SelectTemplateExport.
ERP_SRS acceptance test: · Respects active index filters from request.
ERP_SRS acceptance test: Simple export - column dictionary

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

· As a Procurement Officer, I want to manage payee file attachments, so that documents are stored centrally.

Payees

Payee-Files-009Canonical SRS Graph

· As a Procurement Officer, I want to manage payee file attachments, so that documents are stored centrally.

User Story

· As a Procurement Officer, I want to manage payee file attachments, so that documents are stored centrally.

طبقًا للمصدر الأساسي ERP_SRS: · As a Procurement Officer, I want to manage payee file attachments, so that documents are stored centrally.

Description

طبقًا للمصدر الأساسي ERP_SRS: · As a Procurement Officer, I want to manage payee file attachments, so that documents are stored centrally.

Acceptance Criteria

· Routes: GET /payees/{id}/files (index_File), /files/create (create_File), /files/edit/{file_id} (edit_File), /files/{file_id}/versions (indexAll_File).
· Accessible from Actions dropdown when index_File permission granted.
· FileController shared across modules.

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Requester	User Reference	Yes	Active user and immutable from client
Item or Service	Reference	Yes	Active, branch-enabled and purchasable
Quantity	Decimal(18,4)	Yes	Positive, valid UOM precision and within request limits
Unit of Measure	Reference	Yes	Linked to item with a valid conversion
Needed By	Date	Yes	Not in the past and respects lead time
Budget or Cost Center	Reference	Yes	Active, in scope and has available budget or explicit override

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Procurement Officer سيناريو Manage Payee Files ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: · Routes: GET /payees/{id}/files (index_File), /files/create (create_File), /files/edit/{file_id} (edit_File), /files/{file_id}/versions (indexAll_File).
ERP_SRS acceptance test: · Accessible from Actions dropdown when index_File permission granted.
ERP_SRS acceptance test: · FileController shared across modules.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

· As a Procurement Officer, I want to filter payees, so that I can find suppliers by criteria.

Payees

Payee-Filter-008Canonical SRS Graph

· As a Procurement Officer, I want to filter payees, so that I can find suppliers by criteria.

User Story

· As a Procurement Officer, I want to filter payees, so that I can find suppliers by criteria.

طبقًا للمصدر الأساسي ERP_SRS: · As a Procurement Officer, I want to filter payees, so that I can find suppliers by criteria.

Description

طبقًا للمصدر الأساسي ERP_SRS: · As a Procurement Officer, I want to filter payees, so that I can find suppliers by criteria.

Acceptance Criteria

· Filter panel on index: payee_filters (with contract/payment/supply/canceled/postpaid), industry_id, payee_job_title_id, expense_item_id, type, filter_by_date, date_from, date_to.
· Industry filter uses industry_id FK on Payee model.
· Expense item filter uses payeeRelatedExpenseItems relation.
· Client-side validation prevents date_to before date_from via SweetAlert.
· Filters persist via query string and paginate appends.

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Requester	User Reference	Yes	Active user and immutable from client
Item or Service	Reference	Yes	Active, branch-enabled and purchasable
Quantity	Decimal(18,4)	Yes	Positive, valid UOM precision and within request limits
Unit of Measure	Reference	Yes	Linked to item with a valid conversion
Needed By	Date	Yes	Not in the past and respects lead time
Budget or Cost Center	Reference	Yes	Active, in scope and has available budget or explicit override

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Procurement Officer سيناريو Filter Payees List ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: · Filter panel on index: payee_filters (with contract/payment/supply/canceled/postpaid), industry_id, payee_job_title_id, expense_item_id, type, filter_by_date, date_from, date_to.
ERP_SRS acceptance test: · Industry filter uses industry_id FK on Payee model.
ERP_SRS acceptance test: · Expense item filter uses payeeRelatedExpenseItems relation.
ERP_SRS acceptance test: · Client-side validation prevents date_to before date_from via SweetAlert.
ERP_SRS acceptance test: · Filters persist via query string and paginate appends.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

· As a Procurement Officer, I want to view the payees list, so that I can browse and manage suppliers.

Payees

Payee-List-001Canonical SRS Graph

· As a Procurement Officer, I want to view the payees list, so that I can browse and manage suppliers.

User Story

· As a Procurement Officer, I want to view the payees list, so that I can browse and manage suppliers.

طبقًا للمصدر الأساسي ERP_SRS: · As a Procurement Officer, I want to view the payees list, so that I can browse and manage suppliers.

Description

طبقًا للمصدر الأساسي ERP_SRS: · As a Procurement Officer, I want to view the payees list, so that I can browse and manage suppliers.

Acceptance Criteria

· Route: GET /payees. Permission: index_Payee.
· Paginated list (default 25 per page) with Payee::filter() for industry, job title, expense item, type, contract filters, and date range.
· Columns permission-gated: To Tree checkbox, Name, Email, Tax Card, Phone, Type, Expense Items, Industry, Contacts, Job Title, Details, Added To Tree, Show, Actions.
· Breadcrumb: Home → Purchases → Payees.
· Toolbar: Add (create_Payee), Options dropdown (calendar, new contract, industries, bills, job titles, Excel menu).
· Bulk Add To Tree button visible; row checkboxes for payees not yet in chart of accounts.
· Empty state shows not_found image when no records.

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Requester	User Reference	Yes	Active user and immutable from client
Item or Service	Reference	Yes	Active, branch-enabled and purchasable
Quantity	Decimal(18,4)	Yes	Positive, valid UOM precision and within request limits
Unit of Measure	Reference	Yes	Linked to item with a valid conversion
Needed By	Date	Yes	Not in the past and respects lead time
Budget or Cost Center	Reference	Yes	Active, in scope and has available budget or explicit override

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Procurement Officer سيناريو View Payees List ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: · Route: GET /payees. Permission: index_Payee.
ERP_SRS acceptance test: · Paginated list (default 25 per page) with Payee::filter() for industry, job title, expense item, type, contract filters, and date range.
ERP_SRS acceptance test: · Columns permission-gated: To Tree checkbox, Name, Email, Tax Card, Phone, Type, Expense Items, Industry, Contacts, Job Title, Details, Added To Tree, Show, Actions.
ERP_SRS acceptance test: · Breadcrumb: Home → Purchases → Payees.
ERP_SRS acceptance test: · Toolbar: Add (create_Payee), Options dropdown (calendar, new contract, industries, bills, job titles, Excel menu).
ERP_SRS acceptance test: · Bulk Add To Tree button visible; row checkboxes for payees not yet in chart of accounts.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

· As a Procurement Officer, I want to manage payee reminders, so that follow-ups are tracked.

Payees

Payee-Reminders-010Canonical SRS Graph

· As a Procurement Officer, I want to manage payee reminders, so that follow-ups are tracked.

User Story

· As a Procurement Officer, I want to manage payee reminders, so that follow-ups are tracked.

طبقًا للمصدر الأساسي ERP_SRS: · As a Procurement Officer, I want to manage payee reminders, so that follow-ups are tracked.

Description

طبقًا للمصدر الأساسي ERP_SRS: · As a Procurement Officer, I want to manage payee reminders, so that follow-ups are tracked.

Acceptance Criteria

· Route: GET /reminders?type=Payee&id={payee_id}. Permission: index_Reminder.
· Accessible from Actions dropdown on payee row.
· Reminder module shared; scoped to Payee entity type.

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Requester	User Reference	Yes	Active user and immutable from client
Item or Service	Reference	Yes	Active, branch-enabled and purchasable
Quantity	Decimal(18,4)	Yes	Positive, valid UOM precision and within request limits
Unit of Measure	Reference	Yes	Linked to item with a valid conversion
Needed By	Date	Yes	Not in the past and respects lead time
Budget or Cost Center	Reference	Yes	Active, in scope and has available budget or explicit override

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Procurement Officer سيناريو Manage Payee Reminders ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: · Route: GET /reminders?type=Payee&id={payee_id}. Permission: index_Reminder.
ERP_SRS acceptance test: · Accessible from Actions dropdown on payee row.
ERP_SRS acceptance test: · Reminder module shared; scoped to Payee entity type.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

· As a Procurement Officer, I want to view payee details, so that I can review linked procurement data.

Payees

Payee-Show-004Canonical SRS Graph

· As a Procurement Officer, I want to view payee details, so that I can review linked procurement data.

User Story

· As a Procurement Officer, I want to view payee details, so that I can review linked procurement data.

طبقًا للمصدر الأساسي ERP_SRS: · As a Procurement Officer, I want to view payee details, so that I can review linked procurement data.

Description

طبقًا للمصدر الأساسي ERP_SRS: · As a Procurement Officer, I want to view payee details, so that I can review linked procurement data.

Acceptance Criteria

· Route: GET /payees/show/{id}. Permission: show_Payee.
· Loads contracts, bills, offers, purchase invoices, industry, contacts, expense items.
· View: payees.show - summary hub for payee-related records.
· Opened from list Show eye icon (show_payees.index) in new tab.

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Requester	User Reference	Yes	Active user and immutable from client
Item or Service	Reference	Yes	Active, branch-enabled and purchasable
Quantity	Decimal(18,4)	Yes	Positive, valid UOM precision and within request limits
Unit of Measure	Reference	Yes	Linked to item with a valid conversion
Needed By	Date	Yes	Not in the past and respects lead time
Budget or Cost Center	Reference	Yes	Active, in scope and has available budget or explicit override

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Procurement Officer سيناريو View Payee Detail Hub ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: · Route: GET /payees/show/{id}. Permission: show_Payee.
ERP_SRS acceptance test: · Loads contracts, bills, offers, purchase invoices, industry, contacts, expense items.
ERP_SRS acceptance test: · View: payees.show - summary hub for payee-related records.
ERP_SRS acceptance test: · Opened from list Show eye icon (show_payees.index) in new tab.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

· As a Procurement Officer, I want to edit a payee, so that supplier data stays accurate.

Payees

Payee-Update-003Canonical SRS Graph

· As a Procurement Officer, I want to edit a payee, so that supplier data stays accurate.

User Story

· As a Procurement Officer, I want to edit a payee, so that supplier data stays accurate.

طبقًا للمصدر الأساسي ERP_SRS: · As a Procurement Officer, I want to edit a payee, so that supplier data stays accurate.

Description

طبقًا للمصدر الأساسي ERP_SRS: · As a Procurement Officer, I want to edit a payee, so that supplier data stays accurate.

Acceptance Criteria

· Route: GET /payees/edit/{id} (edit_Payee), PUT /payees/update (update_Payee).
· Preloads expense items filtered by payee type; preselects payeeRelatedExpenseItems ids.
· Replaces all contacts on update (delete then recreate).
· Syncs expense items: deletes PayeeRelatedExpenseItem rows then re-attaches.
· Uses same StorePayeeRequest validation as create.
Edit Payee - field dictionary

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Requester	User Reference	Yes	Active user and immutable from client
Item or Service	Reference	Yes	Active, branch-enabled and purchasable
Quantity	Decimal(18,4)	Yes	Positive, valid UOM precision and within request limits
Unit of Measure	Reference	Yes	Linked to item with a valid conversion
Needed By	Date	Yes	Not in the past and respects lead time
Budget or Cost Center	Reference	Yes	Active, in scope and has available budget or explicit override

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Procurement Officer سيناريو Edit Payee ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: · Route: GET /payees/edit/{id} (edit_Payee), PUT /payees/update (update_Payee).
ERP_SRS acceptance test: · Preloads expense items filtered by payee type; preselects payeeRelatedExpenseItems ids.
ERP_SRS acceptance test: · Replaces all contacts on update (delete then recreate).
ERP_SRS acceptance test: · Syncs expense items: deletes PayeeRelatedExpenseItem rows then re-attaches.
ERP_SRS acceptance test: · Uses same StorePayeeRequest validation as create.
ERP_SRS acceptance test: Edit Payee - field dictionary

Alternative Path

—

Edge Cases

—

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Requester

User Reference

Yes

Active user and immutable from client

Item or Service

Reference

Yes

Active, branch-enabled and purchasable

Quantity

Decimal(18,4)

Yes

Positive, valid UOM precision and within request limits

Unit of Measure

Reference

Yes

Linked to item with a valid conversion

Needed By

Date

Yes

Not in the past and respects lead time

Budget or Cost Center

Reference

Yes

Active, in scope and has available budget or explicit override

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Requester

User Reference

Yes

Active user and immutable from client

Item or Service

Reference

Yes

Active, branch-enabled and purchasable

Quantity

Decimal(18,4)

Yes

Positive, valid UOM precision and within request limits

Unit of Measure

Reference

Yes

Linked to item with a valid conversion

Needed By

Date

Yes

Not in the past and respects lead time

Budget or Cost Center

Reference

Yes

Active, in scope and has available budget or explicit override

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Requester

User Reference

Yes

Active user and immutable from client

Item or Service

Reference

Yes

Active, branch-enabled and purchasable

Quantity

Decimal(18,4)

Yes

Positive, valid UOM precision and within request limits

Unit of Measure

Reference

Yes

Linked to item with a valid conversion

Needed By

Date

Yes

Not in the past and respects lead time

Budget or Cost Center

Reference

Yes

Active, in scope and has available budget or explicit override

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Requester

User Reference

Yes

Active user and immutable from client

Item or Service

Reference

Yes

Active, branch-enabled and purchasable

Quantity

Decimal(18,4)

Yes

Positive, valid UOM precision and within request limits

Unit of Measure

Reference

Yes

Linked to item with a valid conversion

Needed By

Date

Yes

Not in the past and respects lead time

Budget or Cost Center

Reference

Yes

Active, in scope and has available budget or explicit override

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Requester

User Reference

Yes

Active user and immutable from client

Item or Service

Reference

Yes

Active, branch-enabled and purchasable

Quantity

Decimal(18,4)

Yes

Positive, valid UOM precision and within request limits

Unit of Measure

Reference

Yes

Linked to item with a valid conversion

Needed By

Date

Yes

Not in the past and respects lead time

Budget or Cost Center

Reference

Yes

Active, in scope and has available budget or explicit override

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Requester

User Reference

Yes

Active user and immutable from client

Item or Service

Reference

Yes

Active, branch-enabled and purchasable

Quantity

Decimal(18,4)

Yes

Positive, valid UOM precision and within request limits

Unit of Measure

Reference

Yes

Linked to item with a valid conversion

Needed By

Date

Yes

Not in the past and respects lead time

Budget or Cost Center

Reference

Yes

Active, in scope and has available budget or explicit override

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Requester

User Reference

Yes

Active user and immutable from client

Item or Service

Reference

Yes

Active, branch-enabled and purchasable

Quantity

Decimal(18,4)

Yes

Positive, valid UOM precision and within request limits

Unit of Measure

Reference

Yes

Linked to item with a valid conversion

Needed By

Date

Yes

Not in the past and respects lead time

Budget or Cost Center

Reference

Yes

Active, in scope and has available budget or explicit override

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Requester

User Reference

Yes

Active user and immutable from client

Item or Service

Reference

Yes

Active, branch-enabled and purchasable

Quantity

Decimal(18,4)

Yes

Positive, valid UOM precision and within request limits

Unit of Measure

Reference

Yes

Linked to item with a valid conversion

Needed By

Date

Yes

Not in the past and respects lead time

Budget or Cost Center

Reference

Yes

Active, in scope and has available budget or explicit override

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Requester

User Reference

Yes

Active user and immutable from client

Item or Service

Reference

Yes

Active, branch-enabled and purchasable

Quantity

Decimal(18,4)

Yes

Positive, valid UOM precision and within request limits

Unit of Measure

Reference

Yes

Linked to item with a valid conversion

Needed By

Date

Yes

Not in the past and respects lead time

Budget or Cost Center

Reference

Yes

Active, in scope and has available budget or explicit override

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Requester

User Reference

Yes

Active user and immutable from client

Item or Service

Reference

Yes

Active, branch-enabled and purchasable

Quantity

Decimal(18,4)

Yes

Positive, valid UOM precision and within request limits

Unit of Measure

Reference

Yes

Linked to item with a valid conversion

Needed By

Date

Yes

Not in the past and respects lead time

Budget or Cost Center

Reference

Yes

Active, in scope and has available budget or explicit override

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Requester

User Reference

Yes

Active user and immutable from client

Item or Service

Reference

Yes

Active, branch-enabled and purchasable

Quantity

Decimal(18,4)

Yes

Positive, valid UOM precision and within request limits

Unit of Measure

Reference

Yes

Linked to item with a valid conversion

Needed By

Date

Yes

Not in the past and respects lead time

Budget or Cost Center

Reference

Yes

Active, in scope and has available budget or explicit override

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Requester

User Reference

Yes

Active user and immutable from client

Item or Service

Reference

Yes

Active, branch-enabled and purchasable

Quantity

Decimal(18,4)

Yes

Positive, valid UOM precision and within request limits

Unit of Measure

Reference

Yes

Linked to item with a valid conversion

Needed By

Date

Yes

Not in the past and respects lead time

Budget or Cost Center

Reference

Yes

Active, in scope and has available budget or explicit override

جاري تجهيز مساحة العمل