Two questions, in this order. Who owes me money, and how do I ask for it.
Show me the aging on everything outstanding as at today.
Paste this into Claude with the server connected.
statement_aging on the statement-of-account server, for one client or for everyone. It
buckets what is owed into 0 to 30, 31 to 60, 61 to 90 and over 90 days as at any date you name, and
names the oldest overdue invoice.
This tool is free and unlimited on every tier, for one client or for all of them, and the reason is stated in the server's own material: who owes me money is the question this server exists for, and a free tier that hides it is a demo rather than a tool. The metered thing is the document that goes to a client, five distinct statements a calendar month, counted by client, period and currency, so rebuilding one already in the register is free forever.
The invoice server has a second, narrower view: overdue_report lists unpaid invoices
past due with days overdue and outstanding totals per currency, and it is free too.
Draft a firm chaser to Acme for the two invoices in the 31 to 60 bucket.
Paste this into Claude with the server connected.
dunning_text. Friendly and firm are free. The level 3 final demand is Pro, along with
the A4 statement PDF and statements_report, which ranks every client by what is overdue
rather than by what is large and names the oldest overdue invoice in the whole book.
Build Acme's statement of account for the year to date and give me the text version.
Paste this into Claude with the server connected.
statement_build then statement_text. A statement is not an invoice
reprint: it is opening balance, everything invoiced, everything paid, everything credited, closing
balance. In the recorded run in docs/USER_VALUE_R27.md that came to opening 0.00,
invoiced 1,107.00, paid 500.00, credited 110.70, closing EUR 496.30.
Note what that closing balance did that nothing else in the run managed: it netted a credit note
the invoice store could not see. deposit_apply in the same run reported EUR 607.00 for
the same client. The document you send is right where the mid-month balance question is not, and that
gap is recorded as open defect D-R96 rather than left for a client to find.
Check the invoice was actually receivable. A missing address in the BILL TO block, a wrong VAT id
or a due date the client never agreed to are all reasons a chaser gets ignored rather than paid.
invoice_get returns the full stored record for one number, and
client_add fills in an address on a client that was created from a bare name.
No. It writes the text and you send it. There is no mail integration and no network call anywhere in this server, which also means no chaser goes out because a model decided it should.
A combination of client, period and currency. Rebuilding a statement already in the register costs nothing on any tier, so regenerating the same document after a payment lands is free. Five genuinely different statements a calendar month is the limit.
Yes, statement_aging takes the as-at date. Ageing as at the last day of a quarter is the usual reason, and it produces different buckets from ageing today, which is the point.
statement_aging for everyone, statement_text, dunning_text at friendly and firm, and the invoice server's overdue_report. Pro buys the PDF on your invoice layout, the final demand, and statements_report across all clients. Figures from data/facts.json.
All MCP servers and prices · All guides · Buy the bundle $39