Please enable JavaScript.

Coggle requires JavaScript to display documents.

Receipt Module - Coggle Diagram

- - - - branch
      - total in hand(from/to)
      - user name
      - Signed in date range(from / to)
      - user code
  - - - When a cashier is already signed in, then the system should prevent re-signing without a prior sign-off.
      - When the sign-in is successful, then the system displays:Success: <Cashier signed in successfully.\>
    - - When the cashier’s total collection in hand is not zero, then the system should block the sign-off and display:Error: <Cannot sign off until the total collection in hand is zero.\>
      - When the sign-off is successful, then the system displays:Success: <Cashier signed off successfully.>
    - - When the admin enters invalid search criteria (e.g., invalid date formats), then the system should display:Error: <Please enter valid search criteria.>
    - - When sorting fails due to a system error, then the system should display:Error: <An error occurred while sorting. Please try again.\>
    - - When the cashier's status is Signed In, the Exclude button should not be available.
      - If the cashier is New or Signed Off, the system prompts a confirmation before excluding.
      - Upon successful exclusion, the system removes the cashier from the list and displays:
        
        Success Message: <Cashier excluded successfully.\>
      - If the exclusion fails, the system displays:
        
        Error Message: <An error occurred while excluding the cashier. Please try again.\>
    - - When the user attempts to exclude a cashier, a confirmation dialog appears with the options Yes (to confirm) and No (to cancel).
      - If Yes is selected, the exclusion proceeds.
      - If No is selected, the process is aborted without changes.
- - - - Transaction type
      - Class name
      - Product name -Need to select the class first,then products will be loaded according to the selected class. 01/01/2025
      - Business channel name
      - Payment mode name
      - Status
  - - - When user enter an incorrect date range (Back date) Inactive effect date or inactivated date < The entered date is a past date, please try again>( calendar Block).
      - If user entered the same order No for the same note type ,a validation message should display as < Cannot duplicate Order No.Please try again.>
- - - - All required fields (code, description, payment duration, status) must be completed.
      - Payment duration must be a positive number.
      - Status must be "Active" or "Inactive."
    - - If a required field is missing:
        
        <Please fill in all mandatory fields: code, description, payment duration.\>
      - If payment duration is not a positive number:
        
        <Payment duration must be a positive number.\>
      - If the status is not selected:
        
        <Please select a valid status: Active or Inactive.\>
    - - Upon successful creation of a settlement mode:
        
        <New settlement mode added successfully.\>
- - - - Required fields
        
        Transaction type code
        
        Transaction type name
        
        Charge type
        
        status
        
        actvie
        
        inactive
        
        inactive effect date
        
        inactive by
        
        inactive date
      - Charge type
        
        code
        
        description
        
        default
        
        status
  - - - When user enter an incorrect date range (Back date) Inactive effect date or inactivated date < The entered date is a past date, please try again>( calendar Block)
      - When the user exceeding the characteristics of a field, a validation prompt as <the maximum character limit has been exceeded > OR (Limit Block) 23/10/2025
- - - - date from
        date to
        payment mode
        type
        bank slip no
        currency
        amount from
        amount to
- - - - card type
      - linked bank account
        
        Finance