Invoice feedback from Kokichi Watanabe

I’m quite impressed with the human-readable invoice format. I have a feeling that this could be well received on a daily working site. If I may offer a few suggestions:

1. The invoice needs to have

(1) Shipping mark (indispensable for linking the document with the goods).

(2) Discount/surcharge.

(3) A free-write column to absorb any description that falls outside the standard format and is required by the individual contract.

(4) Mark to indicate the existence of an attachment outside the standard format.

2. It would be better to move the column 'Items Shipped' at the end of the paper because the number of repetitions is unpredictable.

3. Ensuring continuity of responsibility for the integrity of the invoice is essential.

It would be helpful to clarify how the responsibility of the original signer extends to the human‑readable rendering, given that the signer cannot directly verify the contents of rendered output.

In the meanwile, is this Lightweight format compatible with EN16931 in general (assuming convertion XML-JSON)?

Best regards

Kokichi Watanabe