June logo
JuneDocumentation
Recipes

Chase overdue invoices

June finds the overdue invoices in your sheet or mailbox, drafts a payment reminder mail for each, and brings the thread back on the day you set to check again.

You get the overdue invoices, a payment mail drafted for each in your mailbox, and the thread back on the day you want to check again.

What you need

  • Where your invoices are: an Excel sheet in OneDrive or SharePoint through Microsoft 365, a Notion database through Notion, or the invoice mails you sent, in your mailbox. For a Google Sheet, give June its link through Google Drive, or attach a CSV export for a one-time review.
  • A mailbox for the drafts: Gmail or IMAP on the Mailbox card, or Outlook through Microsoft 365. Without one, June writes the mails in the chat.

Set it up

In one of your own chats, tell June where the invoices are and what counts as overdue.
June names each overdue invoice with its customer, amount and days overdue, and saves one payment mail per customer as a draft. Check them in your mail app and send the ones you agree with.
Ask for a reminder on the day you want to check again. On that day, reply to the reminder, and June reads the list again and drafts a firmer mail for each invoice still open.
Read Invoices 2026.xlsx in my OneDrive. Which invoices are more than 14 days past due? Draft a friendly payment reminder to each customer and save them as drafts in Outlook
Remind me next Friday at 9:00 Berlin time to check whether Meyer GmbH and Kranz & Söhne have paid
Copy into your current chat
Read Invoices 2026.xlsx in my OneDrive again. For everyone still unpaid, draft a firmer second reminder that names the original due date
Copy into your current chat

To have June check every week without you, use a schedule with the integrations toolset on, from the form or by asking June; see two ways June comes back.

Check the result

Before sending a draft, compare its invoice number, amount, due date, and recipient with your original records. June's list is a starting point for review; a late invoice may already have been paid outside the source you gave it.

Draft a friendly payment reminder for invoice 1042. It is twelve days overdue. Ask when payment is expected, keep it under 100 words, and leave the customer name for me to fill in

Here is a draft. Nothing goes out until you send it. > Hi [customer name], a friendly reminder that invoice 1042 is twelve days overdue. Could you let me know when payment is expected? Please let me know if you need another copy of the invoice. Many thanks, [your name]
The result is a draft to review. This example stays in the chat; a connected mailbox can hold the draft in your mail app.

You are done when the right customers have reviewed drafts and the next check has a confirmed time. If June cannot reach the source, check the connection before setting the check to repeat.

What June does not do

  • This recipe asks for drafts, not sending. Review the recipient and amount before sending in your mail app, or approving a Gmail send through June.
  • The instructions above do not ask June to change the sheet or mark an invoice paid. It checks only when you ask or a work schedule runs; a reminder alone does not check payments.
  • A partial read is not a complete invoice audit. For a spreadsheet in OneDrive, June reads files up to 8 MB, the first 2,000 rows of each sheet, and about 20,000 characters per read (50,000 at most); of a Google Sheet, up to 1,000 rows of one tab per read (200 unless you ask for more).