activities already performed, or application fee of $100 not eligible, but Inspection Fee of $50 is eligible, etc.) based on existing business rules The System shall provide the Applicant with a means to select individual, multiple, or all fee items eligible for refund. The System shall prompt the Applicant to indicate the reason for requesting a refund (both in a structured manner as well as by providing free text explanation) The Applicant submits the refund request. The System routes the request to a departmental Customer Service Representative for review. The System shall provide the capability to allow low complexity, low value refund requests to be automatically accepted and processed. The System shall provide the capability for refund requests to be queued in the System for designated personnel to review and process according to pre-defined business rules. Associations to other Use Cases: Use Case: a Refund Alternative Flow: If a Customer requests a refund for a payment processed in person (see Use Case: Process Payment Made in Person), then the Cashier may process a refund according to pre-defined business rules (e.g., If it is the same day and the cashier has not closed his or her station). Otherwise, the transaction must be routed through the business unit (see Use Case: Issue a Refund). Additional Requirements: The System shall provide functionally to limit which payments are available for refund selection by the Applicant (i.e. The Applicant won’t be able to select a a refund” “request option for an application where the project is nearly completed). eChecks can’t be returned online for 10 days The System shall provide customer service options to contact the City (i.e. online help, chat, email, call). The System shall require an e-signature, or other certification by City staff, for designated transaction types (e.g., issuing a refund). The System shall have the capability to capture electronic signature
activities already performed, or application fee of $100 not eligible, but Inspection Fee of $50 is eligible, etc.) based on existing business rules The System shall provide the Applicant with a means to select individual, multiple, or all fee items eligible for refund. The System shall prompt the Applicant to indicate the reason for requesting a refund (both in a structured manner as well as by providing free text explanation) The Applicant submits the refund request. The System routes the request to a departmental Customer Service Representative for review. The System shall provide the capability to allow low complexity, low value refund requests to be automatically accepted and processed. The System shall provide the capability for refund requests to be queued in the System for designated personnel to review and process according to pre-defined business rules. Associations to other Use Cases: Use Case: a Refund Alternative Flow: If a Customer requests a refund for a payment processed in person (see Use Case: Process Payment Made in Person), then the Cashier may process a refund according to pre-defined business rules (e.g., If it is the same day and the cashier has not closed his or her station). Otherwise, the transaction must be routed through the business unit (see Use Case: Issue a Refund). Additional Requirements: The System shall provide functionally to limit which payments are available for refund selection by the Applicant (i.e. The Applicant won’t be able to select a “request a refund” option for an application where the project is nearly completed). eChecks can’t be returned online for 10 days The System shall provide customer service options to contact the City (i.e. online help, chat, email, call). The System shall require an e-signature, or other certification by City staff, for designated transaction types (e.g., issuing a refund). The System shall have the capability to capture electronic signature
ILMS_Attachment%20H%20-%20to%20be%20use%20cases%20%20-%20COH%20PWE%20To%20Be%20Use%20Cases%20Master%20Deliverable%20-%20ILMS%20Replacement%20v2.docx