Trial Balance & CSV Files | AccountingWEB

Trial Balance & CSV Files

(1)I am using Sage 50 Version 14. The Trial Balance is out of balance by 3,000,000.00. Sage only posted 3,000,000.00 on the debit side nothing on credit. I run Error Checking in the maintenance and gave me all sorts of errors :AMOUNT PAID IN HEADER 18511 DISAGREES WITH AMOUNT PAID IN SPLITS, SPLIT TRANSACTION 27765 IS CROSS LINKED

(2) I have exported the Transaction CSV to Excel so that I should get rid of the 3,000,000-00 above and recreate a new set of Sage company file with no transaction and import the CSV file. I can't see the transaction types SR and PP. 


Data Corruption

johndon68 | | Permalink

1. You have data corruption which, based on the error that you detail is almost certainly the reason why the trial balance does not balance.

2. The standard transaction CSV report does not, by default, export SR, PP, SD and PD and this is because the import routine cannot import those types of transaction.

You have a couple of choices:

1. Import the file as it stands and then manually reenter any transactions that were not exported.

2. It is possible to edit the CSV report to remove the filter which will then allow for those 4 transaction types to be exported.  If you do this there are a couple of things that you need to be aware of - as I mentioned, the import routine cannot handle the import of those transactions so, once created the CSV file would need to be edited as follows:

Change SR to SA

Change PP to PA

Change SD to SC

Change PD to PC

This will allow for the transactions to be imported but you then have to be aware of the following:

None of the SA, PA, SC or PC transactions will automatically be allocated to the invoices that they originally paid so this has to be done manually.  Also, the import routine does not 'group' transactions in the same way as the program itself does.  So, for example, if you enter two invoice lines in Sage with the same date and reference, they will be grouped as a single header - the import routine does not do this so you end up with two seperate transactions.

An alternative to doing all of this would be to look at getting the data fixed - this can be done for far less and, generally, quicker than Sage can do it for you...

Hope this helps...


Add comment
Log in or register to post comments