Copy-ready supplier messages

Product update email template: feature launch, action required and no-action updates

Copy-ready SaaS product update emails for a requested feature, a material workflow change, an action-required notice and a no-action update, grounded in verified release evidence rather than invented benefit claims.

No email gate. Copy the wording only after a human reviewer has checked the exact invoice and the supporting evidence. For UK VAT errors, HMRC guidance says to go back to the supplier for the appropriate replacement/correction rather than silently editing the received invoice.

Copy-ready messages

Name the exact discrepancy. Ask for the exact correction.

Amount or VAT discrepancy — correction requested

Subject: Invoice [INVOICE NUMBER] — correction requested

Hi [SUPPLIER CONTACT],

We are reviewing invoice [INVOICE NUMBER] dated [INVOICE DATE] and found the following discrepancy:

Invoice shows: [AMOUNT / VAT / FIELD AS SHOWN]
Our supporting evidence shows: [EXPECTED VALUE + EVIDENCE REFERENCE]
Difference: [EXACT DIFFERENCE]

Please review and, if the invoice is incorrect, send the appropriate corrected or replacement invoice / credit note so we can continue our internal review.

If your records show the invoice is correct, please reply with the basis for the amount so we can reconcile the exception.

Thanks,
[NAME / AP TEAM]

Possible duplicate invoice — confirmation requested

Subject: Possible duplicate — invoice [INVOICE NUMBER]

Hi [SUPPLIER CONTACT],

During review of invoice [INVOICE NUMBER], we found a possible duplicate against [RELATED INVOICE / REFERENCE].

Please confirm whether both invoices are valid and separately payable. If this invoice was issued in error, please confirm the correct cancellation / credit-note or replacement-document path for your records.

We have not treated the invoice as resolved or approved while this check is open.

Thanks,
[NAME / AP TEAM]

Corrected document received — pending internal review

Subject: Received — correction for invoice [INVOICE NUMBER]

Hi [SUPPLIER CONTACT],

We have received the corrected document / credit note for invoice [INVOICE NUMBER].

It is now pending our normal internal review. This acknowledgement confirms receipt only; it does not confirm invoice approval or payment release.

We will follow the normal AP process if anything else is needed.

Thanks,
[NAME / AP TEAM]

Before sending

The email is the handoff, not the evidence.

- [ ] Affected customer or account segment is named before the message is drafted
- [ ] Subject line describes the verified customer-facing change rather than the internal project name
- [ ] Opening line states what changed for the reader in plain language
- [ ] Customer consequence is limited to behavior the release evidence actually supports
- [ ] Required action is explicit when there is one, including a real deadline where applicable
- [ ] No-action updates say “No action required” instead of manufacturing a CTA
- [ ] Feature availability, plan or rollout limitations are stated when relevant
- [ ] Links point to the exact product screen, documentation or release detail needed for the next step
- [ ] Hoped-for adoption, productivity, revenue or conversion outcomes are not presented as release facts
- [ ] Human reviewer approves audience, claims and send decision before customer distribution

Evidence boundary

A supplier reply is not an approval event.

Keep the original invoice, discrepancy evidence, supplier response and any replacement invoice or credit note linked. Re-review the corrected evidence before closing the exception.

InvoiceGuard can help a human reviewer focus on extracted fields and deterministic exceptions. It does not decide contractual liability, tax treatment, payment rights, accounting entries or whether a supplier-issued correction is legally sufficient for every jurisdiction.

Next: review the evidence, then use the supplier message.

Customer guide

Product update email template: feature launch, action required and no-action updates

Name the exact discrepancy. Ask for the exact correction.

Amount or VAT discrepancy — correction requested

Possible duplicate invoice — confirmation requested

Corrected document received — pending internal review

The email is the handoff, not the evidence.

A supplier reply is not an approval event.

Next: review the evidence, then use the supplier message.

What AP should check before asking for a correction

Write release communication from evidence, not hallucinated product claims

Evidence-backed release notes vs generic AI release-note generator

ShipStory Release Communication Pilot