This one is normally pretty easy to fix, you just... get the debits and credits to equal. But I ran into it today with an Integration Manager integration using eConnect and Analytical Accounting and the fix was not so intuitive.
Exception message: Sql procedure error codes returned: Error Number = 944
Stored Procedure= taGLTransactionHeaderInsert
Error Description = Unbalanced journal entry, the credits do not equal the debits
Node Identifier Parameters: taGLTransactionHeaderInsert
BACHNUMB = BEGBAL JAN14 JRNENTRY = 457 REFRENCE = xx TRXDATE = 1/31/2014 TRXTYPE = 0
<taGLTransactionHeaderInsert>
<BACHNUMB>BEGBAL JAN14</BACHNUMB>
<JRNENTRY>457</JRNENTRY>
<REFRENCE>xxx</REFRENCE>
<TRXDATE>1/31/2014</TRXDATE>
<RVRSNGDT></RVRSNGDT>
<TRXTYPE>0</TRXTYPE>
<SOURCDOC></SOURCDOC>
<NOTETEXT></NOTETEXT>
<Ledger_ID>1</Ledger_ID>
<RequesterTrx>0</RequesterTrx>
</taGLTransactionHeaderInsert>
Stack Trace: at Microsoft.Dynamics.GP.eConnect.EntityMessageProcessor.ExecuteSqlCommands(XElement transactionNode, EntityMessage message) at Microsoft.Dynamics.GP.eConnect.eConnectMethods.ProcessMessageImport(EntityMessage message) at Microsoft.Dynamics.GP.eConnect.eConnectMethods.EntityImportImplementation(String connectionString, String sXML, Boolean isTransaction) at Microsoft.Dynamics.GP.eConnect.eConnectMethods.CreateEntity(String connectionString, String sXML) at Microsoft.Dynamics.GP.eConnect.Service.CreateEntity(String ConnectionString, String sXML)
Exception type: Microsoft.Dynamics.GP.eConnect.eConnectException
Exception message: Error Number = 944
Stored Procedure taGLTransactionHeaderInsert
Error Description = Unbalanced journal entry, the credits do not equal the debits