You’re offline. This is a read only version of the page.
70
Hello,
I have seen a similar question posted without any real solutions, so I am posting it again. Everything is working with Electronic Reconcile except for the fact that during the import of transactions the leading zero in the check number is being removed. I have confirmed that the leading zero is in the csv. I have tried formatting the check number data column in many different ways. I have tried putting single and double quotes around the number. I have also tried doing all these things and saving the file as a txt document instead of a csv.
I still have not had any luck getting the import to leave the leading zero on the check numbers. This obviously causes issues because none of the check transactions will match up automatically.
An example of a check number is 096442. When importing its 96442.
Any ideas on how to format the data within a csv or txt to ensure the import does not trim the zero? I have searched the PartnerSource knowledge base and the Dynamics Community forums and have not found a solution yet. I am debating creating a script to update the imported data directly in the SQL tables before running the reconcile process.
Thanks!
*This post is locked for comments
I have the same question (0)
Follow-up to my question (solved my own issue). Posting this in case someone else encounters this issue.
-The problem was not due to the leading zeros because Dynamics GP will match up check numbers by ignoring leading zeros. The matching/reconcile issue was due to the fact that the csv file contained check paid amounts that were negative numbers. This causes problems with electronic reconcile. Once updating the check paid amounts to be positive numbers in the csv file and re-running the import, GP was able to reconcile the checks.
Share
Report
All responses (
Answers (
