AI Hub/MCP use cases/Approval Route Lookup
Use case · Moss connector

Approval Route Lookup

Last updated
Nov 2026
Built by
Moss Finance

Shows who must approve one specific item, in which order, and which rule routes it.

ApprovalsApproval routesAuditSingle lookupAccountantInternal audit
Who needs to approve the Amazon invoice INV-10429, and where is it now?
Using skill · Approval route lookup
Reading Moss · invoices and approval details

Amazon, invoice INV-10429, EUR 224.50, approved

07 Oct 2026, ID 9031a3fc-0f75-47ee-95fa-8145c0dc2f9c

Rule: Office costs. One step, approved by Daniel Fischer on 08 Oct 2026. Nobody left to decide.

Earlier items of this supplier took a different route:

  1. INV-10311 (EUR 224.50, 07 Jul 2026): rule Default, one step, approved by Sophie Wagner
  2. INV-10102 (EUR 248.10, 15 May 2026): rule Default, two steps, approved by Lukas Meyer and then Emma Becker
Rule: Office costs, 1 step · 2 earlier items compared
Example using sample data · Claude + Moss MCPAnswered in 12 seconds

What it does

Instead of clicking through the item and the approval rules, this prompt shows who has to approve one item, in which order, which rule sent it there and who already decided.

Use it when someone asks why an item is stuck for a quick look-up.

Prompt

Copy the prompt, then replace the highlighted placeholders in your AI assistant.

Approval Route Lookup: Use Moss MCP
Use AskUserQuestion (clickable multiple choice) to collect [inputs] first. Offer my real entities from Moss as options. Ask me to type names, dates and numbers in chat. If I pick Other, ask again for the exact value.

INPUTS
• Entity: [choose an entity or All entities]
• Item: [type an invoice number, or a supplier and amount]
• Compare with earlier items: [same supplier, last number months, optional]

RULES
• Find the item by invoice number first, then by supplier and amount. If several items fit, list them and ask me which one.
• Show the approval route of that item in Moss, from submission to the last step. Do not guess amount limits or how many approvers are needed, because Moss does not return them.

OUTPUT
• The item: supplier, amount, currency, date, transaction ID and status.
• The route: each step in order with the approver, the decision and the date, who still has to decide, and the name of the rule that routes it. Say if the item has no approval route.
• If asked, whether earlier items of the same supplier took the same route.
For whoever sets it up

Set it up

Connect Moss once, then copy the prompt or save it as a skill. Each takes about two minutes.

1

Connect Moss to your AI assistant

Once · about 2 minutes

Add the Moss connector and sign in with your Moss account.

Step 1 of 4 · illustration

On a team or enterprise plan, a workspace admin may need to allow custom connectors before you can add Moss.

2

Choose how you use it

Pick one

Copy the prompt for a quick run, or save it as a skill so Claude runs it the same way every time.

  1. Copy the prompt from this page.
  2. Paste it into a new chat with Moss MCP switched on.
  3. Replace the highlighted placeholders and send.

Check a few transactions through the Moss links before you send any reminders.

How MCP works

MCP is an open standard that lets your LLM look things up in other tools. The Moss MCP gives it read access to your Moss data, so it answers from your real numbers.

01 · Connect

Link Moss to your LLM once

You sign in with your Moss account. After that, your LLM can reach Moss whenever you ask.

02 · Ask

Use a prompt in plain English

Your LLM asks the Moss MCP for what it needs, such as expenses, budgets, bank transactions or receipt files.

03 · Get

An answer from your own data

Lists, summaries and drafts based on what is in Moss. Nothing in Moss is changed.

What MCP can see

You stay in control. The Moss MCP only reads data. It can't change or pay anything.

It canIt can't
Read card transactions and their receipt statusChange, approve or delete anything
Read cardholders, teams and entitiesMake payments or move money

FAQ

Yes, for the data. The connector reads your own Moss data, so you need a Moss account.

Goes well with