Triple Entry Accounting 三式记账法
Abstract:The digitally signed receipt, an innovation from financial cryptography, presents a challenge to classical double entry bookkeeping. Rather than compete, the two melded together form a stronger system. Expanding the usage of accounting into the wider domain of digital cash gives 3 local entries for each of 3 roles, the result of which I calltriple entry accounting.
This system creates bullet proof accounting systems for aggressive uses and users. It not only lowers costs by delivering reliable and supported accounting, it makes much stronger governance possible in a way that positively impacts on the future needs of corporate and public accounting.
摘要:数字签名收据是金融密码学的一项创新，它对传统的复式记账法提出了挑战。 使这两者结合而非相互竞争，能够形成更强大的体系。将会计的使用范围扩大到数字现金的更广泛领域，为3个角色提供了3份本地记录，我称之为三式记账法( triple entry accounting).
This paper brings together financial cryptography innovations such as the Signed Receipt with the standard accountancy techniques of double entry bookkeeping.
本文将金融密码学的创新如签名收据(Signed Receipt), 以及复式记账法(double entry bookkeeping)的标准会计技术这两者结合。
The first section presents a brief backgrounder to explain the importance of double entry bookkeeping. It is aimed at the technologist, and accountancy professionals may skip this. The second section presents how the Signed Receipt arises and why it challenges double entry bookkeeping.
第一部分是简要的背景介绍，以解释复式记账法的重要性。它是写给是技术人员的，会计专业人员可以跳过这一部分。第二部分介绍签名收据(Signed Receipt )如何产生，又为何会挑战复式记账法(double entry bookkeeping)。
The third section integrates the two together and the Conclusion attempts to predict wider ramifications into Governance issues.
This paper benefitted from comments by Graeme Burnett and Todd Boyle[TB]http://iang.org/papers/triple_entry.html#ref_TB).
这篇论文受益于 Graeme Burnett 和 Todd BoyleTB的评论.
A Very Brief History of Accounting - 极简会计史
Accounting or accountancy is these days thought to go back to the genesis of writing; the earliest discovered texts have been deciphered as simple lists of the counts of animal and food stock. The Sumerians of Mesopotamia, around 5000 years ago, usedCuneiformor wedge shaped markings as a base-60 number form, which we still remember as seconds and minutes, and squared, as the degrees in a circle. Mathematics and writing themselves may well have been derived from the need to add, subtract and indeed account for the basic assets and stocks of early society.
如今，会计或会计学(Accounting or accountancy )被认为可以追溯到书写的起源;经过解读发现，所发现的最早的文字是动物和所存食品数量的简单列表。大约在5000年前，美索不达米亚的苏美尔人使用楔形文字(Cuneiform)或楔形标记用作六十进制( base-60 number form)，这个我们今天仍然用作时间计数，其平方，则是圆的度数。早期社会对基本资产和存货的加减计算和记账的需要，很可能就是数学和书写出现的缘由。
Single Entry 单式记账法
Single entry bookkeeping is how 'everyone' would do accounting: start a list, and add in entries that describe each asset. A more advanced arrangement would be to create many lists. Each list or 'book' would represent a category, and each entry would record a date, an amount, and perhaps a comment. To move an asset around, one would cross it off from one list and enter it onto to another list.
Very simple, but it was a method that was fraught with the potential for errors. Worse, the errors could be either accidental, and difficult to track down and repair, or they could be fraudulent. As each entry or each list stood alone, there was nothing to stop a bad employee from simply adding more to the list; even when discovered there was nothing to say whether it was an honest mistake, or a fraud.
Accounting based on single entry bookkeeping places an important limitation on the trust of the books. Likely, only the owner's family or in times long past, his slaves could be trusted with the enterprise's books, leading to a supportive influence on extended families or slavery as economic enterprises.
Double Entry 复式记账法
Double Entry bookkeepingadds an additional important property to the accounting system; that of a clear strategy to identify errors and to remove them. Even better, it has a side effect of clearly firewalling errors aseitheraccidentorfraud.
复式记账法为会计系统增加了额外的重要特性; 即，一种清晰的策略，可以识别并消除错误。更妙的是它的附加影响，可以很明确的区分(firewalling )意外或者欺诈所产生的错误。
This property is enabled by means of three features, being the separation of all books into two groups or sides, calledassetsandliabilities, the redundancy of the duplicativedouble entrieswith each entry having a match on the other side, and thebalance sheet equation, which says that the sum of all entries on the asset side must equal the sum of all entries on the liabilities side.
有三种属性，使得上述特性成为可能: 将所有的账簿分为两组或者两侧，称为资产和负债；冗余重复的复式条目的存在 -- 每个条目在另外一侧都有对应的条目；以及资产负债表等式，是指在资产一侧的条目的总值等于在负债一侧的条目的总值。
A correct entry must refer to its counterparty, and its counterpart entry must exist on the other side. An entry in error might have been created for perhaps fraudulent reasons, but to be correct at the local level, it must refer to its counterparty book. If not, it can simply be eliminated as an incomplete entry. If it does refer, the existance of the other entry can be easily confirmed, or indeed recreated depending on the sense of it, and the loop is thus closed.
一个正确的条目必须涉及到它的交易对手方，交易对方的对应条目必须存在于另一侧。可能由于欺诈的原因产生了错误的条目，但为了能够在本地层面上(at the local level)修正，它必须关联到其交易对象的账簿。如果没有，可以简单地将它当作是不完整的条目而删除。如果它确实提到了，就可以很容易地确认其它条目的存在，或者根据需要可以重新创建，这一循环就此闭合。
Previously, in single entry books, the fraudster simply added his amount to a column of choice. In double entry books, that amount has to come from somewhere. If it comes from nowhere, it is eliminated above as an accidental error, and if it comes from somewhere in particular, that place is identified. In this way, fraud leaves a trail; and its purpose is revealed in the other book because the value taken from that book must also have come from somewhere.
This then leads to an audit strategy. First, ensure that all entries are complete, in that they refer to their counterpart. Second, ensure that all movements of value make sense. This simple strategy created a record of transactions that permitted an accountancy of a business, without easily hiding frauds in the books themselves.
Which Came First - Double Entry or the Enterprise?
Double Entry bookkeeping is one of the greatest discoveries of commerce, and its significance is difficult to overstate. Historians think it to have been invented around the 1300s AD, although there are suggestions that it existed in some form or other as far back as the Greek empire. The earliest strong evidence is a 1494 treatise on mathematics by the Venetian FriarLuca Pacioli. In his treatise, Pacioli documented many standard techniques, including a chapter on accounting. It was to become the basic text in double entry bookkeeping for many a year.
复式记账法是商业上最伟大的发现之一，其重要性再怎么强调也不为过。历史学家认为它是在公元1300年左右发明的，尽管有人认为，早在希腊帝国时期，复式记账法就以各种各样的形式存在了。最早的强有力的证据是1494年威尼斯修士(Luca Pacioli)(http://www-groups.dcs.st-andrews.ac.uk/ ~历史/数学/ Pacioli.html)的数学论文。在他的论文中，Pacioli记录了许多标准的技术，有一章是写会计的。许多年里，这是复式记账法的基本文本形式。
Double Entry bookkeeping arose in concert with the arisal of modern forms of enterprise as pioneered by the Venetian merchants. Historians have debated whether Double Entry was invented to support the dramatically expanded demands of the newer ventures then taking place surrounding the expansion of city states such as Venice or whether Double Entry was an enabler of this expansion.
Our experiences weigh in on the side of enablement. I refer to the experiences of digital money issuers. Our own first deployment of a system was with a single entry bookkeeping system. Its failure rate even though coding was tight was such that it could not sustain more than 20 accounts before errors in accounting crept in and the system lost cohesion. This occurred within weeks of initial testing and was never capable of being fielded. The replacement double entry system was fielded in early 1996 and has never lost a transaction (although there have been some close shaves.
Likewise, the company DigiCash BV of the Netherlands fielded an early digital cash system into a bank in the USA. During its testing period, the original single entry accounting system had to be field replaced with a double entry system for the same reason - errors crept in and rendered the accounting underneath the digital cash system unreliable.
Another major digital money system lasted for many years on a single entry accounting system. Yet, the company knew it was running on luck. When a cracker managed to find a flaw in the system, an overnight attack allowed the creation of many millions of dollars worth of value. As this was more than the contractual issue of value to date, it caused dramatic contortions to the balance sheet, including putting it in breach of its user contract and at dire risk of a 'bank run'. Luckily, the cracker deposited the created value into the account of an online game that failed shortly afterwards, so the value was able to be neutralised and monetarily cleansed, without disclosure, and without scandal.
In the opinion of this author at least, single entry bookkeeping is incapable of supporting any enterprise more sophisticated than a household. Given this, I suggest that evolution of complex enterprises required double entry as an enabler.
Computing Double Entry in Quick Time 计算复式记账法速览
Double Entry has always been the foundation of accounting systems for computers. The capability to detect, classify and correct errors is even more important to computers than it is to humans, as there is no luxury of human intervention; the distance between the user and the bits and bytes is far greater than the distance between the bookkeeper and the ink marks on his ledgers.
How Double Entry is implemented is a subject in and of itself. Computer science introduces concepts such astransactions, which are defined as units of work that areatomic,consistent,isolated, anddurable(or ACID for short). The core question for computer scientists is how to add an entry to the assets side, then add an entry to the liabilities side, and not crash half way through this sequence. Or even worse, have another transaction start half way through. This makes more sense when considered in the context of the millions of entries that a computer might manage, and a very small chance that something goes wrong; eventually something does, and computers cannot handle errors of that nature very well.
复式记账如何实现，这自成一个主题。计算机科学引入了一些概念，比如 事物，这些概念被定义为具有原子性、一致性、独立性和持久性(或简称为ACID)的工作单元。计算机科学家的核心问题是如何在资产一侧增加一个条目，然后在负债方面增加一个条目，而不会在这个序列过程中半路崩溃。甚至更糟糕，半路开始了另外一次事物。当考虑到计算机可能管理数百万条目这一情境，而且出错的可能性要很小，这就更有意义了; 最终，有些事情确实会出错，而计算机不能很好地处理这种性质的错误。
For the most part, these concepts simply reduce to "how do we implement double entry bookkeeping" ? As this question is well answered in the literature, we do no more than mention it here.
A Slightly Less Brief History of the Signed Receipt
Recent advances in financial cryptography have provided a challenge to the concept of double entry bookkeeping. The digital signature is capable of creating a record with some strong degree of reliabilty, at least in the senses expressed by ACID, above. A digital signature can be relied upon to keep a record safe, as it will fail to verify if any details in the record are changed.
If we can assume that the the record was originally created correctly, then later errors are revealed, both of an accidental nature and of fraudulent intent. (Computers very rarely make accidental errors, and when they do, they are most normally done in a clumsy fashion more akin to the inkpot being spilt than a few numbers.) In this way, any change to a record that makes some sort of accounting or semantic sense is almost certainly an attempt at fraud, and a digital signature makes this obvious.
The Digital Signature and Digital Cash 数字签名和数字现金
A digital signature gives us a particular property, to whit:
"at a given point in time, this information was seen and marked by the signing computer."
There are several variants, with softer and harder claims to that property. For example,message digestswithentanglementform one simple and effective form of signature, andpublic key cryptosystemsprovide another form where signers hold a private key and verifiers hold a public key(MB). There are also many ways to attack the basic property. In this essay I avoid comparisons, and assume the basic property as a reliable mark of having been seen by a computer at some point in time.
根据对该特性的声明的严格程度的不同，会存在几种变体。例如,带缠结的消息摘要组成了一种简单高效的签名形式, 而 公钥加密系统则是另一种形式, 签名者持有私钥，验证者拥有公钥(MB)。还有很多抨击该基础属性的观点（ There are also many ways to attack the basic property）。在这篇文章中，我避免比较，并假定上述基本属性是在某个特定时间点上已经被计算机所见到过的可靠标记。
Digital signatures then represent a new way to create reliable and trustworthy entries, which can be constructed into accounting systems. At first it was suggested that a variant known as theblinded signaturewould enable digital cashDC. Then,certificateswould circulate as rights or contracts, in much the same way as the share certificates of old and thus replace centralised accounting systems(RAH).
These ideas took financial cryptography part of the way there. Although they showed how to strongly verify each transaction, they stopped short of placing the the digital signature in an overall framework of accountancy and governance. A needed step was to add in the redundancy implied in double entry bookkeeping in order to protect both the transacting agents and the system operators from fraud.
The Initial Role of a Receipt 收据最初的作用
Designs that derived from the characteristics of the Internet, the capabilities of cryptography and the needs of governance led to the development of thesigned receipt(GH). In order to develop this concept, let us assume a simple three party payment system, wherein each party holds an authorising key which can be used to sign their instructions. We call these playersAlice,Bob(two users) andIvan(the Issuer) for convenience.
签名票据的设计来源于互联网的特点、 密码学的功能和治理的需要(GH)。为了对这一概念进行阐释，让我们假设存在一个简单的三方支付系统，其中每一方持有一个授权密钥，可以用来签署他们的指令。为了方便起见，我们把这些参与者称为Alice， Bob(两个用户)和Ivan(发行人)。
When Alice wishes to transfer value to Bob in some unit or contract managed by Ivan, she writes out the payment instruction and signs it digitally, much like a cheque is dealt with in the physical world. She sends this to the server, Ivan, and he presumably agrees and does the transfer in his internal set of books. He then issues a receipt and signs it with his signing key. As an important part of the protocol, Ivan then reliably delivers the signed receipt to both Alice and Bob, and they can update
their internal books accordingly.
当Alice想要将某单位的价值或者Ivan(发行人)所管理的合同转移给Bob时，她写下支付指令，进行数字签名，就像在物理世界里处理支票一样。她把这个发给了服务商, Ivan, 假定他同意后，在内部的一组账簿中处理了转账。然后，Ivan填开一张收据，并用他的签名密钥来签署。作为协议的重要组成部分，Ivan可靠地将签名收据传递给Alice和Bob, 他们也相应更新了自己的内部账簿。
The Receiptisthe Transaction 收据即交易
Our concept of digital value sought to eliminate as many risks as possible. This was derived simply from one of the high level requirements, that of being extremely efficient at issuance of value. Efficiency in digital issuance is primarily a function of support costs, and a major determinant of support costs is the costs of fraud and theft.
One risk that consistently blew away any design for efficient digital value at reasonable cost was the risk ofinsider fraud. In our model of many users and a single centralised server, the issuers of the unit of digital value (as signatory to the contract) and any governance partners such as the server operators are powerful candidates for insider fraud. Events over the last few years such as the mutual funds and stockgate scandals are canonical cases of risks that we decided to address.
In order to address the risk of insider fraud, the written receipt was historically introduced as being a primary source of evidence. Mostly forgotten to the buying public these days, the purpose of a written receipt in normal retail trade is not to permit returns and complaints by the customer, but rather to engage her in a protocol of documentation that binds the shop attendant into safekeeping of the monies. A good customer will notice fraud by the shop attendant and warn the owner to look out for the monies identified by the receipt; the same story applies to the invention of the cash till or register, which was originally just a box separating the owner's takings from the monies in the shop attendant's pockets. We extend this primary motive into the digital world by using a signed receipt to bind the Issuer into a governance protocol with the users.
We also go several steps further forward. Firstly, to achieve a complete binding, Alice's original authorisation is also included within the record. The receipt then includes all the evidence of both the user's intention and the server's action in response, and it now becomes adominating recordof the event. This then means that the most efficient record keeping strategy is to drop all prior records and keep safe the signed receipt.
This domination effects both the Issuer and the user, and allows us to state the following principle:
The User and the Issuer hold the same information.
As the signed receipt is delivered from Issuer to both users, all three parties hold the same dominating record for each event. This reduces support costs by dramatically reducing problems caused by differences in information.
Secondly, we bind a signed contract of issuance known as aRicardian Contractinto the receipt(IG2). This invention relates a digitally signed document securely to the signed receipt by means of a unique identifier called amessage digest, again provided by cryptography. It provides strong binding for the unit of account, the nature of the issue, the terms, conditions and promises being made by the Issuer, and of course the identity of the Issuer.
其次,我们把一个叫做李嘉图合约的签名发行合约与收据绑定(IG2)。这一发明通过名为消息摘要的独特辨识符(密码学的另一贡献)， 将数字签名文件与签名收据安全关联。这将记账单位、发行的属性(the nature of the issue)、条款、发行人的条件和承诺，当然还有发行人的身份，都强有力的绑定在了一起。
Finally, with these enabling steps in place, we can now introduce the principle:
The Receiptisthe Transaction.
Within the full record of the signed receipt, the user's intention is expressed, and is fully confirmed by the server's response. Both of these are covered by digital signatures, locking these data down. A reviewer such as an auditor can confirm the two sets of data, and can verify the signatures.
The Signed Receipt as a Bookkeeping system 作为记账系统的签名收据
The principle of the Receipt as the Transaction has become sacrosact over time. In our client software, the principle has been hammered into the design consistently, resulting in a simplified accounting regime, and delivering a high reliability. Issues still remain, such as the loss of receipts and the counting of balances by the client side software, but these become reasonably tractable once the goal of receipts as transactions is placed paramount in the designer's mind.
As Single Entry 作为单式记账系统
In order to calculate balances on a related set of receipts, or to present a transaction history, a book would be constructed on the fly from the set. This amounts to using the Signed Receipt as a basis for single entry bookkeeping. In effect, the bookkeeping is derived from the raw receipts, and this raises the question as to whether to keep the books in place.
为了计算一组相关收据的余额，或展现一笔交易的历史，账本可以从这组收据中自动构建出来。这相当于使用了签名收据(Signed Receipt)来作为单式记账法的基础。实际上，账本衍生自原始收据，这就提出了一个问题: 是否还要保留这些账本。
The principles of Relational Databases provide guidance here. Thefourth normal formdirects that we store the primary records, in this case the set of receipts, and we construct derivative records, the accounting books, on the fly<small>[4NF]</small>.
关系型数据库的原则在这里提供了指导。第四范式指导我们保留主记录, 即我们这里所说的一组收据, 可以动态创建出派生的记录和账本。
Recovering Double Entry 复式记账的恢复
Similar issues arise for Ivan the Issuer. The server has to accept each new transaction on the basis of the available balance in the effected books; for this reason Ivan needs those books to be available efficiently. Due to the greater number of receipts and books (one for each user account), both receipts and books will tend to exist, in direct contrast to fourth normal form. A meld between relationally sound sets of receipts and double entry books comes to assist here.
Alice and Bob both are granted a book each within the server's architecture. As is customary, we place those books on the liabilities side. Receipts then can be placed in a separate single book and this could be logically placed on the assets side. Each transaction from Alice to Bob now has a logical contra entry, and is then represented in 3 places within the accounts of the server. Yet, the assets side remains in fourth normal form terms as the liabilities entries are derived, each pair from one entry on the assets side.
By extension, a more sophisticated client-side software agent, working for Alice or Bob, could employ the same techniques. At this extreme, entries are now in place in three separate locations, and each holding potentially three records.
Triple Entry Accounting 三式记账法
The digitally signed receipt, with the entire authorisation for a transaction, represents a dramatic challenge to double entry bookkeeping at least at the conceptual level. The cryptographic invention of the digital signature gives powerful evidentiary force to the receipt, and in practice reduces the accounting problem to one of the receipt's presence or its absence. This problem is solved by sharing the records - each of the agents has a good copy.
In some strict sense of relational database theory, double entry book keeping is now redundant; it is normalised away by the fourth normal form. Yet this is more a statement of theory than practice, and in the software systems that we have built, the two remain together, working mostly hand in hand.
在一些严格的关系数据库理论中，复式簿记是冗余的; 它被第四范式归一化了(normalised away)。然而，这更多的是一种理论阐述而非实践，在我们构建的软件系统中，两者共同存在，联手工作。
Which leads to the pairs of double entries connected by the central list of receipts; three entries for each transaction. Not only is each accounting agent led to keep three entries, the natural roles of a transaction are of three parties, leading to three by three entries.
这就导致了复式账目由收据的中心列表所链接; 每笔交易有三个条目。不只每个会计代理要保留三份条目，一笔交易天然就是包含三方的，这就使得三方各自有三份条目（leading to three by three entries.）。
We term thistriple entry bookkeeping. Although the digitally signed receipt dominates in information terms, in processing terms it falls short. Double entry book keeping fills in the processing gap, and thus the two will work better together than apart. In this sense, our term of triple entry bookkeeping recommends an advance in accounting, rather than a revolution.
Software Considerations 软件方面的考虑
The precise layout of the entries in software and data terms is not settled, and may ultimately become one of those ephemeralimplementation issues. The signed receipts may form a natural asset-side contra account, or they may be a separate non-book list underlying the bookkeeping system and its two sides.
Auditing issues arise where construction of the books derives from the receipts, and normalisation issues arise when a receipt is lost. These are issues for future research.
Likewise, it is worth stating that the technique of signing receipts works both with private key signatures and also with entanglement message digest signatures; whether the security aspects of these techniques is adequate to task is dependent on the business environment.
同样，值得说明的是，签名收据的技术既适用于私钥签名，也适用于缠结消息摘要签名(entanglement message digest signatures); 这些技术在安全方面是否胜任要视业务环境而定。
Roles of the Agents 代理的角色
It will be noted that the above design of triple entry bookkeeping assumed that Alice and Bob were agents of some independence. This was made possible, and reflected the usage of the system as a digital cash system, and not as a classical accounting system.
Far from reducing the relevance of this work to the accounting profession, it introduces digital cash as an alternate to corporate bookkeeping. If an accounting system for a corporation or other administrative entity is recast as a system of digital cash, orinternal money, then experience shows that benefits accrue to the organisation.
Although the core of the system looks exactly like an accounting system, each department's books are pushed out as digital cash accounts. Departments no longer work so much with budgets as have control over their own corporate money. Fundamental governance control is still held within the accounting department by dint of their operation of the system, and by the limited scope of the money as only being usable within the organisation; the accounting department might step in as amarket maker, exchanging payments in internal money for payments in external money to outside suppliers.
We have operated this system on a small scale. Rather than be inefficient on such a small scale, the system has generated dramatic savings in coordination. No longer are bills and salaries paid using conventional monies; many transactions are dealt with by internal money transfers and at the edges of the corporation, formal and informal agents work toexchangebetween internal money and external money. Paperwork reduces dramatically, as the records of the money system are reliable enough to quickly resolve questions even years after the event.
The innovations present in internal money go beyond the present paper, but suffice to say that they answer the obvious question of why this design of triple entry accounting sprung from the world of digital cash, and has relevence back to the corporate world.
Patterns of Commerce 商业模式
Todd Boyle looked at a similar problem from the point of view of small business needs in an Internet age, and reached the same conclusion - triple entry accounting(1). His starting premises were that:
Todd Boyle 从互联网时代小型业务的角度，对类似的问题进行了探讨，然后得到了相同的结论 -- 三式记账法。他的前提是:
The major need is not accounting or payments, per se, but patterns of exchange - complex patterns of trade;
Small businesses could not afford large complex systems that understood these patterns;
They would not lock themselves into proprietary frameworks;
主要的需求不是会计或支付, 而是交换的模式 -- 交易的复杂模式;
From those foundations, Boyle concluded that therefore what is needed is a shared access repository that provides arms-length access. Fundamentally, this repository is akin to the classic double-entry accounting ledger of transaction rows ("GLT" for General Ledger - Transactions), yet its entries are dynamic and shared.
Simple examples will help. When Alice forms a transaction, she enters it into her software. Every GLT transaction requires naming her external counterparty, Bob. When she posts the transaction, her software stores it in her local GLT and also submits it to the shared repository service's GLT.
The Shared Transaction Repository ("STR") then forwards the transaction on to Bob. Both Bob and Alice are now expected to store the handle to the transaction as an index or stub, and the STR then stores the entire transaction.
Boyle's ideas are logically comparable to Grigg and Howland's, although they arive from different directions (the STR is Grigg's Ivan, above) and are not totally equivalent. Where the latter limited themselves to payments, the accuracy of amounts, and protection with hard cryptographic shells, Boyle looked at wider patterns of transactions, and showed that the STR could mediate these transactions, if the core shared data could be extracted and made into a single shared record. Boyle's focus was on the economic substance of the transaction.
Boyle的观点在逻辑上与 Grigg 和 Howland的观点类似，尽管他们从不同的方向出发(Boyle文中的STR 就是 Grigg 上文中的 Ivan)，且并不完全相同。后者将研究范围限定在交易、数额准确性、具有坚实加密学外壳的保护等方面，Boyle 则研究了更广泛的交易模式，并表明如果可以将核心共享数据提取并转换为单条共享记录的话，则可以用STR协调这些交易。Boyle的关注点在于交易的经济实质。
Extending the Humble Invoice 对微不起眼的发票的延伸
Imagine a simple invoicing procedure. Alice creates an invoice and posts it to her software (GLT). As she has named Bob, the GLT automatically posts it to Ivan, the STR, and he forwards it to Bob. At this point Bob has a decision to make, accept or reject. Assuming acceptance, his software can then respond by sending an acceptance message to Ivan. The STR now assembles an accepted invoice record to replace the earlier speculative invoice record and posts that threeways. At some related time (to do with payment policy) Bob also posts a separate transaction to pay for the invoice. This could operate in much the same way as a separate transaction, linking directly to the original invoice.
想象一个简单的发票程序。Alice创建了一张发票并将其提交给她的软件(GLT)。她指定了Bob，GLT会自动将其发送给Ivan，即STR(共享交易存储库), 并将其转发给Bob。此时，Bob需要决定，接受或拒绝。假设接受，他的软件可以通过向Ivan发送一条接收信息来回应。STR 现在收集了一份已接受的发票记录，以取代先前的提议性的(speculative)发票记录, 并将其提交给三方。在某个相应的时间(与支付政策有关)Bob也会发布一笔支付发票的交易。这可以像单独的事务一样操作，直接链接到原始的发票。
Now, as the payment links back, and the invoice is a live transaction within the three entries in the three accounting systems, it is possible for a new updated invoice record to refer back to the payment activity. When the payment clears, the new record can again replace the older unpaid copy and promulgate to all three parties.
Patterns of Transactions 交易模式
Software could be written to facilitate and monitor this flow and similar flows. If the payments system is sufficiently flexible, and integrated with the needs of the users, if might be possible to merge the above invoice with the payment itself, at the Receipts level. Seen in this light, the Signed receipt of Ricardo is simply the smallest and simplest pattern within the more general set of patterns. We could then suggest that the narrow principle ofthe Receipt is the Transactioncould be extended into The Invoice is the Transaction.
A particular transaction in business almost never stands alone. They come in patterns. For example offers and acceptances form a wider transaction but seldom encapsulate the entire fulfillment and payment cycle. Even if there has been a payment accompanying a PO message, the customer then waits for fulfillment.
There is a large body of science and literature built around thesepatterns of transactions. These have been adopted by the Business Process workgroup of ebXML and other standards bodies, where they are called "Commercial Transactions." Where however the present work distinguishes itself is in breaking down these transactions into the atomic elements. It is to that we now turn.
有大量的科学和文献围绕着这些交易模式展开。这些已经被Business Process workgroup of ebXML和其他标准组织所采用，称之为为“商业交易”。然而，目前的工作与众不同之处在于，会将这些交易分解为原子化的元素。我们现在转向这一点。
The Requirements of Triple Entry Accounting 三式记账法的要求
The implementation of Triple Entry Accounting will in time evolve to support patterns of transactions. What has become clear is that double entry does not sufficiently support these patterns, as it is a framework that breaks down as soon as the number of parties exceeds one. Yet, even as double entry is "broken" on the net and unable to support commercial demands, triple entry is not widely understood, nor are the infrastructure requirements that it imposes well recognised.
1 Strong Pseudonymous, At Least. As there are many cycles in the patterns, the system must support a clear relationship of participants. At the minimum this requires a nymous architecture of the nature of Ricardo or AADS. (This requirement is very clear, but space prevents any discussion of it.)
1 强匿名性，这是最起码的。由于模式中有许多循环，系统必须支持参与者之间的清晰关系。至少需要一个具有Ricardo 或者 AADS的特性的署名架构。(这个要求很清楚，但限于篇幅不作讨论了。)
2 Entry Signing. In order to neutralise the threats to and by the parties, a mechanism that freezes and confirms the basic data is needed. This is signing, and we require that all entries are capable of carrying digital signatures (see 1, above, which suggests public key signatures).
3 Message Passing. The system is fundamentally one of message passing, in contrast to much of the net's connection based architecture. Boyle recognised early on that a critical component was the generic message passing nature, and Systemics proposed and built this into Ricardo over the period 2001-2004 (4).
3 消息传递。 该系统从根本上来说是一个消息传递的系统，这与大多数网络的基于连接的架构形成了对比。Boyle 早就认为通用的信息传递特性是一个核心的组成部分，在2001-2004年期间，Systemics 公司计划并将其构建到Ricardo合约之中。
4 Entry Enlargement and Migration. Each new version of a message coming in represents an entry that is either to be updated or added. As each message adds to a prior conversation, the stored entry needs to enlarge and absorb the new information, while preserving the other properties.
5 Local Entry Storage and Reports. The persistent saving and responsive availability of entries. In practice, this is the classical accounting general ledger, at least in storage terms. It needs to bend somewhat to handle much more flexible entries, and its report capabilities become more key as they conduct instrinsic reconciliation on a demand or live basis.
6 Integrated Hard Payments. Trade can only be as efficient as the payment. That means that the payment must be at least as efficient as every other part; which in practice means that a payment system should be built-in at the infrastructure level. C.f., Ricardo.
6 整合硬性支付。交易的效率只会跟支付一样。这意味着支付必须至少和其他部分一样有效; 实际上这意味着支付系统应该内置在基础设施的级别。比如, Ricardo合约。
7 Integrated Application-Level Messaging. As distinct to the messaging at the lower protocol levels (1 above), there is a requirement for Alice and Bob to be able to communicate. That is because the vast majority of the patterns turns around the basic communications of the agents. There is no point in establishing a better payment and invoice mechanism than the means of communication and negotiation. This concept is perhaps best seen in the SWIFT system which is a messaging system, first and foremost, to deliver instructions for payments.
Double Entry bookkeeping provides evidence of intent and origin, leading to strategies for dealing with errors of accident and fraud. The financial cryptography invention of the signed receipt provides the same benefits, and thus challenges the 800 year reign of double entry. Indeed, in evidentiary terms, the signed receipt is more powerful than double entry records due to the technical qualities of its signature.
There remain some weaknesses in strict comparison with double entry bookkeeping. Firstly, in the Ricardo instantiation of triple entry accounting, the receipts themselves may be lost or removed, and for this reason we stress as a principle thatthe entry is the transaction. This results in three active agents who are charged with securing the signed entry as their most important record of transaction.
Secondly, the software ramifications of the triple entry system that are less convenient than that offered by double entry bookkeeping. For this reason, we expand the information held in the receipt into a set of double entry books; in this way we have the best of both worlds on each node: the evidentiary power of the signed entries and the convenience and local crosschecking power of the double entry concept.
其次，三式记账法的相应软件没有复式记账法所提供的软件那么容易使用。为此，我们将收到的信息扩大为一套复式账簿; 这样，我们在每个节点上都能够将两者的优势结合起来: 签名条目的证据性能力，以及复式记账的本地化交叉验证的能力。
Both of these imperitives meld signed receipts in with double entry bookkeeping. As we end up with a logical arrangement of three by three entries, we feel the termtriple entry bookkeepingis useful to describe the advance on the older form.
Drawing in the Agents 吸引代理
To fully benefit from triple entry bookkeeping, we have to expand accounting systems out to agents and offer them direct capabilities to do transactions. That is, we make the agents stakeholders by giving them internal money (5). Use of digital cash to do company accounts empowers the use of this concept as a general replacement for accounting using books and departmental budgets, and is an enabler for verifying and auditing the centralised accounts system by way of signed receipts.
Solving Frauds 解决欺诈问题
Once there, governance receives substantial benefits. Accounts are now much more difficult to change, and much more transparent. It is our opinion that various scandals and failures of governance would have been impossible given these techniques: the mutual funds scandal would have shown a clear audit trail of transactions and thus late timing and otherwise perverted or dropped transactions would have been clearly identified or eliminated completely(NG). The emerging scandal in the USA known asStockgatewould have been impossible as forgery of shares and value for manipulative trading purposes is revealed by signed receipts. Likewise, Barings would still be a force in investment banking if accounts had been organised around easily transparent digital cash with open and irreducible signed receipts that evidence invisible accounts (88888). Enron style scandals would have permitted more direct "follow the money" governance lifting the veil on various innovative but economically meaningless swaps.
一旦上述实现了，管理将从中获得巨大收益。现在，账户变得更加难以改变，而且更加透明。我们认为，如果这些技术存在的话，各种丑闻和治理失败问题将不复存在: 共同基金丑闻将会留下清晰可见的痕迹供审计追踪, 因此之后择时交易和其他形式的篡改或删除的记录，就能够被清晰地辨认出来，或者被彻底清除掉。在美国被称为“Stockgate”的丑闻将会成为不可能，因为处于操纵交易的目的而伪造股票和价格，都能通过签名收据得到披露。同样地，如果围绕着简单的数字现金来组织会计体系，有着公开不可消除的签名收据，隐匿的账户就会留下证据(88888)，那么巴林银行就不会倒闭，现在仍然会是投资银行中的实力派。安然(Enron)类型的丑闻，将允许进行更直接的“跟踪金钱式”的管理方式，把蒙在各种创新但在经济上毫无意义的互换把戏的面纱揭开。
[TB]A draft form of this paper credited Todd Boyle as an author, but this was later withdrawn at his request due to wider differences between the views.
[LP]Friar Luca Pacioli, Summa de Arithmetica, Geometria, Proportioni et Proportionalita 1494, Venice.
[IG1]Ian Grigg "The Twilight Zone," Financial Cryptography blog 16th April 2005
[MB]Entanglement is discussed in: Petros Maniatis and Mary Baker, "Secure History Preservation through Timeline Entanglement," Proc. 11th USENIX Security Symposium, August 2002.
[DC]David Chaum, "Achieving Electronic Privacy," Scientific American, v. 267, n. 2 Aug 1992.
[RAH]Robert A. Hettinga "The Book-Entry/Certificate Distinction" 1995, Cypherpunks
[GH]Gary Howland "Development of an Open and Flexible Payment System1996, Amsterdam, NL.
[IG2]Ian Grigg "The Ricardian Contract,"<cite>First IEEE International Workshop on Electronic Contracting(WEC) 6th July 2004
[4NF]E.F. Codd, "A Relational Model of Data for Large Shared Data Banks,"Comm. ACM 13 (6), June 1970, pp. 377-387.
Todd Boyle, "GLT and GLR: conceptual architecture for general ledgers," Ledgerism.net, 1997-2005.
Todd Boyle, "STR software specification," Goals, 1-5. This section adopts that numbering convention.
Ian Grigg, various design and requirements documents, Systemics, unpublished.
A substantial part of the programming and design was conducted by Edwin Woudt (first demo, SOX layers, UI) and Jeroen van Gelderen (message passing client architecture).
Using internal money instead of an accounting system is not a new idea but has only been recently experienced: Ian Grigg,How we raised capital at 0%, saved our creditors from an accounting nightmare, gave our suppliers a discount and got to bed before midnight. Informal essay (rant), 7 Jul 2003.
[NG]James Nesfield and Ian Grigg "Mutual Funds and Financial Flaws," U.S. Senate Finance Subcommittee 27th January, 2004
荆凯(shuke0327) 区块链技术爱好者，程序员，坚信区块链将会改变潮水的方向，欢迎关注我的公众号: 增长之道