# Expense, purchase and access questions, handled in Slack and Teams

Risotto gives Finance a help desk in Slack and Microsoft Teams. Employees get expense and purchase answers from your own policies, with the source cited, and access to finance systems once the right person approves it. What needs a person reaches Finance's queue with the details already collected, so your team can close the books instead of answering questions about them.

[Book a demo](/demo) · [See every team](/solutions)

**80%** auto-solve rate on transactional queries for ThoughtSpot's Accounting team. [Read the story](/customers/thoughtspot-automates-multi-department-support-with-ai)

## Answers from Finance's own policies

Risotto answers T&E, expense, budget and procurement questions from the policies you already keep in Confluence, Notion, Google Drive, SharePoint, OneNote, Guru or Coda, and cites the page it used. When the policy doesn't cover it, Risotto passes the question to Finance with what it found.

**41%** of Finance requests auto-resolved through approved policy documentation at Docker. [Read the story](/customers/docker-automates-68-percent-it-tickets-with-risotto)

[Knowledge](/product/knowledge)

Testing an expense question as one employee: Risotto answers from the UK expense policy and cites it. Example data.

## The right policy for each office

Scope Finance's sources to the Finance department, and Risotto uses them on Finance's requests. Add a profile filter, such as city equals London, and employees in London get answers from the London policy. A document only Finance should read stays with your team: set its audience to Assistant only, and it never answers a requester.

[Knowledge](/product/knowledge)

A Google Drive folder of Finance policies, scoped to the Finance department and to employees in London. Example data.

## Requests that arrive complete

Vendor onboarding, purchase requests and reimbursement exceptions all need the same details every time. Attach a form to a Risotto runbook, and Risotto collects them before anyone in Finance looks: a Slack form, a Teams card, or one question at a time anywhere else. Ask the Assistant to build the form, and approve it before it saves.

[Runbooks](/product/runbooks)

Dana asks about a new vendor, fills in the runbook's form, and the request goes to Procurement's queue. Example data.

## Built the way Finance works

Risotto fits Finance's teams, approvals and records.

- **A queue for each team.** Sub-departments such as Accounts Payable, Procurement and T&E each get their own queue.
- **Routing you choose.** Round robin, fewest open tickets, or whoever is online in Slack.
- **Private to Finance.** Only Finance's Agents and Supervisors see its tickets, and an admin role elsewhere in Risotto doesn't add them.
- **The Controller approves.** Access to a finance system waits for the person or group your approval policy names.
- **Access that ends.** Access granted through Okta, Microsoft Entra ID, Google Workspace or JumpCloud is removed on the end date your policy sets.
- **A record of every step.** Each request keeps who asked, who approved, what ran and when, on the ticket.

[Access requests](/product/access-requests) · [Security and trust](/security)

## Start from the library

Start from one of these and change it to fit. Open one to see every step and tool, or [browse the library](/library).

### Access and licenses

Access with an approval, and seats before they run out.

- [Okta group access request](/library/runbooks/okta-group-access-request): check your access rules, get the approval, add the person to the group
- [Weekly license seat check](/library/automations/weekly-license-seat-check): run the license seat alert script tool every Monday
- [License seat alert](/library/script-tools/license-seat-alert): a procurement ticket when an app runs low on seats

## Frequently asked questions

### Can Risotto answer expense and reimbursement policy questions?

Yes. Risotto answers from your T&E, expense and procurement policies in Confluence, Notion, Google Drive, SharePoint, OneNote, Guru or Coda, and cites the source. At Docker, 41% of Finance requests are auto-resolved through approved policy documentation. [Knowledge](/product/knowledge)

### Can different offices get different finance policies?

Yes. Add a profile filter to a knowledge source, such as city or country, and employees who match it get answers from that source. To keep a document for Finance staff only, set its audience to Assistant only. [Knowledge](/product/knowledge)

### What happens when a finance question needs a person?

Risotto passes it to Finance's queue with the conversation and what it found. When the runbook has a form, the details Finance needs are already filled in. [Runbooks](/product/runbooks)

### Can Finance split its queue into Accounts Payable, Procurement and T&E?

Yes. Each sub-department gets its own queue, and routing rules assign its tickets by round robin, fewest open tickets, or who is online in Slack. [Ticketing](/product/ticketing)

### How does Risotto keep Finance's requests private?

Only Finance's Agents and Supervisors see Finance's tickets, and an admin role elsewhere in Risotto doesn't add them. Every change to who's in the department is recorded in the audit log. [See every team](/solutions)

## Every policy question is stealing time from the work Finance was hired to do

[Book a demo](/demo)

Source: https://www.tryrisotto.com/solutions/finance
