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)

The mail server cannot archive outgoing emails without further ado. An archiving system stores all existing emails in the archive. However, if they are only sent via SMTP, the email does not exist in the mailbox and therefore cannot be archived.

So far, I see two possible solutions:

  1. Mail server:
    Outgoing emails must be intercepted and archived on the mail server.
  2. Application:
    In the application (Invoice Ninja), outgoing emails must be stored in the “sent” folder, as with a “normal” email client.

I don’t think I would expect InvoiceNinja to have any regulation & compliance systems, especially financial ones. I would think that you’re stuck having to come up with a method of compliance on your own.

Other systems offer such options by simply storing the sent email in the mailbox (as with any conventional email client). Technically, this should not be a major challenge. All that would be required is the use of an additional IMAP connection to store the emails.

If Invoice Ninja implements this feature, it will increase the value of Invoice Ninja, as archiving outgoing invoices by email is mandatory, at least in the EU.

I would suggest making a feature request.

Problem solved!
The SMTP server already transfers the email to the archive. This means that, contrary to my incorrect assumption, storage by a client (Invoice Ninja) is not necessary.

1 Like

Glad to hear it, thanks for the update!