Finance teams handle some of the most sensitive, time-critical work in any organisation, yet most still rely on email chains, spreadsheets, and informal handoffs to manage internal requests. Applying ITSM for finance teams changes that by giving finance a structured, auditable system for receiving, prioritising, and resolving service requests — from purchase approvals to payroll queries — while building the compliance trail that auditors expect.
Why Finance Teams Have a Service Management Problem
Finance is a service provider to the rest of the business. Colleagues raise requests — expense reimbursements, budget queries, invoice approvals, vendor payment status — and finance staff field them through whatever channel happens to be used that day. The result is familiar:
- Requests get lost in shared inboxes or personal email
- There is no visibility into workload or queue depth
- Priority is set by whoever shouts loudest, not by business impact
- There is no audit trail when an auditor asks who approved what and when
- Duplicate effort is common because two analysts pick up the same request
These are not finance problems specifically. They are service management problems, and ITSM practice has solved them for IT departments for decades. The same logic applies here.
Finance leaders often resist formalising internal service delivery because they assume it requires heavy IT involvement or expensive tooling. In practice, a well-configured ESM platform lets finance own and operate its own service desk without depending on IT to manage every queue.
What Finance Service Requests Actually Look Like
Before mapping a process, it helps to be clear about what finance teams actually receive. Most finance request types fall into a small number of categories:
- Payment and invoice queries: vendors chasing payment status, internal teams asking why a supplier invoice has not cleared
- Expense reimbursement: employees submitting claims and chasing approval or payment
- Budget and cost-centre queries: department heads asking for spend reports or requesting budget transfers
- Procurement and purchase order requests: requests to raise a PO, approve a spend threshold, or onboard a new supplier
- Payroll queries: questions about payslips, tax codes, deductions, or payment dates
- Financial reporting requests: ad-hoc reports, variance explanations, or data extracts for management
- Audit and compliance requests: internal audit asking for transaction records, approvals, or policy evidence
- System access requests: access to finance systems such as ERP, expense tools, or reporting platforms
Each of these has a natural owner, a typical resolution time, and a set of information that must be captured upfront. That is exactly what a service catalogue entry and a structured request form can provide.
Building a Finance Service Catalogue
The service catalogue is the foundation of finance service management. It replaces the informal "email finance@" approach with a menu of clearly defined services, each with its own form, workflow, and SLA.
Start With the Most Common Request Types
Run a short exercise with the finance team to list every recurring request they handle. Group them by type and estimate how many arrive per week. The highest-volume, most repetitive requests are the first candidates for catalogue entries.
Define What Information Is Needed Upfront
One of the biggest time-wasters in finance service delivery is back-and-forth to gather missing information. A well-designed request form captures everything at submission:
- For expense claims: amount, date, category, cost centre, receipt attachment
- For PO requests: supplier name, amount, budget code, business justification, approver name
- For payroll queries: employee ID, pay period in question, nature of the query
Capturing this upfront cuts resolution time significantly and reduces frustration on both sides.
Set Realistic SLAs for Each Service
Not every finance request is equal. A payroll query from an employee who has not been paid needs same-day attention. A budget variance explanation for a management report can wait 48 hours. Define response and resolution targets per service type and make them visible to requesters so expectations are set before a ticket is even raised.
Assign Clear Ownership
Each catalogue item should have a named team or individual responsible for resolution. When a request arrives, it routes automatically to the right person rather than sitting in a shared inbox waiting for someone to claim it.
Workflow Automation That Finance Teams Actually Use
Once the catalogue is in place, automation removes the manual steps that slow finance service delivery down.
- Approval routing: purchase requests above a defined threshold automatically route to the relevant budget holder for approval before finance acts on them. No chasing, no manual forwarding.
- Status notifications: requesters receive automatic updates when their ticket moves through stages — received, in progress, pending approval, resolved. This alone eliminates a large proportion of "just checking in" follow-up emails.
- Escalation rules: if a payment query has not been resolved within the agreed SLA, it escalates automatically to a senior team member. SLA breaches do not go unnoticed.
- Recurring request scheduling: some finance tasks are predictable — month-end report requests, quarterly budget review packs. These can be raised automatically on a schedule rather than relying on someone to remember.
The TIKTING service management platform supports all of these workflow patterns out of the box, and finance teams can configure their own queues, forms, and automations without raising a change request with IT.
Audit Readiness and Compliance Through ITSM
This is where ITSM delivers its clearest value for finance beyond operational efficiency. Every regulated organisation needs to demonstrate that financial processes are controlled, that approvals happened before actions were taken, and that records exist to prove it.
A structured ITSM platform creates that evidence automatically:
- Every request has a timestamp showing when it was raised, by whom, and on which system
- Every approval is recorded against the ticket, with the approver's identity and the time of approval
- Every status change is logged in the ticket history
- Comments, attachments, and decisions are stored against the ticket permanently
When internal audit or an external auditor asks for evidence of the purchase approval process, the finance team can pull a filtered report of all PO requests above a threshold, showing the approval chain for each one. No manual reconstruction, no relying on email search.
Segregation of Duties in the Ticket Workflow
Segregation of duties is a core financial control requirement. ITSM workflows enforce it structurally. A request raised by one person routes to a different person for approval, and a third person for payment processing. The system will not allow a single user to approve their own request, because the workflow does not permit it. This is a compliance control built into the process, not bolted on after the fact.
A Practical Step-by-Step Rollout for Finance
Rolling out ITSM in a finance team does not need to be a six-month programme. A focused approach can deliver a working system in a few weeks.
- Step 1: Map current request types. Spend one week logging every request that arrives by email, phone, or walk-up. Categorise and count them.
- Step 2: Identify the top five by volume. Build catalogue entries for these first. Do not try to capture everything at once.
- Step 3: Design the intake forms. Work with the finance team to agree what information is required for each request type. Keep forms short — only ask for what is genuinely needed.
- Step 4: Set SLAs. Agree response and resolution targets for each service. Involve the finance manager and, where relevant, the wider business to set realistic expectations.
- Step 5: Configure routing and approvals. Map who owns each request type and what approval steps are required. Configure these in the platform.
- Step 6: Communicate to the business. Send a clear message to all staff explaining how to raise finance requests going forward. Include a link to the portal and a short guide.
- Step 7: Review after 30 days. Look at ticket volume, resolution times, and any request types that are still arriving by email. Iterate.
Key Takeaways
Applying ITSM to finance service delivery is not about adding bureaucracy. It is about replacing informal, invisible processes with structured ones that work faster, create less frustration, and produce the audit evidence that compliance requires.
- Finance teams are internal service providers and benefit from the same service management discipline as IT
- A structured service catalogue with clear intake forms eliminates back-and-forth and reduces resolution time
- Workflow automation handles approvals, notifications, and escalations without manual effort
- Every ticket creates an automatic audit trail that satisfies internal and external compliance requirements
- Segregation of duties controls can be enforced structurally through workflow design
- A phased rollout starting with the highest-volume request types delivers value quickly without overwhelming the team
The TIKTING service management platform is built for exactly this kind of cross-departmental deployment. Finance teams can configure and own their own service desk within the same platform that IT uses, sharing infrastructure without sharing queues or visibility. If your finance team is still running on email, it is worth exploring what a structured ESM approach could look like in your environment.
