Who owes you, four more report pages — and reminders, notes and a CRM webhook built behind them

Two things below are live for every customer: /owed, and four more report pages. Everything else was built the same evening and is either recording what it would do, or switched off. It is listed so you know it exists, not because you can use it yet.

Who owes you: /owed

An invoice you send is money owed to you until it is paid, and it now lives in the book that way: one entry that says who owes it, the invoice number and, if you give one, the due date. When the payment arrives it is written against the same invoice. Tell the assistant in the chat — “invoice INV-031 to Lotus Studio, 4 200 SGD, due 31 October” — and it is written as owed.

/owed is free: no model, no credits. It reads the book and answers with one total per currency — two currencies are never added together — and a line per customer with the invoice and how many days late it is. Late counts from the due date where there is one, and from the invoice date where there is not.

A payment is matched to the invoice it names. If it names none, it is matched only to the one open invoice for that customer, in that currency, for exactly that amount; otherwise it pays the oldest invoices first. It never pays one customer’s invoice with another customer’s money, or across currencies, and an overpayment shows as a credit rather than disappearing.

finkpr never writes to your customers. Ask the assistant to draft a reminder to one of them and it gives you the text to send yourself.

The assistant knows this shape for invoices: it reached the books with the book update on the evening of 2 October. (#723)

Four more report pages

The month summary and cash by currency now have four companions, each answering one question on its first screen:

• Year to date — the year so far, month by month.
• Accountant view — a trial balance for each currency, debits and credits in their own columns, and the questions still open. Nothing is converted between currencies; where an exchange leaves a currency not netting to zero, the page shows the difference instead of hiding it.
• Month-close check — whether last month is ready to close: which statements cover it, and which entries are still marked uncertain or not yet given an account.
• Statement import — what your latest statement brought in, and which rows still need you. A question answered since the import shows as answered, and the page carries the file’s own counts — rows read, rows already in the book.

They are listed on your book’s page, one row each, and every one has a link you can send to an accountant or a partner that opens that one page and nothing else. In the chat, /report still links to the month summary. (#724)

Built, and not on yet

• A Monday “who owes you” message. At 08:00 in your own time zone, only when something is owed. It is built and running in shadow: it records what it would send, and sends nothing. (#723)
• Reminders you set by asking. “Remind me every month on the 5th to send the payroll file” — the assistant does not promise to remember; it shows a card with the time it understood and two buttons, Set it and Cancel. Nothing is scheduled until you tap Set it, and a double tap still makes one reminder. /reminders lists them, with Cancel on each; those taps are free and never use the model. The assistant has had the ability since the book update on 2 October, so you can set one today — but until messages are switched on, a reminder that comes due is recorded, not sent. (#720)
• Notes when something looks wrong. Three checks, run after your book changes, with no model: a charge that looks like it was recorded twice, an expense more than three times the usual for its account, and a bank or cash account going below zero. Each note comes with buttons to say whether it was right. They are recorded in shadow and sent to no one, so we can read how often they are wrong before any of them reaches you. (#719)
• A signed webhook for your CRM. When a book changes, finkpr can call an address you give it with a signed book.changed message — ids and a count, never amounts or names. Your CRM then reads what changed with its own read-only key. It is built and switched off on our servers; the Twenty recipe is written and has not yet been run against a live Twenty. The book’s feed already carries an entry’s invoice number, due date and customer — that reached the books on 2 October — so a CRM can match a payment to a deal once the webhook is on. (#722)
• Picture cards in the chat. A small picture of the figures in place of a text table. Being tried on our own books first; no customer sees them yet. (#704)