You are being asked to configure a **Jira Service Management (JSM) Finance service project** with a customer portal and a set of structured request types grouped into four areas: **AR (Billing & Collections), AP (Vendor invoices & expense reports), Finance Tools & Access, and Budgeting & Forecasting**. Each request type has a defined intake form (required + optional fields, and some conditional fields that only appear based on a dropdown choice), and tickets should be routed to the correct owner/queue (AR Owner, AP Owner, Tool Owner, Budget/Finance triage). The workflow is intended to be **one shared workflow across all request types** with statuses **New → In Progress → Waiting for Requester / Waiting for Third Party → Done**, plus automations including **auto-closes tickets after 7 days in “Waiting for Requester”**. There is also a requirement to standardize categorisation for reporting (labels and a “request code” style prefix like AR-1, AP-3, etc. since Jira keys cannot be prefixed per request type in a single project). Effort-wise, this is a **medium-sized JSM setup**: roughly **11 request types**, a set of **custom fields** (including select lists and conditional visibility per request type), a **workflow**, **routing rules/queues**, **4-5 automation rules**, and a **basic dashboard** (open by category, resolution time, volume by type, waiting states). A freelancer can usually deliver a first working version in **1–3 days** depending on how fast the missing inputs are provided (owner assignments, cost center dropdown options, and whether external customers need portal access), plus additional time for UAT tweaks.