Invoice Payment Confirmation Email

The Invoice Payment Confirmation email provides the payer with a receipt after an invoice payment is made. It identifies the payment transaction, payer, payment method, amount, fees, and invoices to which the payment applies.

Invoice payments require the A/R Portal license and must be enabled under A/R Integration.

Configure the template

In Setup > Email Manager, edit Linkname InvoicePaymentReceipt. The default subject pattern is:

Payment to Account (#[TransactionID])

The recipient is supplied by the payment context. Keep enough information to identify the transaction while limiting bank and card data to approved masked values.

Replacement tags

This email supports the shared and Customer tags plus:

Tag	Value
[TransactionID]	Payment-provider transaction identifier.
[PaymentAmount]	Payment amount.
[CustomerReference]	Customer reference for the payment.
[CardLastFour]	Last four digits of the payment card.
[CardType]	Payment-card type.
[RoutingNumber]	Bank routing number associated with the payment.
[BankAccountType]	Bank-account type.
[CardExpiration]	Payment-card expiration date.
[PaymentAddress]	Payer address.
[PaymentCity]	Payer city.
[PaymentState], [PaymentProvince]	Payer state or province.
[PaymentZip], [PaymentPostalCode]	Payer postal code.
[PaymentCountry]	Payer country.
[PaymentFirstName]	Payer first name.
[PaymentLastName]	Payer last name.
[PaymentName]	Payer first and last name.
[PaymentEmail]	Payer email address.
[PaymentPhone]	Payer telephone number.
[PaymentSubTotalAmount]	Payment subtotal before the fee.
[PaymentFeeAmount]	Fee charged for the payment.
[PaymentFeeDescription]	Description of the payment fee.
[Account Email Address], [AccountEmailAddress]	Account email address and login ID.
[WebAddress]	Web address configured for the Site.
[Date]	Email or payment receipt date.
[Global]	Global Message configured for the Site.
[InvoiceTable]	Invoices to which the payment was applied, rendered as a table.

Email Parsing Functions can be used in the body.

Do not add full card numbers, security codes, credentials, or unmasked bank-account values to the template. Review any use of routing or expiration data against the organization’s payment-security and privacy requirements.

Test the result

Use approved payment test methods. Verify the recipient, transaction identifier, masked payment information, subtotal and fee arithmetic, invoice table, currency presentation, and Customer tags. Confirm the wording matches whether payments are applied automatically or require manual application.