Simon Clive at 04:50, 8 November 2011

2011-11-08T04:50:23Z

Simon Clive: Created page with "Checking Balances Why do you need to check your balances? On very rare occassions your MySQL tables can get data corruption. These can be caused by any number of reasons from p..."

2011-06-28T00:12:55Z

Created page with "Checking Balances Why do you need to check your balances? On very rare occassions your MySQL tables can get data corruption. These can be caused by any number of reasons from p..."

New page

Checking Balances

Why do you need to check your balances?

On very rare occassions your MySQL tables can get data corruption. These can be caused by any number of reasons
from power surges to simple account set-up issues.

It is always a good idea, that on a monthly basis to confirm that all of your data is sound and has posted correctly
without corruption.

A quick and easy way of confirming this is to simply open your balance sheet and confirm that your assets total, matchs
your liabilities total. Your balance sheet forms the basis of every report, so if this balances, then every thing else will
balance correctly.

Should this not balance, then move the date backwards until you get to the date on the balance sheet, that it does
balance. ie open the date drop down on the report, change the month, backwards by a month and re-check the
assets total to your liabilities total. Once you have the faultly month, then alter the days until it again balances.

Once you know the date, open the "Transaction Journal' report, on that date and filter on the transaction types until you find
which type of transaction is causing the in-balance. ie filter on all invoices and confirm that the totals at the bottom
of the report match.

Once you know the types, filter on these by transaction number until you find the out of balance transaction, then simply
delete the transaction and re-enter it.

@@ Line 1: / Line 1: @@
-Checking Balances
+'''Checking Balances'''
 Why do you need to check your balances?
-On very rare occassions your MySQL tables can get data corruption. These can be caused by any number of reasons
+On very rare occassions your '''MySQL tables''' can get data corruption. These can be caused by any number of reasons from power surges to simple account set-up issues.
 from power surges to simple account set-up issues.
-It is always a good idea, that on a monthly basis to confirm that all of your data is sound and has posted correctly
+It is always a good idea, that on a '''Monthly''' basis to confirm that all of your data is sound and has posted correctly without corruption.
 without corruption.
-A quick and easy way of confirming this is to simply open your balance sheet and confirm that your assets total, matchs
+A quick and easy way of confirming this is to simply open your '''Balance Sheet''' and confirm that your '''Assets''' total, matches your '''Liabilities''' total. Your '''Balance Sheet''' forms the basis of every report, so if this balances, then every thing else will balance correctly.
-your liabilities total. Your balance sheet forms the basis of every report, so if this balances, then every thing else will
 balance correctly.
-Should this not balance, then move the date backwards until you get to the date on the balance sheet, that it does
+Should this '''Not Balance''', then move the date backwards until you get to the date on the '''Balance Sheet''', that it '''Does Balance'''. ie open the date drop down on the report, change the month, backwards by a month and re-check the assets total to your liabilities total. Once you have the faultly month, then alter the days until it again balances.
-balance. ie open the date drop down on the report, change the month, backwards by a month and re-check the
 assets total to your liabilities total. Once you have the faultly month, then alter the days until it again balances.
-Once you know the date, open the "Transaction Journal' report, on that date and filter on the transaction types until you find
+Once you know the date, open the '''"Transaction Journal'''' report, on that date and filter on the transaction types until you find which type of transaction is causing the in-balance. ie filter on all invoices and confirm that the totals at the bottom of the report match.
 which type of transaction is causing the in-balance. ie filter on all invoices and confirm that the totals at the bottom
 of the report match.
-Once you know the types, filter on these by transaction number until you find the out of balance transaction, then simply
+Once you know the types, filter on these by transaction number until you find the out of balance transaction, then simply '''Delete '''the '''Transaction''' and '''Re-Enter''' it.
-delete the transaction and re-enter it.

12 Checking Balances - Revision history

Simon Clive at 04:50, 8 November 2011

Simon Clive: Created page with "Checking Balances Why do you need to check your balances? On very rare occassions your MySQL tables can get data corruption. These can be caused by any number of reasons from p..."