Recording a business transaction into the financial accounts of an organization is one of the main objectives of the invoice. According to financial accounting best practice and CT rules every Taxable person shall keep accounts in sufficient detail for CT to be applied and its application checked by the tax authorities. For that reason, an invoice shall provide for the information at document and line level that enables booking on both the debit and the credit side.

This process forms part of the Buyer’s internal business controls. The invoice shall refer to an authentic commercial transaction. Support for invoice verification is a key function of an invoice. The invoice should provide sufficient information to look up relevant existing documentation, electronic or paper, for example, and as applicable:

An invoice should also contain sufficient information that allows the received invoice to be transferred to a responsible authority, person or department, for verification and approval.

Companies audit themselves as means of internal control or they may be audited by external parties as part of a legal obligation. Accounting is a regular, ongoing process whereas an audit is a separate review process to ensure that the accounting has been carried out correctly. The auditing process places certain information requirements on an invoice. These requirements are mainly related to enable verification of authenticity and integrity of the accounting transaction.

Invoices, conformant to this PEPPOL BIS support the auditing process by providing sufficient information for:

The invoice is used to carry Tax related information from the Seller to the Buyer to enable the Buyer and Seller to correctly handle Tax booking and reporting. An invoice should contain sufficient information to enable the Buyer and any auditor to determine whether the invoice is correct from a Tax point of view.

The invoice shall allow the determination of the Tax regime, the calculation and description of the tax, in accordance with the relevant legislation.

An invoice represents a claim for payment. The issuance of an invoice may take place either before or after the payment is carried out. When an invoice is issued before payment it represents a request to the Buyer to pay, in which case the invoice commonly contains information that enables the Buyer, in the role of a debtor, to correctly initiate the transfer of the payment, unless that information is already agreed in prior contracts or by means of payment instructions separately lodged with the Buyer.

If an invoice is issued after payment, such as when the order process included payment instructions or when paying with a credit card, online or telephonic purchases, the invoice may contain information about the payment made in order to facilitate invoice to payment reconciliation on the Buyer side. An invoice may be partially paid before issuing such as when a pre-payment is made to confirm an order.

Invoices, conformant with this specification should identify the means of payment for settlement of the invoice and clearly state what payment amount is requested. They should provide necessary details to support bank transfers. Payments by means of Credit Transfer, Direct debit, and Payment Card are in scope.

The diagram below shows the self-billing process with the use of this Peppol BIS profile. This process assumes that both the self-billing invoice and the self-billing credit note are exchanged electronically.

The Implementation of self-billing invoice is supported in Japan based on JP PINT.

The self-billing is a billing arrangement between a supplier and a buyer, when the buyer, instead of the supplier, prepares the supplier’s invoice and sends it to the supplier to get confirmation.

So that, in self-billing transactions, the buyer and the sender of self-billing invoice is the same entity, as is the supplier and the receiver of self-billing invoice.

Legal requirements for self-billing invoice are same as standard invoice. So that the semantic model of self-billing invoice is identical to standard invoice.

However, self-billing invoice requires a different processing to standard invoice. So that, it needs a separate specification and different specification/customization identifications (Consequently, the rules applied are different from standard invoice a little).

The negative self-billing invoice is usually used to correct a mistake. Self-billing invoice (document type code:389) is usually used as the negative self-billing invoice.

Seller is mandatory information and provided in element cac:AccountingSupplierParty

Buyer is mandatory information and provided in element cac:AccountingCustomerParty

Payment receiver is optional information. If this information is not supplied, the seller is the payment receiver. When payee information is sent this is indicating that a factoring situation is being documented.

To reflect the assignment of an Invoice to a factor there is a need to:

Tax representative party for the seller is relevant for sellers delivering goods and services in a country without having a permanent establishment in that country. In such cases information on the tax representative shall be included in the invoice.

The purchase order reference is a conditional business term. If the customer has issued a purchase order should be referenced by providing its identifier in the resulting invoice, otherwise the Buyer reference should be used (see Buyer reference).

If the purchase order is referenced at the invoice header level, the order reference element on line level can be used to state the relevant line numbers in the order .

A sales order is issued by the seller, confirming the sale of specified products and may be provided in the invoice.

The buyer reference, known as Your ref, is conditional. An invoice shall have either the buyer reference or the order reference (see Purchase order and sales order reference)

The element is used for the reference of who ordered the products/services. Example being the name of the person ordering, employee number or a code identifying this person or department/group. Your ref is often used for internal routing at recipient, and hence it is important to fill this element with the correct values according to the need of the recipient.

If neither buyer reference nor a reference to an order is supplied by the customer, the name of the person ordering or appointed for the customer can be supplied in buyer reference if known by the supplier.

The invoiced object identifier is the identifier for an object on which the invoice is based, given by the Seller. Examples may be a subscription number, telephone number, meter point, vehicle, person etc., as applicable.

If it is not clear to the receiver what scheme is used for the identifier, an optional scheme identifier attribute should be used, that shall be chosen from the Invoiced object identifier scheme code list.

The invoiced object reference is provided by using the element cac:AdditionalDocumentReference with the document type code = 130

To reference or match an invoice to a purchase contract, the contract number could be specified like this:

To identify the call for tender or lot the invoice relates to, use the 'OriginatorDocumentReference'. The identifier is, in most cases, the Procurement Procedure Identifier.

The project reference is optional to use, and is sent in an invoice in the element cac:ProjectReference/cbc:ID. In a credit note, this element does not exist, and project reference is sent by using the element cac:AdditionalDocumentReference[cbc:DocumentTypeCode='50']/cbc:ID.

A credit note or negative invoice can refer to one or more initial invoice(s). This is done in the business group BG-3 Preceding invoice reference, providing the invoice number and issue date. The issue date shall be provided in case the preceding invoice reference is not unique.

In case correction applies to a large number of invoices, the invoicing period (BG-14), as necessary combined with a clarifying invoice note (IBT-22), may instead be given at document level.

An invoice may contain a supportive document as informative. Examples of such documents may be work reports, certificates or other documents that relate to the purchase or the invoiced items. A supportive document can be attached to the invoice in two ways: by providing a direct hyperlink through which the document can be downloaded or by embedding the document into the invoice. A compliant receiver is required to be able to receive an attached supportive document and, in case of embedded files, to convert it into a file but he is not required to handle the content of that file since it is only provided as informative.

When attaching a document using an uri the hyperlink shall point directly to the file that is to be downloaded.

An embedded document is contained in the invoice as binary object using base64 encoding and shall be supplemented with information about the name of the document file and a mime code indicating the type of the file. This allows the receiver to convert the binary code into a file that has the same name as the original file and allows him to associate the received file to a suitable application for viewing its content. The set of allowed codes for the file type (mime code) is limited to types that can be opened with applications that are commonly used and available.

As is with other file types, when an attached file is an XML file the receiver is expected to be able to receive and convert the binary object into an XML file but the sender can not expect the receiver to view or process the content of that XML file. Any further handling of an embedded XML file attachment is optional for the receiver.

In Summarised invoicing process, the supplier sends a Delivery Note to the customer with each delivery and the buyer uses the information in the Delivery Note to verify the reception of the items. The Delivery Note is focused on providing information about the items that are being delivered. At the end of a period (usually a month) the supplier sends an invoice that summarises the items that were delivered during that period.

To reference or match an invoice to a despatch or receipt advice use the following elements:

If payment is made by credit transfer, the Payment account identifier (IBT-84) is mandatory

Examples of codes for payment by credit transfer are:

If the Buyer had opted to pay by using a payment card such as a credit or debit card, information on the Primary Account Number (PAN) shall be present in the invoice.

Examples of codes for payment by card are:

In an invoice line the seller item identifier, the buyer item identifier and the standard item identifier can be provided. For sellers and buyers item identifiers, no scheme attribute is used, whilst the schemeID is mandatory for the standard item identification, and must be from the ISO 6523 ICD list.

Several different item classification codes can be provided per invoice line, and the codes must be from one of the classification schemes in code list UNCL7143.

Consumption Tax system in Japan is a broad-based tax levied on nearly all domestic supplies of goods and services, which is almost same as VAT in other jurisdictions.

There are two rates. One is a standard rate (10%) and the other is a reduced rate (8%). The reduced rate is only applied to transactions of foods and beverages (excluding liquors) and of subscribed newspapers issued twice or more per week.

A taxpayer of Consumption Tax is a business. A business with its taxable sales of more than 10 million JPY (during the reference taxable period*) shall be categorized as a taxable business. On the other hands, a business with its taxable sales of 10 million JPY or under shall be exempt from Consumption Tax (an exempt business).

*The “the reference taxable period” is the year or the business year before the previous one.

From October 1st, 2023, a “Qualified Invoice based method” is implemented as an input tax credit system, which is almost same as Invoice based method in other jurisdictions.

Under the method, only a taxable business allows to be registered as a registered taxable business and a registered taxable business can issue a Qualified Invoice. This means that, for instance, a non-registered taxable business and an exempt business can’t allow to issue a Qualified Invoice.

For input tax credit purpose, in principle*, both an accounting book with certain descriptions and a Qualified Invoice issued by a registered taxable business are required to be retained. In addition, a Self-Billing Invoice* is also allowed. A registered taxable business can claim an input tax credit by retaining a Self-Billing Invoice that is created by itself.

*A Self-Billing is a billing arrangement between a supplier and a buyer, when the buyer, instead of the supplier, prepares an invoice and shares it with the supplier to get confirmation. A Self-Billing Invoice is supported by “JP BIS Self Billing Invoice” (JP Self-Billing Invoice).

A Qualified Invoice must contain the following information.

*1 The number is coded as 0221 in ISO code list.

*2 If a taxable transaction is subject to the reduced rate, a statement clarifying this must be included.

*3 The tax amount in a Qualified Invoice should be expressed in JPY.

The tax amount per tax rate is required to be calculated by multiplying the taxable amount per tax rate (tax excluded) and the tax rate. On the other hands, it is also allowed to be calculated by dividing the taxable amount per tax rate (tax included) by the tax rate.

In addition, the tax amount per tax is required to be rounded to integer and the result of the rounding shall be between the floor and ceiling.

If the invoice currency is different from the accounting currency, this is expressed in the invoice by stating the accounting currency in the element Tax accounting currency (IBT-6), and the amount of TAX payable in accounting currency is stated in the element Invoice total TAX amount in accounting currency (IBT-111).

Following sections given information on how the tax is applied in the relevant jurisdiction.

From October 1st, 2023 to September 30th, 2029, a transactional special measure is applicable. Under the special measure, a taxable business can claim input tax paid on a taxable transaction with a non-registered taxable business and an exempt business by retaining both an accounting book with certain descriptions and the Document*.

*The Document is supported by “JP BIS Invoice for Non-tax registered Businesses” (JP non-tax invoice).

The Document is a different from a Qualified Invoice since it can be issued by a non-registered taxable business and an exempt business. The Document must contain the following information.

*If a taxable transaction is subject to the reduced rate, a statement clarifying this must be included.

In general, there are some ways to correct an error and a mistake in a Qualified Invoice or the Document since the Consumption Tax Law doesn’t define the exact correction ways.

For instance, a business can issue a new Qualified Invoice or the Document to rectify the preceding one. Otherwise, the business can only provide the corrective information.

AA registered business shall issue a Qualified Invoice for return when it returns sales. The Qualified Invoice for return must contain the following information.

*1 The number is coded as 0221 in ISO code list.

*2 In practice, the preceding invoice issue date is used as “Date of taxable transaction return”.

*3 If a taxable transaction is subject to the reduced rate, a statement clarifying this must be included.

*4 The tax amount in a Qualified Invoice for return should be expressed in JPY.

Formulas for the calculations of totals are as follows:

The following elements show the legal monetary totals for an invoice or credit note

Allowance and charge on document- and line level consists of elements carrying information on the allowance/charge base amount and the allowance/charge percentage. These are, if present in the invoice instance, used for calculating the allowance/charge amount.

If base amount is present, the percentage shall also be present, and if percentage is present, the base amount shall also be present, and the calculation of the amount shall be:

A maximum of two digits are allowed for the following amounts in an invoice.

Tax breakdown (ibg-23) shall be provided for each distinct combination of Tax category code and Tax rate. For each distinct combination of CT category code and CT rate the calculations are:

All messages contains Business process type (IBT-23) and Specification identifier (IBT-24). Business process type (IBT-23) identifies what business process a given message is part of, and Specification identifier (IBT-24) identifies the kind of message and the rules applied.

Profiles are connected to one business process, and may contain multiple document types. Valid document instances shall contain corresponding Business process type (IBT-23) and Specification identifier (IBT-24).

In the table below you will find the values to be used as the specification identifier (IBT-24) and the business process type (IBT-23) for this profile

Semantic data type content may be of the following primitive types. These primitive types were taken from ISO15000, Annex A.

The different semantic data types are described in the tables below, where various features such as attributes, format, and decimals as well as the basic type are defined for each semantic data type. They are based on {ISO15000}.

When used in an instance of an invoice, each data element will contain data. In the below tables this is identified as the “content”. Whenever a business term is used this term shall always have content and therefore the content is always mandatory.