Agents In Use
What’s new todayLast update
1005 additions

Claude Code builds invoices with bank matching

van der Eng reports sending monthly invoices from a Claude Code-built tool with branded PDFs, payment QR codes, bookkeeper BCC and bank-reference matching, after importing history back to 2018.

OUR ADAPTATION

Suggested prompt

Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.

Build an invoicing workflow with branded PDFs, payment QR codes and the agreed bookkeeper copy. Import existing invoice history, match paid status only using verified invoice references, and show unmatched payments and reminder drafts for review.

What happened

van der Eng reports sending monthly invoices from a Claude Code-built tool with branded PDFs, payment QR codes, bookkeeper BCC and bank-reference matching, after importing history back to 2018.

Reported by Mark van der Eng

How the agent did it

  1. Define the invoice PDF, QR payment and bookkeeper-copy requirements.
  2. Build the workflow with Claude Code and import historical invoice records.
  3. Send the month’s invoices through the new tool.

Where a person stepped in

van der Eng chooses requirements and sends invoices and reminders. The post does not document exception handling or independently audited compliance.

Mark van der Eng uses Claude Code to build his own invoicing tool and reports sending that month’s invoices through it. The operational requirements are concrete: branded PDFs, payment QR codes and a copy to his bookkeeper, plus less manual checking of the business bank account.

He imports invoice history back to 2018 before using the new workflow. The running tool watches for payments containing an invoice number in the reference and marks the matching invoice paid. He also adds three reminder levels, from friendly to final notice, in Dutch and English, each initiated with a click.

Claude Code is credited with building the software; the post does not establish that a language-model agent makes each live payment match. The described matching condition depends on a usable invoice reference. No fallback for missing or ambiguous references is shown.

The author characterises the invoices as compliant, but the post supplies no independent legal or accounting audit. This entry therefore records the operational artifact and the author’s actual monthly use, without guaranteeing compliance or universal savings. The useful detail is joining payment status to a stable invoice identifier and importing historical records before replacing an existing workflow. Review of totals, message recipients and exceptional bank references remains necessary for anyone adapting that pattern.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: LinkedIn · Mark van der Eng

Frequently asked questions

What links a payment to an invoice?

The invoice number placed in the payment reference.

What history was imported?

The author reports importing all invoice history back to 2018.

Does this establish legal compliance?

No. Compliance is the author’s description, without an independent audit or sufficient detail to verify every requirement.

More details

Remaining steps

  1. Match payments using their invoice-number reference.
  2. Initiate the appropriate Dutch or English reminder level when needed.

About this account

Claude Code constructs the invoicing tool; its running payment watcher matches invoice references and updates status, without a demonstrated live LLM decision at each match.

Firsthand account by Mark van der Eng; original publication date verified against Main LinkedIn post metadata datePublished2026-08-16T07:15:48.917Z; nested comments excluded. Outcomes are the author’s reports, not independently reproduced. Suggested prompt written by Agents In Use; not the author’s original prompt.

Credit: Mark van der Eng

Source published 16 Aug 2026

Source checked 14 Oct 2026

Tools and topics

Claude Code · Branded invoice PDFs · Payment QR codes · Bank payment references · Bookkeeper BCC

Invoice-reference matching · Historical invoice migration · Clicked bilingual reminders

Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.