ATW-INPUT-TYPE — E-Invoice Validation Rule & Fix

Fixture ID: wrongType · XPath: N/A (Computed / Semantic Rule)

1. Why This Rule Triggers (Diagnostic Message)

payment.meansCode should be text, but it is a number. The rules and the generators rely on the InvoiceInput types.

2. How to Fix ATW-INPUT-TYPE

Set payment.meansCode to text, or leave it out. A value parsed from JSON or a form is the usual cause: "19" where 19 is expected, or null for a field that is simply absent.

3. Valid Code / Payload Example