Skip to content
Hypamoon

For teams that run on Standard Books

Standard Books payment reminders on a schedule

Standard Books can text customers about unpaid invoices and email them a statement, but someone has to start that run by hand from a maintenance function, so reminders wait until there is time. Excellent itself names a notice when a customer passes the due date as something worth automating. Sales staff also ask the accountant whether a customer has paid before a visit.

How it goes today

  1. Open the unpaid invoices in Standard Books and filter on the due date.
  2. Go through the receipts since the last run to see who has paid.
  3. Start the text or statement run for the customers that need a reminder.
  4. Keep track of who already had a second reminder and who should get a call.

How it can go

Overdue invoices get a friendly reminder on your schedule, and payments clear them from the list.

Each morning you see which confirmed invoices are past their due date with an amount open, per customer, worked out from the receipts booked in Standard Books. On your yes, or on the schedule you set, for example 7 and 21 days after the due date, each customer gets one email with their open invoices, sent from your own address. Invoices marked for no reminders are left out, and a customer who pays drops off the next list. Interest and collection stay with you.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. Standard Books first switches on access for your company when you ask them, which can take a few business days. After that you create the key yourself and paste it in the portal, never in the chat.

Your request

With Hypamoon, each morning, list the Standard Books invoices that are past their due date with an amount open, per customer. Send each of those customers a friendly reminder with their open invoices from our address 7 days after the due date, and a second one after 21 days. Leave out customers who have paid since, and send me a summary of who got what.

You ask Excellent to switch on the API module for your company; in the cloud version their administrator also sets up the secure web address. You then create a separate API user with a validated email address in a user group with the Rest API right and access to the registers it needs. Its sign-in details are the key, and they stay yours.