Could you explain the Closing Balance Report?
1. The Statement Ending Balance is what the bank tells us is our current statement balance.
2. However, ABR tells us that there are unreconciled statement transactions, so we REVERSE these from the
Statement Ending Balance to get back to a reconciled statement balance (Net Ending Balance).
3. We then add on to the reconciled statement balance the unreconciled GL transaction to get a figure which should agree to what Dynamics GP tells us is the bank balance (Overall Book Balance).
Why aren’t some statement transactions appearing on the Reconcile window?
The first thing to look at when unreconciled statement transactions do not appear on the right hand side of the Reconcile window is to make sure that the statement which the transactions appear on is balanced. That is, on the Bank Statement Entry window, check that the user-entered Ending Balance in the statement header information is equal to the calculated Ending Balance at the bottom right of the window.
The calculated Ending Balance is the Starting Balance plus all the statement transaction amounts. An unbalanced statement can be saved by the user overriding a warning message, but none of the transactions will appear on the Reconcile window.
How can I modify the Account Number or Routing Number in an ABR Bank Account?
If the Bank Account or Routing Number need to be modified for an existing ABR Bank Account, the values will need to be updated in the NCABR001 table. Edit the following SQL script to include the appropriate Bank Account Number (BNKACTNM), Routing Number (TRNSTNBR). Then replace the ‘BANKID’ text with the appropriate ABR Bank ID, and then run the script against the Dynamics GP company database .
UPDATE NCABR001 SET BNKACTNM = ‘0123456789012’, TRNSTNBR = ‘012345678’ WHERE BANKID = ‘BANKID’
How do I delete a duplicate statement?
You can delete any unreconciled statements by calling it up in the Bank Statement Entry window ( Transactions >> Financial >> Bank Statement Entry) and clicking the Delete button at the top of the window. However, if this does not cause the statements after the deleted statement to have their starting and ending balances calculated automatically, you could try the following:
1. Make sure that you have a good backup of your data, and that all users are logged out of ABR.
2. Run an ABR Checklinks, for the appropriate Bank ID only, with the Report Only Option checked. You may need to add the Checklinks to the Shortcut Bar - it's in the Financial Series of the Nolan’s Advanced Bank Rec product.
3. Check the report produced, if there are no fatal errors reported (they have the words 'Checklinks cannot fix this' in the error message) then proceed to 4), otherwise contact the Nolan Business Solutions Support Desk for advice.
4. Re-run the ABR Checklinks with the Report Only option unchecked. This will correct any non-fatal errors, and also recalculate the statement starting and ending balances. Please be aware that the checklinks will also renumber the statements so that they are in sequence, so any breaks in the sequence of statement numbers will be corrected.
How do I remove duplicate statement transactions from the ABR Reconcile window?
1. If the duplicated transactions are all on the same statement number, then go in to Bank Statement Entry, call up the appropriate Bank ID and Statement Number and click on the Delete button at the top of the Bank Statement Entry window.
2. If the duplicated statement transactions are on a statement number which also contains valid statement transactions, then go in to Bank Statement Entry, select the appropriate Bank ID and Statement Number and, for each of the duplicated transactions, highlight the transaction in the scrolling window, click on the Edit menu item in the toolbar, and choose Delete Row from the dropdown menu. The Statement Ending Balance will then need to be adjusted to reflect the new value before saving the statement.
3. In both of the above cases you will need to refresh the Reconcile window for the appropriate Bank ID by clicking on the Delete button in the Reconcile window. This will not delete any of the statement transactions themselves, but will delete transactions from the copy table that the Reconcile window uses. Re-entering the Bank ID into the Reconcile window will cause the copy table to be rebuilt from the underlying transactions. Please be aware that refreshing the Reconcile window in this way will cause any match or checked information already in the Reconcile window to be lost.
How do I populate ABR Check Number when using Integration Manager
On the ABR Reconcile window for GL transactions the Reference field corresponds to the Reference (REFRENCE) column in the GL Open table (GL20000), and the Document / Cheque Number corresponds to the Originating Document Number (ORDOCNUM) column.
Either of these fields can be used to set up reconcile rules which will allow automatic propose / matching of GL
transactions with statement transactions
Why are negative bank statement amounts showing as zero on the reconcile window?
The problem being encountered is due to the fact that the Bank Statement Entry window doesn't like negative amounts in the Withdrawal and Deposit columns. It processes the amounts entered so that withdrawals become negative amounts on the ABR Reconcile window, and deposits become positive amounts.
To rectify the problem, delete the rows with the negative amounts from the Bank Statement Entry window, then re- enter any negative deposits as a withdrawal, and any negative withdrawals as a deposit.
How can I extract GL transactions from a historical year?
Normally the ABR GL Extract process will only extract GL transactions from the GL Open table (GL20000) into the ABR Unreconciled GL transactions table. However, in some cases, it is necessary to extract transactions from the GL Historical Transactions table (GL30000).
NOTE: In later releases of v6.00 ABR and all releases of v7.00 ABR, this can be accomplished as follows - Exit from Dynamics GP, edit the Dex.ini file in the Dynamics GP client directory (in GP 10 the file located inside the Data directory of your GP directory)on the workstation from which you will run the historical extract to add the line:
HistoryExtract=TRUELog back into Dynamics GP and, when you open the ABR Extract window, you should see an extra button marked Extract From History. This button performs exactly the same function as the normal Extract button, but will work on the GL30000 table instead of the GL20000 table. The History Extract facility should be used with care, we would recommend keeping the date range of the extract as small as possible, and removing the facility once it is no longer needed by removing the appropriate line in the Dex.ini file, or changing it to:
HistoryExtract=FALSE
How can I make a GL posting that won't be extracted into ABR?
The way to enter a transaction against the Bank GL account and ensure that it is not extracted into ABR, is to give it a Source Document type of NCABR. This document type is usually reserved for GL postings made by the ABR module itself, and is ignored by the ABR extract.
How can I remove incorrectly extracted GL transactions from ABR?
** These actions are best carried out under the supervision of Nolan Support **
Unfortunately, this is a bit of a 'grey area'. There is no way via the ABR front end to remove unreconciled GL transactions from the Reconcile window. What we usually do in this case is to delete the transactions from the underlying tables.
There are three tables involved (Assuming Dynamics GP v6.00 and above) - the unreconciled GL transactions table (NCABR304), the matched GL transactions table (NCABR012), and the extract keys table which keeps a record of all of the transactions that have been extracted (NCABR201). The approved method is to uniquely identify the transactions that you want to delete in these tables, then delete them.
The only problem with this is that, as we are deleting rows from the extract keys table, the transactions could be potentially be extracted again if the appropriate date range were entered. We could just omit deleting the rows from the keys table, but the next time that an ABR Checklinks is run it will realise that the rows in the keys table refer to transactions which don't exist anywhere else in ABR, and will delete them itself anyway.
Error Message: A remove operation on table NC_Unreconciled_GL_TRX failed
If you receive the error message 'A remove operation on table NC_Unreconciled_GL_TRX failed because record could not be locked' when running an ABR reconcile, this usually indicates that the reconcile has failed for some reason.
Please see the FAQ 'How Do I Back out a Reconcile' for details on how to unreconcile the failed reconcile.
How do I remove unwanted unreconciled transactions?
1. Enter a GL journal with a source document type of GJ between the bank account and a suspense account for an amount which will contra off the unwanted transaction.
2. Enter an equal and opposite journal to 1) above, with a source document type of NCABR. This will not be extracted by the ABR Extract as it ignores transactions with a source document type of NCABR because this is what ABR uses when it is posting reconcile journals.
3. Run an ABR Extract, which will extract the transaction from 1). This can be matched against the unwanted transaction in the ABR Reconcile window and reconciled. There will be no effect on your GL from the journals in 1) and 2) as they are equal and opposite.
Regarding unwanted statement transactions:
You can remove unwanted statement transactions by accessing the statement via the Bank Statement Entry window, highlighting the appropriate statement lines and clicking on Edit >> Delete Row. You will need to adjust the statement ending balance to reflect the new statement total before you are able to save the sta tement.
What does the ABR “Check Links” do?
The ABR Checklinks will perform the following checks on the data and correct anomalies where possible:
1. Check that for every row in the reconciled statement line auxiliary table (NCABR033) there is a matching row in the main reconciled statement line table (NCABR020).
2. Check that for every row in the reconciled GL line auxiliary table (NCABR032) there is a matching row in the main reconciled GL line table (NCABR019).
3. Check that for every row in the unreconciled statement line (NCABR008) and reconciled statement line (NCABR020) tables, there is a header row in the unreconciled statement header (NCABR007) and reconciled statement header (NCABR029) tables.
4. Recalculate the statement starting and ending balances in the unreconciled and reconciled statement header tables (NCABR007 and NCABR029), and update the last statement balance in the last statement number table (NCABR023).
5. If there are any statements which have rows in the unreconciled statement header table (NCABR00 7) but which have no lines in the unreconciled statement line table (NCABR008), remove the orphaned header row.
6. Check that all statement headers have a statement date, if not set the header statement date to the latest date of this statement's lines.
7. Check that each row in the extract keys table (NCABR201) has a matching row either in the unreconciled GL transactions (NCABR304) or reconciled GL transactions (NCABR019 and NCABR032) tables. If it doesn't, then remove the row from the keys table.
8. Check that the totals for each Match Number in the reconciled GL transactions table (NCABR032) and reconciled statement line table (NCABR033) agree. If not then flag an error.
9. Remove all rows from the matched GL transactions table (NCABR012) and matched statement trans action table (NCABR011) so that these tables are rebuilt the next time the Bank ID is entered into the Reconcile window. Be aware that this will cause all match / mark information present when the checklinks is run to be lost.
If I reset the Dynamics GP journal numbers at the beginning of each year, will it cause an issue with Nolan’s Advanced Bank Reconciliation?
Advanced Bank Reconcillation tables contain an index that requires the journal numbers to be unique. Therefore, if the Dynamics GP journal numbers are being reset at the beginning of each year, they will need to be reset using a unique identifier, such as a two (2) digit year at the beginning of the journal number (example: 1000000 for the year
2010, 1100000 for the year 2011, etc)
How do I uninstall ABR?
1. From later releases of v6.00 Nolan’s ABR on SQL onwards, stored procedures are created in EACH company database. If they are present they will need to be removed using MS SQL Enterprise Manager. The stored procedures are:
ncExtractGLTransactions ncUpdateMatchedTable ncReconcile
2. In each client directory, delete the abr.dic dictionary, and, if present, the NCLF2440.dic and NCLR2440.dic modified forms and reports dictionaries. Edit the Microsoft Dynamics GP.set file to remove all references to Nolan’s ABR.
3. Remove all Nolan ABR menu items. These are:
Transactions >> Financial
Bank Statement Entry, ABR Reconcile, ABR Ex.Rate Assign
Routines >> Financial
ABR Extract Trx, ABR Statement Import
Tools >> Setup >> Financial
ABR Import Maint, ABR Import Format, ABR Reconcile Rules, ABR Bank Setup, ABR Extract Setup
Reports >> Financial
Adv. Bank Rec.
Utilities >> Financial
ABR Extract Except, ABR Bank Cleardown, ABR Bank TRX Cleardown
Enquiry >> Financial
ABR Bank Statements, ABR Reconcile, ABR Cheque Enquiry
4. If desired (although this is not strictly necessary), remove all ABR tables from the company databases. These all begin with NCABR.
