Archiving in accordance with GoBD

Version ie <v5.10.30>

5.12.28

Environment <Docker/Shared Hosting/Zip/Other>

Webserver

Checklist

Describe the bug

Hello,
According to GoBD, incoming and outgoing emails must be archived in an audit-proof manner.
How is it possible to archive outgoing emails with invoices in an audit-proof manner using Invoice Ninja?

Usually, when archiving (a system for this already exists), incoming and outgoing mail is archived. However, this would require Invoice Ninja (via IMAP) to store the outgoing email in the mailbox. Sending a copy is not permitted according to GoBD.

Hence the question:
How can Invoice Ninja be used to archive outgoing emails in an audit-proof manner?

Translated with DeepL.com (free version)

Steps To Reproduce

Expected Behavior

Additional context

Screenshots

Logs

Hi,

Could this be handled by the email server rather than Invoice Ninja?

It probably should be handled by the email provider vs the erp.

@RoundAboutWEB: If you’re bound by retention requirements through either litigation or regulation you can either pay for a service like mimecast to create an immutable record of all email traffic that goes through it or you can set up a pop or imap archiver on your own… InvoiceNinja I don’t think would be able to provide a service beyond action tracking like it already does.

Obviously doing it on your own will take more time but cost way less.

I’ve heard good things about https://www.mailpiler.org/ and I’ll likely be standing this up myself.

FYI is does have a statement regarding GoBD for you: GoBD notes (in German)