ROIGPT

Money · Built, limited · $299 USD/mo

The books, done

Request a consultation

Built, limited. The software exists. We have not checked it running today, and each business is set up by hand.

Picture this. The invoice was paid on Tuesday. On Thursday a reminder goes out anyway.

That is the mistake this module is built to avoid. When the follow-up job runs, it asks Stripe whether an invoice is still unpaid before it writes a word, and it skips anything already paid, so the customer who settled the bill is left alone.

What it is

The books, done has two jobs. One chases overdue invoices. The other helps you file the bank and card lines behind your books.

Both are built, with limits. Overdue invoice follow-up has the most behind it, so it comes first below.

Overdue invoice follow-up

  • It checks Stripe first

    Before the job writes anything, it asks Stripe whether the invoice is still unpaid. Anything already paid is skipped. The job reads your Stripe account. It does not write to it.

  • It stops itself

    It waits between reminders, stops after a set number, and sends a capped batch each time it runs. If your customer replied, it stops.

  • One switch decides what it does

    Switched off, the job writes drafts for a person to review. Switched on, it sends by the rules, and nobody approves each message first. Which setting suits you is a question for the consultation.

  • One reminder at a time, by hand

    A single reminder sent by hand needs an admin to approve it. The approval covers the exact preview the admin saw.

This part reads Stripe invoices only.

Bank and card lines

You choose a statement file. The software checks that the file matches before it imports anything.

Imported lines go through a review screen and a journal screen before they are filed. Gathering the evidence and committing the entry are separate steps.

Where a person approves

Scheduled invoice reminders

The switch

Off, the job writes drafts for a person to review. On, it sends by the rules, with no approval of each message.

One reminder sent by hand

An admin

The admin approves it explicitly, on the exact preview shown.

Bank statement import

The file check

The import goes ahead only when the file matches the statement you selected.

Ledger entries

A person on the review screens

Evidence and committing the entry are separate requests.

What this does not claim

  • The books do not keep themselves. In the record below, 174 lines had waited about two months before anyone sat down with the screens.
  • No promise of time saved, money collected or fewer late payments. A reminder asks for payment. It cannot make anyone pay.
  • We have not checked this module running today, and the current setting of the follow-up switch was not read.
  • With the switch on, no person approves each message first.
  • Invoice follow-up reads Stripe invoices only.

What the record shows

One record, from Purrify, the founder's own company. It is a past report. It does not show this module running today.

Purrify, the founder's own company ·

A backlog of bank and card lines, filed through the review screens

A written report on working through a backlog of unfiled bank and card lines, using the review and journal screens of the app Purrify runs on. The report calls that app the hub.

Done through the hub's own review and journal screens, run locally. Stripe was only read. Nothing sent or spent.

No line had been filed since about 2026-08-22; 174 lines were waiting, the oldest from 2026-08-04.

157 lines, about [AMOUNT] net out: 130 on the hub's own suggestions (the 10 "maybe duplicate" lines checked: all separate charges), 27 by the standing rules [...]

28 lines remain in the review queue.

What the record shows

  • On October 19, 2026, a backlog of 174 bank and card lines was worked through the app's own review and journal screens.
  • 157 lines were filed. 130 followed the app's own suggestions and 27 followed saved rules. 28 lines stayed in the review queue.
  • Stripe was read and not written.

What this does not claim

  • That the books keep themselves. The report says no line had been filed since about August 22, so a person had to start the work.
  • Who did the work or how long it took.
  • Any benefit. It shows no time saved and no money recovered.
  • Use on a live site. The report says the work ran locally.
  • A clean set of feeds. Two of the three bank connections in the report were out of date or dead.
  • Anything beyond that day. It is the author's own written account, with no screenshot or log.

Settled in the consultation

  • Which setting the follow-up switch would start on for you.
  • What access to Stripe you would grant.
  • How your data would be handled.

Start with a free consultation

Tell us where to reach you, your website and what you want fixed. The consultation is free.

Please do not send customer invoice records through the form.

Request a consultation
Will it send my customers a reminder for an invoice they already paid?
When the follow-up job runs, it asks Stripe whether the invoice is still unpaid before it writes anything, and it skips anything already paid. We have not checked the job running today, so we promise the check and not a result.
Do I approve each reminder before it goes out?
It depends on the switch. Switched off, the job writes drafts for a person to review. Switched on, it sends by the rules with no approval of each message. A one-off reminder sent by hand needs an admin's approval.
Does it need to write to my Stripe account?
The books module reads Stripe and does not write to it. What access you would grant is settled in the consultation.
Modules you are asking about

This covers module fees only. Setup is quoted after your consultation and is not in this figure.

Request a consultation

Share your email, your website and what you want help with. Please do not send customer records through this form.

Modules you are asking about: The books, done

For example: I print shipping labels by hand, or my social posts go out late. One or two sentences is plenty.

We store your request: your email, website, what you want help with, the modules you chose and, if you give it, how you heard about us. See the privacy notice for what we keep. Privacy policy.