The AgentivUse cases

Chase overdue FlowAccount bills every Monday

An agent that reads overdue billing notes and tax invoices from FlowAccount through FlowAccount's own MCP server in read only mode, checks receipts for each customer, and drafts polite Thai payment reminders in Gmail for the owner to check and send

Function: FinanceEffort: About a weekPublished: 2026-10-24Market: Thailand
FlowAccountClaude CodeGmail

The problem

Thai SMEs that give customers credit terms issue billing notes and tax invoices in FlowAccount, then someone has to scroll through every document each week to see who is past the due date and still has not paid. The reminders go out late or not at all, because writing a polite Thai follow up to a regular customer feels awkward, and the cash stays with customers longer than it should.

How the agent works

  1. It starts

    Every Monday morning a Claude Code routine starts FlowAccount's open source MCP server with the company's Open API credentials in its default read only mode, which exposes only GET tools such as list_tax_invoices, get_tax_invoice, list_receipts and list_contacts.

  2. The agent works

    The agent pulls the last few months of billing notes and tax invoices with the server's date filters, keeps the ones whose dueDate has passed, and checks the receipts issued since then for the same customer; anything that looks paid, part paid or short by withholding tax is put on a 'verify' list instead of being chased. For each remaining customer it groups every overdue document into one reminder in Thai (or English for foreign clients), with document numbers, amounts and due dates taken from FlowAccount and the company's receiving bank account read from FlowAccount, never typed from memory or copied from an email. Each reminder is saved as a Gmail draft through the Gmail connector, and the owner gets a summary table of customer, documents, days overdue and total, plus the verify list.

  3. The result

    The accountant checks the verify list against the bank statement, the owner reads the drafts and sends them, and the agent never gets write access to FlowAccount.

Worked example

The api-mcp README in FlowAccount's open-api repository on GitHub describes a local stdio MCP server, one process per company, that reads credentials from ~/.config/flowaccount/openapi.json, signs in with the client_credentials grant and keeps the Authorization header away from the model. It exposes 34 read only GET tools by default; --allow-write raises that to 166 tools including create, payment and delete, and the README warns that those writes are real and should be tried on the sandbox first. The bundled API spec shows due date fields (dueDate, creditDays) and contact fields (contactName, contactEmail, contactTaxId) on documents, and FlowAccount also offers a hosted AI Connector at mcp.flowaccount.com that signs in by browser OAuth for owners without Open API credentials. The reminder pattern follows Anthropic's invoice-chase skill: one email per customer covering all their overdue invoices, recent payers set aside as 'possibly paid, verify', and nothing queued without the owner's approval; that skill supports Xero, QuickBooks and other ledgers but not FlowAccount, which is the gap the MCP server fills. Neither source reports a customer result, so measure your own: the overdue total each Monday and the days from due date to payment.

Data protection. This use case touches personal data, so check the rules where you operate (for example GDPR, PDPA). Billing contacts are often named people with their own email and phone number, which is personal data under Thailand's PDPA, and for sole proprietor customers the tax ID is their national ID number. Keep the agent read only, keep tax IDs out of the drafts and the summary, send the summary only to the owner and the accountant rather than a group chat, and check your AI vendor's data processing terms before connecting production data.

Join the Agent OS Club

8 weeks to the AI team a 50 person company would hire. Instant access to our agent blueprints. USD 15 a month, cancel any time.

Join the Agent OS Club

Building this for an organization? Learn more at theagentiv.com

Sources

Related use cases

Monday morning, the whole business on one page

A weekly owner brief that puts cash, sales, pipeline and overdue invoices on one page every Monday, built from the accounting, CRM and payment tools the business already uses, with Claude Cowork

FinanceEffort: An afternoonClaude Cowork · Intuit QuickBooks · Xero

The owner of a small company starts Monday by opening the bank app, the accounting software, the CRM and the payment dashboard, and still cannot say in one sentence how the business stands. The numbers live in four tools, nobody has time to stitch them together, and overdue invoices get noticed when cash runs short.

Payroll and invoices prepared for one approval

An agent that turns a stack of pay slips into one bulk payroll transfer and a client list into drafted invoices, with deterministic checks beside the model and the owner's approval before anything moves, the way Qonto built it on Claude

FinanceEffort: About a weekClaude · Qonto · Amazon Bedrock

At month end the owner of a ten person company keys every salary into the bank one transfer at a time, then creates each client invoice by hand from a spreadsheet. The work is repetitive, the typing errors are expensive, and it always lands on the busiest days of the month.

Every LINE payment slip checked with the bank

A LINE agent that verifies every payment slip a customer sends against the bank through EasySlip, matches the amount to the order in Google Sheets, catches duplicate and fake slips, and confirms the order or flags it for a person

FinanceEffort: About a weekLINE · EasySlip · n8nThailand

An online shop in Thailand that takes bank transfers through its LINE Official Account has someone comparing slips to the bank app all day. Miss one and the goods ship against an edited slip, or the same slip pays for two orders, and the busier the day the more that slips through.