We gave up on expecting Beanworks' staff properly read and input invoice details within a few months of starting. Our Controller assigns all the invoice dates (we record in batches: It's always the 6th of the month. Simple.), and frequently inputs the dollar amounts, too. Sales taxes seem beyond Beanworks' staffs' comprehension.
Seemingly arbitrary aspects of the UI impair usability without serving any apparent purpose, and lead to more printing: Column widths are based on a percentage of window size (rather than being defined by a number of pixels, such as in excel). This means that I must view Beanworks in a maximized browser window if I want to read anything in the columns (things like Vendor Name, Invoice Number, or Invoice Amount). This becomes an issue when I need to compare, for instance, all the invoices processed in a time-range, with all the invoices I've captured in a report. I end up having to print the other list out in hardcopy, rather than having Beanworks on one half of my fairly large monitor, and whatever I'm working on on the other.
Processing time for EFT payments so far has been ~5 business days, which seems unreasonably long.
More than one of our vendors in receipt of physical cheques produced by by Beanworks payment solutions have let us know they almost threw out the cheque because it didn't have any identifying marks on it, and they thought it was junk. Cheques themselves all say "Powered by Beanworks" in the memo field, depriving us of a meaningful information source for our bank records and complicating our bank reconciliations. We are required to note certain identifying numbers/comments on some payments, and I just can't do that with Beanworks' cheques.
If a payment is important, I write a manual cheque.
These things don't negate Beanworks' value, but they do require work-arounds and added scrutiny.