You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
German bookkeeping requirements are prevalent in Germany, Austria and Switzerland.
It requires every transaction to have its reference document (proof).
“No transaction without reference document.”
The books are usually furthered starting from the reference documents:
sort reference documents chronologically
enumerate them sequentially with unique identifier, without any leap
assignment to specific account to book the document to (group them by target account)
make the actual transaction per account
As you see, the process is driven by the reference documents.
Reference documents can be:
digital, single or multiple pages
physical, single or multiple pages
Semantically:
cash and non-cash
outgoing invoices
ingoing invoices
non-cash
bank statements
cash
cashier receipts
Hard requirements:
a. Progressive validity: Starting from each reference document every transaction must be verifiable.
b. Retrograde validity: Starting from each transaction, each reference document must be verifiable.
Implementation requirements:
Do not permit any transaction without reference document (see b.)
Transaction must refer at minimum sequential reference document number, like P123-2 (P for physical, 123 for document id, 2 for page no or sub-sequence)
Reference documents might be referred to by one or more transactions (a reference existing in the system without a transaction should raise an error, see a.)
Digital documents should be able to get referenced in transactions, with a click.
Option:
A later transaction is not considered to be valid if it uses the same reference document of a transaction that is separated by a any other transaction(s).
Transaction dates should be consistent with used reference document ids.
support for viewing such attachments in hledger-web would be great. It sounds like an easy project. Just needs a bit of design - perhaps the simplest would be to reserve the file: tag and link that. (That would work for a single attachment per transaction or posting or account. Though I guess you could repeat it too. )
German bookkeeping requirements are prevalent in Germany, Austria and Switzerland.
It requires every transaction to have its reference document (proof).
“No transaction without reference document.”
The books are usually furthered starting from the reference documents:
As you see, the process is driven by the reference documents.
Reference documents can be:
Semantically:
Hard requirements:
a. Progressive validity: Starting from each reference document every transaction must be verifiable.
b. Retrograde validity: Starting from each transaction, each reference document must be verifiable.
Implementation requirements:
Available hledger functionality:
Additional required hledger functionality: It would be helpful to be able to
How to organise digital references?
Beancount suggests one scenario to organise the digital references by mirroring the accounts hierarchy.
The text was updated successfully, but these errors were encountered: