Skip to content

Andrew

My feedback

1 result found

  1. 2,350 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Andrew commented  · 

    If others haven't seen it Xero have announced a feature in HubDoc that will convert PDF bank statements to CSV - https://www.xero.com/blog/2022/07/import-transaction-data-into-xero/

    This won't be of any use for us, and probably not for a lot of other people on this thread, but it may help some. Interestingly, if enough people use this feature and then get fed up having to manually import the CSV files, it could give fresh impetus for some way to automate that import process (either via the API as we would like, or even something simple like the ability to select multiple files when you're using the manual upload option!)

    An error occurred while saving the comment
    Andrew commented  · 

    +1 for this. For a couple of years now we've had to rely on a routine that generates a CSV file with transaction data from PayPal, Stripe and our Chase Paymentech credit card processor. We then have to manually import and reconcile the CSV files every day.

    You may ask why we don't use the Xero integration with PayPal and Stripe? For the former it's because the PayPal feed is missing crucial information we use to automatically categorise and reconcile the transactions. For the latter it's because everything comes through as Sales Invoices and when we have dozens of transactions a day it's completely unworkable.

    All we need is the ability to be able to POST line item data via the API in the same way as your CSV import routine reads each line of a CSV file. That way we can amend our existing scripts so instead of generating and emailing a CSV to us it could push the data straight into Xero.

    I can't understand why this has taken so long - I know you have a large roadmap but that API functionality would instantly enable you to offer support for pretty much every financial institution out there where Yodlee feeds aren't available or are not reliable. The only reason I can think you haven't done this is if you have pressure from your partners not to make this sort of API publicly available, as it would then undermine the various paid-for commercial solutions people currently have to resort to.

Feedback and Knowledge Base