eInvoicing with Timing Billing/Activity Slips

Hello,

I'm hoping to get some advice from the community regarding an invoicing issue we're facing with MYOB AccountRight Plus. For the past few years, we've been using the Time Billing function - specifically the Activity Slips feature - to track our staff's monthly hours with clients. After entering the hours for each staff member against the relevant activity, we generate the invoice automatically using MYOB's standard functionality. This process helps us generate invoices on our custom templates while also giving us the ability to report on individual staff hours through activities, which is a key part of our business.

Now, we're in the process of transitioning to eInvoicing with a client who requires compliance with the PEPPOL standard. However, after exploring this functionality, we've found that eInvoicing is only available in the web version of MYOB, not the client/desktop version. While this isn't a dealbreaker, we've run into an issue: the web version doesn't support time billing or activity tracking, which is essential for us.

In the web version, we would have to manually configure a template and enter individual line items for each staff member and their hours. While we can save these eInvoices for reuse in the future, this doesn't allow us to track the hours against activities, which is crucial for our reporting.

We would love to see time billing and activity tracking integrated into the web version, but we understand that's not currently possible. So, we're looking for a workaround. We've had an idea to create the eInvoice in the web version while entering the staff hours against activities in the client version. The downside is that this would result in multiple pending invoices in the client version. Is there a way to cancel these pending invoices while still retaining the activity records for reporting?

We'd appreciate any suggestions or guidance from others who have faced a similar challenge. We've already reached out to MYOB support, but they weren't able to offer a viable workaround. We'd be grateful for any advice or tips from the community on how best to handle this.

Thanks so much for your time and help - we look forward to your thoughts!

Regards - Chris