Skip to content
Hypamoon

For teams that run on Minuba

Minuba invoices per customer: one mail

In Minuba each order gets its own invoice. A housing association, a shop chain or a property manager with ten small jobs a month then gets ten separate invoices, and the office downloads each PDF and puts them in one email by hand.

How it goes today

  1. Find the approved invoices of that customer for the month.
  2. Download each invoice as a PDF and save it.
  3. Write a mail and attach the PDFs one by one.
  4. Keep a note of which invoices went in which mail.

How it can go

A customer with many jobs gets their invoices together, with an overview.

For the customers you pick, the approved invoices of the month are gathered after the last working day. You get one mail ready to send per customer, with each invoice as a PDF and an overview on top with invoice number, order, address and amount, and the total. Each invoice stays its own invoice in Minuba, so payments and reminders work as they do now.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. Minuba works with a sign-in instead of a key, through an app that has to be approved first. That can take several business days; after that you sign in to Minuba once, never in the chat.

Your request

With Hypamoon, for the customers I pick, gather their approved Minuba invoices of the month after the last working day. Make one mail per customer with each invoice as a PDF and an overview on top with invoice number, order, address, amount and the total. Show me the mails before they go out.

Minuba gives each app its own client ID and secret through a Minuba partner manager, who registers the app first. After that someone with a Minuba login signs in once and approves what the app may read and change. It stays yours.