Hi, just to make sure I have understood the DT Help file regarding DT4 audit-proof databases: Is it correct that all documents in audit-proof databases are read-only, so you cannot edit them? This would be surprising to me. I would expect an audit-proof database to just record all changes so that previous version can be restored without problems and that the audit trail can show who did changes and when. Can you please clarify? Thank you very much.
Documents cannot be edited.
Read the Getting Started > Building Your Database section.
To quote from the lovely documentation in the section about audit-proof databases:
They are not working databases, but ones in which you store and âlock awayâ important documents.
So, no: You do not get an audit trail. You get a database whose documents are locked. Think of it as an accounting program where youâve done your annual accounts (âJahresabschlussâ). After that, you canât modify anything in this year. Which is a good thing.
If you use DT to collect your invoices, tax receipts, account statements, you could have, I think, audit-proof databases for each year that is tax-wise closed. No need to edit those documents anymore (and I never have a need to edit an invoice anyway 
)
1 Like
Thank you chrillek. I happen to be a certified auditor. From this perspective I hate to say that even for your scenario, editable documents are of high importance. During the preparation of annual accounts, the clients usually perform calculations in excel files, have documentation in word and excel documents and also modify original receipts by putting stamps and notes on them. if one now used DT4 as document management system, you would need to first perform all your preparation work in the normal file system or in a non-audit proof database in DT4 and only when everything is finished could you move the files into DT4 audit-proof database. This is not very realistic and does not meet the needs for someone that uses DT4 for purposes that are also tax relevant. Moreover, if you just move the finished files into the audit-proof database, then tax authorities could say that you have not saved all the interim versions and changes and that there is no audit trail which shows who did what and when. So the current locked database concept does not meet the legal requirements for an audit-proof database. That being said, I will stay with the normal databases and use the backup system with versioning as a workaround. but for companies, that is of course not feasible.
So, perhaps the term âaudit-proofâ is not well-chosen. In any case, the âwho did whatâ question canât be reliably answered in DT as it doesnât have concept of different users.
And frankly: believing that any operation on a computer can be protected against later manipulation seems naive to me. Even if the underlying OS is more secure than macOS.
But on macOS? Come on, a simple sudo vi audit.log does the trick. And no one will be the wiser.
So, an âaudit-proofâ database might be useful for some. But expecting a real auditing environment on macOS? Who does that?
1 Like
None of which answers the question posed, as itâs simply shifting the point of argument.
Personally, Iâve looked into the audit-proof database capabilities (though not an auditor) due to work-place related requirements around internal audit and risk management systems, and Iâve also come to the conclusion that, as implemented, the audit proof capabilities of DT4 donât quite meet my needs as I need to log multiple versions of single documents, and otherwise edit them in a way that can be trailed for audit purposes. Iâm sure they will for some and will continue to monitor this area of DT4âs development.
I think some good points are raised in this thread. Maybe for the next Beta the nomenclature about âAudit-proofâ could be adjusted and comments solicited.