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

Safes

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

User StoryDescriptionAcceptance CriteriaField ValidationJourneyScenarios

SAME DOCUMENT LAYOUT

As a Finance User, I want clear safe balance definitions, so that I can correctly understand available money and financial impact.

Safes

Safe-Balance-007Canonical SRS Graph

As a Finance User, I want clear safe balance definitions, so that I can correctly understand available money and financial impact.

User Story

As a Finance User, I want clear safe balance definitions, so that I can correctly understand available money and financial impact.

طبقًا للمصدر الأساسي ERP_SRS: As a Finance User, I want clear safe balance definitions, so that I can correctly understand available money and financial impact.

Description

طبقًا للمصدر الأساسي ERP_SRS: As a Finance User, I want clear safe balance definitions, so that I can correctly understand available money and financial impact.

Acceptance Criteria

Actual Balance represents physically or operationally available money in the safe before reservation holds.
Reserved Amount represents active remaining Cash Reservations linked to this safe.
Available Balance = Actual Balance - Active Reserved Amount.
Financial Custody creation decreases actual safe balance because money leaves the safe.
Custody expense creation/update does not affect safe balance.
Custody refund increases actual safe balance.
Cash Reservation creation/approval decreases available balance only, not actual balance.
Cash Reservation release increases available balance only.
Payment without custody or reservation follows normal safe deduction rules.
Credit Card safe balance follows credit limit, used amount, paid amount, outstanding, and available credit rules.

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 Balance Definitions ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: Actual Balance represents physically or operationally available money in the safe before reservation holds.
ERP_SRS acceptance test: Reserved Amount represents active remaining Cash Reservations linked to this safe.
ERP_SRS acceptance test: Available Balance = Actual Balance - Active Reserved Amount.
ERP_SRS acceptance test: Financial Custody creation decreases actual safe balance because money leaves the safe.
ERP_SRS acceptance test: Custody expense creation/update does not affect safe balance.
ERP_SRS acceptance test: Custody refund increases actual safe balance.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As an Admin or Finance Manager, I want to create a safe, so that financial operations can be linked to a controlled cash account.

Safes

Safe-Create-003Canonical SRS Graph

As an Admin or Finance Manager, I want to create a safe, so that financial operations can be linked to a controlled cash account.

User Story

As an Admin or Finance Manager, I want to create a safe, so that financial operations can be linked to a controlled cash account.

طبقًا للمصدر الأساسي ERP_SRS: As an Admin or Finance Manager, I want to create a safe, so that financial operations can be linked to a controlled cash account.

Description

طبقًا للمصدر الأساسي ERP_SRS: As an Admin or Finance Manager, I want to create a safe, so that financial operations can be linked to a controlled cash account.

Acceptance Criteria

Name English, name Arabic, type, payment type, currency, start date and start point rules are required, also Responsible person.
The system validates unique safe names per company/branch where applicable.
Initial balance must be numeric and cannot be negative unless business configuration explicitly allows overdraft.
New safe status defaults to Active unless created as inactive by permission.
Safe is available for financial operations only when status is Active.
The safe serial number is generated automatically using the Core Serial Number Configuration module.
A responsible person is required on safe creation and will be used as the default recipient for safe notifications.
Minimum available balance alert, large IN transaction alert threshold, and large OUT transaction alert threshold are optional safe-level notification settings and should be added in the Create/Edit Safe form, not removed from the notification logic.
The serial number must be unique and visible on the safe list, details, transactions, imports, and related source references.
Create / Edit safe — 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
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

ينفذ Admin or Finance Manager سيناريو Create Safe ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: Name English, name Arabic, type, payment type, currency, start date and start point rules are required, also Responsible person.
ERP_SRS acceptance test: The system validates unique safe names per company/branch where applicable.
ERP_SRS acceptance test: Initial balance must be numeric and cannot be negative unless business configuration explicitly allows overdraft.
ERP_SRS acceptance test: New safe status defaults to Active unless created as inactive by permission.
ERP_SRS acceptance test: Safe is available for financial operations only when status is Active.
ERP_SRS acceptance test: The safe serial number is generated automatically using the Core Serial Number Configuration module.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As an Admin, I want to delete unused safes, so that invalid or test records can be removed safely.

Safes

Safe-Delete-005Canonical SRS Graph

As an Admin, I want to delete unused safes, so that invalid or test records can be removed safely.

User Story

As an Admin, I want to delete unused safes, so that invalid or test records can be removed safely.

طبقًا للمصدر الأساسي ERP_SRS: As an Admin, I want to delete unused safes, so that invalid or test records can be removed safely.

Description

طبقًا للمصدر الأساسي ERP_SRS: As an Admin, I want to delete unused safes, so that invalid or test records can be removed safely.

Acceptance Criteria

Delete is allowed only if the safe has no transactions and no linked financial records.
Delete is blocked if the safe is linked to Financial Custody, Cash Reservation, Credit Card repayment, Company Expense, Purchase Invoice, public bill payment, payee bill payment, or journal/payment movement.
If delete is blocked, the system displays a clear message and suggests deactivation.
Credit Card safe delete rules must follow CreditCardSafe-Delete-003 when type is Credit Card.

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

ينفذ Admin سيناريو Delete Safe with Blocking Rules ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: Delete is allowed only if the safe has no transactions and no linked financial records.
ERP_SRS acceptance test: Delete is blocked if the safe is linked to Financial Custody, Cash Reservation, Credit Card repayment, Company Expense, Purchase Invoice, public bill payment, payee bill payment, or journal/payment movement.
ERP_SRS acceptance test: If delete is blocked, the system displays a clear message and suggests deactivation.
ERP_SRS acceptance test: Credit Card safe delete rules must follow CreditCardSafe-Delete-003 when type is Credit Card.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a Finance Manager, I want to list safes with filters and totals, so that I can monitor cash availability and balance health.

Safes

Safe-List-001Canonical SRS Graph

As a Finance Manager, I want to list safes with filters and totals, so that I can monitor cash availability and balance health.

User Story

As a Finance Manager, I want to list safes with filters and totals, so that I can monitor cash availability and balance health.

طبقًا للمصدر الأساسي ERP_SRS: As a Finance Manager, I want to list safes with filters and totals, so that I can monitor cash availability and balance health.

Description

طبقًا للمصدر الأساسي ERP_SRS: As a Finance Manager, I want to list safes with filters and totals, so that I can monitor cash availability and balance health.

Acceptance Criteria

Filter by name, type, payment type, currency, status, and date range (from / to).
Show columns including safe name, type, payment type, currency, actual balance, reserved amount, available balance, status and action buttons.
Available balance must consider active Cash Reservations when the safe supports reservations.
Credit Card safes must show credit limit, used amount, paid amount, outstanding, and available credit when applicable.
Inactive safes remain visible for audit but cannot be used in new financial operations.
Users can open safe details, transactions, edit, or delete according to permissions and blocking rules.
The list page must display summary cards such as total actual balance, total reserved amount, total available balance, and totals by currency.
Summary cards must change dynamically based on the selected filters.

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 سيناريو View and Monitor Safes ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: Filter by name, type, payment type, currency, status, and date range (from / to).
ERP_SRS acceptance test: Show columns including safe name, type, payment type, currency, actual balance, reserved amount, available balance, status and action buttons.
ERP_SRS acceptance test: Available balance must consider active Cash Reservations when the safe supports reservations.
ERP_SRS acceptance test: Credit Card safes must show credit limit, used amount, paid amount, outstanding, and available credit when applicable.
ERP_SRS acceptance test: Inactive safes remain visible for audit but cannot be used in new financial operations.
ERP_SRS acceptance test: Users can open safe details, transactions, edit, or delete according to permissions and blocking rules.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a Finance Manager, I want safe-related notifications based on the safe responsible person and optional threshold configuration, so that balance issues and critical movements are handled on time by the correct user.

Safes

Safe-Notification-010Canonical SRS Graph

As a Finance Manager, I want safe-related notifications based on the safe responsible person and optional threshold configuration, so that balance issues and critical movements are handled on time by the correct user.

User Story

طبقًا للمصدر الأساسي ERP_SRS: As a Finance Manager, I want safe-related notifications based on the safe responsible person and optional threshold configuration, so that balance issues and critical movements are handled on time by the correct user.

Description

Acceptance Criteria

The responsible person is required on safe creation and is the default recipient for safe notifications.
Notify the responsible person and configured recipients when the safe available balance falls below the configured minimum available balance threshold, if this threshold is configured for the safe.
Notify the responsible person and configured recipients when a Cash Reservation causes the safe available balance to fall below the configured minimum available balance threshold, if configured.
Notify card holders for Credit Card payment due reminders according to Epic-3 rules.
Notify relevant users on large IN or OUT transactions when the transaction amount reaches the configured IN / OUT transaction threshold, if configured. If notification thresholds are not configured, the system must not send threshold-based alerts and should continue only with standard safe and credit card notifications. Notification recipients must be driven by the safe responsible person, additional configured recipients, and permission/configuration rules, not hardcoded users.

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 سيناريو Safe Balance and Transaction Notifications ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: The responsible person is required on safe creation and is the default recipient for safe notifications.
ERP_SRS acceptance test: Notify the responsible person and configured recipients when the safe available balance falls below the configured minimum available balance threshold, if this threshold is configured for the safe.
ERP_SRS acceptance test: Notify the responsible person and configured recipients when a Cash Reservation causes the safe available balance to fall below the configured minimum available balance threshold, if configured.
ERP_SRS acceptance test: Notify card holders for Credit Card payment due reminders according to Epic-3 rules.
ERP_SRS acceptance test: Notify relevant users on large IN or OUT transactions when the transaction amount reaches the configured IN / OUT transaction threshold, if configured. If notification thresholds are not configured, the system must not send threshold-based alerts and should continue only with standard safe and credit card notifications. Notification recipients must be driven by the safe responsible person, additional configured recipients, and permission/configuration rules, not hardcoded users.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As an Admin, I want safe statuses to control usage, so that inactive or blocked safes cannot be used incorrectly.

Safes

Safe-Status-009Canonical SRS Graph

As an Admin, I want safe statuses to control usage, so that inactive or blocked safes cannot be used incorrectly.

User Story

As an Admin, I want safe statuses to control usage, so that inactive or blocked safes cannot be used incorrectly.

طبقًا للمصدر الأساسي ERP_SRS: As an Admin, I want safe statuses to control usage, so that inactive or blocked safes cannot be used incorrectly.

Description

طبقًا للمصدر الأساسي ERP_SRS: As an Admin, I want safe statuses to control usage, so that inactive or blocked safes cannot be used incorrectly.

Acceptance Criteria

Allowed statuses are Active and Inactive by default is active; additional statuses may be configured if needed.
Only Active safes appear in new financial operation dropdowns.
Inactive safes remain visible in history and reports.
A safe cannot be deactivated if there are unresolved operational dependencies unless policy allows it with warning.
Expired Credit Card safes block new expenses but allow repayments according to Credit Card Safe rules.

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

ينفذ Admin سيناريو Control Safe Statuses and Usage Rules ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: Allowed statuses are Active and Inactive by default is active; additional statuses may be configured if needed.
ERP_SRS acceptance test: Only Active safes appear in new financial operation dropdowns.
ERP_SRS acceptance test: Inactive safes remain visible in history and reports.
ERP_SRS acceptance test: A safe cannot be deactivated if there are unresolved operational dependencies unless policy allows it with warning.
ERP_SRS acceptance test: Expired Credit Card safes block new expenses but allow repayments according to Credit Card Safe rules.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a Finance User, I want to view all safe transactions, so that I can audit all cash movements and related sources.

Safes

Safe-Transactions-006Canonical SRS Graph

As a Finance User, I want to view all safe transactions, so that I can audit all cash movements and related sources.

User Story

As a Finance User, I want to view all safe transactions, so that I can audit all cash movements and related sources.

طبقًا للمصدر الأساسي ERP_SRS: As a Finance User, I want to view all safe transactions, so that I can audit all cash movements and related sources.

Description

طبقًا للمصدر الأساسي ERP_SRS: As a Finance User, I want to view all safe transactions, so that I can audit all cash movements and related sources.

Acceptance Criteria

The transaction page is accessible from a safe list and safe details.
Filter by type, direction, source type, user, receiver/payer, date range, Filter By (related by date range), and currency.
Display total IN, total OUT, and net movement for selected filters.
Transaction table shows direction, transaction type, source, receiver/payer, user, creation date, amount, currency, payment type, safe, and notes.
Cash Reservation approval/release does not create actual safe transactions, but consumption through payment may reference the reservation.
Financial Custody creation creates OUT from safe; custody refund creates IN to safe.
Custody expenses must not create additional safe OUT transactions to avoid double deduction.
Transaction columns

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 سيناريو View Safe Transactions ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: The transaction page is accessible from a safe list and safe details.
ERP_SRS acceptance test: Filter by type, direction, source type, user, receiver/payer, date range, Filter By (related by date range), and currency.
ERP_SRS acceptance test: Display total IN, total OUT, and net movement for selected filters.
ERP_SRS acceptance test: Transaction table shows direction, transaction type, source, receiver/payer, user, creation date, amount, currency, payment type, safe, and notes.
ERP_SRS acceptance test: Cash Reservation approval/release does not create actual safe transactions, but consumption through payment may reference the reservation.
ERP_SRS acceptance test: Financial Custody creation creates OUT from safe; custody refund creates IN to safe.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a Finance Manager, I want to edit safe information, so that corrections can be reflected without breaking financial history.

Safes

Safe-Update-004Canonical SRS Graph

As a Finance Manager, I want to edit safe information, so that corrections can be reflected without breaking financial history.

User Story

As a Finance Manager, I want to edit safe information, so that corrections can be reflected without breaking financial history.

طبقًا للمصدر الأساسي ERP_SRS: As a Finance Manager, I want to edit safe information, so that corrections can be reflected without breaking financial history.

Description

طبقًا للمصدر الأساسي ERP_SRS: As a Finance Manager, I want to edit safe information, so that corrections can be reflected without breaking financial history.

Acceptance Criteria

Name, notes, status, responsible person, reservation flag, and notification threshold settings can be edited according to permission.
Currency cannot be changed if the safe has any transaction, custody, reservation, repayment, company expense, or purchase invoice linked to it.
Type and payment type cannot be changed if the safe has financial movements.
Initial balance cannot be edited after the safe has transactions unless an opening balance adjustment flow is used.
If the safe is inactive, it cannot be selected in new payments, reservations, custodies, imports, or repayments.
Credit Card safe edit rules must follow CreditCardSafe-Update-002 when type is Credit Card.

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 سيناريو Edit Safe with Financial Constraints ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: Name, notes, status, responsible person, reservation flag, and notification threshold settings can be edited according to permission.
ERP_SRS acceptance test: Currency cannot be changed if the safe has any transaction, custody, reservation, repayment, company expense, or purchase invoice linked to it.
ERP_SRS acceptance test: Type and payment type cannot be changed if the safe has financial movements.
ERP_SRS acceptance test: Initial balance cannot be edited after the safe has transactions unless an opening balance adjustment flow is used.
ERP_SRS acceptance test: If the safe is inactive, it cannot be selected in new payments, reservations, custodies, imports, or repayments.
ERP_SRS acceptance test: Credit Card safe edit rules must follow CreditCardSafe-Update-002 when type is Credit Card.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a Finance User, I want to view a safe details page, so that I can understand its balances, transactions, and related reservations.

Safes

Safe-View-002Canonical SRS Graph

As a Finance User, I want to view a safe details page, so that I can understand its balances, transactions, and related reservations.

User Story

As a Finance User, I want to view a safe details page, so that I can understand its balances, transactions, and related reservations.

طبقًا للمصدر الأساسي ERP_SRS: As a Finance User, I want to view a safe details page, so that I can understand its balances, transactions, and related reservations.

Description

طبقًا للمصدر الأساسي ERP_SRS: As a Finance User, I want to view a safe details page, so that I can understand its balances, transactions, and related reservations.

Acceptance Criteria

The safe details page displays safe information, type, payment type, currency, status, and notes.
Balance summary displays actual balance, reserved amount, available balance, total IN, and total OUT.
If the safe is Credit Card type, display credit limit, used amount, paid amount, outstanding, and available credit.
Display active Cash Reservations linked to this safe.
Display latest transactions with a link to the full transactions page.
Safe details become read-only when the user does not have edit permission or when blocking rules apply.

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 سيناريو View Safe Details and Balance Summary ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: The safe details page displays safe information, type, payment type, currency, status, and notes.
ERP_SRS acceptance test: Balance summary displays actual balance, reserved amount, available balance, total IN, and total OUT.
ERP_SRS acceptance test: If the safe is Credit Card type, display credit limit, used amount, paid amount, outstanding, and available credit.
ERP_SRS acceptance test: Display active Cash Reservations linked to this safe.
ERP_SRS acceptance test: Display latest transactions with a link to the full transactions page.
ERP_SRS acceptance test: Safe details become read-only when the user does not have edit permission or when blocking rules apply.

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

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

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