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

Credit Card Safe

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

User StoryDescriptionAcceptance CriteriaField ValidationJourneyScenarios

SAME DOCUMENT LAYOUT

Defines behavior for expired credit cards.

Credit Card Safe

CreditCardSafe-CardValidity-013Canonical SRS Graph

Defines behavior for expired credit cards.

User Story

Defines behavior for expired credit cards.

طبقًا للمصدر الأساسي ERP_SRS: Defines behavior for expired credit cards.

Description

طبقًا للمصدر الأساسي ERP_SRS: Defines behavior for expired credit cards.

Acceptance Criteria

If expiry date < today:
Block new expenses using the card
Allow repayment operations only
The system must show a warning on the card details page.

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

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

Scenarios

ERP_SRS acceptance test: If expiry date < today:
ERP_SRS acceptance test: Block new expenses using the card
ERP_SRS acceptance test: Allow repayment operations only
ERP_SRS acceptance test: The system must show a warning on the card details page.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a finance user, I want to create a safe with type Credit Card from the Cash Management page, so that I can use it as a payment method for business expenses.

Credit Card Safe

CreditCardSafe-Create-001Canonical SRS Graph

As a finance user, I want to create a safe with type Credit Card from the Cash Management page, so that I can use it as a payment method for business expenses.

User Story

As a finance user, I want to create a safe with type Credit Card from the Cash Management page, so that I can use it as a payment method for business expenses.

طبقًا للمصدر الأساسي ERP_SRS: As a finance user, I want to create a safe with type Credit Card from the Cash Management page, so that I can use it as a payment method for business expenses.

Description

Acceptance Criteria

The safe creation page is accessible from the Cash Management page.
The user selects Type = Credit Card and Payment Type = Credit Card.
When Type = Credit Card is selected, the credit card specific fields appear on the creation form.
All required fields must be filled before the safe can be saved.
The saved credit card safe appears in the Cash Management safe list
Field Validations
Edit is available on a credit card safe only if no expenses have been recorded against it.
Once any expense has been made using the credit card safe, the Edit action is disabled and all fields are locked.

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

Scenarios

ERP_SRS acceptance test: The safe creation page is accessible from the Cash Management page.
ERP_SRS acceptance test: The user selects Type = Credit Card and Payment Type = Credit Card.
ERP_SRS acceptance test: When Type = Credit Card is selected, the credit card specific fields appear on the creation form.
ERP_SRS acceptance test: All required fields must be filled before the safe can be saved.
ERP_SRS acceptance test: The saved credit card safe appears in the Cash Management safe list
ERP_SRS acceptance test: Field Validations

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a finance user, I want to delete a credit card safe that is no longer needed, so that the safe list remains clean and accurate.

Credit Card Safe

CreditCardSafe-Detele-003Canonical SRS Graph

As a finance user, I want to delete a credit card safe that is no longer needed, so that the safe list remains clean and accurate.

User Story

As a finance user, I want to delete a credit card safe that is no longer needed, so that the safe list remains clean and accurate.

طبقًا للمصدر الأساسي ERP_SRS: As a finance user, I want to delete a credit card safe that is no longer needed, so that the safe list remains clean and accurate.

Description

طبقًا للمصدر الأساسي ERP_SRS: As a finance user, I want to delete a credit card safe that is no longer needed, so that the safe list remains clean and accurate.

Acceptance Criteria

Delete is available on a credit card safe only if no expenses have been recorded against it.
Once any expense has been made using the credit card safe, Delete action is permanently disabled.

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

Scenarios

ERP_SRS acceptance test: Delete is available on a credit card safe only if no expenses have been recorded against it.
ERP_SRS acceptance test: Once any expense has been made using the credit card safe, Delete action is permanently disabled.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

Ensure all Credit Card Safe user-facing labels, messages, validation errors, and notifications are available in supported system languages.

Credit Card Safe

CreditCardSafe-Lang-010Canonical SRS Graph

Ensure all Credit Card Safe user-facing labels, messages, validation errors, and notifications are available in supported system languages.

User Story

Ensure all Credit Card Safe user-facing labels, messages, validation errors, and notifications are available in supported system languages.

طبقًا للمصدر الأساسي ERP_SRS: Ensure all Credit Card Safe user-facing labels, messages, validation errors, and notifications are available in supported system languages.

Description

طبقًا للمصدر الأساسي ERP_SRS: Ensure all Credit Card Safe user-facing labels, messages, validation errors, and notifications are available in supported system languages.

Acceptance Criteria

All user-facing messages, labels, and notifications must be available in English and Arabic.
Date formats and decimal separators must follow system locale settings.

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

ينفذ Business / System User سيناريو Localize Credit Card Safe Labels and Messages ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: All user-facing messages, labels, and notifications must be available in English and Arabic.
ERP_SRS acceptance test: Date formats and decimal separators must follow system locale settings.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

Defines currency conversion behavior between card currency and source safe currency.

Credit Card Safe

CreditCardSafe-MultiCurrency-011Canonical SRS Graph

Defines currency conversion behavior between card currency and source safe currency.

User Story

Defines currency conversion behavior between card currency and source safe currency.

طبقًا للمصدر الأساسي ERP_SRS: Defines currency conversion behavior between card currency and source safe currency.

Description

طبقًا للمصدر الأساسي ERP_SRS: Defines currency conversion behavior between card currency and source safe currency.

Acceptance Criteria

If repayment > outstanding:
If repayment is safe currency ≠ card currency, the system applies an exchange rate.
Outstanding is stored in card currency.
Journal entries are created in base currency.
The exchange rate must be captured and auditable.

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

ينفذ Business / System User سيناريو Multi-Currency Handling ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: If repayment > outstanding:
ERP_SRS acceptance test: If repayment is safe currency ≠ card currency, the system applies an exchange rate.
ERP_SRS acceptance test: Outstanding is stored in card currency.
ERP_SRS acceptance test: Journal entries are created in base currency.
ERP_SRS acceptance test: The exchange rate must be captured and auditable.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a card holder, I want to receive an in-app notification one day before the payment due day when there is an outstanding balance, so that I am reminded to make the repayment before the deadline.

Credit Card Safe

CreditCardSafe-NOTF-ReceivePayment-008Canonical SRS Graph

As a card holder, I want to receive an in-app notification one day before the payment due day when there is an outstanding balance, so that I am reminded to make the repayment before the deadline.

User Story

As a card holder, I want to receive an in-app notification one day before the payment due day when there is an outstanding balance, so that I am reminded to make the repayment before the deadline.

طبقًا للمصدر الأساسي ERP_SRS: As a card holder, I want to receive an in-app notification one day before the payment due day when there is an outstanding balance, so that I am reminded to make the repayment before the deadline.

Description

Acceptance Criteria

The system runs a daily check for upcoming payment due dates.
On the day before the Payment Due Day each month, if the outstanding balance is greater than 0, an in-app notification is sent to the assigned card holder.
If the outstanding balance is 0, no notification is sent.
The notification is sent only to the card holder assigned to the credit card safe.

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

ينفذ card holder سيناريو Receive Payment Due Reminder ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: The system runs a daily check for upcoming payment due dates.
ERP_SRS acceptance test: On the day before the Payment Due Day each month, if the outstanding balance is greater than 0, an in-app notification is sent to the assigned card holder.
ERP_SRS acceptance test: If the outstanding balance is 0, no notification is sent.
ERP_SRS acceptance test: The notification is sent only to the card holder assigned to the credit card safe.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

Defines behavior when repayment exceeds outstanding.

Credit Card Safe

CreditCardSafe-Overpayment-006Canonical SRS Graph

Defines behavior when repayment exceeds outstanding.

User Story

Defines behavior when repayment exceeds outstanding.

طبقًا للمصدر الأساسي ERP_SRS: Defines behavior when repayment exceeds outstanding.

Description

طبقًا للمصدر الأساسي ERP_SRS: Defines behavior when repayment exceeds outstanding.

Acceptance Criteria

If repayment > outstanding:
Outstanding becomes 0
Extra amount is stored as credit balance on the card
Available credit increases accordingly
Overpayment credit can be used to offset future expenses.

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

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

Scenarios

ERP_SRS acceptance test: If repayment > outstanding:
ERP_SRS acceptance test: Outstanding becomes 0
ERP_SRS acceptance test: Extra amount is stored as credit balance on the card
ERP_SRS acceptance test: Available credit increases accordingly
ERP_SRS acceptance test: Overpayment credit can be used to offset future expenses.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a finance user, I want to record a repayment against a credit card safe outstanding balance, so that the outstanding balance decreases and the available credit is restored.

Credit Card Safe

CreditCardSafe-Repayment-005Canonical SRS Graph

As a finance user, I want to record a repayment against a credit card safe outstanding balance, so that the outstanding balance decreases and the available credit is restored.

User Story

As a finance user, I want to record a repayment against a credit card safe outstanding balance, so that the outstanding balance decreases and the available credit is restored.

طبقًا للمصدر الأساسي ERP_SRS: As a finance user, I want to record a repayment against a credit card safe outstanding balance, so that the outstanding balance decreases and the available credit is restored.

Description

Acceptance Criteria

The repayment section is available on the credit card safe limit page.
Only cash and treasury safes appear in The Safe dropdown; credit card safes are excluded.
A successful repayment decreases outstanding balance and increases available credit by the repaid amount.
After saving, the repayment appears in the repayment history section.
Field Validations

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

Scenarios

ERP_SRS acceptance test: The repayment section is available on the credit card safe limit page.
ERP_SRS acceptance test: Only cash and treasury safes appear in The Safe dropdown; credit card safes are excluded.
ERP_SRS acceptance test: A successful repayment decreases outstanding balance and increases available credit by the repaid amount.
ERP_SRS acceptance test: After saving, the repayment appears in the repayment history section.
ERP_SRS acceptance test: Field Validations

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a finance user, I want to view all repayments made on a credit card safe, so that I can track the full repayment activity on the card.

Credit Card Safe

CreditCardSafe-RepaymentHistory-007Canonical SRS Graph

As a finance user, I want to view all repayments made on a credit card safe, so that I can track the full repayment activity on the card.

User Story

As a finance user, I want to view all repayments made on a credit card safe, so that I can track the full repayment activity on the card.

طبقًا للمصدر الأساسي ERP_SRS: As a finance user, I want to view all repayments made on a credit card safe, so that I can track the full repayment activity on the card.

Description

طبقًا للمصدر الأساسي ERP_SRS: As a finance user, I want to view all repayments made on a credit card safe, so that I can track the full repayment activity on the card.

Acceptance Criteria

The repayment history section is displayed on the credit card safe limit page.
Each repayment record displays row number, date, source safe, amount, and note.
Each record in the history displays:

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

Scenarios

ERP_SRS acceptance test: The repayment history section is displayed on the credit card safe limit page.
ERP_SRS acceptance test: Each repayment record displays row number, date, source safe, amount, and note.
ERP_SRS acceptance test: Each record in the history displays:

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a finance user, I want to view all in/out transactions on a credit card safe, so that I can see the complete movement history of the card.

Credit Card Safe

CreditCardSafe-Transactions-009Canonical SRS Graph

As a finance user, I want to view all in/out transactions on a credit card safe, so that I can see the complete movement history of the card.

User Story

As a finance user, I want to view all in/out transactions on a credit card safe, so that I can see the complete movement history of the card.

طبقًا للمصدر الأساسي ERP_SRS: As a finance user, I want to view all in/out transactions on a credit card safe, so that I can see the complete movement history of the card.

Description

طبقًا للمصدر الأساسي ERP_SRS: As a finance user, I want to view all in/out transactions on a credit card safe, so that I can see the complete movement history of the card.

Acceptance Criteria

The transactions page is accessible from the credit card safe.
The page includes a filter panel with Type, Investors, Payees, Customers, User, Direction, and Date Range.
The page displays a summary showing Total In and Total Out amounts.
Both incoming (IN) and outgoing (OUT) transactions are displayed.
The transaction table shows the following 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 Transactions ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: The transactions page is accessible from the credit card safe.
ERP_SRS acceptance test: The page includes a filter panel with Type, Investors, Payees, Customers, User, Direction, and Date Range.
ERP_SRS acceptance test: The page displays a summary showing Total In and Total Out amounts.
ERP_SRS acceptance test: Both incoming (IN) and outgoing (OUT) transactions are displayed.
ERP_SRS acceptance test: The transaction table shows the following columns:

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

Defines constraints on updating credit limits.

Credit Card Safe

CreditCardSafe-Update-Limit-012Canonical SRS Graph

Defines constraints on updating credit limits.

User Story

Defines constraints on updating credit limits.

طبقًا للمصدر الأساسي ERP_SRS: Defines constraints on updating credit limits.

Description

طبقًا للمصدر الأساسي ERP_SRS: Defines constraints on updating credit limits.

Acceptance Criteria

The credit limit cannot be reduced below the current used amount.
Increasing credit limit is allowed with audit trail.
Changes must be logged with old and new values.

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

ينفذ Business / System User سيناريو Credit Limit Update Rules ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: The credit limit cannot be reduced below the current used amount.
ERP_SRS acceptance test: Increasing credit limit is allowed with audit trail.
ERP_SRS acceptance test: Changes must be logged with old and new values.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a finance user, I want to view the credit card safe balance summary and repayment information, so that I can monitor the outstanding balance and credit usage at any time.

Credit Card Safe

CreditCardSafe-View-004Canonical SRS Graph

As a finance user, I want to view the credit card safe balance summary and repayment information, so that I can monitor the outstanding balance and credit usage at any time.

User Story

As a finance user, I want to view the credit card safe balance summary and repayment information, so that I can monitor the outstanding balance and credit usage at any time.

طبقًا للمصدر الأساسي ERP_SRS: As a finance user, I want to view the credit card safe balance summary and repayment information, so that I can monitor the outstanding balance and credit usage at any time.

Description

Acceptance Criteria

A dedicated page exists for each credit card safe showing its limit data and repayment information.
The repayment section is available on this page.
The repayment history table is displayed on this page.
The page displays Credit Limit, Used Amount, Paid Amount, Outstanding, and Available Credit.

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

Scenarios

ERP_SRS acceptance test: A dedicated page exists for each credit card safe showing its limit data and repayment information.
ERP_SRS acceptance test: The repayment section is available on this page.
ERP_SRS acceptance test: The repayment history table is displayed on this page.
ERP_SRS acceptance test: The page displays Credit Limit, Used Amount, Paid Amount, Outstanding, and Available Credit.

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

Defines accounting entries for credit card expense and repayment operations and aligns Outstanding with GL liability.

Credit Card Safe

IMPCTCreditCardSafe-Accounting-015Canonical SRS Graph

Defines accounting entries for credit card expense and repayment operations and aligns Outstanding with GL liability.

User Story

Defines accounting entries for credit card expense and repayment operations and aligns Outstanding with GL liability.

طبقًا للمصدر الأساسي ERP_SRS: Defines accounting entries for credit card expense and repayment operations and aligns Outstanding with GL liability.

Description

طبقًا للمصدر الأساسي ERP_SRS: Defines accounting entries for credit card expense and repayment operations and aligns Outstanding with GL liability.

Acceptance Criteria

Expense using Credit Card
- Dr Expense Account
- Cr Credit Card Liability Account
- Dr Credit Card Liability Account
- Cr Cash / Treasury Safe
Outstanding must equal GL balance (liability).
Journal entries must be created before marking any related record as paid.
The system must create journal entries only when Chart of Accounts integration is enabled.
If Chart of Accounts integration is disabled, no journal entry is created automatically.
If Chart of Accounts integration is enabled, created journal entries must follow the GA approval workflow.
Generated journal entries must be created with status Pending by GA until approved by General Accounting.
Credit Card Safe balances must still be updated operationally even when journal entry creation is disabled.

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

ينفذ Business / System User سيناريو Accounting Impact for Credit Card ويطابق النتيجة مع Acceptance Criteria في ERP_SRS، مع UI/API/Data/Audit evidence.

Scenarios

ERP_SRS acceptance test: Expense using Credit Card
ERP_SRS acceptance test: - Dr Expense Account
ERP_SRS acceptance test: - Cr Credit Card Liability Account
ERP_SRS acceptance test: - Dr Credit Card Liability Account
ERP_SRS acceptance test: - Cr Cash / Treasury Safe
ERP_SRS acceptance test: Outstanding must equal GL balance (liability).

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

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

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