Use this topic to review Smart AI settings for customer matching, prompt hierarchy, tolerance, identifier variants, and remittance validity.

Smart AI configurations support the following matching and extraction behaviors:

• Customer matching: Customer matching uses sender email, sender domain, and payer or remitter name to identify the customer associated with a remittance. When Zuora detects an accounts payable (AP) portal or consolidator, Zuora ignores the email signal because these services use generic domains. Examples include Coupa, Tipalti, and Taulia.

• Prompt hierarchy: Extraction uses three layers: System, Account, and Customer. The System layer provides global defaults. The Account layer defines alternative identifiers, adjustment types, and the free-text How to identify entities note. The Customer layer defines per-customer column mappings, format notes, and the Additional Notes field. The most specific layer takes precedence.

• Match conditions and tolerance: A remittance matches a payment when its amount falls within the configured absolute or percentage tolerance. The default tolerance is ±$1 or ±0.5%. This tolerance accounts for bank charges, foreign exchange (FX) rounding, and withheld tax.

• Identifier variants: Identifier variants define accepted forms of invoice, purchase order (PO), and credit memo numbers. Examples include INV-001, 001, and INV001. These variants allow remittances that use the customer format to match the corresponding records.

• Remittance validity: Remittances older than the configured validity window are treated as expired and excluded from matching. The default window is 30 days.