POS 2.0 Integration with Quickbooks

I am having the same problem with integrating quickbooks with POS 2.0. Whenever I am trying to post to accounting I get an error message that the accounts are not in balance. I can't figure out which accounts are wrong. If anyone can help that would be great!

Reply to
LCBT
Loading thread data ...

Post a batch to quickbooks file and open it with notepad. You should be able to see where the offending transaction is and change your GL mapping accordingly. It can be a little tricky because depending on what accounting method you use some of them may be debit or credit only. There is a KB article on customersource that goes into detail on how to set up the GL mapping. Craig

Reply to
Craig

This is the error message that I get

Batch 1 - QuickBooks error code 3180 - There was an error when saving a General Journal transaction. QuickBooks error message: Transaction not in balance.

It doesn't give me details of what is out of balance. Where is that article you are talk> Post a batch to quickbooks file and open it with notepad. You should be able

Reply to
LCBT

Reply to
LCBT

Check to make sure that all your GL accounts are assigned and have matching QB accounts. In my case the culprit was Layaways - No one told me we were doing them, so I didn't set up the GL or QB accounts to handle them. RMS just threw the $$ into a black hole because it didn't know what to do with it; I had to go back thru the Z report (I think, anyway) to find the missing $ and modify/balance the .iif file for importing.

genesisgroupmont wrote:

Reply to
Jennifer

I've got this same problem A YEAR LATER and there is no way to post the transaction. The trx (per Z report) is actually NOT out of balance and I had to manually enter the data into QB, but this date continues to sit in POS day after day.

I am unclear how we could post, export or edit that data just to get RID of the darn thing!

Is is possible that there once was a way to do that which went away in their updates?

Appreciate any help you can offer - microsoft is just pathetic with supporting this product! ARGH! :)

Reply to
Karyn Stegeman

Just export the offending batch to an iif file and then delete it. Craig

Reply to
Craig

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.