Need more, need help now?
- - - - - - - - - - - - - - - - - - pay-as-you-go support - no contract - tenth of an hour billing - expert help - fast service - no call queues
Need integration?
- - - - - - - - - - - - - - - - - - with your shipping system - website - invoicing system - crm - cms - manufacturing - order import - back to back orders..
Need a report?
- - - - - - - - - - - - - - - - - - Excel reporting that pulls data from Sage - custom layouts - layouts that change adapt to your brands and/or for drop shipping.
Want web hosting?
- - - - - - - - - - - - - - - - - - Your own domain name - email - a shop - wordpress - woo commerce - ticket systems - help desks - forums - portals
- - - - - - - - - - - - - - - - - - pay-as-you-go support - no contract - tenth of an hour billing - expert help - fast service - no call queues
Need integration?
- - - - - - - - - - - - - - - - - - with your shipping system - website - invoicing system - crm - cms - manufacturing - order import - back to back orders..
Need a report?
- - - - - - - - - - - - - - - - - - Excel reporting that pulls data from Sage - custom layouts - layouts that change adapt to your brands and/or for drop shipping.
Want web hosting?
- - - - - - - - - - - - - - - - - - Your own domain name - email - a shop - wordpress - woo commerce - ticket systems - help desks - forums - portals
MISMATCH WITH HEADER TRANSACTION
MISMATCH WITH HEADER TRANSACTION
I have some problems with my sage 50 accounts, although monthly invoices have been posted and appear on the account they are not coming up on the statement - when checking for errors I have mismatched with header transaction on multiple transactions that are split and not linked to ledgers - any help gratefully received
-
- User
- Posts: 132
- Joined: 14 Apr 2011, 18:02
- Sage Version: v2014 20 UK/Europe/Africa
Re: MISMATCH WITH HEADER TRANSACTION
It means that you have data corruption. You can try the following:
1. Take a backup.
2. Run the Clear Audit Trail routine with a date of 01/01/1980.
3. In File -> Maintenance, run both ReIndex and Compress.
4. Run Check Data again.
If you still have errors, you have the following choices:
1. Restore a clean backup that has no errors albeit any data entered since then will need to be reentered.
2. Send the data to Sage to fix - potentially expensive and you could be without your data for 4-5 days unless you pay a huge amount (up to around £800+VAT) for an overnight fix.
3. Send the data to a Sage Developer who offers a Data Fixing service which is generally cheaper and quicker than sending it to Sage. Bruce who runs this site offers such a service as does at least one other person I can think of
John
1. Take a backup.
2. Run the Clear Audit Trail routine with a date of 01/01/1980.
3. In File -> Maintenance, run both ReIndex and Compress.
4. Run Check Data again.
If you still have errors, you have the following choices:
1. Restore a clean backup that has no errors albeit any data entered since then will need to be reentered.
2. Send the data to Sage to fix - potentially expensive and you could be without your data for 4-5 days unless you pay a huge amount (up to around £800+VAT) for an overnight fix.
3. Send the data to a Sage Developer who offers a Data Fixing service which is generally cheaper and quicker than sending it to Sage. Bruce who runs this site offers such a service as does at least one other person I can think of

John
Last edited by leyburnsolutions on 02 Sep 2011, 14:07, edited 1 time in total.
Re: MISMATCH WITH HEADER TRANSACTION
Many thanks John, I will give it a go.
- brucedenney
- Site Admin
- Posts: 4664
- Joined: 28 Feb 2006, 09:56
- Sage Version: v30 UK/Europe/Africa
Re: MISMATCH WITH HEADER TRANSACTION
I think that you will find that once transactions are mismatched there is not a lot that can be done at the user end to match them up again.
Indeed a data repair would not match them up it would only remove them, and you would have to rekey them.
I have seen data with thousands of mismatches where the data just is not there to be recovered. Bacuk before doing any fix, because fix can make things worse.
Indeed a data repair would not match them up it would only remove them, and you would have to rekey them.
I have seen data with thousands of mismatches where the data just is not there to be recovered. Bacuk before doing any fix, because fix can make things worse.
For just about anything Sage :- Discount subscriptions, pay-as-you-go support, application integration, reports, layouts, linked excel spreadsheets, analysis or any other help making life with sage easier/less time consuming Contact me.
Who is online
Users browsing this forum: No registered users and 3 guests