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 · كل القصص في صفحة واحدة

Financial Impact

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

User StoryDescriptionAcceptance CriteriaField ValidationJourneyScenarios

SAME DOCUMENT LAYOUT

As a General Accounting user, I want expenses and invoices with a linked chart of accounts to wait for GA approval, so that accounting entries are validated before payment.

Financial Impact

IMPCT-Accounting-GA-006Canonical SRS Graph

As a General Accounting user, I want expenses and invoices with a linked chart of accounts to wait for GA approval, so that accounting entries are validated before payment.

User Story

As a General Accounting user, I want expenses and invoices with a linked chart of accounts to wait for GA approval, so that accounting entries are validated before payment.

طبقًا للمصدر الأساسي ERP_SRS: As a General Accounting user, I want expenses and invoices with a linked chart of accounts to wait for GA approval, so that accounting entries are validated before payment.

Description

Acceptance Criteria

Accrual Journal Entry is created for expense/invoice.
Expense or invoice status becomes Pending by GA.
Rows do not appear in the Non-Cash Management unpaid tab until GA approves accrual.
After GA approval, status becomes Confirmed by GA and the row appears in the Unpaid tab.
Payment details move row to Ready to Pay and create payment JE pending GA if configured.
GA rejection at accrual stage sets record to Rejected by GA and hides it from payment tabs.

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
Amount	Decimal(18,4)	Yes	Greater than zero, within approval limit and currency precision
Currency	Reference	Yes	Active currency enabled for the company
Exchange Rate	Decimal(18,8)	Yes	Positive, effective on transaction date; overrides require permission and reason
Transaction Date	Date	Yes	Must belong to an open fiscal period and not exceed close date
Reason	Text 3..1000	Yes	Trimmed length 3–1000 with unsafe markup rejected

Dropdown / Select Options (DDL)

—

User Journey

ينفذ General Accounting user سيناريو Apply GA Approval Workflow for Linked Chart of Accounts ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: Accrual Journal Entry is created for expense/invoice.
ERP_SRS acceptance test: Expense or invoice status becomes Pending by GA.
ERP_SRS acceptance test: Rows do not appear in the Non-Cash Management unpaid tab until GA approves accrual.
ERP_SRS acceptance test: After GA approval, status becomes Confirmed by GA and the row appears in the Unpaid tab.
ERP_SRS acceptance test: Payment details move row to Ready to Pay and create payment JE pending GA if configured.
ERP_SRS acceptance test: GA rejection at accrual stage sets record to Rejected by GA and hides it from payment tabs.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a General Accounting user or Finance User, I want expenses and invoices without a linked chart of accounts to proceed without GA approval, so that payment can continue based on normal non-cash flow.

Financial Impact

IMPCT-Accounting-GA-006-01Canonical SRS Graph

As a General Accounting user or Finance User, I want expenses and invoices without a linked chart of accounts to proceed without GA approval, so that payment can continue based on normal non-cash flow.

User Story

طبقًا للمصدر الأساسي ERP_SRS: As a General Accounting user or Finance User, I want expenses and invoices without a linked chart of accounts to proceed without GA approval, so that payment can continue based on normal non-cash flow.

Description

Acceptance Criteria

Created expense/invoice status becomes Pending.
The record appears in the Non-Cash Management unpaid tab.
Finance users can add payment details.
Row moves to Ready to Pay.
Finance users can mark paid, then status becomes Closed/Paid.

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
Amount	Decimal(18,4)	Yes	Greater than zero, within approval limit and currency precision
Currency	Reference	Yes	Active currency enabled for the company
Exchange Rate	Decimal(18,8)	Yes	Positive, effective on transaction date; overrides require permission and reason
Transaction Date	Date	Yes	Must belong to an open fiscal period and not exceed close date
Reason	Text 3..1000	Yes	Trimmed length 3–1000 with unsafe markup rejected

Dropdown / Select Options (DDL)

—

User Journey

ينفذ General Accounting user or Finance User سيناريو Apply Unlinked Chart of Accounts Flow ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: Created expense/invoice status becomes Pending.
ERP_SRS acceptance test: The record appears in the Non-Cash Management unpaid tab.
ERP_SRS acceptance test: Finance users can add payment details.
ERP_SRS acceptance test: Row moves to Ready to Pay.
ERP_SRS acceptance test: Finance users can mark paid, then status becomes Closed/Paid.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As the System, I want to create accounting journal entries for financial operations, so that accounting traceability is maintained.

Financial Impact

IMPCT-Accounting-JournalEntries-007Canonical SRS Graph

As the System, I want to create accounting journal entries for financial operations, so that accounting traceability is maintained.

User Story

As the System, I want to create accounting journal entries for financial operations, so that accounting traceability is maintained.

طبقًا للمصدر الأساسي ERP_SRS: As the System, I want to create accounting journal entries for financial operations, so that accounting traceability is maintained.

Description

طبقًا للمصدر الأساسي ERP_SRS: As the System, I want to create accounting journal entries for financial operations, so that accounting traceability is maintained.

Acceptance Criteria

Accrual JE must be created when applicable during expense/invoice import or conversion.
Payment JE must be created before a record is marked as paid in flows requiring accounting entry.
The system must maintain an audit trail of JE creation, status, and approval.
Failures in JE creation must prevent marking the record as paid and return clear row-level errors during import.
Finance users can mark paid, then status becomes Closed/Paid.

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
Amount	Decimal(18,4)	Yes	Greater than zero, within approval limit and currency precision
Currency	Reference	Yes	Active currency enabled for the company
Exchange Rate	Decimal(18,8)	Yes	Positive, effective on transaction date; overrides require permission and reason
Transaction Date	Date	Yes	Must belong to an open fiscal period and not exceed close date
Reason	Text 3..1000	Yes	Trimmed length 3–1000 with unsafe markup rejected

Dropdown / Select Options (DDL)

—

User Journey

ينفذ System سيناريو Create Accrual and Payment Journal Entries ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: Accrual JE must be created when applicable during expense/invoice import or conversion.
ERP_SRS acceptance test: Payment JE must be created before a record is marked as paid in flows requiring accounting entry.
ERP_SRS acceptance test: The system must maintain an audit trail of JE creation, status, and approval.
ERP_SRS acceptance test: Failures in JE creation must prevent marking the record as paid and return clear row-level errors during import.
ERP_SRS acceptance test: Finance users can mark paid, then status becomes Closed/Paid.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a Finance User, I want payment completion to depend on journal entry creation rather than GA approval when configured, so that bulk operations can proceed faster while keeping accounting traceability.

Financial Impact

IMPCT-Accounting-Payment-008Canonical SRS Graph

As a Finance User, I want payment completion to depend on journal entry creation rather than GA approval when configured, so that bulk operations can proceed faster while keeping accounting traceability.

User Story

طبقًا للمصدر الأساسي ERP_SRS: As a Finance User, I want payment completion to depend on journal entry creation rather than GA approval when configured, so that bulk operations can proceed faster while keeping accounting traceability.

Description

Acceptance Criteria

When configured, the system creates accrual JE and payment JE immediately.
Paid Date is required and saved.
Records can become Closed/Paid or Paid - JE Pending Approval without waiting for GA approval.
The system must never mark paid without creating required journal entries.
For custody-related records, no safe deduction occurs again; reserved custody balance is consumed instead.
For non-custody records, normal safe deduction applies.

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
Amount	Decimal(18,4)	Yes	Greater than zero, within approval limit and currency precision
Currency	Reference	Yes	Active currency enabled for the company
Exchange Rate	Decimal(18,8)	Yes	Positive, effective on transaction date; overrides require permission and reason
Transaction Date	Date	Yes	Must belong to an open fiscal period and not exceed close date
Reason	Text 3..1000	Yes	Trimmed length 3–1000 with unsafe markup rejected

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Finance User سيناريو Allow Payment Completion Based on JE Creation ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: When configured, the system creates accrual JE and payment JE immediately.
ERP_SRS acceptance test: Paid Date is required and saved.
ERP_SRS acceptance test: Records can become Closed/Paid or Paid - JE Pending Approval without waiting for GA approval.
ERP_SRS acceptance test: The system must never mark paid without creating required journal entries.
ERP_SRS acceptance test: For custody-related records, no safe deduction occurs again; reserved custody balance is consumed instead.
ERP_SRS acceptance test: For non-custody records, normal safe deduction applies.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a System, I want all financial modules to use consistent currency and exchange rate rules, so that balances and accounting remain correct.

Financial Impact

IMPCT-Currency-008Canonical SRS Graph

As a System, I want all financial modules to use consistent currency and exchange rate rules, so that balances and accounting remain correct.

User Story

As a System, I want all financial modules to use consistent currency and exchange rate rules, so that balances and accounting remain correct.

طبقًا للمصدر الأساسي ERP_SRS: As a System, I want all financial modules to use consistent currency and exchange rate rules, so that balances and accounting remain correct.

Description

طبقًا للمصدر الأساسي ERP_SRS: As a System, I want all financial modules to use consistent currency and exchange rate rules, so that balances and accounting remain correct.

Acceptance Criteria

Safes must have a valid active currency on creation.
Financial Custody stores currency and exchange rate and uses them for reporting and entries.
Cash Reservation stores currency and exchange rate when multi-currency is used.
Credit Card Safe outstanding is stored in card currency and journal entries are created in base currency when enabled.
Company Expenses and Purchase Invoices capture currency and exchange rate at creation/import time.
Payments between different currencies require captured exchange rate and auditable conversion.
Reports should show transaction amount and base currency amount when applicable.

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
Amount	Decimal(18,4)	Yes	Greater than zero, within approval limit and currency precision
Currency	Reference	Yes	Active currency enabled for the company
Exchange Rate	Decimal(18,8)	Yes	Positive, effective on transaction date; overrides require permission and reason
Transaction Date	Date	Yes	Must belong to an open fiscal period and not exceed close date
Reason	Text 3..1000	Yes	Trimmed length 3–1000 with unsafe markup rejected

Dropdown / Select Options (DDL)

—

User Journey

ينفذ System سيناريو Impact on applying Currency Rules Across ERP Financial Modules ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: Safes must have a valid active currency on creation.
ERP_SRS acceptance test: Financial Custody stores currency and exchange rate and uses them for reporting and entries.
ERP_SRS acceptance test: Cash Reservation stores currency and exchange rate when multi-currency is used.
ERP_SRS acceptance test: Credit Card Safe outstanding is stored in card currency and journal entries are created in base currency when enabled.
ERP_SRS acceptance test: Company Expenses and Purchase Invoices capture currency and exchange rate at creation/import time.
ERP_SRS acceptance test: Payments between different currencies require captured exchange rate and auditable conversion.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

I want the system to correctly reflect the impact of custody issuance and expenses on the safe balance

Financial Impact

IMPCT-Custody-Balance-001Canonical SRS Graph

I want the system to correctly reflect the impact of custody issuance and expenses on the safe balance

User Story

I want the system to correctly reflect the impact of custody issuance and expenses on the safe balance

طبقًا للمصدر الأساسي ERP_SRS: I want the system to correctly reflect the impact of custody issuance and expenses on the safe balance

Description

طبقًا للمصدر الأساسي ERP_SRS: I want the system to correctly reflect the impact of custody issuance and expenses on the safe balance

Acceptance Criteria

1. Custody creation (disbursement from safe) - System deducts reserved balance from safe full total balance - Reserved balance is transferred to custody owner - Safe balance = full total − reserved - Custody total_expenses = 0 - Custody remaining = reserved
2. Custody expense creation / update - Must NOT affect safe balance - Must NOT affect reserved balance - System recalculates total_expenses and remaining
3. Custody remaining calculation - remaining = reserved − total_expenses - Represents unused employee-held funds
4. No double impact on safe - Expenses must NOT deduct from safe again - Safe must not be affected by expenses
5. Closing custody (refund scenario) - Create refund transaction (IN to safe) - Safe increases by remaining - Status = Closed - Remaining = 0
6. Closing custody (fully consumed) - No refund transaction - Safe unchanged - Status = Closed
7. Terminology clarification - Reserved balance = outside safe (employee-held) - Expenses = spending from custody

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
Amount	Decimal(18,4)	Yes	Greater than zero, within approval limit and currency precision
Currency	Reference	Yes	Active currency enabled for the company
Exchange Rate	Decimal(18,8)	Yes	Positive, effective on transaction date; overrides require permission and reason
Transaction Date	Date	Yes	Must belong to an open fiscal period and not exceed close date
Reason	Text 3..1000	Yes	Trimmed length 3–1000 with unsafe markup rejected
Custody Owner	Employee Reference	Yes	Active employee in scope and eligible for custody
Safe	Safe Reference	Yes	Active permitted safe with matching currency and sufficient balance
Start Date	Date	Yes	Must not exceed end date and must be in an allowed period
End Date	Date	Yes	On/after start date and within policy limit

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Business / System User سيناريو Custody Disbursement & Expense Impact on Safe Balance ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: 1. Custody creation (disbursement from safe) - System deducts reserved balance from safe full total balance - Reserved balance is transferred to custody owner - Safe balance = full total − reserved - Custody total_expenses = 0 - Custody remaining = reserved
ERP_SRS acceptance test: 2. Custody expense creation / update - Must NOT affect safe balance - Must NOT affect reserved balance - System recalculates total_expenses and remaining
ERP_SRS acceptance test: 3. Custody remaining calculation - remaining = reserved − total_expenses - Represents unused employee-held funds
ERP_SRS acceptance test: 4. No double impact on safe - Expenses must NOT deduct from safe again - Safe must not be affected by expenses
ERP_SRS acceptance test: 5. Closing custody (refund scenario) - Create refund transaction (IN to safe) - Safe increases by remaining - Status = Closed - Remaining = 0
ERP_SRS acceptance test: 6. Closing custody (fully consumed) - No refund transaction - Safe unchanged - Status = Closed

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

I want clear definitions for all custody and safe-related balances

Financial Impact

IMPCT-Custody-Balance-002Canonical SRS Graph

I want clear definitions for all custody and safe-related balances

User Story

I want clear definitions for all custody and safe-related balances

طبقًا للمصدر الأساسي ERP_SRS: I want clear definitions for all custody and safe-related balances

Description

طبقًا للمصدر الأساسي ERP_SRS: I want clear definitions for all custody and safe-related balances

Acceptance Criteria

1. Full total balance - Available money in safe - Decreases on custody creation - Increases on refund
2. Reserved balance - Money issued to employee - Considered outside safe - Fixed after creation
3. Expenses on custody - Total of all expenses - Includes approved and pending - Increases over time
4. Remaining amount - remaining = reserved − expenses - Decreases with expenses - Returned on closure if > 0
5. Relationship between values - Creation → safe decreases, reserved assigned - Expenses → safe unaffected, remaining decreases - Closure → remaining returned to safe
6. Important clarification - Reserved is outside safe - Expenses from custody not safe - Safe reflects actual available money

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
Amount	Decimal(18,4)	Yes	Greater than zero, within approval limit and currency precision
Currency	Reference	Yes	Active currency enabled for the company
Exchange Rate	Decimal(18,8)	Yes	Positive, effective on transaction date; overrides require permission and reason
Transaction Date	Date	Yes	Must belong to an open fiscal period and not exceed close date
Reason	Text 3..1000	Yes	Trimmed length 3–1000 with unsafe markup rejected
Custody Owner	Employee Reference	Yes	Active employee in scope and eligible for custody
Safe	Safe Reference	Yes	Active permitted safe with matching currency and sufficient balance
Start Date	Date	Yes	Must not exceed end date and must be in an allowed period
End Date	Date	Yes	On/after start date and within policy limit

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Business / System User سيناريو Balance Definitions & Terminology ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: 1. Full total balance - Available money in safe - Decreases on custody creation - Increases on refund
ERP_SRS acceptance test: 2. Reserved balance - Money issued to employee - Considered outside safe - Fixed after creation
ERP_SRS acceptance test: 3. Expenses on custody - Total of all expenses - Includes approved and pending - Increases over time
ERP_SRS acceptance test: 4. Remaining amount - remaining = reserved − expenses - Decreases with expenses - Returned on closure if > 0
ERP_SRS acceptance test: 5. Relationship between values - Creation → safe decreases, reserved assigned - Expenses → safe unaffected, remaining decreases - Closure → remaining returned to safe
ERP_SRS acceptance test: 6. Important clarification - Reserved is outside safe - Expenses from custody not safe - Safe reflects actual available money

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a Finance User, I want to select multiple Ready to Pay rows and mark them as paid, so that I can pay multiple company expenses or purchase invoices at once.

Financial Impact

IMPCT-NonCachManagment-Paid-003Canonical SRS Graph

As a Finance User, I want to select multiple Ready to Pay rows and mark them as paid, so that I can pay multiple company expenses or purchase invoices at once.

User Story

As a Finance User, I want to select multiple Ready to Pay rows and mark them as paid, so that I can pay multiple company expenses or purchase invoices at once.

طبقًا للمصدر الأساسي ERP_SRS: As a Finance User, I want to select multiple Ready to Pay rows and mark them as paid, so that I can pay multiple company expenses or purchase invoices at once.

Description

Acceptance Criteria

Add a checkbox before the ID column in the Ready to Pay table.
Users can select multiple rows across different safes.
Bulk Mark as Paid button appears only when at least one row is selected.
Each selected row is validated independently.
If one row fails, the system returns a clear error message per row without hiding successful results.
Paid rows status becomes Closed/Paid and payment date is updated.

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
Amount	Decimal(18,4)	Yes	Greater than zero, within approval limit and currency precision
Currency	Reference	Yes	Active currency enabled for the company
Exchange Rate	Decimal(18,8)	Yes	Positive, effective on transaction date; overrides require permission and reason
Transaction Date	Date	Yes	Must belong to an open fiscal period and not exceed close date
Reason	Text 3..1000	Yes	Trimmed length 3–1000 with unsafe markup rejected

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Finance User سيناريو Bulk Mark as Paid ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: Add a checkbox before the ID column in the Ready to Pay table.
ERP_SRS acceptance test: Users can select multiple rows across different safes.
ERP_SRS acceptance test: Bulk Mark as Paid button appears only when at least one row is selected.
ERP_SRS acceptance test: Each selected row is validated independently.
ERP_SRS acceptance test: If one row fails, the system returns a clear error message per row without hiding successful results.
ERP_SRS acceptance test: Paid rows status becomes Closed/Paid and payment date is updated.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a Finance User, I want the payment impact to depend on whether the record is custody-related, so that safe balances are not deducted twice.

Financial Impact

IMPCT-NonCachManagment-Safe-004Canonical SRS Graph

As a Finance User, I want the payment impact to depend on whether the record is custody-related, so that safe balances are not deducted twice.

User Story

As a Finance User, I want the payment impact to depend on whether the record is custody-related, so that safe balances are not deducted twice.

طبقًا للمصدر الأساسي ERP_SRS: As a Finance User, I want the payment impact to depend on whether the record is custody-related, so that safe balances are not deducted twice.

Description

طبقًا للمصدر الأساسي ERP_SRS: As a Finance User, I want the payment impact to depend on whether the record is custody-related, so that safe balances are not deducted twice.

Acceptance Criteria

If the row is related to Financial Custody, the amount is deducted from the custody reserved amount only.
Custody-related payment must not be deducted from the safe available balance again.
If the row is not related to Financial Custody, the amount is deducted from the related safe based on normal payment logic.
The system must validate available balance for non-custody rows before payment.
Payment ledger must clearly indicate source: custody-funded or safe-funded.

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
Amount	Decimal(18,4)	Yes	Greater than zero, within approval limit and currency precision
Currency	Reference	Yes	Active currency enabled for the company
Exchange Rate	Decimal(18,8)	Yes	Positive, effective on transaction date; overrides require permission and reason
Transaction Date	Date	Yes	Must belong to an open fiscal period and not exceed close date
Reason	Text 3..1000	Yes	Trimmed length 3–1000 with unsafe markup rejected

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Finance User سيناريو Apply Safe Deduction Rules by Source ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: If the row is related to Financial Custody, the amount is deducted from the custody reserved amount only.
ERP_SRS acceptance test: Custody-related payment must not be deducted from the safe available balance again.
ERP_SRS acceptance test: If the row is not related to Financial Custody, the amount is deducted from the related safe based on normal payment logic.
ERP_SRS acceptance test: The system must validate available balance for non-custody rows before payment.
ERP_SRS acceptance test: Payment ledger must clearly indicate source: custody-funded or safe-funded.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a Finance User, I want records to appear in the correct Non-Cash Management tabs, so that payment workflow is clear.

Financial Impact

IMPCT-NonCachManagment-Tabs-005Canonical SRS Graph

As a Finance User, I want records to appear in the correct Non-Cash Management tabs, so that payment workflow is clear.

User Story

As a Finance User, I want records to appear in the correct Non-Cash Management tabs, so that payment workflow is clear.

طبقًا للمصدر الأساسي ERP_SRS: As a Finance User, I want records to appear in the correct Non-Cash Management tabs, so that payment workflow is clear.

Description

طبقًا للمصدر الأساسي ERP_SRS: As a Finance User, I want records to appear in the correct Non-Cash Management tabs, so that payment workflow is clear.

Acceptance Criteria

Linked charts of accounts records do not appear unpaid before GA approval unless flexible payment approval rules create paid state directly.
After GA approval, records appear in the Unpaid tab.
Payment details move records to Ready to Pay.
Paid records move to Closed/Paid or paid history view.
Unlinked chart of accounts records appear in Unpaid immediately after creation.

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
Amount	Decimal(18,4)	Yes	Greater than zero, within approval limit and currency precision
Currency	Reference	Yes	Active currency enabled for the company
Exchange Rate	Decimal(18,8)	Yes	Positive, effective on transaction date; overrides require permission and reason
Transaction Date	Date	Yes	Must belong to an open fiscal period and not exceed close date
Reason	Text 3..1000	Yes	Trimmed length 3–1000 with unsafe markup rejected

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Finance User سيناريو Display Records in Correct Non-Cash Tabs ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: Linked charts of accounts records do not appear unpaid before GA approval unless flexible payment approval rules create paid state directly.
ERP_SRS acceptance test: After GA approval, records appear in the Unpaid tab.
ERP_SRS acceptance test: Payment details move records to Ready to Pay.
ERP_SRS acceptance test: Paid records move to Closed/Paid or paid history view.
ERP_SRS acceptance test: Unlinked chart of accounts records appear in Unpaid immediately after creation.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a Finance Manager, I want safe availability to consider cash reservations, so that payment decisions are based on real available liquidity.

Financial Impact

IMPCT-Safe-Reservation-008Canonical SRS Graph

As a Finance Manager, I want safe availability to consider cash reservations, so that payment decisions are based on real available liquidity.

User Story

As a Finance Manager, I want safe availability to consider cash reservations, so that payment decisions are based on real available liquidity.

طبقًا للمصدر الأساسي ERP_SRS: As a Finance Manager, I want safe availability to consider cash reservations, so that payment decisions are based on real available liquidity.

Description

طبقًا للمصدر الأساسي ERP_SRS: As a Finance Manager, I want safe availability to consider cash reservations, so that payment decisions are based on real available liquidity.

Acceptance Criteria

If a safe allows reservation, active reservations reduce available balance.
Draft, pending, rejected, cancelled, fully consumed, and released reservations do not increase active reserved amounts.
Payment validation should use available balance for non-custody and non-credit-card safe-funded payments when reservation control is enabled.
Reservation consumed through actual payment decreases actual balance and decreases remaining reserved amount.
The system must prevent double deduction between Cash Reservation consumption and normal payment transaction.
Safe list and safe details must show reservation breakdown or link to filtered reservation list.

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
Amount	Decimal(18,4)	Yes	Greater than zero, within approval limit and currency precision
Currency	Reference	Yes	Active currency enabled for the company
Exchange Rate	Decimal(18,8)	Yes	Positive, effective on transaction date; overrides require permission and reason
Transaction Date	Date	Yes	Must belong to an open fiscal period and not exceed close date
Reason	Text 3..1000	Yes	Trimmed length 3–1000 with unsafe markup rejected

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Finance Manager سيناريو Apply Cash Reservation Impact on Safe Availability (new) ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: If a safe allows reservation, active reservations reduce available balance.
ERP_SRS acceptance test: Draft, pending, rejected, cancelled, fully consumed, and released reservations do not increase active reserved amounts.
ERP_SRS acceptance test: Payment validation should use available balance for non-custody and non-credit-card safe-funded payments when reservation control is enabled.
ERP_SRS acceptance test: Reservation consumed through actual payment decreases actual balance and decreases remaining reserved amount.
ERP_SRS acceptance test: The system must prevent double deduction between Cash Reservation consumption and normal payment transaction.
ERP_SRS acceptance test: Safe list and safe details must show reservation breakdown or link to filtered reservation list.

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

Amount

Decimal(18,4)

Yes

Greater than zero, within approval limit and currency precision

Currency

Reference

Yes

Active currency enabled for the company

Exchange Rate

Decimal(18,8)

Yes

Positive, effective on transaction date; overrides require permission and reason

Transaction Date

Date

Yes

Must belong to an open fiscal period and not exceed close date

Reason

Text 3..1000

Yes

Trimmed length 3–1000 with unsafe markup rejected

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

Amount

Decimal(18,4)

Yes

Greater than zero, within approval limit and currency precision

Currency

Reference

Yes

Active currency enabled for the company

Exchange Rate

Decimal(18,8)

Yes

Positive, effective on transaction date; overrides require permission and reason

Transaction Date

Date

Yes

Must belong to an open fiscal period and not exceed close date

Reason

Text 3..1000

Yes

Trimmed length 3–1000 with unsafe markup rejected

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

Amount

Decimal(18,4)

Yes

Greater than zero, within approval limit and currency precision

Currency

Reference

Yes

Active currency enabled for the company

Exchange Rate

Decimal(18,8)

Yes

Positive, effective on transaction date; overrides require permission and reason

Transaction Date

Date

Yes

Must belong to an open fiscal period and not exceed close date

Reason

Text 3..1000

Yes

Trimmed length 3–1000 with unsafe markup rejected

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

Amount

Decimal(18,4)

Yes

Greater than zero, within approval limit and currency precision

Currency

Reference

Yes

Active currency enabled for the company

Exchange Rate

Decimal(18,8)

Yes

Positive, effective on transaction date; overrides require permission and reason

Transaction Date

Date

Yes

Must belong to an open fiscal period and not exceed close date

Reason

Text 3..1000

Yes

Trimmed length 3–1000 with unsafe markup rejected

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

Amount

Decimal(18,4)

Yes

Greater than zero, within approval limit and currency precision

Currency

Reference

Yes

Active currency enabled for the company

Exchange Rate

Decimal(18,8)

Yes

Positive, effective on transaction date; overrides require permission and reason

Transaction Date

Date

Yes

Must belong to an open fiscal period and not exceed close date

Reason

Text 3..1000

Yes

Trimmed length 3–1000 with unsafe markup rejected

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

Amount

Decimal(18,4)

Yes

Greater than zero, within approval limit and currency precision

Currency

Reference

Yes

Active currency enabled for the company

Exchange Rate

Decimal(18,8)

Yes

Positive, effective on transaction date; overrides require permission and reason

Transaction Date

Date

Yes

Must belong to an open fiscal period and not exceed close date

Reason

Text 3..1000

Yes

Trimmed length 3–1000 with unsafe markup rejected

Custody Owner

Employee Reference

Yes

Active employee in scope and eligible for custody

Safe

Safe Reference

Yes

Active permitted safe with matching currency and sufficient balance

Start Date

Date

Yes

Must not exceed end date and must be in an allowed period

End Date

Date

Yes

On/after start date and within policy limit

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

Amount

Decimal(18,4)

Yes

Greater than zero, within approval limit and currency precision

Currency

Reference

Yes

Active currency enabled for the company

Exchange Rate

Decimal(18,8)

Yes

Positive, effective on transaction date; overrides require permission and reason

Transaction Date

Date

Yes

Must belong to an open fiscal period and not exceed close date

Reason

Text 3..1000

Yes

Trimmed length 3–1000 with unsafe markup rejected

Custody Owner

Employee Reference

Yes

Active employee in scope and eligible for custody

Safe

Safe Reference

Yes

Active permitted safe with matching currency and sufficient balance

Start Date

Date

Yes

Must not exceed end date and must be in an allowed period

End Date

Date

Yes

On/after start date and within policy limit

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

Amount

Decimal(18,4)

Yes

Greater than zero, within approval limit and currency precision

Currency

Reference

Yes

Active currency enabled for the company

Exchange Rate

Decimal(18,8)

Yes

Positive, effective on transaction date; overrides require permission and reason

Transaction Date

Date

Yes

Must belong to an open fiscal period and not exceed close date

Reason

Text 3..1000

Yes

Trimmed length 3–1000 with unsafe markup rejected

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

Amount

Decimal(18,4)

Yes

Greater than zero, within approval limit and currency precision

Currency

Reference

Yes

Active currency enabled for the company

Exchange Rate

Decimal(18,8)

Yes

Positive, effective on transaction date; overrides require permission and reason

Transaction Date

Date

Yes

Must belong to an open fiscal period and not exceed close date

Reason

Text 3..1000

Yes

Trimmed length 3–1000 with unsafe markup rejected

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

Amount

Decimal(18,4)

Yes

Greater than zero, within approval limit and currency precision

Currency

Reference

Yes

Active currency enabled for the company

Exchange Rate

Decimal(18,8)

Yes

Positive, effective on transaction date; overrides require permission and reason

Transaction Date

Date

Yes

Must belong to an open fiscal period and not exceed close date

Reason

Text 3..1000

Yes

Trimmed length 3–1000 with unsafe markup rejected

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

Amount

Decimal(18,4)

Yes

Greater than zero, within approval limit and currency precision

Currency

Reference

Yes

Active currency enabled for the company

Exchange Rate

Decimal(18,8)

Yes

Positive, effective on transaction date; overrides require permission and reason

Transaction Date

Date

Yes

Must belong to an open fiscal period and not exceed close date

Reason

Text 3..1000

Yes

Trimmed length 3–1000 with unsafe markup rejected

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