Hi all,
bank reconciliation is my nightmare. This time I have a strange case as described in the Question title. Here a screenshot 
How is that possible ?
Thanks,
Gilles
Hi all,
bank reconciliation is my nightmare. This time I have a strange case as described in the Question title. Here a screenshot 
How is that possible ?
Thanks,
Gilles
Ping. DId someone read my question ?
Thanks
Hi Gilles Plante ,
Thanks for reaching out. In Sage 50 Canada ank reconciliations, Discrepancy and Adjustment Required/Unresolved are calculated from different parts of the reconciliation, so they don’t have to match. The Discrepancy typically points to an opening balance / opening outstanding mismatch, while the Unresolved amount relates to what’s needed to bring the ending book and statement figures into alignment.
When you see both values (and they don’t match), it often means something changed in the background (for example: an incorrect GL opening balance, clearing an invalid transaction, or bank reconciliation records that need repair).
Best-practice checks to pinpoint it:
Helpful references:
If you can confirm whether any previously cleared deposits/withdrawals were edited, voided, or re-cleared after a prior reconciliation, the community can help narrow down the most likely culprit.
If this helps, please mark it as verified
Hy Erzsi_I ,
sorry for the long reply. I will check again the reconciliation, thanks for definitions in your first paragraph. I hope I won't have to do point 3.
The 4 links at the bottom of your answer do not work for me. As far as I understand, that means these links would be available only internally to Sage. The one about the rebuild tool is of particular interest.
Have a nice day,
Gilles
The KB articles linked here should be working for you as they are external articles that aren't gated, can you confirm Gilles Plante if they work for you on another device like a mobile phone?
Hi Erzsi_I ,
I just checked a few link, I still have the same issue:
Type Rapport d'exception
message Request header is too large
description La requête envoyée par le client était syntaxiquement incorrecte.
exception
java.lang.IllegalArgumentException: Request header is too large org.apache.coyote.http11.Http11InputBuffer.parseHeaders(Http11InputBuffer.java:602) org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:287) org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63) org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:896) org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1744) org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191) org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) java.base/java.lang.Thread.run(Thread.java:1583)
note La trace complète de la cause mère de cette erreur est disponible dans les fichiers journaux de ce serveur.
*Community Hub is the new name for Sage City