Digitalization of Small and Medium Enterprises through Core Invoice<\/h1>\n\nTable of Contents<\/div>\n\n- 1. Is JP PINT a Panacea?<\/a><\/li>\n
- 2. Think of it as Cargo Ship Container Transshipment<\/a><\/li>\n
- 3. Syntax Binding<\/a><\/li>\n
- 4. Journal Entry Information Search Browser<\/a><\/li>\n
- 5. Digitalization of Accounting Initiated by Electronic Invoices<\/a><\/li>\n
- 6. Explanation for XML Technologists<\/a>\n
\n- 6.1. Logical Model of Digital Invoice<\/a><\/li>\n
- 6.2. Elements of Digital Invoice<\/a><\/li>\n
- 6.3. XML Syntax and XPath<\/a><\/li>\n<\/ul>\n<\/li>\n
- 7. Basics of XML Syntax and XPath<\/a>\n
\n- 7.1. Fundamentals of XML<\/a><\/li>\n
- 7.2. Basics of XPath<\/a><\/li>\n
- 7.3. Utilizing XML Syntax and XPath<\/a><\/li>\n<\/ul>\n<\/li>\n
- 8. Detailed Explanation of Syntax Binding<\/a>\n
\n- 8.1. JP PINT Syntax Binding<\/a><\/li>\n
- 8.2. SME Common EDI Syntax Binding<\/a><\/li>\n<\/ul>\n<\/li>\n
- 9. Detailed Analysis of Journal Information Search Browser and Logical Binding<\/a><\/li>\n
- 10. Conclusion: Standard Format CSV = Hierarchical Tidy Data<\/a><\/li>\n<\/ul>\n<\/div>\n<\/div>\n\n\n\n\n
Nobuyuki SAMBUICHI
\nISO\/TC295 Audit data services<\/a>\/SG1 Semantic model Convener<\/p>\n<\/div>\n\nThe Japanese version of Core Invoice was named inspired by the European standard Core Invoice. The European standard Core Invoice is the standard format for electronic invoices used in Europe.<\/p>\n<\/div>\n
\nThis article introduces the background of business requirements and key technical points of implementation for the XBRL Japan’s POC (Proof of Concept).<\/p>\n<\/div>\n
\nThe Core Invoice Gateway trial version is available from the following URL, provided by Sambuichi Professional Engineers Office<\/a>:
\nhttps:\/\/www.wuwei.space\/core-japan\/<\/a><\/p>\n<\/div>\n\nThe Journal Entry Search Exclusive Browser trial version is available from:
\nhttps:\/\/www.wuwei.space\/core-japan\/journal_entry\/<\/a><\/p>\n<\/div>\n\nThose interested in syntax binding should continue reading, including section 6.<\/p>\n<\/div>\n
\nThe standard format CSV is defined as Hierarchical Tidy Data. In Tidy data:<\/p>\n<\/div>\n
\n\n\nTidy data is a standard way of mapping the meaning of a dataset to its structure. A dataset is messy or tidy depending on how rows, columns and tables are matched up with observations, variables and types. In tidy data:<\/p>\n<\/div>\n
\n\n- \n
Each variable forms a column.<\/p>\n<\/li>\n
- \n
Each observation forms a row.<\/p>\n<\/li>\n
- \n
Each type of observational unit forms a table.<\/p>\n<\/li>\n<\/ol>\n<\/div>\n<\/blockquote>\n
\n— Hadley Wickham
\nTidy Data Journal of Statistical Software August 2014<\/cite>\n<\/div>\n<\/div>\n\nYou can download original paper from the following
\nhttps:\/\/www.jstatsoft.org\/article\/view\/v059i10<\/a><\/p>\n<\/div>\n\nFor more information on Hierarchical Tidy Data, please refer to the following articles:
\nHierarchical Tidy Data and Data Transformation<\/a>
\nA New Era of Data Transformation: Hierarchical Tidy Data<\/a>.
\nKindly check both for a comprehensive understanding.<\/p>\n<\/div>\n<\/div>\n<\/div>\n\n1. Is JP PINT a Panacea?<\/h2>\n\n\nWith the spread of electronic invoicing, standardization of accounting data and information sharing have advanced, leading to expectations for efficiency improvements in the tasks of accountants and businesses. This facilitates centralized data management, reduction of errors, and makes information search and analysis easier, thus enabling efficient business management and cost reduction.<\/p>\n<\/div>\n
\nStatus of Initiatives Regarding Electronic Invoices<\/div>\n\n\n\n![\"Status](\"https:\/\/www.sambuichi.jp\/wp-content\/uploads\/2023\/01\/fig1.png\")
\n<\/div>\n<\/div>\n<\/blockquote>\n\n— IT Strategic Headquarters of the Cabinet Secretariat
\nDecember 9<\/cite>\n<\/div>\n<\/div>\n\nSource: Status of Initiatives Regarding Electronic Invoices<\/a> Cabinet Secretariat IT Strategic Headquarters, December Reiwa 2<\/p>\n<\/div>\n\nEfforts Toward the Popularization of Digital Invoices<\/div>\n\n\n\n![\"Efforts](\"https:\/\/www.sambuichi.jp\/wp-content\/uploads\/2023\/08\/83340eaa0f72d2628008d1e378c35c07.png\")
\n<\/div>\n<\/div>\n<\/blockquote>\n\n— Digital Agency
\nMarch Reiwa 4<\/cite>\n<\/div>\n<\/div>\n\nSource: Efforts Toward the Popularization of Digital Invoices<\/a> Digital Agency, March Reiwa 4<\/p>\n<\/div>\n\nIn December of Reiwa 2, the IT Strategic Headquarters of the Cabinet Secretariat announced the adoption of Peppol, one of the standards for international e-commerce networks, to standardize the specifications of electronic invoices. In October of Reiwa 4, the first version of the Japanese edition of Peppol (JP PINT) was released, and its operations are supervised by the Digital Agency.<\/p>\n<\/div>\n
\nAs shown in Figure 1, JP PINT service providers only accept electronic invoices from OpenPeppol, limiting their scope.<\/p>\n<\/div>\n
\n\n![\"Figure](\"https:\/\/www.sambuichi.jp\/wp-content\/uploads\/2023\/08\/Figure1_2.png\")
\n<\/div>\n<\/div>\n\nOpenPeppol’s jurisdiction is from C2 to C3, so the connection between businesses and access points depends on the provider. For instance, if a C2 provider offers a connection with the Small and Medium Enterprise Common EDI, as depicted in Figure 2, Business Z (C1), even if they use the SME Common EDI, can send a converted electronic invoice to Business Y (C4). This setup is similar to when accounting software supporting JP PINT connects to OpenPeppol through a provider.<\/p>\n<\/div>\n
\n\n![\"Figure](\"https:\/\/www.sambuichi.jp\/wp-content\/uploads\/2023\/08\/Figure3.png\")
\n<\/div>\n<\/div>\n\nSpecifically, as illustrated in Figure 3, by using a gateway that converts data between different formats like the Small and Medium Enterprise Common EDI and JP PINT, businesses participating in the SME Common EDI can also connect to Peppol, a global electronic invoice network.<\/p>\n<\/div>\n
\nPlaying a crucial role here is “syntax binding.” In the eInvoice of the CEF (Connecting Europe Facility) that aims for a unified European market, syntax binding is provided to integrate various electronic invoice formats used in different systems or countries. This allows companies and public entities to exchange electronic invoices of different formats using common data items, thereby improving data interoperability.<\/p>\n<\/div>\n
\nTo interconnect various electronic invoices, a “Japanese Core Invoice Model” is necessary, covering all electronic invoices including EDI. Based on its standard data item definitions, the “Japanese Core Invoice Gateway” can be used to mutually convert different syntaxes, enabling interconnectivity.<\/p>\n<\/div>\n
\nThe Japanese Core Invoice Gateway is currently being tested and can be accessed [here](https:\/\/www.wuwei.space\/core-japan\/<\/a>).<\/p>\n<\/div>\n\n\n![\"Japanese](\"https:\/\/www.sambuichi.jp\/wp-content\/uploads\/2023\/07\/core-japan.png\")
\n<\/div>\n<\/div>\n\nThe Japanese Core Invoice Gateway is also a handy tool for small and medium-sized businesses to use electronic invoices.<\/p>\n<\/div>\n<\/div>\n<\/div>\n
\n2. Think of it as Cargo Ship Container Transshipment<\/h2>\n\n\nTo understand the Core Invoice system, imagine the transshipment of containers in cargo ship transportation.<\/p>\n<\/div>\n
\nThe Core Invoice system is designed to handle invoices represented in different data formats, such as the Small and Medium Enterprise Common EDI or JP PINT, in a standardized and uniform format. Picture a port where containers are being transshipped. According to a picking list, various details like the invoiced amount, product names, quantities, prices, and tax rates are extracted and stored in designated cargo holds, albeit in different configurations.<\/p>\n<\/div>\n
\nThis task is performed by automated cranes, which operate based on directives given in the standard data item definitions of the Core Invoice, picking sheets, and storage instruction lists. These instructions are represented using a taxonomy-defined dictionary.<\/p>\n<\/div>\n
\nIn essence, the Core Invoice system standardizes various data formats, enabling efficient invoice processing. The Japanese Core Invoice Gateway provides the functionalities necessary for this system. Just like transshipping containers with automated cranes, it converts invoices of various formats into one standardized format, managing them uniformly.<\/p>\n<\/div>\n<\/div>\n<\/div>\n
\n3. Syntax Binding<\/h2>\n\n\nSyntax binding refers to the rules and procedures for converting data of different formats into a unified format. This allows for easy acquisition and setting of electronic invoice information.<\/p>\n<\/div>\n
\nFor example, suppose different companies use different formats to represent certain information. One company might represent information in the order of “product name-quantity-price”, while another might use “quantity-product name-price”. In such cases, because the way the same information is expressed differs, each requires a different reading method, and constantly changing the reading method (or modifying the program) is inefficient. Hence, syntax binding is introduced to establish specific rules and procedures, such as unifying to the “product name-quantity-price” format. This allows information from any company to be read in the same way, enabling efficient handling of information.<\/p>\n<\/div>\n
\nIn Europe, based on the Directive 2014\/55\/EU of the European Parliament and the Council, the European standard EN 16931 series has been defined, and the promotion of digital invoicing is underway. As of 2014, each member state was promoting eInvoice and eProcurement centered on government procurement, but cross-border transactions were hindered because each country adopted different standards. The European Parliament defined the minimum common elements of electronic invoices as “core elements of electronic invoices” and decided to specify “syntax binding” by selecting from the XML syntax adopted in each country.<\/p>\n<\/div>\n
\nSyntax Binding<\/div>\n\n\n\n![\"Syntax](\"https:\/\/www.sambuichi.jp\/wp-content\/uploads\/2023\/08\/syntax_binding.png\")
\n<\/div>\n<\/div>\n<\/blockquote>\n\n— Martin Forsberg
\neInvoicing from a user\u2019s perspective<\/cite>\n<\/div>\n<\/div>\n\nJP PINT has adopted UBL, and the common EDI for small and medium-sized enterprises adopts UN\/CEFACT CII. Although there are common elements in each syntax binding, the element names and structures of UBL and CII differ, requiring mapping. European standards define a logical model in EN 16931-1, specify syntax binding in CEN\/TS 16931-3-1, and define syntax binding with UBL in 16931-3-2 and with UN\/CEFACT CII in 16931-3-3.<\/p>\n<\/div>\n
\nFor instance, the element corresponding to the issuer of the invoice in UBL is cac:AccountingSupplierParty<\/code>, and in CII, it’s ram:SellerCITradeParty<\/code>. To map these, the Japanese core invoice gateway defines “seller” in the logical model and defines syntax binding for that item to UBL and CII.<\/p>\n<\/div>\n\nCEN\/TS 16393-3-1 also describes cross-mapping between XML syntaxes. Issues with mapping can result in information loss. Mapping issues can arise at the logical level, structural level, difference in repetition levels, or data type level. Mapping is a crucial means to enable binding between different syntaxes. Accurate mapping can minimize information loss.<\/p>\n<\/div>\n
\nFor the invoice number BT-1 defined in EN 16931-1 (A unique identification of the Invoice.), in UBL 2.1 it corresponds to \/Invoice\/cbc:ID<\/code>, and in UN\/CEFACT CII 16B it corresponds to \/rsm:CrossIndustryInvoice\/rsm:ExchangedDocument\/ram:ID<\/code>.<\/p>\n<\/div>\n\nSyntax binding based on European standards allows data exchange between business systems and XML documents by reading and writing XML element values at specific positions in the XML document.<\/p>\n<\/div>\n
\nThe Japanese version of the core invoice encompasses all necessary electronic invoice items in the logical model and defines the relationship between each syntax (such as Peppol’s JP PINT invoice or the common EDI for small and medium-sized enterprises’ UN\/CEFACT CII) in XPath. This information is managed in the business dictionary (taxonomy), allowing for easy management of logical model updates and revisions to the electronic invoice syntax.<\/p>\n<\/div>\n
\nIt may also be necessary to utilize past accounting data. While detailed discussions are still underway, from a digitization perspective, it’s important to effectively use these accumulated data. Using a business dictionary (taxonomy), you can use accumulated electronic data in comparison with the business dictionary (taxonomy) at that time. In the business dictionary (taxonomy), not only nationwide standard definitions but also unique definitions for each company must be linked and managed.<\/p>\n<\/div>\n
\n
- \n
- 1. Is JP PINT a Panacea?<\/a><\/li>\n
- 2. Think of it as Cargo Ship Container Transshipment<\/a><\/li>\n
- 3. Syntax Binding<\/a><\/li>\n
- 4. Journal Entry Information Search Browser<\/a><\/li>\n
- 5. Digitalization of Accounting Initiated by Electronic Invoices<\/a><\/li>\n
- 6. Explanation for XML Technologists<\/a>\n
- \n
- 6.1. Logical Model of Digital Invoice<\/a><\/li>\n
- 6.2. Elements of Digital Invoice<\/a><\/li>\n
- 6.3. XML Syntax and XPath<\/a><\/li>\n<\/ul>\n<\/li>\n
- 7. Basics of XML Syntax and XPath<\/a>\n
- \n
- 7.1. Fundamentals of XML<\/a><\/li>\n
- 7.2. Basics of XPath<\/a><\/li>\n
- 7.3. Utilizing XML Syntax and XPath<\/a><\/li>\n<\/ul>\n<\/li>\n
- 8. Detailed Explanation of Syntax Binding<\/a>\n
- \n
- 8.1. JP PINT Syntax Binding<\/a><\/li>\n
- 8.2. SME Common EDI Syntax Binding<\/a><\/li>\n<\/ul>\n<\/li>\n
- 9. Detailed Analysis of Journal Information Search Browser and Logical Binding<\/a><\/li>\n
- 10. Conclusion: Standard Format CSV = Hierarchical Tidy Data<\/a><\/li>\n<\/ul>\n<\/div>\n<\/div>\n
\n\n\n\nNobuyuki SAMBUICHI
\nISO\/TC295 Audit data services<\/a>\/SG1 Semantic model Convener<\/p>\n<\/div>\n\nThe Japanese version of Core Invoice was named inspired by the European standard Core Invoice. The European standard Core Invoice is the standard format for electronic invoices used in Europe.<\/p>\n<\/div>\n
\nThis article introduces the background of business requirements and key technical points of implementation for the XBRL Japan’s POC (Proof of Concept).<\/p>\n<\/div>\n
\nThe Core Invoice Gateway trial version is available from the following URL, provided by Sambuichi Professional Engineers Office<\/a>:
\nhttps:\/\/www.wuwei.space\/core-japan\/<\/a><\/p>\n<\/div>\n\nThe Journal Entry Search Exclusive Browser trial version is available from:
\nhttps:\/\/www.wuwei.space\/core-japan\/journal_entry\/<\/a><\/p>\n<\/div>\n\nThose interested in syntax binding should continue reading, including section 6.<\/p>\n<\/div>\n
\nThe standard format CSV is defined as Hierarchical Tidy Data. In Tidy data:<\/p>\n<\/div>\n
\n\n
\nTidy data is a standard way of mapping the meaning of a dataset to its structure. A dataset is messy or tidy depending on how rows, columns and tables are matched up with observations, variables and types. In tidy data:<\/p>\n<\/div>\n
\n- \n
- \n
Each variable forms a column.<\/p>\n<\/li>\n
- \n
Each observation forms a row.<\/p>\n<\/li>\n
- \n
Each type of observational unit forms a table.<\/p>\n<\/li>\n<\/ol>\n<\/div>\n<\/blockquote>\n
\n— Hadley Wickham
\nTidy Data Journal of Statistical Software August 2014<\/cite>\n<\/div>\n<\/div>\n\nYou can download original paper from the following
\nhttps:\/\/www.jstatsoft.org\/article\/view\/v059i10<\/a><\/p>\n<\/div>\n\nFor more information on Hierarchical Tidy Data, please refer to the following articles:
\nHierarchical Tidy Data and Data Transformation<\/a>
\nA New Era of Data Transformation: Hierarchical Tidy Data<\/a>.
\nKindly check both for a comprehensive understanding.<\/p>\n<\/div>\n<\/div>\n<\/div>\n\n1. Is JP PINT a Panacea?<\/h2>\n
\n\nWith the spread of electronic invoicing, standardization of accounting data and information sharing have advanced, leading to expectations for efficiency improvements in the tasks of accountants and businesses. This facilitates centralized data management, reduction of errors, and makes information search and analysis easier, thus enabling efficient business management and cost reduction.<\/p>\n<\/div>\n
\nStatus of Initiatives Regarding Electronic Invoices<\/div>\n\n
\n\n\n<\/div>\n<\/div>\n<\/blockquote>\n\n— IT Strategic Headquarters of the Cabinet Secretariat
\nDecember 9<\/cite>\n<\/div>\n<\/div>\n\nSource: Status of Initiatives Regarding Electronic Invoices<\/a> Cabinet Secretariat IT Strategic Headquarters, December Reiwa 2<\/p>\n<\/div>\n
\nEfforts Toward the Popularization of Digital Invoices<\/div>\n\n
\n\n\n<\/div>\n<\/div>\n<\/blockquote>\n\n— Digital Agency
\nMarch Reiwa 4<\/cite>\n<\/div>\n<\/div>\n\nSource: Efforts Toward the Popularization of Digital Invoices<\/a> Digital Agency, March Reiwa 4<\/p>\n<\/div>\n
\nIn December of Reiwa 2, the IT Strategic Headquarters of the Cabinet Secretariat announced the adoption of Peppol, one of the standards for international e-commerce networks, to standardize the specifications of electronic invoices. In October of Reiwa 4, the first version of the Japanese edition of Peppol (JP PINT) was released, and its operations are supervised by the Digital Agency.<\/p>\n<\/div>\n
\nAs shown in Figure 1, JP PINT service providers only accept electronic invoices from OpenPeppol, limiting their scope.<\/p>\n<\/div>\n
\n\n\n<\/div>\n<\/div>\n\nOpenPeppol’s jurisdiction is from C2 to C3, so the connection between businesses and access points depends on the provider. For instance, if a C2 provider offers a connection with the Small and Medium Enterprise Common EDI, as depicted in Figure 2, Business Z (C1), even if they use the SME Common EDI, can send a converted electronic invoice to Business Y (C4). This setup is similar to when accounting software supporting JP PINT connects to OpenPeppol through a provider.<\/p>\n<\/div>\n
\n\n\n<\/div>\n<\/div>\n\nSpecifically, as illustrated in Figure 3, by using a gateway that converts data between different formats like the Small and Medium Enterprise Common EDI and JP PINT, businesses participating in the SME Common EDI can also connect to Peppol, a global electronic invoice network.<\/p>\n<\/div>\n
\nPlaying a crucial role here is “syntax binding.” In the eInvoice of the CEF (Connecting Europe Facility) that aims for a unified European market, syntax binding is provided to integrate various electronic invoice formats used in different systems or countries. This allows companies and public entities to exchange electronic invoices of different formats using common data items, thereby improving data interoperability.<\/p>\n<\/div>\n
\nTo interconnect various electronic invoices, a “Japanese Core Invoice Model” is necessary, covering all electronic invoices including EDI. Based on its standard data item definitions, the “Japanese Core Invoice Gateway” can be used to mutually convert different syntaxes, enabling interconnectivity.<\/p>\n<\/div>\n
\nThe Japanese Core Invoice Gateway is currently being tested and can be accessed [here](https:\/\/www.wuwei.space\/core-japan\/<\/a>).<\/p>\n<\/div>\n
\n\n\n<\/div>\n<\/div>\n\nThe Japanese Core Invoice Gateway is also a handy tool for small and medium-sized businesses to use electronic invoices.<\/p>\n<\/div>\n<\/div>\n<\/div>\n
\n2. Think of it as Cargo Ship Container Transshipment<\/h2>\n
\n\nTo understand the Core Invoice system, imagine the transshipment of containers in cargo ship transportation.<\/p>\n<\/div>\n
\nThe Core Invoice system is designed to handle invoices represented in different data formats, such as the Small and Medium Enterprise Common EDI or JP PINT, in a standardized and uniform format. Picture a port where containers are being transshipped. According to a picking list, various details like the invoiced amount, product names, quantities, prices, and tax rates are extracted and stored in designated cargo holds, albeit in different configurations.<\/p>\n<\/div>\n
\nThis task is performed by automated cranes, which operate based on directives given in the standard data item definitions of the Core Invoice, picking sheets, and storage instruction lists. These instructions are represented using a taxonomy-defined dictionary.<\/p>\n<\/div>\n
\nIn essence, the Core Invoice system standardizes various data formats, enabling efficient invoice processing. The Japanese Core Invoice Gateway provides the functionalities necessary for this system. Just like transshipping containers with automated cranes, it converts invoices of various formats into one standardized format, managing them uniformly.<\/p>\n<\/div>\n<\/div>\n<\/div>\n
\n3. Syntax Binding<\/h2>\n
\n\nSyntax binding refers to the rules and procedures for converting data of different formats into a unified format. This allows for easy acquisition and setting of electronic invoice information.<\/p>\n<\/div>\n
\nFor example, suppose different companies use different formats to represent certain information. One company might represent information in the order of “product name-quantity-price”, while another might use “quantity-product name-price”. In such cases, because the way the same information is expressed differs, each requires a different reading method, and constantly changing the reading method (or modifying the program) is inefficient. Hence, syntax binding is introduced to establish specific rules and procedures, such as unifying to the “product name-quantity-price” format. This allows information from any company to be read in the same way, enabling efficient handling of information.<\/p>\n<\/div>\n
\nIn Europe, based on the Directive 2014\/55\/EU of the European Parliament and the Council, the European standard EN 16931 series has been defined, and the promotion of digital invoicing is underway. As of 2014, each member state was promoting eInvoice and eProcurement centered on government procurement, but cross-border transactions were hindered because each country adopted different standards. The European Parliament defined the minimum common elements of electronic invoices as “core elements of electronic invoices” and decided to specify “syntax binding” by selecting from the XML syntax adopted in each country.<\/p>\n<\/div>\n
\nSyntax Binding<\/div>\n\n
\n\n\n<\/div>\n<\/div>\n<\/blockquote>\n\n— Martin Forsberg
\neInvoicing from a user\u2019s perspective<\/cite>\n<\/div>\n<\/div>\n\nJP PINT has adopted UBL, and the common EDI for small and medium-sized enterprises adopts UN\/CEFACT CII. Although there are common elements in each syntax binding, the element names and structures of UBL and CII differ, requiring mapping. European standards define a logical model in EN 16931-1, specify syntax binding in CEN\/TS 16931-3-1, and define syntax binding with UBL in 16931-3-2 and with UN\/CEFACT CII in 16931-3-3.<\/p>\n<\/div>\n
\nFor instance, the element corresponding to the issuer of the invoice in UBL is
cac:AccountingSupplierParty<\/code>, and in CII, it’sram:SellerCITradeParty<\/code>. To map these, the Japanese core invoice gateway defines “seller” in the logical model and defines syntax binding for that item to UBL and CII.<\/p>\n<\/div>\n\nCEN\/TS 16393-3-1 also describes cross-mapping between XML syntaxes. Issues with mapping can result in information loss. Mapping issues can arise at the logical level, structural level, difference in repetition levels, or data type level. Mapping is a crucial means to enable binding between different syntaxes. Accurate mapping can minimize information loss.<\/p>\n<\/div>\n
\nFor the invoice number BT-1 defined in EN 16931-1 (A unique identification of the Invoice.), in UBL 2.1 it corresponds to
\/Invoice\/cbc:ID<\/code>, and in UN\/CEFACT CII 16B it corresponds to\/rsm:CrossIndustryInvoice\/rsm:ExchangedDocument\/ram:ID<\/code>.<\/p>\n<\/div>\n\nSyntax binding based on European standards allows data exchange between business systems and XML documents by reading and writing XML element values at specific positions in the XML document.<\/p>\n<\/div>\n
\nThe Japanese version of the core invoice encompasses all necessary electronic invoice items in the logical model and defines the relationship between each syntax (such as Peppol’s JP PINT invoice or the common EDI for small and medium-sized enterprises’ UN\/CEFACT CII) in XPath. This information is managed in the business dictionary (taxonomy), allowing for easy management of logical model updates and revisions to the electronic invoice syntax.<\/p>\n<\/div>\n
\nIt may also be necessary to utilize past accounting data. While detailed discussions are still underway, from a digitization perspective, it’s important to effectively use these accumulated data. Using a business dictionary (taxonomy), you can use accumulated electronic data in comparison with the business dictionary (taxonomy) at that time. In the business dictionary (taxonomy), not only nationwide standard definitions but also unique definitions for each company must be linked and managed.<\/p>\n<\/div>\n
\n
- 8.2. SME Common EDI Syntax Binding<\/a><\/li>\n<\/ul>\n<\/li>\n
- 7.2. Basics of XPath<\/a><\/li>\n
- 6.2. Elements of Digital Invoice<\/a><\/li>\n
- 2. Think of it as Cargo Ship Container Transshipment<\/a><\/li>\n
![\"Journal](\"https:\/\/www.sambuichi.jp\/wp-content\/uploads\/2023\/07\/192ac04796f28e2ad9cd37a65e95bc07.png\")
\n<\/div>\n![\"Standardization](\"https:\/\/www.sambuichi.jp\/wp-content\/uploads\/2023\/08\/standard_interface.png\")
\n<\/div>\n<\/div>\n![\"Q&A](\"https:\/\/www.sambuichi.jp\/wp-content\/uploads\/2023\/04\/230423fig1-5.png\")
<\/span>