You are here: Home » General » billFLO: an old idea that keeps coming around

billFLO: an old idea that keeps coming around

by Dennis Howlett on April 21, 2009

billFLO wants to take the drudge out of processing invoices between systems by making invoices machine readable. This is an issue that surfaces every now and again but has sop far proven elusive to crack. billFLO makes the claim that:

Vendors simply email computer-readable billFLO invoices to customers who, in turn, use billFLO to instantly import the electronic invoice into their accounting systems.

You have to be very careful reading that claim because it is not ALL accounting systems but the ones with which the company has partnered namely Freshbooks, Harvest, LessAccounting, Blinksale and Quickbooks. The company implies this accounts for some 23 million small businesses (mostly in the US.) I have no way of knowing if that figure is correct although Intuit claims to have 50 million people in its customer orbit across all product lines.

The way it works is that both ’sides’ of the transaction need their version of billFLO (buyer or seller) in order for the system to work. Sellers generate an email to the customer who in turn is able to automate the input, thus avoiding re-keying errors. This is not a new concept but is a welcome move in the on-demand space.

The ideal scenario is where invoices seamlessly flow between buyers and sellers, much as happens with EDI. Ben Kepes at CloudAve uses this as a reason for emphasizing the role OAccounts might play. I have severe doubts whether the industry will plough that particular furrow. All past attempts have failed because a single data standard at the transaction level renders all vendors vulnerable to fast switching between applications.

However, getting the bills between systems is barely half the battle. Invoices still need checking for correctness. Without a corresponding automated purchase order system, that’s nigh on impossible.So while billFLO is tilting at the problem from the time savings perspective, I wonder just how much total processing time is really saved.

A much bigger win occurs when businesses are able to automate the handling of bank transactions. Xero has done a lot of that work for the NZ market. I believe they got a bit of a shock when they turned up in the UK and found out how disparate the file formats for the UK banks turned out to be. Or rather how relatively tough data exchange in the UK can be.

Even so, billFLO should be commended for endeavouring to fill a need,especially as it is acting in a vendor neutral capacity. The claim that:

Each year nearly 20 billion paper invoices are exchanged between businesses at the price of nearly $30 billion in lost productivity. billFLO completely eliminates paper invoices by electronically connecting both the vendor and customer accounting systems.

…seems reasonable. I deal with many organizations and the amount of legwork needed to get invoices in and out of systems is horrendous. As Sunir Shah at Freshbooks says:

I believe that sooner or later all invoices will be machine readable, but I’d prefer sooner.

Amen to that.

Reblog this post [with Zemanta]
GD Star Rating
loading...
GD Star Rating
loading...
  • Share/Bookmark
  • We're working on OCR technology which reads standard invoices. The obvious advantage being that you don't need to force a standard invoice format, simply scan paper invoices or have your supplier send their invoices directly into your accounting system inbox as an image.

    The OCR technology usually needs a little training on the first invoice from each supplier, but after that it's able to process future invoices from the same supplier automatically. The training part can be accomplished by the bookkeeper.

    The outcome of all training is stored in a central knowledge base of all suppliers, which in SaaS terms means everyone who's using the same accounting software, so that the system quickly builds up an extensive set of definitions covering the most common supplier invoices.
  • An electronic standard is a great ideal, but most SME's will continue to receive paper or paper-based image invoices for the forseeable future, hence our focus on getting OCR to work. It really streamlines the processing and approval of supplier invoices.

    Eliminating paper is a key part of this - ideally, the invoices will be received as images, but even if they are sent in paper form the paper copy can be destroyed once it has been scanned and uploaded to the accounting system.
  • "the paper copy can be destroyed once it has been scanned and uploaded to the accounting system."

    People with a fine paranoia of audits simply won't do that.... ;)
  • @mark - you're making the erroneous assumption that most SME's will not see the value in on-demand options that allow electronic file creation and transmission. It's already happening. Of course the Sage die-hards are going to be with us for a while but they will fade away. Far better to offer a slicker method of operating from the get go and especially in challenging times?
  • @Dennis - No such assumption on my part. We already support fully-electronic invoices in Scandinavia and will do in other geographies too. It's my feeling that OCR is still a worthwhile investment of development resources because of the vast number of companies/bookkeepers who will continue to deal with invoices for some time to come.
  • Mark,

    billFLO supports OCR of pdf's as well. We believe there is a place for OCR but frankly, it doesnt make sense in the long run. Why use paper as the interface between systems that are already electronic?

    That said, from e-conomic's perspective, I woud think it makes sense to support as many ways as possible to get the data into the system.

    Ian
  • The problem with OCR is that it can be error prone but I've not seen comparative stats comparing machine to machine and OCR so not sure what the comparative error rates look like. Even so, I wouldn't be a fan of OCR unless I could dispense with paper along the way. I've not had a printer for 3+ years :)
  • [oops, posted this on EI site - should have posted here first!]

    Dennis,

    you've honed in on some important points. As you say, there's more to the life of an invoice than getting the invoice data to the other side. There's the aggregation of the data that goes into the data on the seller side, and the review-approve-reconcile cycle that needs to happen on the receivers side. There are many great tools out there for those needs (Aggregation: Harvest,Freshbooks, Timeslips, etc. Approval:bill.com, beanbills, etc)
    We made a conscious effort not to do that and to focus on eliminating the manual handling and data entry, i.e. bridging the accounting systems of the buyer and seller. So you're absolutely right when you say we're the Switzerland (although I prefer to say Ireland!) in that we're neutral. We'll get the data there so you can use your choice of system to run you business.

    thanks
    Ian Sweeney
    CEO, Anoowa Inc, Developers of billFLO

    P.S. @Martyn: I'm told the industry term for when your big vendor or supplier says you have to use their EDI is... the "EDI Bomb"!
  • Martyn Shiner
    Dennis,

    I like the comment

    "The ideal scenario is where invoices seamlessly flow between buyers and sellers, much as happens with EDI"

    I have direct experience of this - and 'seamlessly' is not a word I would use to describe EDI - nightmare more like!

    Martyn
  • Think how much more deliciously straightforward the audit work would be too.

    I recall sitting in a cramped cell reviewing invoices. Oh what joy it was to flee.
blog comments powered by Disqus

Previous post:

Next post: