Our 2012 Roadmap has the public beta release for Quickbooks Desktop and Xero integrations slated as the last week in January.
UPDATE: New beta invites for XERO accounced.
The bad news is that we’re running a few weeks behind, the good news is that we’ve opted for a whole lot more integration fidelity than originally planned. And also the extra few weeks have given us more time to better test and de-bug than we’d normally spend. I know some people have been anxiously waiting for this release, but it is critical we get it right as getting it wrong is potentially catastrophic for a business (!).
This is where it is at…
Xero Integration
The Xero integration provides synchronisation of invoices, payments and contacts. The synchronisation process is configured within WORK[etc] and is optionally setup as either one or two way automated process. In other words, once configured WORK[etc] will communicate with Xero on a scheduled basis to:
- Synchronise WORK[etc] items to Xero
- Synchronise WORK[etc] items from Xero
- Synchronise WORK[etc] items to and from Xero
The configuration of the integration is straightforward and requires the completion of a streamlined authorisation process to enable WORK[etc] to communicate with your Xero account.
Xero integration supports invoice mapping of:
- An associated sales account
- Shipping and discount items
- Tax codes
The integration maintains the high level of granularity provided by WORK[etc]’s invoicing structure. For example, a WORK[etc] invoice synchronised to Xero will have:
- A separate line item for each WORK[etc] line item
- An appropriate tax code if there are applicable taxes for each WORK line item
- A separate line item for each discount item of each WORK line item
- A separate line item for each shipping item of each WORK line item
- Associated line item charges appear sequentially
- A single line item for invoice level discounts
The contact synchronisation process synchronises, name, address and contact details allowing users to be able to quickly invoice new accounts from either system.
Plugin for QuickBooks Desktop
The WORK[etc] Plugin for QuickBooks will offer the import of WORK[etc] invoices and payments from within QuickBooks Desktop. WORK[etc] provides a high level of granularity within its invoicing structure including:
- Support for multiple taxes per line item
- Line item shipping
- Item and invoice level discounts
The WORK[etc] Plugin for QuickBooks maintains this level of granularity for the customer’s convenience and clarity. For example, if your WORK[etc] invoice imported using the plugin will produce the following in QuickBooks:
- A separate line item for each WORK[etc] line item
- A separate line item for each tax item of each WORK line item
- A separate line item for each discount item of each WORK line item
- A separate line item for each shipping item of each WORK line item
- Associated line item charges appear sequentially
- A single line item for invoice level discounts
The plugin has configurable options for mapping shipping, discount and tax to suitable QuickBooks items. In addition, it also supports mapping of the WORK[etc] line item types to generalised item types in QuickBooks. A number of desktop editions of QuickBooks have practical limits on the number of items that can be created and WORK[etc] has endeavoured to design a plugin that works within these bounds so that all users can take advantage of its features.
So when….?
We are still going to be at minimum 10 days from public beta – possibly longer depending on how long it takes for each product to be properly certified by their respective vendors. If you’ve put your hand up for the beta in these previous posts (Xero, Quickbooks) then support will be in touch.
We’ll be starting work on Quickbooks Online immediately after and development time for this will be significantly shorter (as we’ve already resolved all the “gotchas”).
And of course permissions, roles, saved views, sales pipeline and custom fields 2.0 are all teetering on the edge of beta as well.
February is shaping up to be a massive month.
