As of 3/4/2015 – these are the main differences between MethodCRM desktop and Method QBO as far as treatment of tables and processes go..
This document was developed by the Not So West Coast Method Partner group. If you would like more information about this group, please send an email to Fran Reed at Fran@freedupdataoptics.com or Steve Blaustein at firstname.lastname@example.org
Working with Method Classic and QBO
2/9/2015 update 3/4/2015 by Fran
As Intuit pushes more and more clients towards QBO. We would expect to see more and more requests to hook up with Method.Method helps to fill in the gaps where QBO is lacking but there are also lots of other differences that a Method developer needs to be aware of.
We consider the two to be similar, but QBO and QuickBooks desktop are built on different platforms. What’s available for syncing and handling of data is just different. And on top of this, how Method handles can also be different from desktop to QBO version. This guide is intended to outline the differences and to help the Solution Provider with Method QBO projects.
General and very important differences:
QBO and Method do not sync:
- Invoice Lines generated from Time Ticket entries don’t always sync and sometimes not at all … there is an open ticket to resolve this issue
- Purchase Orders – Method issue
- Bills – Method (but its coming) – half built in Method – Bills can now be entered
- Bill Payments – not integrated
- Expenses – not integrated
- Checks – not integrated
- Custom Fields on sales forms – IPP issue (only available on Sales forms anyway)
- Sales Orders concept does not not exist in QBO –
- but there are estimates in ‘plus’
- Estimates do sync
- QBO does not require Items or vendor names but Method does. And this is a bad habit for clients not to enter in Item names or vendor names anyway. QBO allows ‘missing items’ as additional description lines, however, should prohibit entry of rates and quantity, but doesn’t — IPP assumes lines without items are just description and won’t retrieve the remainder of the record
- QBO does not have a concept of SalesRep. To get around this, Method uses an Assigned To Field. This is based on the user logged in, not a Sales Rep list.
Treatment of Names and imports are different. Test out some sample names. Start in QBO then see how syncs to Method. Likewise start in Method and review name in QBO. Then resync to see how “round trip” looks. (sometimes it changes). Confer with Client on whether they want contact name to be “display name” or company name. QBO only requires a first name, Method prefers full name. If first name only present, Method will populate in Last name. Display Name is the required Name field. (fullname is required field in desktop; update name which fills in fullname)
Using Method’s Import Tool for Names:
Customer or Vendor table:
- “Name” is required field. If “blank”, Method will fill in FName and LastName. First Name and Last name need to be included in import. There is no ContactName (concatenated first and Last name) in the entity table as there is in QBD In QBO “Name” field is “display as” field.
- If you wish to populate the Sales Tax code associated with a Customer. QBO allows full text. Method will only allow 3 digit code as in the desktop version. Keep this in mind when setting up new file.
- Street Address is imported into Billing Address1
- Name is contact name, FullName is Customer or Company Name. Primary Contact has a special Type of “Contact” whereas other contacts do not. (Its populated when importing customers).
- ComanyName field is NOT populated for additional contacts.
- Entity is RecordID of “Name”.
- Fullname is required field in Contacts table. This joins it with Customer Table.
- Contact Title is limited to 25 characters.
- ParentRefName is not populated unless add a “Sub Customer”