Clearing Account and Liability Account Issues
We recently have had issues with the QuickBooks Online and Expensify connection, in that the journal entries that remove the expenses from the clearing account and the liability account are not being automatically created. These were happening up until November month-end, and we had to manually create journal entries to to clear both accounts at the end of November and December. We have the schedule-submit feature on, which is a requirement for the process to work, but the journal entries are still not being created after the reports are fully approved and synched.
Is this happening to anyone else?
Hey @mparker, thanks for reaching out! This sounds unusual. Can you contact us at [email protected] so that we can take a closer look at a couple of specific reports that aren't creating these journal entries? Thanks!
Hi @Ben Fitz - I contacted them and they've been looking into it for a few weeks now. I was just curious if this was happening to others or if it was unique to our account.
I'm in the exact same situation with the exact same time frame for when the journal entries stopped posting. I've been waiting for an answer from support for a while now too and no response. Please let me know if you hear anything, it's really frustrating posting the journal entries manually.
Hi @mparker and @ChristinaB
Sorry you've been having trouble with this! Our engineers have been working hard to get this issue resolved and I have good news - a fix was implemented for this just a couple of days ago!
Could you please have a look to see if this is now resolved for you? If you continue to run into trouble, just reach out to us on [email protected]
This issue has been resolved. The issue turned out to be that the linkage, or process, between Expensify and QBO is not retroactive. We made the change to Schedule Submit in the first week of December, but the journal entries were not automatically created at December month-end. It wasn't until the end of January that the process worked correctly.
@mparker Thanks for letting us know with that extra context, that's extremely helpful!