For teams that run on Abacus
Abacus overdue invoices, sent to each owner
In Abacus the open items and the reminder run sit with accounting. The people who talk to the customer, such as project leads and account managers, often work outside Abacus, so someone in finance pulls a list and sends it around.
How it goes today
- Open the open items list in Abacus accounts receivable.
- Export it to Excel and filter the invoices that are past due.
- Split the rows by the person in charge of each customer or project.
- Email each part to the right person and ask what they know.
How it can go
Everyone sees the overdue invoices of their own customers each Monday.
Every Monday the open invoices are read from Abacus with their amount, invoice date and payment terms. Invoices past their due date are grouped by the person in charge on the invoice, or by a customer list per person that you give. Each person gets one email with their customers, the open amount, the days late and how late that customer usually pays. Replies are collected in one list for accounting, and the reminders themselves stay in Abacus.
Say this in ChatGPT, Claude or Copilot
Your chat gets connected to Hypamoon first, with this request filled in. Abacus first switches on access for your company when you ask them, which can take a few business days. After that you get the key, or create it yourself, and paste it in the portal, never in the chat.
With Hypamoon, every Monday, read our open invoices from Abacus and take the ones past their due date. Group them by the person in charge on the invoice, or by the customer list per person that I give, and email each person their customers with the open amount, the days late and how late that customer usually pays. Collect their replies in one list for accounting and leave the reminders to Abacus.
Your Abacus administrator creates an API connection with a service user in program Q910 and copies its Client ID and Client Secret, with the address of your Abacus server, which has to be reachable over HTTPS. Abacus Research AG then enables your client for the API and approves the service user within 21 days. It stays yours.