TW201801009A - Method for storing electronic invoices by using blockchain improving the security of the electronic invoices and avoiding forgery, tampering, impersonation and double delivery - Google Patents

Abstract

A method for storing electronic invoices by using a blockchain, comprising the steps of: generating a block; storing one or a plurality of electronic invoices in the block, and generating a corresponding electronic invoice hash value based on the content of each electronic invoice; chain-linking each electronic invoice with zero or one or more other related electronic invoices based on the corresponding electronic invoice hash value; generating a corresponding block hash value based on the content of the block when the block is full with these electronic invoices, and recording a current time stamp showing the time when the block is concurrently established in order to complete the establishment of the block; and string-linking the block with the adjacent previous block according to the hash value of the previous block that is adjacent to the block in order to establish the described blockchain; thereby ensuring the information of each block or each electronic invoice not to be tampered and improving the security of electronic invoices.

Description

Method for storing electronic invoices using blockchain

This creation is about a method for storing electronic invoices, especially a method for storing electronic invoices using blockchain.

Based on the consideration of cost saving, energy saving, carbon reduction and environmental protection, the proposal of replacing traditional paper invoices with electronic invoices (e-invoice) has become a topic that governments, industry and even the whole people pay attention to. The deeper impact involves many aspects. For example, for the operators, the use of electronic invoices can not only save the costs and schedules of issuing, mailing or delivering invoices, but also speed up the efficiency of reconciliation and payment. For the government, through the integrated service platform of electronic invoicing, it can provide more tax services, perform more rigorous tax checking operations and stricter monitoring of goods on the market. For the public, in addition to reducing the inconvenience of collecting and sorting paper invoices and the possibility of loss and damage, it can also protect individual consumer rights and interests, so as to avoid accidents of false or invoicing by the industry.

Although there are many advantages to electronic invoices, the security challenges faced by electronic invoice technology are indeed the main obstacles and bottlenecks in the promotion of electronic invoices. Specifically, if a security breach occurs in the process of transmitting or publishing an electronic invoice, such as forgery, tampering, transmission or retransmission of an electronic invoice, it will have a serious impact on the relevant unit that uses the electronic invoice. In addition, in terms of food safety or product quality tracking and tracing, when food safety problems or product quality problems occur, current paper or electronic invoices have problems that are not easy to trace to upstream and downstream related manufacturers. Therefore, how to improve and even solve the security and traceability problems of electronic invoice technology is the primary key for government agencies and related businesses to jointly promote electronic invoices.

The purpose of this creation is to provide a method for storing electronic invoices using the blockchain, to solve the problem of forgery, tampering, transmission or retransmission in the process of transmission or release of electronic invoices, and to provide traceability , Can trace upstream and downstream related electronic invoices.

In order to achieve the purpose of the previous disclosure, the method proposed in this creation for storing electronic invoices using a blockchain is implemented on one or more network servers. The method for storing electronic invoices using a blockchain includes generating a block ; Store one or more electronic invoices in this block, and generate a corresponding one of the electronic invoice hash values according to each of the electronic invoices; each of the electronic invoices is linked to zero or more than one other according to the corresponding electronic invoice hash value Associated electronic invoices; when the block is full of such electronic invoices, a corresponding block hash value is generated from the block content and a timestamp is recorded at the time the block was created to complete the creation of the block; and The block is linked in series with the adjacent previous block according to the hash value of the adjacent previous block to establish the block chain.

With the proposed method of using a blockchain to store electronic invoices, it is ensured that the data of each block or each electronic invoice cannot be tampered with, and the security of the electronic invoice is improved.

In order to better understand the techniques, methods and effects adopted by this creation to achieve the intended purpose, please refer to the following detailed descriptions and drawings of this creation. I believe that the purpose, characteristics and features of this creation can be in-depth and Specific understanding, however, the drawings are provided for reference and explanation only, and are not intended to limit the creation.

The technical content and detailed description of this creation are described below in conjunction with the drawings.

As shown in FIG. 1, the architecture of the blockchain disclosed in this case is formed by a plurality of blocks, that is, N blocks (block 1 to block N). Adjacent two blocks, such as block 1 and block 2, block 2 and block 3, and so on, and even block N-1 and block N are chained in series to form the Blockchain 100. As for the linking method between two blocks, it will be explained in more detail later. The blockchain 100 and its blocks can be established and stored on one or more network servers, and each of the servers is connected by a network, and the network can be a private network. Road (private network), public network (public network) or hybrid network (hybrid network). However, the implementation of this creation is not restricted by these types of networks.

As shown in Figure 2, the content of a single block, that is, the content stored in the single block, taking block N as an example, is a block hash value (a hashing value of the previous block), that is, a block hash value of one previous block N-1 of the block N, a record of one or more electronic invoices stored in the block N, that is, n records Record of electronic invoice (electronic invoice N1 ~ electronic invoice Nn), a time stamp for the completion of the establishment of the block N, and a hash value of a block of the block N. The hash value of the block N is the hash value of the block N-1 before the block N, the record of the one or more electronic invoices N1 ~ Nn, and the block. The timestamp when the establishment is completed is generated by a cryptographic hash function. The security hash algorithm used in this creation is not limited to the SHA-512 algorithm. Furthermore, the SHA-512 algorithm is a widely used algorithm that can calculate and convert data into a fixed-length value. Therefore, the operation and conversion method of the SHA-512 algorithm will not be repeated here.

Taking the block N as the current block for storing electronic invoices as an example, the block N is defined as an operation block. In this creation, since the operation block is the block N, all blocks before the block N, that is, block 1 to block N-1 have been established, in other words, the N The contents of -1 blocks can no longer be changed. Therefore, by verifying whether the block hash value of each of the blocks associated with the block has changed, it can be determined whether the contents of the blocks 1 to N-1 have been tampered with.

In this creation, the hash value of the block N-1 is stored in the block N. Therefore, the block N-1 and the block N are linked to each other. Similarly, the block 2 stores the hash value of the block 1, the block 3 stores the hash value of the block 2, and so on, and the block N stores the block N-1. The hash value of the block. In this way, through the link of two or two adjacent blocks, blocks 1 to N are serially linked to form the block chain 100. Furthermore, by linking the hash value of the block of the block N-1 immediately before the block N, once the data content of any of the blocks in the block chain 100 has been tampered with, it can be immediately, Precise detection to determine whether the data is complete and to ensure the integrity of the data.

The electronic invoices N1 ~ Nn stored in the block N do not necessarily have an associated relationship. Taking the commercial transaction between an upstream supplier and a downstream distributor as an example, the upstream supplier is the unit that issues the electronic invoice, and the downstream distributor is the unit that receives the electronic invoice. The upstream supplier issues the All electronic invoices can be defined as related relationships. Therefore, the electronic invoices N1 ~ Nn stored in the block N do not necessarily have an associated relationship, which means that all electronic invoices issued by the upstream supplier to the downstream distributor are not necessarily stored in the same In the block, the actual time difference of issuing invoices also makes these related electronic invoices not necessarily stored in the same block. In this embodiment, the associated electronic invoices are randomly issued, and the time of the electronic invoice is stored in the block in the current operation, that is, it may be partially stored in the same block, or it may be Partly scattered in different blocks.

The timestamp of the block N is defined when the block N is full of the electronic invoices N1 ~ Nn, that is, when other electronic invoices are no longer received, the definition of the block N is completed, and the zone The time stamp of the block N is the current date and time when the block N is completed. In addition, the time stamp is recorded and stored in the time format of milliseconds, which converts the date and time format required by various access terminals. By recording the timestamp information when different blocks are created, and matching the time sequence relationship of the blocks before and after the blockchain 100, that is, the timestamp of the later block must be later than the timestamp of the previous block. In other words, the number of milliseconds of the timestamp of the later block must be greater than the number of milliseconds of the timestamp of the previous block. In this way, by judging the sequence information of time stamps between different blocks, it is possible to verify whether any block has been tampered with or forged, and to verify the rationality of the establishment time of these blocks.

In summary, the hash value of the block N is the hash value of the block N-1, the records of the multiple electronic invoices N1 ~ Nn, and the time when the block is completed. The stamp is generated by this secure hash algorithm.

As shown in FIG. 3, the content of a single electronic invoice, taking the electronic invoice N1 of FIG. 2 as an example, includes the issuer's public key of one of the issuing units of the electronic invoice N1, and the receipt of the electronic invoice N1. Receiver's public key of one of the units, transaction content of the electronic invoice N1, the hash value of the electronic invoice of zero or more electronic invoices associated with the electronic invoice N1, and one of the time when the electronic invoice N1 was issued A time stamp and a hash value of one of the electronic invoices N1. Among them, the public key of the issuing unit of the electronic invoice N1 and the public key of the receiving unit of the electronic invoice N1 can use RSA algorithm (Rivest-Shmir-Adleman cryptography) or elliptic curve cryptography , ECC), however, it is not limited by the above two algorithms. The hash value of the electronic invoice N1 is the public key of the issuing unit of the electronic invoice N1, the public key of the receiving unit of the electronic invoice N1, the transaction content of the electronic invoice N1, and The electronic invoice hash value of the zero or more electronic invoices associated with the electronic invoice N1 and the timestamp when the electronic invoice N1 is issued are generated by a cryptographic hash function.

The security hash algorithm used in this creation is not limited to the SHA-512 algorithm. Through this, through the complete information of the electronic invoice N1 (including the public key of the issuing unit, the public key of the receiving unit, the transaction content of the electronic invoice N1, and the zero associated with the electronic invoice N1 The hash value of the electronic invoice of one or more electronic invoices and the timestamp when the electronic invoice N1 was issued) are calculated. As a result, due to the calculation characteristics of the hash value, once any data of the electronic invoice N1 has been tampered with, it can be accurately detected that the electronic invoice N1 has been destroyed to ensure the integrity of the data of the electronic invoice N1 (integrity ).

The public key of the issuing unit of the electronic invoice N1 is the public key provided by the issuing unit of the electronic invoice. The public key of the receiving unit of the electronic invoice N1 is the public key provided by the unit receiving the electronic invoice N1. Taking the aforementioned business transactions of the upstream and downstream vendors as an example, the upstream vendor is the unit that issues the electronic invoice N1, and the downstream vendor is the unit that receives the electronic invoice N1. A related electronic invoice issued based on the transaction content of the electronic invoice N1 and its related raw materials may be defined as an electronic invoice that is associated with the electronic invoice N1.

With reference to FIG. 4, taking this embodiment as an example, the electronic invoice associated with the electronic invoice N1 includes three electronic invoices X, electronic invoice Y, and the electronic invoice Z. Among them, the contents of each electronic invoice are shown in FIG. 3, so FIG. 4 only shows that each electronic invoice includes its electronic invoice hash value. For the generation method of the electronic invoice hash value, please refer to FIG. 3 and the corresponding content of the description, which will not be repeated here. Because there are three electronic invoices associated with the electronic invoice N1, the electronic invoice hash value associated with the electronic invoice N1 also has three electronic invoice hash values corresponding to the electronic invoice X, the electronic invoice Y, and the electronic invoice Z. . The electronic invoice N1 may store the hash value of the electronic invoice X, the electronic invoice Y, and the electronic invoice Z by using an index, an array, or an attribute-value pair. However, it is not restricted in the above manner. Through this, the electronic invoice N1 is used to link other related electronic invoice records (such as the business transactions between upstream suppliers and downstream distributors of raw materials related to the electronic invoice transaction content). The hash value of electronic invoices from downstream distributors meets the need to track upstream and downstream bidirectional traceability.

The time stamp of the electronic invoice N1 is the current date and time when the electronic invoice N1 was issued. In addition, the time stamp is recorded and stored in the time format of milliseconds, which converts the date and time format required by various access terminals.

The transaction content of the electronic invoice N1 includes the invoice number of the electronic invoice N1, the seller's name, the seller's code (such as the name of the upstream manufacturer, the code), the buyer's name, and the buyer's code (such as the name of the downstream company, the code) , Transaction items, transaction quantities, unit prices, subtotals, taxes, amounts, and remarks related transaction information, however, it is not limited by the above-mentioned transaction information, and the relevant transaction information of the transaction content of the electronic invoice can be viewed as actual transactions Demand increases or decreases or no value is entered.

In summary, the electronic invoice hash value of the electronic invoice N1 is the transaction of the public key of the issuing unit of the electronic invoice N1, the public key of the receiving unit of the electronic invoice N1, and the transaction of the electronic invoice N1. The content, the electronic invoice hash value of the zero or more electronic invoices associated with the electronic invoice N1, and the timestamp when the electronic invoice N1 was issued are generated through the secure hash algorithm.

As shown in FIG. 5, the record of the electronic invoice N1 is a choice of whether to further affix an electronic invoice digital signature of one of the electronic invoices N1. Attachment refers to the digital signature of the electronic invoice, which is not stored in the electronic invoice N1 record, that is, not stored in the electronic invoice N1 record itself, but is externally "attached (added)" to the electronic invoice. After the invoice N1 is issued, the two (that is, the electronic invoice N1 record itself and the electronic invoice digital signature of the electronic invoice N1) can choose whether or not to "send the same" to the receiving unit of the electronic invoice. Subject to the above-mentioned "addition" and "combined transmission" as restrictions, you can also choose not to add, and do not transmit at the same time. For example, you can use two methods such as separate transmission and two transmissions. Allow the receiving unit of the electronic invoice to verify the electronic invoice record. The verification method and process will be detailed later. As shown in FIG. 6, the digital signature of the electronic invoice N1 is obtained by hashing the record of the electronic invoice N1 with the issuer's private key of one of the issuing units of the electronic invoice N1. Digital signature generation operation "is generated by signing encryption. Among them, the digital signature generation operation of the electronic invoice can use RSA algorithm or elliptic curve algorithm, however, the above two algorithms are not limited.

See Figure 7. The issuing unit of the electronic invoice N1 issues the electronic invoice N1 (S11), and transmits the electronic invoice N1 to the receiving unit (S12) of the electronic invoice N1, and the receiving unit of the electronic invoice N1 receives the electronic invoice N1 (S13). The issuing unit calculates a hash value of one of the electronic invoices N1 (S14) through the aforementioned security hash algorithm, and then uses the hash key of the electronic invoice N1 record as the secret key of the issuing unit to pass the "digital "Signature generation operation" performs signature encryption to generate an electronic invoice digital signature (S15). The issuing unit transmits the digital signature of the electronic invoice to the receiving unit (S16). In the above, the electronic invoice N1 and the digital invoice digital signature are not restricted to be transmitted to the receiving unit before and after, that is, the electronic invoice digital signature can be attached to the electronic invoice N1 and transmitted to the receiving unit at the same time. In other words, step (S12) and step (S16) can be integrated into the same step, and executed after step (S15).

After the receiving unit receives the electronic invoice N1 and the digital invoice digital signature (S17), if it wants to confirm whether the received electronic invoice N1 has been tampered with and verify that the electronic invoice is actually issued by the issuing unit Issuing, which can be verified. The receiving unit calculates an electronic invoice hash value H1 of the electronic invoice N1 through the aforementioned secure hash algorithm (S18). In addition, the digital signature of the electronic invoice can be decrypted by using a public key provided by the issuing unit to obtain a set of decrypted electronic invoice hash values H2 (S19). Then verify and compare the electronic invoice hash value H1 and the electronic invoice hash value H2 (S1A). If the electronic invoice hash value H1 is the same as the electronic invoice hash value H2, it can be confirmed that the electronic invoice N1 has not been tampered with. And confirm that the electronic invoice is indeed issued by the issuing unit. Conversely, if the hash value H1 of the electronic invoice is different from the hash value H2 of the electronic invoice, it means that the electronic invoice N1 has been tampered with or the electronic invoice was issued by a non-issue unit to provide the receiving unit for subsequent follow-up Response measures. With this, using the calculation characteristics of the digital signature, once any data of the electronic invoice N1 is altered or the electronic invoice is issued by a non-issuer, the digital signature of the electronic invoice will be changed accordingly. The verification of the hash value of the electronic invoice can achieve the integrity, authentication, and non-repudiation of the electronic invoice N1.

The definition and description of the block and electronic invoice of this creation have been described in the foregoing description, and then the steps of the method of storing electronic invoices using the blockchain 100 in this creation are further explained. Referring to FIG. 8, first, a block is generated (S10). Among them, the block defined as the current storage of the electronic invoice is an operation block. The operation block is provided for storing one or more electronic invoices therein, and each of the electronic invoices generates a corresponding one of the electronic invoice hash values according to the contents of the electronic invoices (S20). For example, an electronic invoice N1 in the operation block generates an electronic invoice hash value of the electronic invoice N1, an electronic invoice N2 generates an electronic invoice hash value of the electronic invoice N2, and so on.

Then, the electronic invoice N1 can be linked to zero or more related electronic invoices, and the hash value of the electronic invoice of the zero or more related electronic invoices is stored in the electronic invoice N1, so that the The electronic invoice N1 is linked to the electronic invoice associated with the zero or more (S30). Next, it is determined whether the operation block is full of the electronic invoices (S40). If the operation block has not been filled with such electronic invoices, step (S20) is executed to continue storing the electronic invoices. Conversely, if the operation block is full of these electronic invoices, the operation block generates a hash value of the block and records the time stamp at the time the block was created to complete the block (S50). Among them, the completed block is based on the hash value of a block adjacent to the block adjacent to the block that has been completed to establish a block chain (S60). As for the detailed description of the steps of this method of creating electronic invoices by using blockchain, please refer to Figures 1 to 7 and the corresponding description.

As shown in FIG. 9, each node can be regarded as the issuing unit of an electronic invoice (such as an upstream raw material supplier), the receiving unit of an electronic invoice (such as a downstream distributor or consumer), or a verification A validator or observer (such as a national financial institution or a local financial institution). For convenience of explanation, it is assumed that a first node n1 and a second node n2 shown in FIG. 9 are a first upstream raw material supplier and a second upstream raw material supplier, respectively; a third node n3 is a downstream path And is the common sales target of the first upstream raw material supplier and the second upstream raw material supplier; a fourth node n4 is a national financial institution, such as the Ministry of Finance.

The first upstream raw material supplier (corresponding to the first node n1) and the second upstream raw material supplier (corresponding to the second node n2) are issuers of electronic invoices, that is, the issuing unit of the electronic invoice. Taking the first upstream raw material supplier as an example, the first upstream raw material supplier releases an electronic invoice issued on the network, for example, issues the electronic invoice to the downstream distributor (corresponding to the third node n3) , And simultaneously issue the electronic invoice to the national financial institution (corresponding to the fourth node n4). The network may be a peer-to-peer network (P2P network), a client-server model, or a directly connected network architecture. And, it can run on public network architecture, private network architecture, or hybrid network architecture. However, the above-mentioned network architecture is not used to limit the implementation of this creation.

All nodes stored in the Blockchain in the present invention and all the electronic invoice data in each block, all nodes have a copy, and all nodes can access. In this way, the national financial institution or other unit can audit each of the blocks and each of the electronic invoices against the received blockchain data to verify the legality and validity of each of the blocks and each of the electronic invoices. rationality. All upstream raw material suppliers or downstream distributors can also confirm each of the blocks and each of the electronic invoices for the received blockchain data to verify each of the blocks and each of the electronic invoices. Legality and rationality. For the verification method and content, refer to the content described in the foregoing description, which is not repeated here.

Because all nodes (units) also obtain and store the same blockchain data. Once any node (unit) fails and cannot be accessed, the same blockchain data can be obtained through other nodes (units) that store the blockchain data to ensure high availability of the blockchain data ( high availability).

In summary, this creative department has the following characteristics and advantages:

1. The link between the block and the adjacent previous block provides the block's security protection mechanism by the block's time stamp and the hash value of the block to ensure that the block cannot be tampered with at all, and the block is realized. Block data integrity.

2. With the time stamp of the electronic invoice, the hash value of the electronic invoice, and the digital signature of the encrypted electronic invoice, the electronic invoice security protection mechanism is provided to ensure that the electronic invoice cannot be tampered with at all, and the integrity and verification of the electronic invoice data are achieved. Sex and undeniable.

3. Through the link between the electronic invoice and the related electronic invoice, the need to track the two-way source tracing of upstream and downstream is achieved.

4. All nodes (units) also obtain and store the same blockchain data. If any node fails and cannot be accessed, the same blockchain data can be obtained through other nodes that store blockchain data. To ensure high availability of blockchain data.

100‧‧‧ Blockchain
n1 ~ n7‧‧‧node

Figure 1: A block diagram of a blockchain that stores electronic invoices for the creative blockchain. Figure 2: A block diagram of creating a single block of content. Figure 3: A block diagram of the contents of a single electronic invoice for this creation. Figure 4: A block diagram of the link between the creative electronic invoice and the associated electronic invoice. Figure 5: A flowchart of a method for generating digital signatures for electronic invoices for this creation. Figure 6: A block diagram of the digital signature of an electronic invoice attached to the electronic invoice created. Figure 7: Schematic diagram of digital signature creation and verification of electronic invoices for the creation of this invoice. Figure 8: The flowchart of the method of using the blockchain to store electronic invoices. Figure 9: A schematic diagram of the application of the creative blockchain in the network.

Claims (10)

A method for storing electronic invoices using a blockchain is executed on one or more network servers. The method for storing electronic invoices using a blockchain includes: generating a block; storing one or more electronic invoices in In this block, a corresponding hash value of an electronic invoice is generated according to the content of each electronic invoice; each electronic invoice is linked to zero or more than one other related electronic invoice according to the corresponding hash value of the electronic invoice; when the area is The block is filled with such electronic invoices, and a corresponding block hash value is generated based on the block content and a time stamp is recorded at the time of the block establishment to complete the establishment of the block; The block hash value is linked in series with the adjacent previous block to establish the block chain. The method for storing electronic invoices using a blockchain as described in item 1 of the scope of the patent application, wherein each block includes the hash value of the block adjacent to the previous block, the record of one or more electronic invoices, and the block. A timestamp when the establishment is completed and the block hash value of the block, where the block hash value of the block is the hash value of the block from the previous previous block, the one or more electrons The record of the invoice and the timestamp when the block was created are generated by a secure hash algorithm calculation. The method for storing electronic invoices using the blockchain as described in item 1 of the scope of patent application, wherein each record of the electronic invoice contains a public key of one of the issuing units of the electronic invoice and one of the receiving units of the electronic invoice. Key, the electronic invoice hash value of zero or more electronic invoices associated with the electronic invoice, a timestamp when the electronic invoice was issued, the transaction content of the electronic invoice, and the electronic invoice hash value of the electronic invoice, The hash value of the electronic invoice of the electronic invoice is the public key of the issuing unit of the electronic invoice, the public key of the receiving unit of the electronic invoice, the zero or more than one transaction associated with the electronic invoice. The electronic invoice hash value of the electronic invoice, the transaction content of the electronic invoice, and the timestamp when the electronic invoice was issued are generated by a secure hash algorithm calculation. As described in item 3 of the scope of the patent application, the method for storing electronic invoices by using the blockchain, wherein each record of the electronic invoice can choose whether or not to attach an electronic invoice digital signature, which is the digital signature of the electronic invoice. The electronic invoice hash value is generated by signing and encrypting the private key of one of the issuing units of the electronic invoice through a digital signature generation operation. As described in item 2 of the scope of the patent application, the method of storing electronic invoices using the blockchain is used, wherein the hash value of the block adjacent to the previous block is read when the current block is generated and established. The hash value of the block in the previous block; the hash value of the block in the block is completed by the hash value of the block in the previous previous block, the record of the one or more electronic invoices, and the block. The time stamp at the time of establishment is calculated by a secure hash algorithm. The method for storing electronic invoices using the blockchain as described in item 2 of the scope of the patent application, wherein the time stamp when the block is completed is the current date and time when the block is created, in millisecond time format Record and store, and various access terminals will convert the required date format and time format by themselves. The method for storing an electronic invoice using a blockchain as described in item 3 of the scope of patent application, wherein the public key of the issuing entity of the electronic invoice is the public key provided by the entity issuing the electronic invoice; The public key of the receiving unit of the electronic invoice is the public key provided by the unit receiving the electronic invoice. The method for storing electronic invoices using the blockchain as described in item 3 of the scope of the patent application, wherein zero or more electronic invoices associated with the electronic invoice are in the same block as the electronic invoice or with the electronic invoice In different blocks. The method for storing electronic invoices using the blockchain as described in item 3 of the scope of the patent application, wherein the time stamp when the electronic invoice is issued is the current date and time when the electronic invoice was issued, in millisecond time format Record and store, and various access terminals will convert the required date format and time format by themselves. The method for storing electronic invoices using the blockchain as described in item 3 of the scope of patent application, wherein the transaction content of the electronic invoice includes the electronic invoice number, the seller's name, the seller's code, the buyer's name, the buyer's code, the transaction item, and the transaction quantity , Unit price, subtotal, tax, amount, and remarks related transaction information, and the relevant transaction information of the transaction content of the electronic invoice may be increased or decreased depending on actual transaction requirements or not filled in value.