Ebillity Time Tracker no syncing with 2018 RAH

  • 2
  • Problem
  • Updated 3 months ago
  • Solved
Is anyone else having trouble syncing timesheets with Time Tracker from Ebillity with the new Reckon Accounts Hosted 2018.

My timesheets were syncing immediately before changing from 2017 to 2018 RAH and now will not sync.

Is this an API update issue as a result of the new software?
Photo of Anthony

Anthony

  • 268 Points 250 badge 2x thumb
  • frustrated

Posted 3 months ago

  • 2
Photo of Anthony

Anthony

  • 268 Points 250 badge 2x thumb
....and I need them to run payroll on Monday 2 July!!!!!!!!!
Photo of Don Froude

Don Froude

  • 140 Points 100 badge 2x thumb
mate this is out of control
I havent updated to the new one yet but at no stage can i afford for this to no sync
let me know if you get thru it please

this has cost me a fortune in money and time having this not working and or accessable
Photo of Anthony

Anthony

  • 268 Points 250 badge 2x thumb
FYI below
Photo of Anthony

Anthony

  • 268 Points 250 badge 2x thumb
Have been dealing with support from ebillity for 5 hours on Fri arvo and testing more this Sunday afternoon. No luck - nothing has changed from their end so it shouldn't be their issue. 

I called Reckon on Friday for support and after a 24 min hold all they told me to do was ask Ebillity to email a random reckon API email address.

What a crock. 
Photo of Anthony

Anthony

  • 268 Points 250 badge 2x thumb
Hi Jason

I've just had someone manually enter all 24 of them this morning. Could you please shoot through the template just in case we need it for today's timesheets?

Thanks
Anthony
Photo of Jason Hollis

Jason Hollis, Head of Product

  • 9,434 Points 5k badge 2x thumb

HERE is the import file for timesheets into Reckon Accounts (IIF – Intuit Interchange Format). 

From the screenshots below you should be able to determine how the import interacts with the UI. Time data is then used to populate the pay data to create a pay for an employee).

Non-billable


Billable


Notes:

  • Always backup your file before performing an IIF import.
  • Date must be in US date format (see example).
  • If you are not billing your time, then there is no requirement for Customer:Job or indeed Service Item.
  • You can bill a customer (on its own) or job, however if billing a job you need to use the format CUSTOMER:JOB as a job is really a child of the customer.
  • Of course you would need to ensure the same items (data) with the same names exist in your company file.
Photo of Anthony

Anthony

  • 268 Points 250 badge 2x thumb
HI Jason

What is the latest on this? The IIF function is what we previously used and was the reason we switched to eBillity. eBillity have not come back to me overnight at all. 

Really need to get this fixed as it is costing the business money to have someone manually do all staff timesheets.

Thanks
Anthony
Photo of Jason Hollis

Jason Hollis, Head of Product

  • 9,434 Points 5k badge 2x thumb
Hi Anthony. That was a short-term solution only. eBillity have fixed so just confirming with them the expected release time. 
Photo of Anthony

Anthony

  • 268 Points 250 badge 2x thumb
Hi Jason

Is there an update on this?

Thanks
Anthony
Photo of Jason Hollis

Jason Hollis, Head of Product

  • 9,434 Points 5k badge 2x thumb
UPDATE

eBillity have confirmed the update has been released and the application is working as expected.  The team at eBillity have advised to review their set-up to make any changes to your login that may be required. 

The primary change Reckon made to the API was to ensure the company file (QBW) had a dedicated user created for the API (that wasn't Admin). This user should have FULL ACCESS rights. We recommend naming the user the same as the integrated application. In this case, ebillity

In Reckon Accounts Hosted go to Company > Users > Set Up Users & Roles...

Notes
  • The user name is case sensitive therefore must be the same in both Reckon Accounts Hosted and the integrated application.
  • You must use a password for the new user in the company file.
Photo of Jason Hollis

Jason Hollis, Head of Product

  • 9,434 Points 5k badge 2x thumb
IMPORTANT NOTE

Although we work closely with 3rd-party developers when there is a connection issue between products, the responsibility does lie with the 3rd-party to ensure their connection functions as expected.

In this case the issue was not caused by the release of Accounts Hosted 2018 R2, but a change to the Hosted API that was communicated to all developer partners mid-June. 

That said, eBillity have been fantastic and responded very quickly when it was released the integration was effected by these changes, so I thank the team for their responsiveness. 

Again I apologise for any inconvenience on their behalf, and we'll continue to test the connection at both ends to ensure continued connectivity. 

This conversation is no longer open for comments or replies.