KB Category: Sage 50 Accounts

Bank account appears in red

There are two reasons why your bank account may appear in red:

• The Balance value is less than the Minimum Limit value.
• The bank account has not refreshed.This article explains how to check or amend the bank account so it no longer appears in red.

1. Bank > select the relevant bank account > Bank Record.

Sage Accounts 2012 and below – Bank > select the relevant bank account > Record.
2. Check that the Balance value is not less than the Minimum Limit value.

If required, increase the value in the Minimum Limit box.
3. Save.

Tip: When you click Save, even if no changes have been made this refreshes the bank account.

Fixing bucket corruption

Within each nominal, customer and supplier record, the monthly values in the Actuals column are called buckets. Bucket corruption occurs when one or more of these bucket values disagree with the total on the record activity for the same period.

A common symptom of nominal bucket corruption is if the debit and credit totals on the trial balance report don’t match.

Fixing bucket corruption

Did you find this video helpful?

To fix bucket corruption

Note: Before you follow these steps, in Help > About you must check when the clear audit trail was last ran. If you’ve cleared the audit trail using a date within the current financial year, the monthly buckets prior to the clear audit trail date will be incorrect after recalculating. In this scenario, print any required reports before you recalculate.

Sage 50 Accounts 2012 (v18) and above

1. File > Maintenance > Yes to close any open windows.
2. Check Data > Recovery Tools > follow the prompts to take a backup of your data > OK.
3. Recalculate Period Values > OK > Close > Close.

Sage 50 Accounts 2011 (v17)

1. Take a backup of the data.
2. File > Maintenance > Recalculate.

Note: Revaluation transactions may be added to the bucket values on rebuild.

Possible causes and best practice

Bucket corruption may be caused by issues including crashes and power failures. There are also some specific causes that you should be aware of:

• Crashing out of the Year End process – The Year End process may take some time to run, during which the Task Manager may show ‘Not Responding’. You should not crash out of the year end routine.
• 3rd party data import – Data imported from third party software may cause bucket corruption. You should check your bucket values are correct after such imports.
• Nominal codes missing from the chart of accounts – Before running the Year End routine it is important to check the chart of accounts to ensure no codes are missing

Aged Creditors does not reconcile to Creditors Control

It’s good practice to reconcile the balance on your Aged Creditors nominal code with an aged creditors report. There may be occasions where the figures do not balance and there are a number of reasons why this may happen. This article is designed to help you to quickly locate and resolve any discrepancies in the figures.

For help with reconciling your aged debtors balance, please refer to article 14319

Go through the detailed steps in order, from Step 1 to 7 to find out why your creditors not balancing:

1. Ensure that you run the correct aged creditors report with the correct criteria
2. Ensure that you run the correct trial balance report with the correct criteria
3. Check for journals posted to the Creditors Control Account nominal code
4. Download and run the Aged Reconciliation reports
5. Run Check Data to check for errors or a warning relating to the purchase aged balance
6. Check for bucket corruption
7. Check for currency corruption

Check for currency corruption (7)

If the currency information in your data is corrupt, this may cause the aged creditors reports to show an incorrect balance.

To check for currency corruption, remove the currency code and currency symbol from the aged report.

1. Suppliers > Reports.

2. Select the Aged Creditors Analysis (Summary) report > Edit.

3. Select the Currency Symbol variable > press Delete.

4. Select the Currency Code variable > press Delete.

5. File > Save As > ensure Save in is My Supplier Reports > Save.

6. Close Report Designer and the Report Browser.

7. Reports > My Supplier Reports > select the Aged Creditors Analysis (Summary) report > Preview.

8. Enter the criteria > OK.

Check for bucket corruption (6)

Bucket corruption occurs when the nominal code bucket values disagree with the total of the activity for the same period.

Sage Instant Accounts, Sage Instant Accounts Plus and Sage 50 Accounts

Run the Nominal Activity report for each month in the current financial year and compare each history balance to the buckets.

Step 1 – Run the Nominal Activity report

1. Nominal codes > Reports > Nominal activity > Nominal Activity.Sage Accounts 2014 (v20) and below – Modules > Nominal Ledger > Reports > Nominal activity > Nominal Activity.
2. In the Criteria, enter the first and last date of the month and do not select the Inc B/Fwd Tran check box.

Step 2 – Check the value in the nominal bucket

1. Nominal codes > double-click the relevant nominal code.Sage Accounts 2014 (v20) and below – Modules > Nominal Ledger > double-click the relevant nominal code.
2. Check the actual figure in the bucket for the required month.

For example, for nominal code 4000, if the Nominal Activity report shows a history balance of £100 in February, but the February bucket shows £50, there is bucket corruption.

Sage 50 Accounts Plus and above

Another way of testing for bucket corruption is to run the transactional management reports. These reports build their figures based on transactions instead of reading the nominal bucket values

To run the transactional reports

1. Nominal codes > Reports > Profit and loss / Balance sheet > Transactional Profit & Loss / Transactional Balance Sheet.Sage Accounts 2014 (v20) and below – Modules > Financials > Reports > Profit and loss / Balance sheet > Transactional Profit & Loss / Transactional Balance Sheet.
2. In the Criteria, enter the first and last date of the month.

For example, run the Profit and Loss report for the month of January 2017 run the Transactional Profit and Loss report entering the date range from 01/01/2017 to 31/01/2017. If the values are different, this indicates bucket corruption.

If running these reports indicates bucket corruption, to resolve this please refer to article 13921.

If there is no difference in these reports click Next.

Click here Continue to (7) or  here to go back to Summary

Run Check Data to check for errors or a warning relating to the purchase aged balance (5)

To run Check Data, File > Maintenance > Check Data.

Errors

Any errors reported may be causing the problem and must be corrected before continuing. For further information about correcting errors, please contact us on 051-395900 or support@pimbrook.ie

Warnings

The only warning which indicates problems with aged creditors is:

‘Purchase Aged Balance disagrees with Creditors Control by (amount)’

The two reasons for this warning are:

• Journals posted to the Creditors Control Account – Step 4 will identify these.
• Link removed transactions – Step 5 will identify these. For further information about link removed transactions, please refer to Ask Sage article 14578. If this warning does not appear, go to step 6.
• If this warning appears, to go to Step 3 click Next.

Click here Continue to (6) or  here to go back to Summary