Docparser est un logiciel web de traitement de documents qui permet aux utilisateurs de récupérer des données bloquées dans des documents PDF. Avec Docparser, les utilisateurs peuvent extraire des champs texte (par exemple, numéro de commande, date, adresse de livraison) et des données tabulaires à partir de documents PDF, et de mettre les données là où elles doivent être. Docparser comprend un certain nombre d'options d'intégration permettant aux utilisateurs d'aller chercher automatiquement des documents chez leur fournisseur de stockage cloud et de copier les données extraites dans leur base de données, leurs feuilles de calcul, leurs systèmes ERP, etc.
Time and money saved by automating the input of sales lead information into our CRM with Salesforce. It's awesome.
The ease of setting up a new document is fantastic. The biggest issue I've had in the past with other services is that it is rarely consistent with the accuracy when parsing the information. I use it to pull information from sales leads that come in by email with a PDF attachment that contains the lead information. My process in the past was to have to manually type the info into a spreadsheet or into my Salesforce account directly; which is very time consuming for my clerical staff.
I've automated this process by having the email automatically forwarded to my Zapier account, then they Zap it to Docparser. Docparser then works their magic and sends it back to Zapier that takes the accurate information and uploads it to my Salesforce and starts the lead followup campaign and notifies me that there is a new lead to contact.
I tried other services in the past, but if there was any variation in the information on the PDF (even one extra space) the information was not accurately parsed. I've set Docparser up and have run 100s of leads through it with 100% accuracy and no need to tweak anything. It is worth every penny and has saved me an absurd amount of time and money spent on paying my staff to manually input the information; not to mention, it allows me to get back to the potential client in a matter of a couple minutes from the initial inquiry time.
Thank you Docparser!
PS - The Customer Support department rocks too. They were very helpful!
time savings. I'm trying to bring a store that was operated for 25 years without an inventory system into a modern age.
I like being able to have multiple document templates as each vendor tends to have their own "take" on what is useful to include in an invoice or order and formatting can vary a great deal.
Therefore, my templates are not based on vendor name - they are based on the data found in the invoices. Example file names: "line-qty-units-isbn13-desc-discount-level-ext-dollar" or "line-qty-desc-unit-ext-float"
Vendors aren't always consistent from invoice to invoice. They may be using software that resizes table columns to fit the text, which means you have to adjust your table format slightly each time to ensure the parsing is correct. That's easy to do.
The forums and Q&A resources are usually helpful and I've found them responsive to email.
1. The UI for making changes to the template. I hate the popup box routine at the end of making a change. It takes a lot of mouse clicks.
2. I've never gotten the subtemplates to work. (see note above about vendor formats being inconsistent.) Subtemplates "supposedly" take care of minor variations and can be grouped according to a vendor name. Maybe this works for other customers, as it is a great idea.
3. There are a lot of little tweaks to be made that aren't obvious to improve character recognition. Why not start with the highest level of quality (ie. turn on OCR) at the start? If that makes file size a problem for storage or performance when processing a lot of files at once, walk people through how to "downgrade" to an acceptable level or establish a recommended number of files not to exceed some size limit. For example, during a trial scan there were no extra spaces or funky characters in the document but then I figured out about half of the "6s" had been transformed to "8s" - not terribly helpful. I want to be able to trust the result rather than having to proof hundreds of line items.
4. Given the inconsistencies I have with the input data sources, I don't think I'll be able to automate the parsing tasks - such as grabbing attachments from email automatically. Again, I have a small business, so I'm OK with the workaround.
I've tried several services now, this got me to where i wanted to go and it works flawlessly with MS Flow or Zapier... so i upgraded and will go full in on DocParser.
DocParser's approach to creating parsing rules has been the BEST fit for what i use it for. Delve fully and explore all the available methods and you'll find a way to extract the data you want.
Sometimes line by line changes take an extra second to save and the pages take an extra second to load, adding to the overall time it takes to set something up. I'm sure speed will improve over time, the product makes up for this shorterm annoyance.
Has a lot of flexibility to identify data that may be displayed in multiple ways using a dictionary of words to detect what you are looking for. DocParser has allowed us to extract data from purchases and put it into a database to analyze for future purchasing needs.
I have nothing bad to say about DocParser thus far. If you think there is a feature that's lacking I suggest browsing their documentation because I learned I was doing a work around for a feature they had already implemented (different layouts under the same parser).
Apart from the ability to parse documents, I am very impressed with the integration tools especially the API that I am using at the moment. I can connect Qlik Sense Desktop directly to Docparser API, and that makes my workflow a lot easier and faster.
I found the Layout Model is a bit confusing. For example in a Layout Model, when I click at "Add Parsing Rule" I am expecting to see a list of parsing rules that I can copy or create a new one.
- User-friendly interface.
- Easy to use.
- Does not require much time to understand the process.
- A lot of integration tools.
- API documentation should have been more example.
- I could not find the way to copy an existing parsing rule into a Layout Model. It would be better to be able to copy and alter an existing one rather than creating from the ground up.
- For a large organisation, it will be quite a lot of parsing rules; it would be nice if I can search or categorise the parsing rules.
Voici quelques-unes des questions fréquentes sur Docparser.
Types de licences disponibles pour Docparser :
À partir de: $19/mois
Type de licence: Abonnement
version d'essai gratuite: Disponible
Nous n'avons pas d'informations sur les fonctionnalités de Docparser.
Utilisateurs habituels du logiciel Docparser :
Auto-entrepreneurs, Grandes entreprises, Entreprises de taille moyenne, PME
Langues dans lesquelles Docparser est disponible :
Types de licences disponibles pour Docparser:
Nous n'avons pas d'informations sur les appareils pris en charge par Docparser.
Applications s'intégrant à Docparser :
Box, Dropbox, Google Docs, Microsoft OneDrive, Salesforce Sales Cloud, Stamplay, Workato, Zapier
Ressources d'aide disponibles pour Docparser :
Support en ligne, Support téléphonique