Skip to end of metadata
Go to start of metadata

When sending reports and notices to your investors, follow this guide


In addition to sending notices and reports over email, you can send them to investor datarooms that your investors can access through the investor portal. 

Step-by-step guide

Once your notices and reports are in the transacted status, you will see a 'notifications' button when you open the corresponding 'notice group' or 'report group'. You will see the following screen.

Under the Email column, you will see the status of your last notification request. A value of '-' represents that a file has not been sent previously. An 'exclamation mark'corresponds to a previously failed sent request, while a 'tick'corresponds to a successfully sent file. In order to send a notification request:

  1. Simply check the rows corresponding to the relevant reports, or leave all rows unchecked to send all reports.

  2. Click the 'Notify Investors' dropdown, followed by the 'Send to Poral' link. A confirmation screen will pop up.

  3. Select the 'Send' button to send the files to portal.

  4. The pop-up will change to the following:

  5. The files will be visible to investors on the investor portal


Verifying Successful Delivery

Fundwave has a notification log where you can see either a 'tick' mark, an 'exclamation' mark or a dash that represent a a successful email delivery, a send failure and a non attempted delivery respectively.However, please note that a 'tick' mark does not guarantee a successful delivery. It is only a confirmation that an email has been sent successfully through Fundwave. You may still come across bounces or delivery failure notifications if the delivery has failed for any reason, such as a full mailbox of the recipient or an outdated email address. You should look out for any delivery failure notifications in the inbox that you specified in the 'from address'.In case you see the 'exclamation' mark next to a report or a notice, please confirm that the contact details of your investors are set correctly. If you are unable to trace the issue, please raise a support request at