Arise Software Ltd

Support and Help Docs

23. October 2019 20:28
by Admin
0 Comments

Export Excel Error

23. October 2019 20:28 by Admin | 0 Comments

When exporting reports to Excel, it may show an error saying it cannot open Excel.

Save the file to Desktop, ignore the error, then copy the file from the server desktop to your desktop that has Excel.

12. August 2019 11:00
by Admin
0 Comments

Batch Update

12. August 2019 11:00 by Admin | 0 Comments

GDPro allows batch updating of certain fields, such as shareholder Regions. The following example is for updating regions.

Ensure region codes are entered:

Ensure spreadsheet is saved as xls version.

 

Access import facility:

 

Process

  • Load file by clicking […] and selected file.
  • Enter worksheet name (in this example AUS>Wellington)
  • Select column with SHID (in this example column A)
  • Select the field to be updated (Region)
  • Select column that contains the data to update GDPro (in this example, Region is being updated which is column U in the spreadsheet)
  • Click Run – not this process is irreversible

26. June 2019 18:36
by Admin
0 Comments

Cannot create PDF

26. June 2019 18:36 by Admin | 0 Comments

If you get the following when trying to create PDF

Please try the following:

Please go to Payments click on * select a date before or after date shown, press tab to ensure date selection saves

Then on same screen do the same with the opening balance date

Then retry owner pdf

2. April 2019 12:41
by Admin
0 Comments

Large Database Size

2. April 2019 12:41 by Admin | 0 Comments

Microsoft records all activity in the LDF file and can get large. The activities can be removed although we then cannot do database audit forensics on it later, if ever required. To empty the LDF file via sql server management studio, query analyser

USE master

ALTER DATABASE gdpro SET RECOVERY SIMPLE WITH NO_WAIT

use gdpro

DBCC SHRINKFILE(gdpro_log, 1)

USE master

ALTER DATABASE gdpro SET RECOVERY FULL WITH NO_WAIT

2. April 2019 11:52
by Admin
0 Comments

Rounding Transactions

2. April 2019 11:52 by Admin | 0 Comments

Old GDPro used 4 decimal places for financial transactions when going things like successions and distributions. New GDMA automatically rounds transactions to 2 decimal places.

Avoid distributions and successions in GDPro and do them in GDMA. To round financial transactions to 2 decimal places:

In gdma go to options

 

Then Round…

7. March 2019 16:14
by Admin
0 Comments

Custom fields on main screen

7. March 2019 16:14 by Admin | 0 Comments

Custom fields that use to be in the Misc tab are now on the main screen. If they have not been used prior, the screen will look similar to this:

To update the captions, go to Misc tab

Click Update Text

Update the captions:

Restart GDPro/GDMA and they will now show with the updated captions

 

 

 

20. February 2019 15:20
by Admin
0 Comments

BNZ International DC Payments

20. February 2019 15:20 by Admin | 0 Comments

An option to pay overseas via BNZ International Direct Credit online banking, is available via the normal payment system called BNZ Intl.

BNZ requires:

  • Owner Name
  • Owner Address (requires 2 address lines and no PO Box or Private Bag)
  • Owner Bank Account
  • Owner Country code.
  • Bank Country code.
    • This is the country of the owner’s bank and would typically be the same as owner country code.
  • Owner Bank BIC Swift Code, if country code is not AU
    • Refer to note below.
  • Correspondent Bank Fee Indicator.
    • This is either B or O. B = beneficiary(owner) pays fee or O = the trust pays fee
  • Owner Bank Clearing Code.
    • Refer to note below.

Owner Bank BIC Swift Code and Owner Bank Clearing Code. This information is obtained from the owner and is key to the BNZ international payment system. There is no automated way we can get this info and must be entered manually once obtained by the owner, into GDPro’s/GDMA’s bank account details field for each owner that requires a BNZ International Direct Credit payment.

If the country code is AU then only the Owner Bank Clearing Code is required and not the Owner Bank BIC Swift Code.

Please refer to https://www.bnz.co.nz/assets/business-banking-help-support/internet-banking/ib4b-file-format-guide.pdf?v=3 page 28 and discuss with BNZ.

 

The format of the BNZ requirement that is to be entered in GDPro’s/GDMA’s bank account details field is as follows:

PT*<Owner Country Code, 2 characters>*<Bank Country Code, 2 characters>*<Owner Bank BIC Swift Code, 11 characters>*<Correspondent Bank Fee Indicator, 1 character>*<Owner Bank Clearing Code, 15 characters>

 

This is an example that is entered into the bank account details field: PT*AU*AU**O*AU123456

The above states that a payment is to be made to an <Owner Country Code> AU, <Bank Country Code> AU, <Owner Bank BIC Swift Code> (there is no BIC Swift Code as the country code is AU), <Correspondent Bank Fee Indicator> O the trust pays the international payment fee and <Owner Bank Clearing Code> is AU123456

 

Although a bit complex, these are the requirements from BNZ as stipulated here https://www.bnz.co.nz/assets/business-banking-help-support/internet-banking/ib4b-file-format-guide.pdf?v=3 from page 19.

 

Creating the file is the same as creating the current BNZ file for local NZ payments - by selecting bank option BNZ Intl - although the steps to import into BNZ online banking will be slightly different. The best people to talk about how this is done is your BNZ manager(s).