Paid and Failed Payments
- Last updated
- Nov 2026
- Built by
- Moss Finance
Lists paid and failed payments in a period and any later payment to the same payee.
Paid: 34 invoice payments, £88,905.00
Failed: 2 payments, £2,100.00
| Date | Supplier | Invoice | Amount | ID | Later payment |
|---|---|---|---|---|---|
| 12 Oct | Amazon | INV-2291 | £1,480.00 | 7c1e04b2-5d38-4f6a-9a2e-3b8d61f0c4aa | Paid again on 16 Oct |
| 03 Nov | Adobe | INV-0457 | £620.00 | 2a9d7e15-8c04-41b3-b6f7-5e1c93d0a8b2 | None, still open |
What it does
After a payment run you want to know what went through and what failed. Instead of checking the bank list line by line, this prompt lists paid and failed payments and tells you if the same payee was paid again later, so nothing stays open.
Use it after every payment run and at month-end.
Prompt
Copy the prompt, then replace the highlighted placeholders in your AI assistant.
Paid and Failed Payments: 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] • Time frame: [last X days or start date to end date] • Outcomes: [paid, failed or both] • Payment types: [invoices, reimbursements or both] • Delivery: [overview in chat, or Excel overview] RULES • List all payments in the time frame by outcome, paid or failed. • Take the outcome from the payment status: PAID (invoices) or COMPLETED (reimbursements) is paid, FAILED is failed. A later payment is any payment to the same payee after the failed one. OUTPUT • One row per payment: transaction ID, date, payee, gross amount, currency, outcome and invoice number. • For failed payments: the later payment to the same payee, or that there is none. • Count and total per outcome and currency.
Set it up
Connect Moss once, then copy the prompt or save it as a skill. Each takes about two minutes.
Connect Moss to your AI assistant
Once · about 2 minutesAdd the Moss connector and sign in with your Moss account.
On a team or enterprise plan, a workspace admin may need to allow custom connectors before you can add Moss.
Choose how you use it
Pick oneCopy the prompt for a quick run, or save it as a skill so Claude runs it the same way every time.
- Copy the prompt from this page.
- Paste it into a new chat with Moss MCP switched on.
- 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.
Link Moss to your LLM once
You sign in with your Moss account. After that, your LLM can reach Moss whenever you 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.
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 can | It can't |
|---|---|
| Read card transactions and their receipt status | Change, approve or delete anything |
| Read cardholders, teams and entities | Make 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
Quick Past Coding Lookup
Shows how a supplier or invoice was coded in the past, over all time or a period you choose.
Overdue Suppliers Ranking
Lists suppliers with overdue invoices, ranked by days overdue and by amount.