A selected export
The invoice rows below, reviewed on . No other records are needed for this example.
Work in practice
Prepare the reminders.
Leave sending to me.
Checking unpaid invoices is familiar work. A useful first task is to prepare the reminders, with the amount and due date easy to check before anyone sends them.
Inspect the exampleOne useful task.
A clear finish.
“Use this export to prepare reminder drafts for overdue, unpaid invoices. Leave out anything already paid or not yet due. Flag missing details for me to check.”
Drafts you can check
Each draft keeps its invoice number, amount and due date attached to the source row.
Review, then send
Check the details and whether a reminder is appropriate. Sending remains a separate action.
Four rows.
Different next steps.
The review date is fixed at 24 October 2026, so you can check why each row is included or left out.
| Invoice and customer | Amount | Due | In the export | Next step |
|---|---|---|---|---|
| INV-104Canal Studio | €1,280.00 | Unpaid | Prepare a draftUnpaid and overdue, with the details needed for a draft. | |
| INV-105North Workshop | €480.00 | Paid | Leave it outAlready marked paid. | |
| INV-106Park Office | €950.00 | Unpaid | Leave it outNot overdue on the review date. | |
| INV-107Harbour Print | Amount missing | Unpaid | Check the missing detailDetails are missing or invalid. Ask the source owner before preparing a reminder. |
One reminder
ready for review.
North Workshop is already marked paid. Park Office is not due yet. Harbour Print needs its missing amount checked. Only Canal Studio has the details needed for an overdue reminder.
Draft for Canal Studio
Source row: INV-104Subject: Invoice INV-104 — payment reminder Hello Canal Studio team, Invoice INV-104 for €1,280.00 was due on 16 October 2026. It is marked unpaid in the export reviewed on 24 October 2026. Could you let us know when we can expect payment? If you have already paid, please share the payment reference so we can check it. Thank you, [Your name]
Before sending: check the recipient, amount, due date and whether a payment arrived after this export.
Put the boundary
in the setup.
An instruction to “prepare, but don’t send” describes the job. The connected tools determine what an agent can actually reach.
The setup we would agree for this task
- Read
- The selected invoice export, with read-only access.
- Write
- A separate place for reminder drafts.
- Not connected
- Email sending, payment tools and changes to the accounting records.
- Stop and ask
- A missing detail, a different source or a request to take an action outside that setup.
There is room to finish the preparation work. Sending a reminder would require a separate tool and decision. We would verify those permissions and the execution environment before a real run.
This is an example design, not a claim that every Odin integration has these permissions or isolation. Read the execution and guard boundaries. The approach follows OWASP’s guidance on least agency.
What would you
hand over first?
Bring one task, the material it needs and the decision you want to keep. We can work through the setup together.