Showing posts with label accounting apps. Show all posts
Showing posts with label accounting apps. Show all posts
Thursday, October 22, 2015
Project based businesses - Apps for QuickBooks Online
Do you want to know more about apps for project-based businesses? Check out this article on Apps.com featuring these five awesome apps that work with QuickBooks Online:
Labels:
accounting apps,
accounting automation,
accounting technology,
aero workflow,
billquick,
bqe,
buildertrend,
ecosystem engineering,
mavenlink,
qbo,
quickbooks,
servicem8,
small business
Friday, July 10, 2015
The Artful Engagement - Close More Business with Practice Ignition
If you've been taking advantage of live education over the last 12 months, you have probably seen the adorable astronauts passing out Tam Tam's in the expo halls of many accounting conferences across the globe...
But what do they do?
If you are not familiar with or already using Practice Ignition (PI), let me give you the scoop:
PI is an amazing app that creates and manages proposals/engagements letters and their approvals on a web based platform. Using this app streamlines the time it takes to prep an engagement letter, send it to a client, make potential revisions, get it approved and get paid.
We started using PI about 6 months ago. Prior to using PI we had word templates that we would have to comb and revise, making sure that the client company names were changed everywhere and that dates and services were accurate. We would cut out irrelevant portions depending on the project and add more stuff in where needed. Once an engagement letter was accepted we would collect project deposits and relay the information to team member assigned to the project. IT SUCKED. On top of all that, we had to store the signed engagement letter in client files either in a drawer (yes, those do still exist) or in their folder on the drive.
Since moving over to PI, we simply enter the client, choose our template, assign services and hit SEND. I am able to assign the managing team member so that once the engagement is approved, they can invoice for the deposit through QBO (or we can send an invoice for deposit simultaneously with the engagement, OR we can insert our own custom deposit hyperlinks!).
The potential client received a beautiful, professional engagement proposal that allows them to provide an electronic signature. They love this because it cuts out the step of them printing, signing, and returning. It's so fast! We can even insert hyperlinks to our client portal so that they can begin uploading the documents required from them in the client contributions sections.
Deets on the US Platform:
But what do they do?
If you are not familiar with or already using Practice Ignition (PI), let me give you the scoop:
PI is an amazing app that creates and manages proposals/engagements letters and their approvals on a web based platform. Using this app streamlines the time it takes to prep an engagement letter, send it to a client, make potential revisions, get it approved and get paid.
We started using PI about 6 months ago. Prior to using PI we had word templates that we would have to comb and revise, making sure that the client company names were changed everywhere and that dates and services were accurate. We would cut out irrelevant portions depending on the project and add more stuff in where needed. Once an engagement letter was accepted we would collect project deposits and relay the information to team member assigned to the project. IT SUCKED. On top of all that, we had to store the signed engagement letter in client files either in a drawer (yes, those do still exist) or in their folder on the drive.
Since moving over to PI, we simply enter the client, choose our template, assign services and hit SEND. I am able to assign the managing team member so that once the engagement is approved, they can invoice for the deposit through QBO (or we can send an invoice for deposit simultaneously with the engagement, OR we can insert our own custom deposit hyperlinks!).
The potential client received a beautiful, professional engagement proposal that allows them to provide an electronic signature. They love this because it cuts out the step of them printing, signing, and returning. It's so fast! We can even insert hyperlinks to our client portal so that they can begin uploading the documents required from them in the client contributions sections.
Deets on the US Platform:
- Full disclosure - payment processing within PI is not yet available in the US - but they are expecting to have it rolled out in about 90 days. Use my method of inserting payment hyperlinks or sending an invoice with the proposal
- PI can push invoices over to Xero or QuickBooks Online upon engagement acceptance
- Pricing plans are based on the number of engagements and can fluctuate each month as your proposals scale up and down
- The trial period does not require you to enter your credit card info! SWEET.
- The have an AWESOME website plug in that allows your clients to get real time quotes and submit an engagement request!
- If you're using Xero Practice Manager, a whole new world features opens up to you!
- Available in US, UK, Austraila, Canada and New Zealand. Word on the street is that also have clients in South Africa (where I also hear Sage is about to roll out some cool stuff....)
Want it? Of course you do. Sign up to get started for free, and if you are ready to sign on before August 9th you can enter the discount code MAKEACCOUNTINGFUN for an additional 10% discount on an annual plan, which is already discounted at 20% below the monthly plan! It doesn't get much better than that ;-)
Friday, July 18, 2014
Your Platform Should Be More than just a POS Point of Sale System
And you know what we mean by POS.
Multi-channel sales is the way of the world today.
Multi-channel sales is the way of the world today.
Traditional brick and mortar stores are looking at shopping cart add-ins. Paypal is raking in the dollars with processing fees for businesses who know no other way. Most retail companies sell online or wish that they could, but the industry is not making it easy for them to start, grow and remain compliant.
As a firm that specializes in accounting technology and business processes, we absolutely dread the process of revising systems for clients with multi-channel sales.
We love to help our clients, which is why it so frustrating when you cannot find the right tool to lead your client to growth and success. Many of these businesses need multiple features like an in house POS, a mobile POS, a webstore, and inventory management. Some limitations that we see in many of the current options are:
- Scalability - platforms with all of the features are out of the price range for growing businesses or they are 'overkill'
- Customer Tax Rates - taxibility is a simple yes/no or a stagnant, pre-assigned rate that does not auto-adjust by shipping address
- Sales Tax Reports - reports are too narrow, have to dissect income numbers to categorize the taxable income amounts
- Offline Availability - we are huge advocates of the cloud, but business cannot stop if the internet is down
Your 'industry specificity' could be holding you back. It is awesome to have solutions that are the perfect solution for an industry. But what about everybody else? What about that group of features that don't cater to a specific industry, but cater to almost everyone else? For example, Lettuce is a beautiful system that is great for wholesale and inventory - but they are missing retail customer management. Vend is a lovely solution that we use for brick and mortar stores with multiple locations, but they are limited in shipping and tax management. Lightspeed is a great solution for most everything multi-channel, but their limitations in sales tax are the one thing that prevents me from being able to implement them as the perfect solution.
The biggest problem with today's multi-channel sales systems is that they do not support complex sales tax situations.
Even if you are in one of the 4 states with no local or state sales taxes, it is still very likely that you should be remitting sales tax to somebody, somewhere. Some may say that complex sales tax situations are rare and that those companies should just shell out for an overkill solution to handle their own problem. Anyone who lives in a state with multiple sales tax rates by jurisdiction knows that it is very easy to find yourself in a 'complex' sales tax situation...
There is a very simple answer to improving your multi-channel POS system, and it's called Avalara. Aside from providing an awesome platform that links up with shopping carts, inventory and a local register (preferably iPad with offline availability), you must offer a solution to handle the sales tax complexities that come with multi-channel sales. The financial repercussions of a sales tax audit with a poor tracking system far outweigh any benefits that your solution can offer operationally. I don't care how many bells and whistles your system has, if it cannot survive the most rigid sales tax audit then it has no value to my multi-channel sales clients.
Do you have the perfect solution?
Tell us about it below to tweet to the world @PetersonBizSvcs
Friday, June 20, 2014
Does this App Belong in my Ecosystem?
Yes?
No?
Maybe?
All of the above.
But how do we know? We encounter too many scenarios with our clients where they are looking for a cut and dry response that we cannot provide for them. Just like nearly every other question when it comes to apps, accounting and taxation - it depends.
What does the app do?
We all know the phrase - there's an app for that! But what, exactly, is that? Is your app a time tracker, a payroll add-on with time tracking, a POS, a POS with time tracking, an inventory manager, an inventory manger with POS, an inventory manager with POS and time tracking, blah blah blah? There are a million different things that your app could be capable of, and the first thing that you need to know is exactly what the capabilities and limitations are. Once you know what your app can and cannot do, you can decide on the next question.
What is the app's role in the Ecosystem?
Many of us have taken the term 'Appify' and ran with it. Some of us ran the course, and some have gone off-roading... The biggest problem I see are app stacks instead of app systems (no relation to AppStack mobile site builder). Piling one app on top of another on top of another and so one just creates a huge mess. Many times an app will be integrated and later you find out that it is missing a feature, so you get another add on to fill that need and you end up with a million apps that no one can keep track of. There are plenty of awesome ecosystems that involve a strand of apps working together, and knowing each role and result in depth will help you decide which ones qualify as a system and which ones just make a crap pile.
Stack vs. System
When we are designing an ecosystem for a client, we look at multiple options for each process that requires a solution. A good saying here would be 'if you fail to plan you are planning to fail'. Let's compare two examples of a landscaping company:
A: Implements When I Work with GPS for time, Zen Payroll for processing, and SalesForce for appointments while using QBO for back-end accounting.
B: Implements Jobber for time/appointments/field management and QBO with payroll for back-end accounting.
(If you are not sure which of these is a stack and which is a system, please send me a private email for a consulting session...)
The moral of the story is that both of these examples fill the need, but they are not created equally. You need to know your end goal and choose the apps that work together effectively to make the most streamlined system.
Stack vs. System
When we are designing an ecosystem for a client, we look at multiple options for each process that requires a solution. A good saying here would be 'if you fail to plan you are planning to fail'. Let's compare two examples of a landscaping company:
A: Implements When I Work with GPS for time, Zen Payroll for processing, and SalesForce for appointments while using QBO for back-end accounting.
When I Work > Zen Payroll > QB Online < Sales Force
B: Implements Jobber for time/appointments/field management and QBO with payroll for back-end accounting.
Jobber > < QBO/QBOP
(If you are not sure which of these is a stack and which is a system, please send me a private email for a consulting session...)
The moral of the story is that both of these examples fill the need, but they are not created equally. You need to know your end goal and choose the apps that work together effectively to make the most streamlined system.
How much control do you need/want over the data?
I have overheard waaaay to much whining that all app data needs to 'sync seamlessly into QuickBooks' to be perfect. I say NO WAY!!! One of the BIGGEST benefits I see to appification is that you can choose an app based on its ability to feed information into your back-end accounting system. We all have 'that client' that no matter how much we train them, they will always mess up their books. I love that I have platform options so that I can put 'that guy' on the POS that allows me to look at their beautiful reports and post them as journal entries (rather than automatically sending every erroneous transaction into QB for me to clean out). I believe that the best apps are those that give you options on how you retrieve your data.
What does your data look like once it is in the back-end system?
My answer to this: who cares? As long as it is accurate and not redundant, I prefer ONE posting from the app to summarize the information. Most people ask my why I would not want every transaction to come through... Well, if I wanted every transaction spelled out in QuickBooks then why the heck did I buy the app??? Of course the expectations for import will vary depending the goal you are trying to achieve, and if you have completed the proper ecosystem engineering process then you should be able to assess the part quite simply. Just remember that you are looking for a streamlined system, not a redundant stack.
I have overheard waaaay to much whining that all app data needs to 'sync seamlessly into QuickBooks' to be perfect. I say NO WAY!!! One of the BIGGEST benefits I see to appification is that you can choose an app based on its ability to feed information into your back-end accounting system. We all have 'that client' that no matter how much we train them, they will always mess up their books. I love that I have platform options so that I can put 'that guy' on the POS that allows me to look at their beautiful reports and post them as journal entries (rather than automatically sending every erroneous transaction into QB for me to clean out). I believe that the best apps are those that give you options on how you retrieve your data.
What does your data look like once it is in the back-end system?
My answer to this: who cares? As long as it is accurate and not redundant, I prefer ONE posting from the app to summarize the information. Most people ask my why I would not want every transaction to come through... Well, if I wanted every transaction spelled out in QuickBooks then why the heck did I buy the app??? Of course the expectations for import will vary depending the goal you are trying to achieve, and if you have completed the proper ecosystem engineering process then you should be able to assess the part quite simply. Just remember that you are looking for a streamlined system, not a redundant stack.
Would you be interested in a course on this subject?
Tell us on Twitter @PetersonBizSvcs
The Pro-Apptive Approach to Working with Developers.
I have been hearing a
lot of talk and questions from my peers about apps. What they love and what they
hate, but mostly what they wonder... There is always a question of why... Why don't you have this, why does this do that, why does this import, why doesn't
that export... In my opinion, many of these whys aren't really whys at all,
they are When's. What we really want to know is when will it do this, when
will that fixed, when can I use this app the way I want too? Basically,
we suck at explaining ourselves to developers. I was given some great
opportunities to speak with developers at multiple companies this week. Aside from being able to communicate my ideas to them, I was able to learn how
they need to receive information I order for it to have any value to their
teams.
They don't know what
you're saying because it doesn't make sense.
Draw a picture,
compare a competitor, remind them that you don't speak their language. I am
constantly reminding developers that I have no idea what they have to do on the
back end to make my dream come true, and encourage them to re-direct my
thoughts according to technical feasibility. Most of the time when we are
trying to explain something we are looking at it from a 1-client view or an 'I
want' perspective. The most effective way to validate your suggestion is to
prove that your 'want' adds value not just to you, but to the platform as a
whole. Paint them a picture not just of the what, but also of the why. The how is up to them.
We give input without implementation experience.
Many times we turn
away from a product due to the 'feature lack' that we see in a demo. We may not
implement that product because of one little thing that is missing, therefore our
only experience is the demo. Once we have made the decision NOT to try a
product, we need to accept that since we have absolutely no working experience
with the program, we have no place discrediting it's application. For
example I wanted to integrate Lettuce for a client but I needed a more robust
sales tax module, so I only demoed it. I know of some other industries it would
be great in and I would apply it in a heart beat. The fact that I
implemented Vend instead of Lettuce does not make Vend a better app, it makes
it a better app for that client. We need to quit pretending like every
industry should have a shoe box solution and work on becoming educated
ecosystem engineers.
When you divorce a
vendor, forget the no contact order.
I'm sure ALL of us
have had bad experiences with apps... Spending hours fixing things that we
can't bill for because it was our dumb@$$ that suggested the implementation. I
have divorced many an app (I even took a year off from QBO once), but we need to remember to be civil. You are much better off leaving
amicably so that you can keep yourself educated on any new things that may put that app ahead. We need to forgive developers of their past mistakes so
that we can take advantage of their future triumphs.
Fool me once, shame
on you. Fool me twice, shame on me.
When I demo a product
I usually go in super excited about where I want to use it and the clients
that I'll put on it. By the end of the demo I generally have a huge
paradigm shift and realize that it is not what I thought it was at all. If they
fool you once with their sales rep, email, or misleading advertisement, then
shame on them for not being clear. I always look at this thankfully with a
'crisis-averted' attitude and throw the app in my toolbox for future use. Now
if you choose to implement the product anyway because it's pretty or cheap or whatever,
and it turns out not be the right fit, that is YOUR OWN fault. If you have
demoed a product thoroughly and asked
all of the right questions then there should be nothing that they told you
that you did not verify before implementation. Test Test Test!! It is up to you
to be the expert.
What's your opinion? Feel free to post, tweet or email your thoughts on the matter.
Wednesday, September 18, 2013
Accounting Automation and Online Banking (The good, the bad and the ugly...)
Monday I was reading an article on IntuitiveAccountant.com that was discussing the hope that Intuit got it right with their new bank feeds in QuickBooks 2014. I was intrigued, pleased to learn that they were integrating the same solution from their online product into the desktop solution. I got excited that I would finally be able to link up US Bank accounts to desktop files and that the transaction posting faster would be so much quicker. Sunshine and rainbows are in our future!
Some of the main points in the article were about the ineffectiveness of Web Connect and Direct Connect options. I never liked Direct Connect, it wasn't worth the crazy fees that the banks would charge and I would usually encounter some sort of connection issue. I didn't mind Web Connect, except for when my in-software browser didn't want to download or I accidentally 'over downloaded' transactions (let's be honest, who doesn't have at least one client file with super old duplicates waiting for acceptance in the online banking center?) Then there is batch-entry, a feature that I love to have but hate when I actually have to use it (though that has improved with 2014 as well). For the purpose of this article we will skip that solution ;-).
So what does all of this have to do with the Online Banking solution provided by your bank? Well.... I'm glad you asked!
The Good
What does this have to do with QuickBooks? To be competitive for QB users, banks should offer the Web Connect, Direct Connect and (obviously) the bank feed option. The detailed information that you can pull from online banking enables you to find information and verification for your transactions. Chase has made themselves a prime banking choice for cloud based accounting and QuickBooks users of all editions.
There are other banks that are competitive with Chase's services (Wells Fargo is one), but I have yet to find one that is competitive with the services and fees.
The Bad
There are many smaller banks whose download features are buried and hidden within the banking site and have date restrictions that make the feature useless when doing year end projects. Having continuous feed running all year, even for those you only see once a year, will be a huge time saver at tax time.
The Ugly....
Grrrr.....
If you have already used QuickBooks Online and synced up an account, you know how the acceptance process works. You skim the list, make sure that vendor names on transactions are posting the proper accounts, and accept accept match accept. Woo hoo! Good to go.
So how can this go wrong? What could be so ugly about it? Maybe some of you have experienced this before when syncing up with a smaller bank or credit union:
Name THAT vendor! Now imagine a whole month of this, or even longer with some interval clients. Some of you may be wondering what the big deal is... I'll explain. The 2nd column of the downloaded transactions window has the cute little excerpt that your online banking portal or bank statement would give you. Each institution seems to provide a varying number of characters on this screen, but as you can see all of the debit card transactions from this credit union begin with 'Xx Chk Purch', with the only variation being 'Xx Chk Purck Sig' in some places. Luckily we do have a little 'details' pull down that gives extended information, however the time lost from having pull the details on every card transactions is so significant in some cases that I wish I could just curl up with my Web Connect on QB Desktop.
Some of the other ugly's are bank changeovers. The sync window in QBO is not always updated immediatley with the bank change, preventing access (I've experienced this with the West Coast/Columbia change over recently) and sometimes the login window does not accommodate different account types (for example they will only take a username password when your account type may have a username, business ID and password).
* * *
So how do we avoid the ugly situations?
Pay attention to the services that your clients banks are offering. Even if the individual client is not utilizing all of the services you will have the answer when they (or a new client) may need it.
Build relationships with bankers at various banks and educate them on what works for their bank. One commercial lender I know would tell everyone to use QBO (as their bank did not offer Direct or Web Connect), but we all know that QBO is not the right solution for everyone! This should become less of a problem now that we can get bank feeds in QB Desktop 2014.
Inform and other professionals who influence your clients. Share your knowledge with the attorneys, insurance agents and financial planners in your network so that they can guide your mutual or future clients accordingly.
Share your insight about local national banks below or on one of other sites:
contact@petersonbusinessservices.com
twitter.com/petersonbizsvcs
facebook.com/petersonbusinessservices
Friday, September 6, 2013
Fool-proof(ish) Accounting with QuickBooks Online Apps
Are you tired of your clients screwing things up?
If the answer is no, then congratulations! You have achieved ultimate zen in your practice.
If the answer is yes, then ME TOO!
Many of my clients, contractors specifically, are always on the go. Many small service based companies have busy and slow seasons, which makes it hard to justify having a staff person to handle their accounting needs.
So what do they do? Well, DUH! They do it themselves like any good entrepreneur would! They are business owners ya know, which automatically qualifies them to run every part of their business. IGAAP you say? EFTPS you say? Insert-Acronym-Here, you say? Regardless of how fantastically skilled these business owners are at their chosen trade, they may not necessarily be qualified to man their own accounting department.
Luckily, technology is enabling us to keep a broader perspective on our clients books throughout the month/quarter/year, whereas before we would just have to sort it out at closing time. My personal favorite component to my monthly monitoring plans for service based businesses is the QuickBooks Online app for Iphone (of course there is a Droid app too...)
One of my favorite things about the QuickBooks Online app is the simplicity.
I actually love the fact that it has limited features and does not allow banking access. My clients don't need to be touching their registers from anywhere on their phone; if they want to check their account they can use their online banking app. My clients are told to do TWO simple things from their phone: Enter invoices, and receive payments.
That is literally all that I have many clients doing.
Why just these two things?
Well, because I can figure everything else out for myself! I can download and monitor the accounts from my laptop (though I will be SUPER thrilled when CloudSway has an app ready for account monitoring... that's another blog to come) and I can review all of their documentation at month end. If clients need additional assistance with A/P, I put them on Bill.com and have everything sent into the portal. Oh wait, did I mention that Bill.com syncs beautifully with QuickBooks Online? Yeah, I know, your welcome.
Questions?
Subscribe to:
Posts (Atom)








