Category: Digital Invoice

  • Structured CSV: Expressing XML Hierarchies in a Single Sheet

    Structured CSV: Expressing XML Hierarchies in a Single Sheet

    Views: 2 Structured CSV: Expressing XML Hierarchies in a Single Sheet Nobuyuki Sambuichi 2025-04-13 Structured CSV is a standards-based format derived from the xBRL-CSV specification, enabling complex hierarchical data to be recorded in a flat, tabular form. It is not a simple dump of relational tables. Instead, it uses structured conventions and a metadata-driven approach to express multi-level business documents — such as invoices or journal entries — in a single CSV sheet. 1. Based on xBRL-CSV Structured CSV follows the xBRL-CSV syntax model, where: A CSV file holds the fact data — one row per fact. A JSON metadata file defines the table structure, the dimensions and members for […]

  • Peppol Implementation in Finland: Expansion from e-Invoicing to Commercial Transactions and Logistics

    Peppol Implementation in Finland: Expansion from e-Invoicing to Commercial Transactions and Logistics

    Views: 4 Peppol Implementation in Finland: Expansion from e-Invoicing to Commercial Transactions and Logistics ChatGPT (Edited by Nobuyuki Sambuichi) Peppol (Pan-European Public Procurement On-Line) is an international project aimed at promoting the standardization of e-procurement and e-commerce. In Finland, the implementation and adoption of Peppol have been actively promoted alongside the mandatory introduction of e-Invoicing. Particular attention has been paid to the utilization of Post Award functions such as Advanced Ordering and Peppol Logistics. The adoption of Peppol standards in Finland has been led by the State Treasury, serving as the Peppol Authority, which promotes the digitalization of not only e-Invoicing but also order processing and logistics processes. As a […]

  • Feedback on JP PINT V1.0 Current State

    Feedback on JP PINT V1.0 Current State

    Views: 16 Feedback on JP PINT V1.0 Current State Table of Contents 1. What is XML Selector? 1.1. XML Selector and XPath for UBL Invoice 1.2. Issue with Selector cac:PartyTaxScheme[cac:TaxScheme = “VAT”] 2. Enhancing Open Peppol Standards with the Adoption of XPath 2.1. The Benefits of Adopting XPath 2.2. Recommendation to Open Peppol 3. Elements correctly defined in syntax binding through selector specification 3.1. Selector for Additional Document Reference (DocumentTypeCode = 130) 3.2. Selector for LINE OBJECT IDENTIFIER 4. Errors in Syntax Binding 4.1. Issue with Selector for Additional Document Reference (DocumentTypeCode != 130) 4.2. Issue with Selector for Party Identification (SEPA scheme) 4.3. Selector for Party Tax Scheme (TaxScheme […]

  • Digitalization of Small and Medium Enterprises through Core Invoice

    Digitalization of Small and Medium Enterprises through Core Invoice

    Views: 24 Digitalization of Small and Medium Enterprises through Core Invoice Table of Contents 1. Is JP PINT a Panacea? 2. Think of it as Cargo Ship Container Transshipment 3. Syntax Binding 4. Journal Entry Information Search Browser 5. Digitalization of Accounting Initiated by Electronic Invoices 6. Explanation for XML Technologists 6.1. Logical Model of Digital Invoice 6.2. Elements of Digital Invoice 6.3. XML Syntax and XPath 7. Basics of XML Syntax and XPath 7.1. Fundamentals of XML 7.2. Basics of XPath 7.3. Utilizing XML Syntax and XPath 8. Detailed Explanation of Syntax Binding 8.1. JP PINT Syntax Binding 8.2. SME Common EDI Syntax Binding 9. Detailed Analysis of Journal […]

  • The New Era of Data Conversion: Data Binding through Hierarchical Tidy Data

    The New Era of Data Conversion: Data Binding through Hierarchical Tidy Data

    Views: 18 The New Era of Data Conversion: Semantic and Syntactic Binding through Hierarchical Tidy Data Table of Contents 1. Overview 2. Standardized CSV through Hierarchical Tidy Data 2.1. Hierarchical Tidy Data 2.2. Example: Invoice with Detail Lines 2.3. Adding Tax Amounts by Taxation Classification 3. Hierarchically Defined Semantic Model 4. Syntax Binding 4.1. JP PINT Syntax Binding 4.2. SME (Small and Medium Enterprises) Common EDI Syntax Binding 4.3. Core Invoice Gateway Conversion Process 5. Semantic Binding 5.1. Processing Flow 5.2. Processing Flow of Semantic Binding and Syntax Binding 5.3. Detailed Semantic Binding 6. Example: Japan PINT Invoice UBL Example1-minimum.xml Nobuyuki SAMBUICHI ISO/TC295 Audit data services/SG1 Semantic model Convener This […]

  • The Risk of Unauthorized Code Addition to Standardized Tables by Open Peppol

    The Risk of Unauthorized Code Addition to Standardized Tables by Open Peppol

    Views: 7 The Risk of Unauthorized Code Addition to Standardized Tables Nobuyuki SAMBUICHI ISO/TC295 Audit data services/SG1 Semantic model Convener The United Nations Code List is revised twice a year. The designated contact point for this process is the United Nations Centre for Trade Facilitation and Electronic Business (UN/CEFACT) Japan Committee, represented by the Supply Chain Information Platform Study Group (SIPS). If additional codes are required for JP PINT compliance, it is advisable to follow the official procedure by submitting an application through this contact point for registration. While Singapore has independently added codes for their own requirements, there are certain issues associated with it. Therefore, the proper approach for […]

  • Can schematron validation rules from JP PINT 0.9.2 make your validation  Compliant?

    Can schematron validation rules from JP PINT 0.9.2 make your validation Compliant?

    Views: 57Peppol authority of Japan announced new releaseJP PINT 0.9.2 . PINT Complience states; Senders compliance to PINT based BIS A sending party may claim compliance to the Peppol International model if they send invoices that comply with the rules of the Peppol International Invoice when applied without any specialized rules even if that document may at the same time comply with any set of specialized rules. Processing of rules A sender SHALL NOT send messages that are not compliant to the BIS specification identified by the customization. A sender shall validate an outgoing message that are in line with the customsation identifier. I would like to compare this version […]

  • Pool/template rules with abstract Schematron

    Pool/template rules with abstract Schematron

    Views: 53Comment from Mr. Oriol Bausà on 2022-02-27. There was an additional idea behind this architecture: the possibility to use different syntaxes to implement the same rules. In the EN, this was a must, as the EN shall be implemented in UBL and CII (at a certain point, there was an EDI implementation as well). So the rules are defined by business experts in natural prose. And the Schematron experts shall implement the XPath expressions to support the requirements expressed in the text rules. CEF’s GitHub EN16931 Validation artifacts v.1.3.2 is maintained by Oriol and these files have interesting characteristics by defining abstract business rule definition and schematron implementation. Directory […]

  • PoC: e-Invoice and XBRL

    PoC: e-Invoice and XBRL

    Introducing Open Peppol simply add a new EDI to the existing EDI, and said, “It has become a” technical debt “with soaring maintenance and operating costs, and we cannot repay it. It is feared that DX’s obstacles of “not allocating funds and human resources to strategic IT investment (a hindrance to DX promotion)” (Ministry of Economy, Trade and Industry) will remain.