Invoice Memo

Overview

Invoice memo is an optional note attached to an invoice to provide context such as an internal reference, customer instruction, service period, purchase-order number, or brief explanation. It is usually not a structured financial field and should not replace line items, contractual terms, destination tags, or payment identifiers. Visibility must be defined because a memo can appear on customer pages, reports, exports, callbacks, or internal dashboards.

A customer-facing memo can explain what the invoice covers or include a non-sensitive reference. An internal memo can document collection or review details and should not be exposed externally.

In blockchain contexts, memo can also mean a network-level destination identifier. Invoice systems should use separate field names so a free-text invoice note is never mistaken for a required payment memo.

Free text should be length-limited, safely encoded, and protected from HTML, spreadsheet-formula, log, or command injection. Sensitive personal data should be avoided.

Risks include leaking internal notes, unsupported characters, malicious content, inconsistent translations, and critical payment instructions hidden inside an unvalidated note.

Systems should store memo type, audience, author, timestamp, locale, original text, sanitization, version, and any structured references separately.

For Invoice Memo, the operational boundary with Payment Memo and Address with Tag or Memo should be explicit. Identifiers for Invoice Memo should connect those records without allowing either linked status to overwrite its own state.

For Invoice Memo, the invoice and the payment used to settle it should remain separate records. When Invoice Memo interacts with Payment Memo, the invoice defines the commercial obligation, parties, amount, denomination, tax, due date, and revision history; payment records hold quotes, addresses, transaction identifiers, confirmations, fees, refunds, and settlement. In the relationship between Invoice Memo and Address with Tag or Memo, keeping these layers separate prevents a late payment, repricing event, or refund from silently changing the document originally issued to the customer.