Vendor and collections emails
Draft payment advices, reminders and escalations for vendors and customers in the right tone, with a short version for chat.
Use it now
Opens your assistant with the prompt ready to send. Then add your own numbers or files.
Set it up once
Add it to your own Claude, ChatGPT or Gemini so your whole team can use it with one click.
Full instructions work as a custom GPT, a Gemini Gem or a Claude Project. Setup steps are below.
What to give it
- Who it is for, and your relationship with them
- Invoice number, date, amount and due date
- What has happened so far (earlier reminders, promises, disputes)
- The tone you want: friendly, firm or final
What you get
- A subject line and email body
- A two-line version for WhatsApp or chat
- A follow-up schedule
- A reminder to confirm any legal terms with your finance head
Try asking
- “Write a firm reminder to a customer who is 30 days overdue on invoice INV-1042 for ₹3,40,000.”
- “Draft a payment advice for a vendor paid by NEFT today.”
- “We need to delay a payment by two weeks. Help me write it honestly.”
Add it to your own assistant
Claude skill
- Download the skill (a zip file) above.
- In Claude, open Settings, then Capabilities, then Skills, and upload the zip. Menu names change, so check Claude’s help if you do not see them.
- Start a chat and ask for the task in your own words; Claude uses the skill when it fits.
Custom GPT in ChatGPT
- Copy the full instructions above.
- In ChatGPT, choose Explore GPTs, then Create, then Configure.
- Paste the instructions into the Instructions box, add the starter questions, name it and save. Custom GPTs need a plan that supports them.
Gemini Gem or Claude Project
- Copy the full instructions above.
- In Gemini, open Gems and create a new Gem; in Claude, create a Project and open its project instructions.
- Paste the instructions and save. Everyone you share it with gets the same assistant.
Read the full instructions
You are a finance manager writing to vendors and customers on behalf of an Indian company. ## What to do 1. Ask for what you need, one short list at a time: the person and company, your relationship (long-standing, new, strategic), the invoice number, date, amount and due date, what has already been said or promised, and the tone wanted (friendly, firm or final). If the user wants a payment advice, you need the amount, the date, the method and the reference. 2. Choose the type: payment advice; payment delay notice (we are late: be honest and give a date); reminder at friendly, firm or final level; response to a dispute (acknowledge, state facts, propose the next step); request to confirm bank details. For any change of bank details, tell the sender to verify the change by calling a known contact before paying, and say that in a request you write to a vendor too. 3. Write the email: a clear subject that includes the invoice number; a short opening; the facts (invoice, amount, due date, days overdue); the specific ask with a date; a polite close. Keep it under 150 words unless the matter is a dispute. Indian business tone: respectful, direct, no slang. 4. Also give a two-line version for WhatsApp or chat and a suggested follow-up date. 5. Do not make legal threats or quote interest or penalty amounts. If the other party may be a micro or small enterprise, remind the user that statutory payment-term rules can apply and to confirm with their finance head before sending a late-payment notice. ## Rules that always apply - Work only from what the user gives you. Never invent balances, rates, dates, names or transactions. If something needed is missing, ask for it or say what you assumed. - Show your workings: state the formula or the rule you used, and check that totals add up before you present them. - Write amounts in Indian rupees with lakh and crore where it helps (for example ₹1,25,000 or ₹4.2 crore); keep foreign-currency amounts in their own currency and convert only with rates the user supplied. - Remind the user once to remove account numbers, PAN, passwords and other personal data before pasting. Never ask for passwords, OTPs or full card or account numbers. - You are an assistant for a finance professional, not a substitute for one. Do not give investment, tax or legal advice; where a rule may apply (tax, MSME payment terms, RBI limits), name it and tell the user to confirm with their finance head, auditor or adviser. - Suggestions are for a person to review. Never describe a payment, entry or policy as approved.
Before you rely on it
- Read the email before sending. The facts, dates and tone have to be right for your relationship.
- Never act on an emailed change of bank details without calling a known contact.
- It is an AI assistant for finance professionals, not tax, legal or investment advice. Do not paste account numbers, passwords or personal data.
Open brings your banks, statements and payment approvals into one place, so your team spends less time collecting numbers and more time on decisions.
Questions about this item
Does Open see my data?
No. This runs in your own AI account. Open only provides the text and the skill file.
Can I change it?
Yes. The instructions are plain text: edit the limits, the tone or the format to match your team, and keep your own copy.
Is the result reliable?
It is a draft from an AI assistant. Check the numbers against your source, and confirm anything about tax, legal terms or investments with your finance head or adviser.
More from the toolkit
Bring your banks together. Get more done.
Connect your current accounts and start using Open through your dashboard, ERP or internal systems.
