Invoice template feedback - from Kokichi Watanabe

Posting this on behalf of Kokichi San.

Dear group members of UNVTD 2026.04.16 UNVTD Invoice Template proposal by Kokichi Watanabe (observer, Japan)

Regarding the Invoice Template, I would like to present two proposals that aim to support and complement the existing UNVTD framework.

1. Renderable Invoice Template A draft renderable invoice format was presented in a previous session. Drawing on my background in the business sector, I reviewed the draft with Recommendation No. 6 in mind. The attached proposal and comments reflect this practical viewpoint and are intended to support implementation while fully respecting the UNVTD model. For an example of the reviewal, in the draft, “Expiration Date” appears under the “Document Verification” section. While this date may be important for VC‑related functions, invoices remain valid until the statutory limitation period expires, which varies by country. To avoid confusion, it would be preferable to use a different label name (“Expiration Date of Current VC” may be a candidate) and not render this item. It has been pointed out that the supply‑chain network may become congested where stakeholders cannot utilize JSON within UNVTD. In addition, field operators—who frequently handle cargo and other tasks using visual documents—place high value on clear and compact rendering. To support their needs while maintaining the integrity of the UNVTD model, I propose distinguishing between information required for business operations and information needed mainly for functions such as VC. Business‑relevant items would be rendered, while other data could remain in the background, preserving a familiar and efficient layout for on‑site use. To keep the visible portion compact, business‑related information should also be selected carefully, omitting items already evident from contractual arrangements. The free‑write area and attachments serve as flexible mechanisms, even if these elements fall outside automated algorithmic processing unless appropriate measures are taken. It is intended only for contractually indispensable information that cannot be omitted but does not fit within the main template. Addressing these operational realities and gaining support from field operators may be important for promoting UNVTD.

2. Optional Fixed, Ready‑Made Template Without Customization In addition to the standard use of this template as an internationally standardized format, I propose introducing a separate optional mode: a “ready‑made mode.” The template itself, used in this mode would be exactly the same as the rendering template to be officially published on the UNVTD website. The only difference lies in how it is used. In the ready‑made mode, users would not customize the template, and using it in this mode would imply acceptance of predefined usage rules. The rule would serve as a shared operational understanding among users, rather than a formal international agreement. In effect, it would function as a pre‑defined set consisting of the template and its associated rules. This approach enables a practical adoption pathway. For example, an importer could request exporters in multiple countries to use the ready‑made invoice set published on the UNVTD website. Because the template and rules are openly available, exporters would not require additional explanation or prior coordination; they would simply check the published set and respond accordingly. For importers or exporters without IT departments or similar resources, this could dramatically lower the barrier to adopting UNVTD. The key point of the ready‑made template and rule‑set concept is that private‑sector entities engaged in day‑to‑day operations cannot individually develop such a set and promote it globally. Only international organizations such as UN/CEFACT are in a position to take on such an initiative.