<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Ideas for Parseur</title>
  <subtitle>Ideas for Parseur as submitted to our Feature Upvote board. Ideas are ordered by 'new' and the 50 top matches are included.</subtitle>
  <link href="https://feedback.parseur.com"/>
  <id>pr_9jhc9h3zxoxobnc</id>
  <updated>2025-11-18T16:13:25Z</updated>
  <entry>
    <title>Add data analysis and data visualization</title>
    <link href="https://feedback.parseur.com/suggestions/709104/add-data-analysis-and-data-visualization"/>
    <id>sug_wigv6bc72gd0pbj</id>
    <published>2026-04-27T14:23:02Z</published>
    <updated>2026-05-01T07:37:07Z</updated>
    <content type="text/plain">We’re exploring a new set of features to help you better work with the data extracted from your Parseur mailboxes, including tools to explore, analyze, and visualize your data.&#13;
&#13;
Some potential use cases:&#13;
&#13;
* Ask Parseur AI questions about your extracted data: for example, when was the last payment date for customer Acme Inc.&#13;
* Summarize and analyze data (for example, from a mailbox of invoices: identify your top 5 customers, calculate total spend per customer or per country, etc.)&#13;
* Create charts to visualize your data (for example, total expense amount per month over the past 12 months)&#13;
* Export results as CSV, Markdown, images, or PDF&#13;
&#13;
Since this is a significant addition, we want to gauge interest and better understand how you would use it. This will help us build something genuinely useful.&#13;
&#13;
If this sounds relevant, please share your use case in the comments or reach out via chat if you’d like to be considered for beta testing.</content>
  </entry>
  <entry>
    <title>Send emails with parsed data</title>
    <link href="https://feedback.parseur.com/suggestions/714787/send-emails-with-parsed-data"/>
    <id>sug_iwrm4eirdsclrbw</id>
    <published>2026-06-02T19:04:33Z</published>
    <updated>2026-06-02T19:04:33Z</updated>
    <content type="text/plain">Offer the ability to automate sending emails with data parsed from imported documents. This is currently only possible by sending parsed data to one of our connected workflow platforms like Zapier: https://zapier.com/apps/parseur/integrations/smtp</content>
  </entry>
  <entry>
    <title>Offer dictionary upload to function as reference and allow lookup</title>
    <link href="https://feedback.parseur.com/suggestions/713073/offer-dictionary-upload-to-function-as-reference-and-allow-lookup"/>
    <id>sug_str3m7iccpbu9wu</id>
    <published>2026-05-21T17:43:52Z</published>
    <updated>2026-05-21T17:43:51Z</updated>
    <content type="text/plain">A feature where a user would upload a CSV with a list of their suppliers / orders / customers / product numbers / part numbers and then do lookup on it. &#13;
&#13;
Example:&#13;
&#13;
1. User parses supplier invoices&#13;
2. They extract the supplier name from each invoice&#13;
3. For each invoice, they need to also extract their internal Supplier ID so that when they send the webhook on the other end, their system knows which ID to use to upload the data in their database&#13;
4. So a user could upload a CSV with a supplier_name and supplier_id columns then whenever they extract the name, we would use that CSV, search for the name extracted and retrieve the id</content>
  </entry>
  <entry>
    <title>Automatic Re-process when missing fields</title>
    <link href="https://feedback.parseur.com/suggestions/711736/automatic-reprocess-when-missing-fields"/>
    <id>sug_pqpj8pyrc289vv7</id>
    <published>2026-05-13T09:51:33Z</published>
    <updated>2026-05-13T09:51:33Z</updated>
    <content type="text/plain">Sometimes the AI Engine failes to find an obvious pdf field altough OCR seems to have scanned it. After a couple of reprocesses it manages to find it. So i suggest automatically reprocessing a Process failed (missing field) document for something like 5 times, depending on the setting. Maybe even use a credit for an automatic reprocess.</content>
  </entry>
  <entry>
    <title>Upload lists of reference for choice mapping and data validation</title>
    <link href="https://feedback.parseur.com/suggestions/711394/upload-lists-of-reference-for-choice-mapping-and-data-validation"/>
    <id>sug_zncgik2edkep9eg</id>
    <published>2026-05-11T11:32:17Z</published>
    <updated>2026-05-11T11:32:16Z</updated>
    <content type="text/plain">Let users upload excel or CSV of data in order to:&#13;
1. Use it as a data source for accepted choice fields&#13;
2. Use it for mapping values. E.g. search extracted value in column "Customer Name" and, if found, return corresponding value from column "Customer ID" &#13;
3. Perform additional search and validation in Post Processing</content>
  </entry>
  <entry>
    <title>Selecting specific documents to export into one file.</title>
    <link href="https://feedback.parseur.com/suggestions/708316/selecting-specific-documents-to-export-into-one-file"/>
    <id>sug_n7oi7oaymqaba4x</id>
    <published>2026-04-23T11:03:26Z</published>
    <updated>2026-04-23T11:03:26Z</updated>
    <content type="text/plain">When i select a few documents and procceed to click on download data, I end up getting all the documents importered  into the excel-file. Sometimes i have a specific documents ( still a larg amount)  i want to export but they're spreaded over several days so the option to select a date or month is not practical in this case.</content>
  </entry>
  <entry>
    <title>Offer a quota check via the API</title>
    <link href="https://feedback.parseur.com/suggestions/707200/offer-a-quota-check-via-the-api"/>
    <id>sug_zja0utmgw65cf2e</id>
    <published>2026-04-17T14:25:15Z</published>
    <updated>2026-04-17T14:25:14Z</updated>
    <content type="text/plain">Currently there is no way to poll the API for how many credits are left during my quota, I have to log in to see this.&#13;
&#13;
I'd like to monitor it programmatically to trigger alerts before hitting the quota, rather than relying on the 90% email notification.</content>
  </entry>
  <entry>
    <title>Please add a column for page count in each document on the Documents screen.</title>
    <link href="https://feedback.parseur.com/suggestions/701706/please-add-a-column-for-page-count-in-each-document-on-the-documents-screen"/>
    <id>sug_xw6yzfp2nmnccut</id>
    <published>2026-03-18T14:57:59Z</published>
    <updated>2026-03-18T14:57:59Z</updated>
    <content type="text/plain">There is plenty of space for an extra column to display the page count for each document on the Documents screen. This will be helpful for users who need to split documents after uploading said document when there are variable # of pages for document files.</content>
  </entry>
  <entry>
    <title>Add show/hide labels toggle in Export options</title>
    <link href="https://feedback.parseur.com/suggestions/701551/add-showhide-labels-toggle-in-export-options"/>
    <id>sug_nz5a96bnemberoa</id>
    <published>2026-03-17T18:39:00Z</published>
    <updated>2026-03-17T18:39:00Z</updated>
    <content type="text/plain">Some software requires there be no header row when manually importing XLS/CSV files. It would be nice to have the option for the download to include just the raw data with no header.</content>
  </entry>
  <entry>
    <title>Ability to organize mailboxes into folders</title>
    <link href="https://feedback.parseur.com/suggestions/701523/ability-to-organize-mailboxes-into-folders"/>
    <id>sug_lnymuynbso7l4ag</id>
    <published>2026-03-17T16:10:58Z</published>
    <updated>2026-03-17T16:10:58Z</updated>
    <content type="text/plain">I would love it if I could organize my mailboxes into folders. I am going on to 22 mailboxes, using Parseur for multiple departments of the company I work for. If I could organize those mailboxes into folders, it would make my Parseur significantly more organized.</content>
  </entry>
  <entry>
    <title>Accept HEIC</title>
    <link href="https://feedback.parseur.com/suggestions/700454/accept-heic"/>
    <id>sug_guj7yomie7k0byk</id>
    <published>2026-03-12T01:18:14Z</published>
    <updated>2026-03-12T01:18:13Z</updated>
    <content type="text/plain">The AI importer works with JPG etc but doesn't accept HEIC which is the iOS default format for images captured on iPhone etc. Can the AI importer accept HEIC and potentially convert to JPG on the fly, so that users can email images from iPhone without requiring them to convert/change settings.</content>
  </entry>
  <entry>
    <title>Add PDF Portfolio file support</title>
    <link href="https://feedback.parseur.com/suggestions/699989/add-pdf-portfolio-file-support"/>
    <id>sug_win4gacdbbcbry4</id>
    <published>2026-03-09T16:32:15Z</published>
    <updated>2026-03-09T16:32:14Z</updated>
    <content type="text/plain">We currently do not support PDF Portfolios wherein multiple PDF files are archived inside of another PDF file (PDFception?)</content>
  </entry>
  <entry>
    <title>Extract the original sender (not the forwarder) from forwarded emails</title>
    <link href="https://feedback.parseur.com/suggestions/698207/extract-the-original-sender-not-the-forwarder-from-forwarded-emails"/>
    <id>sug_8oymeeqvbhvno9o</id>
    <published>2026-03-05T17:54:55Z</published>
    <updated>2026-03-05T17:54:55Z</updated>
    <content type="text/plain">The current metadata field "Sender" returns the person who forwarded the email, not the original sender. It would be awesome to add another metadata field for the original sender of the email.</content>
  </entry>
  <entry>
    <title>Host Parseur on US-located datacenters and service providers</title>
    <link href="https://feedback.parseur.com/suggestions/698030/host-parseur-on-uslocated-datacenters-and-service-providers"/>
    <id>sug_kw7sejtsxufvm6a</id>
    <published>2026-03-04T19:43:20Z</published>
    <updated>2026-03-04T19:43:20Z</updated>
    <content type="text/plain"/>
  </entry>
  <entry>
    <title>Allow setting up custom domains to receive emails</title>
    <link href="https://feedback.parseur.com/suggestions/695498/allow-setting-up-custom-domains-to-receive-emails"/>
    <id>sug_3pmmxwlzm9d0aej</id>
    <published>2026-02-18T17:12:39Z</published>
    <updated>2026-02-18T17:12:39Z</updated>
    <content type="text/plain">Currently all mailboxes are created with @in.parseur,com domain. Allow setting up custom domains so inboxes can be created with branded domains like @mybrand.com</content>
  </entry>
  <entry>
    <title>Neither form on the website for requesting prices or contact work</title>
    <link href="https://feedback.parseur.com/suggestions/694996/neither-form-on-the-website-for-requesting-prices-or-contact-work"/>
    <id>sug_hhnilmdgivd80kv</id>
    <published>2026-02-16T08:57:15Z</published>
    <updated>2026-05-21T17:06:30Z</updated>
    <content type="text/plain"/>
  </entry>
  <entry>
    <title>Retain all headers and columns with Google Sheets export.</title>
    <link href="https://feedback.parseur.com/suggestions/694781/retain-all-headers-and-columns-with-google-sheets-export"/>
    <id>sug_9rxf77kk5tfual2</id>
    <published>2026-02-15T00:04:59Z</published>
    <updated>2026-02-15T00:04:59Z</updated>
    <content type="text/plain">Currently with AI parse, there is no option to retain empty columns, causing a dynamic header / column listing depending on which fields are populated. An option to always return all columns regardless of content would be really helpful. My work around has been to leave a couple of files in my inbox that between them keep every cell populated. An ineligant solution. And one that makes my setup fragile should a user delete those documents, as it will break the functionality of my Google Sheet due to the changed column alignment.</content>
  </entry>
  <entry>
    <title>Ability to extract and Output JPEG or PNG</title>
    <link href="https://feedback.parseur.com/suggestions/694073/ability-to-extract-and-output-jpeg-or-png"/>
    <id>sug_27sabrbvdgw8hn1</id>
    <published>2026-02-11T18:56:58Z</published>
    <updated>2026-02-11T18:56:58Z</updated>
    <content type="text/plain"/>
  </entry>
  <entry>
    <title>pricing plan</title>
    <link href="https://feedback.parseur.com/suggestions/694001/pricing-plan"/>
    <id>sug_uqatwi3cbkmwbvc</id>
    <published>2026-02-11T13:31:25Z</published>
    <updated>2026-02-11T13:31:25Z</updated>
    <content type="text/plain">how about a $20/month plan? &#13;
it's a BIG jump from zero to $49</content>
  </entry>
  <entry>
    <title>Make webhook response status be able to put document status on skipped</title>
    <link href="https://feedback.parseur.com/suggestions/693547/make-webhook-response-status-be-able-to-put-document-status-on-skipped"/>
    <id>sug_rn3dza5heqdpfwf</id>
    <published>2026-02-09T09:30:17Z</published>
    <updated>2026-02-09T09:30:17Z</updated>
    <content type="text/plain">In some cases we skip invoices based on our internal systems settings (for example supplier name). It would be nice if for example our webhook would return a 4xx status code that would parseur put the file status on skipped. (so we can still see which files are skipped in parseur)</content>
  </entry>
  <entry>
    <title>Allow deep copy of mailbox</title>
    <link href="https://feedback.parseur.com/suggestions/692656/allow-deep-copy-of-mailbox"/>
    <id>sug_funvzzqvgka0ho9</id>
    <published>2026-02-03T22:29:47Z</published>
    <updated>2026-02-03T22:29:47Z</updated>
    <content type="text/plain">I would like to duplicate a mailbox and carry over its [already processed] documents. I am testing scripts using the API and would like to make a duplicate of an existing mailbox (which I can do), but would like to copy over its existing documents without wasting credits to reprocess them. Surely this is pretty easy to implement and would make it much friendlier for developers to interface with Parseur and do proper testing and validation without incurring costs to reprocess documents that we've already spent credits on&#13;
&#13;
&#13;
Alternately, I'd be fine with the ability to add "dummy" documents to a mailbox, which for all I care can be lorem ipsum and don't need to use any server resources whatsoever. &#13;
&#13;
Thank you,&#13;
Thor</content>
  </entry>
  <entry>
    <title>Offer the ability to mass-update Apprentice parser fields</title>
    <link href="https://feedback.parseur.com/suggestions/692650/offer-the-ability-to-massupdate-apprentice-parser-fields"/>
    <id>sug_nil42exzfewubcf</id>
    <published>2026-02-03T22:02:24Z</published>
    <updated>2026-02-03T22:02:24Z</updated>
    <content type="text/plain">It would be nice if in the UI there was an ability to pass updates to the Master mailbox fields onward to all Apprentice mailboxes.</content>
  </entry>
  <entry>
    <title>Canceling Bulk Processing</title>
    <link href="https://feedback.parseur.com/suggestions/690489/canceling-bulk-processing"/>
    <id>sug_kkkxhjowcm8dhkp</id>
    <published>2026-01-22T21:44:40Z</published>
    <updated>2026-01-22T21:44:40Z</updated>
    <content type="text/plain">Users should be able to cancel bulk operations such as the processing of  all "unprocessed" documents.</content>
  </entry>
  <entry>
    <title>Ability to cancel bulk operations</title>
    <link href="https://feedback.parseur.com/suggestions/690488/ability-to-cancel-bulk-operations"/>
    <id>sug_vtwo1cp52ancy6w</id>
    <published>2026-01-22T21:42:18Z</published>
    <updated>2026-01-22T21:42:18Z</updated>
    <content type="text/plain">The ability to cancel the process all "unprocessed" function should have a cancel button so users can stop processing remaining unprocessed documents if needed.</content>
  </entry>
  <entry>
    <title>Clearer Warnings on the 25 Page Limit for Processing ( highlight the Split Option before uploading )</title>
    <link href="https://feedback.parseur.com/suggestions/687206/clearer-warnings-on-the-25-page-limit-for-processing-highlight-the-split-option-"/>
    <id>sug_5qm0t2sqhenzwgm</id>
    <published>2026-01-06T00:22:26Z</published>
    <updated>2026-01-06T00:22:26Z</updated>
    <content type="text/plain">Please add clearer warnings that t you need to split large documents BEFORE uploading OR allow already processed documents to split into smaller segments without having to reupload as "spilt" an incur more credit charges</content>
  </entry>
  <entry>
    <title>Microsoft Excel Online Integration</title>
    <link href="https://feedback.parseur.com/suggestions/684531/microsoft-excel-online-integration"/>
    <id>sug_cc0s1s02rmclnfd</id>
    <published>2025-12-17T19:31:56Z</published>
    <updated>2025-12-17T19:31:56Z</updated>
    <content type="text/plain">Offer the ability for users to send parsed data as new rows in existing Excel Online spreadsheets</content>
  </entry>
  <entry>
    <title>Zoho CRM Integration</title>
    <link href="https://feedback.parseur.com/suggestions/684530/zoho-crm-integration"/>
    <id>sug_6zl6uqhrxdyvgxo</id>
    <published>2025-12-17T19:30:36Z</published>
    <updated>2025-12-17T19:30:36Z</updated>
    <content type="text/plain">Allow users to create new objects in Zoho CRM from parsed data in emails and documents</content>
  </entry>
  <entry>
    <title>Salesforce CRM Integration</title>
    <link href="https://feedback.parseur.com/suggestions/684528/salesforce-crm-integration"/>
    <id>sug_4sjh5c63rjwvfyl</id>
    <published>2025-12-17T19:29:45Z</published>
    <updated>2025-12-17T19:29:44Z</updated>
    <content type="text/plain">Offer users the ability to create new Salesforce objects from parsed data in emails and documents</content>
  </entry>
  <entry>
    <title>Airtable Integration</title>
    <link href="https://feedback.parseur.com/suggestions/684527/airtable-integration"/>
    <id>sug_jf9sziiy1bw7uw9</id>
    <published>2025-12-17T19:28:13Z</published>
    <updated>2025-12-17T19:28:12Z</updated>
    <content type="text/plain">Offer users an Airtable integration allowing them to send parsed data as new rows in a table</content>
  </entry>
  <entry>
    <title>Log for templates</title>
    <link href="https://feedback.parseur.com/suggestions/680550/log-for-templates"/>
    <id>sug_q032ljacaql1z6a</id>
    <published>2025-12-03T03:04:58Z</published>
    <updated>2025-12-03T03:04:57Z</updated>
    <content type="text/plain">Adding log for who created a template</content>
  </entry>
  <entry>
    <title>AI Engine to parse vertically oriented text</title>
    <link href="https://feedback.parseur.com/suggestions/678856/ai-engine-to-parse-vertically-oriented-text"/>
    <id>sug_6r3r4hwza4msv41</id>
    <published>2025-11-22T00:11:54Z</published>
    <updated>2026-05-21T17:32:01Z</updated>
    <content type="text/plain">I've tried over and over to get the AI engine to parse vertically oriented text from an otherwise horizontally oriented text (pdf) document. I deal primarily with invoices, and often receive documents with text either handwritten, typed, or even added digitally after scanning to pdf from a physical document. This text is sometimes oriented vertically, and the AI engine fails to capture it regardless of the custom instructions provided to the engine.&#13;
&#13;
A template is not a feasible solution, as the text can be located on a different portion of the document with each example.</content>
  </entry>
  <entry>
    <title>Replace “,” with “;” in CSV</title>
    <link href="https://feedback.parseur.com/suggestions/678374/replace-with-in-csv"/>
    <id>sug_ogvcxmlyxbhtyb4</id>
    <published>2025-11-19T14:43:24Z</published>
    <updated>2025-11-19T14:43:24Z</updated>
    <content type="text/plain">The current CSV extraction uses “,” as separators. Some software programs consider “;” as separators rather than “,”. Add the option to choose the separator format for CSV (“,” or “;”).</content>
  </entry>
  <entry>
    <title>For docs longer than 500 pages - that are split into 500 pages after upload - INCREASE to 1,000</title>
    <link href="https://feedback.parseur.com/suggestions/678210/for-docs-longer-than-500-pages-that-are-split-into-500-pages-after-upload-increa"/>
    <id>sug_gya5jinvo9egmqg</id>
    <published>2025-11-18T16:28:47Z</published>
    <updated>2025-11-18T16:28:47Z</updated>
    <content type="text/plain">Currently documents with more than 500 pages are split into multiple docs of 500 pages each after upload. So when I upload a document that is 1,011 pages, it gets split into a doc for 1-500, 501-1000, 1001-1011 (for example). Because the AI doesn't get all of the data correctly we need to manually add in data and the 3 groupings make this more difficult ----- if there was a way to increase the 500 page limit to 1,000 pages it would be very helpful.</content>
  </entry>
  <entry>
    <title>Duplicate Check to Prevent Data Errors</title>
    <link href="https://feedback.parseur.com/suggestions/676283/duplicate-check-to-prevent-data-errors"/>
    <id>sug_1cz52e4h55xctmv</id>
    <published>2025-11-08T10:30:05Z</published>
    <updated>2025-11-08T10:30:05Z</updated>
    <content type="text/plain">A built-in duplicate detection feature would help reduce errors and improve data integrity.&#13;
When documents or records with the same key fields (e.g., invoice number, supplier, or order ID) are uploaded or processed multiple times, the system should automatically recognize potential duplicates and alert the user or block the import.&#13;
Benefits:&#13;
Prevents double entries and processing errors&#13;
Ensures cleaner, more reliable datasets&#13;
Saves time by avoiding manual verification&#13;
Increases confidence in automation workflows&#13;
Ideally, the duplicate check could be configured by the user (e.g., selecting which fields define a duplicate) and optionally applied at the mailbox, folder, or global level.</content>
  </entry>
  <entry>
    <title>Debugging templates through the Debugger tool: compare also with the master templates</title>
    <link href="https://feedback.parseur.com/suggestions/675938/debugging-templates-through-the-debugger-tool-compare-also-with-the-master-templ"/>
    <id>sug_8pvwi3d1nblqojd</id>
    <published>2025-11-06T11:42:47Z</published>
    <updated>2025-11-06T11:42:47Z</updated>
    <content type="text/plain">When debugging templates for a specific document inside a mailbox through the Debugger tool: can you also compare with the master templates in addition to the local templates?&#13;
It would be very useful to avoid creating double templates.</content>
  </entry>
  <entry>
    <title>Add original attribute to Name format</title>
    <link href="https://feedback.parseur.com/suggestions/675300/add-original-attribute-to-name-format"/>
    <id>sug_qbp15tyfr49zz03</id>
    <published>2025-11-03T09:50:23Z</published>
    <updated>2026-05-12T06:43:06Z</updated>
    <content type="text/plain">Could you add the original value to your ‘name’ field before your transformation is applied? The transformation can sometimes make mistakes and changes the capitalization, which may actually carry useful information.”&#13;
&#13;
Original description: Bonjour, pourriez vous dans votre type «name» ajouter la valeur originel avant votre transformation qui peut se tromper et modifie la casse qui peut-être une indication ?</content>
  </entry>
  <entry>
    <title>Allow defining for which cases you want to receive alerts</title>
    <link href="https://feedback.parseur.com/suggestions/674735/allow-defining-for-which-cases-you-want-to-receive-alerts"/>
    <id>sug_1nord0oiklkihea</id>
    <published>2025-10-30T14:28:19Z</published>
    <updated>2025-10-30T14:28:18Z</updated>
    <content type="text/plain">Allow defining for which cases you want to receive alerts&#13;
By document type (PDF, DOC, etc.)&#13;
By type of receipt (attachment, email content, etc.)</content>
  </entry>
  <entry>
    <title>Dynamic Document Renaming Based on Parsed Fields</title>
    <link href="https://feedback.parseur.com/suggestions/674356/dynamic-document-renaming-based-on-parsed-fields"/>
    <id>sug_mucdu7krzbsifor</id>
    <published>2025-10-28T13:27:57Z</published>
    <updated>2025-10-28T13:27:57Z</updated>
    <content type="text/plain">It would be extremely useful if Parseur could automatically rename documents using a naming pattern builder that pulls values from parsed fields within each document. This would allow consistent, structured filenames without manual intervention.&#13;
&#13;
Example use case:&#13;
&#13;
Invoice_&lt;Date&gt;_&lt;Supplier&gt;_&lt;InvoiceNumber&gt;.pdf&#13;
&#13;
Benefits:&#13;
Improved file organization and searchability&#13;
Elimination of manual renaming steps&#13;
Standardized naming conventions across suppliers and document types&#13;
Ideally, the feature would allow users to define a customizable template (using parsed field variables) directly in the mailbox settings.</content>
  </entry>
  <entry>
    <title>Preserve the original case (uppercase/lowercase) when inputting first and last names.</title>
    <link href="https://feedback.parseur.com/suggestions/671997/preserve-the-original-case-uppercaselowercase-when-inputting-first-and-last-name"/>
    <id>sug_tdt0nuskshguyqi</id>
    <published>2025-10-14T13:50:57Z</published>
    <updated>2025-10-14T13:50:57Z</updated>
    <content type="text/plain">The 'name' field output should match the case sensitivity of the input document to ensure proper name parsing. &#13;
Currently, names like Guillaume MARTIN are output as Guillaume Martin, making it impossible to distinguish the first name from the last name. Preserving the original case (e.g., keeping MARTIN in uppercase) ensures accurate identification of surnames vs. given names.</content>
  </entry>
  <entry>
    <title>Archive Processed documents</title>
    <link href="https://feedback.parseur.com/suggestions/671256/archive-processed-documents"/>
    <id>sug_bvuwpo3pmoyz6om</id>
    <published>2025-10-09T23:25:36Z</published>
    <updated>2025-10-09T23:25:36Z</updated>
    <content type="text/plain">Documents processed successfully should have an ability to archive them for future reference.</content>
  </entry>
  <entry>
    <title>Include content-based page filtering to preclude processing of unnecessary pages within signle doc</title>
    <link href="https://feedback.parseur.com/suggestions/670989/include-contentbased-page-filtering-to-preclude-processing-of-unnecessary-pages-"/>
    <id>sug_pmjlje0zeceiwnd</id>
    <published>2025-10-08T17:32:04Z</published>
    <updated>2025-10-08T17:32:03Z</updated>
    <content type="text/plain">Incidentally, our business receives documents with intermittent blank pages and superfluous content. Rather than process the entire document for importation (all pages contained therein), I am seeking to create instructions that examine the document for only relevant pages (i.e., the pages I need for the extraction phase). &#13;
&#13;
This capability would eliminate our physical, human task of trimming/excising irrelevant pages before forwarding/importing the document to the Parseur mailbox. Currently, mailbox settings only permit page-based filtering. Therefore, content-based page filtering importation would be very instrumental for our business needs. Nonetheless, I recognize that content-based filtering would employ AI power, so I understand that it would expend credits. However, it would be ideal to forgo the subsequent field instructions creation phase. Thank you for considering this suggestion.</content>
  </entry>
  <entry>
    <title>Add SplitParentID metadata field</title>
    <link href="https://feedback.parseur.com/suggestions/669911/add-splitparentid-metadata-field"/>
    <id>sug_zyqvmp2vu1jsao9</id>
    <published>2025-10-03T07:17:06Z</published>
    <updated>2025-10-07T06:08:15Z</updated>
    <content type="text/plain"/>
  </entry>
  <entry>
    <title>download data from selected documents</title>
    <link href="https://feedback.parseur.com/suggestions/667837/download-data-from-selected-documents"/>
    <id>sug_dfx4nobtzzpjxfn</id>
    <published>2025-09-23T18:28:46Z</published>
    <updated>2025-09-23T18:28:45Z</updated>
    <content type="text/plain">The option to download parsed data from selected documents only. Right now it downloads data from all the documents in mailbox, even if they are not checked. Example: I processed 5 documents today, but want to download only 3 to excel. how can this be done? there should be another option aside from selecting date range or selecting last document.</content>
  </entry>
  <entry>
    <title>Move documents between mailboxes</title>
    <link href="https://feedback.parseur.com/suggestions/667784/move-documents-between-mailboxes"/>
    <id>sug_yzspjoeqofkawap</id>
    <published>2025-09-23T13:57:09Z</published>
    <updated>2025-09-23T18:30:12Z</updated>
    <content type="text/plain">Allow AI processed documents to be moved from one mailbox to another without incurring the cost of the initial analysis again.</content>
  </entry>
  <entry>
    <title>Add a 'force OCR' as a parameter in an API processing call</title>
    <link href="https://feedback.parseur.com/suggestions/667516/add-a-force-ocr-as-a-parameter-in-an-api-processing-call"/>
    <id>sug_8thjs53mhnpan7r</id>
    <published>2025-09-22T09:05:24Z</published>
    <updated>2025-09-22T09:05:23Z</updated>
    <content type="text/plain">When the AI parser doesn't find any data I would like to reprocess it via an API call with 'Force OCR' set. In the portal I've found this setting  can yield the results I want however I don't want it on all the time.</content>
  </entry>
  <entry>
    <title>Synchronous API Call for Document Processing</title>
    <link href="https://feedback.parseur.com/suggestions/667259/synchronous-api-call-for-document-processing"/>
    <id>sug_8amoyb5b8bvwulr</id>
    <published>2025-09-20T19:34:09Z</published>
    <updated>2025-09-20T19:34:09Z</updated>
    <content type="text/plain">At the moment, after uploading a document via the API, one has to wait for a webhook to return the processed content. This complicates workflows and requires additional logic to handle callbacks. A suggested improvement is to add a synchronous API call - meaning the request would wait until the content is ready and then return the processed document directly. This would enable continuing the process in the same step, without relying on webhooks, and would simplify building complex integrations.</content>
  </entry>
  <entry>
    <title>Support for File Upload via URL</title>
    <link href="https://feedback.parseur.com/suggestions/667258/support-for-file-upload-via-url"/>
    <id>sug_kzjhirxvcwpm004</id>
    <published>2025-09-20T19:33:33Z</published>
    <updated>2025-09-20T19:33:33Z</updated>
    <content type="text/plain">Currently, documents can only be uploaded using binary data. It would be extremely helpful to also allow uploads via a direct file URL (e.g., a file hosted in cloud storage or an external server). This would eliminate unnecessary steps of downloading and re-encoding files, simplify integration with existing systems, and significantly improve efficiency when connecting the API to automation workflows.</content>
  </entry>
  <entry>
    <title>Recent Change to Search Function Now Requires Exact File Name with Extension</title>
    <link href="https://feedback.parseur.com/suggestions/666661/recent-change-to-search-function-now-requires-exact-file-name-with-extension"/>
    <id>sug_rlsrtehzjfrrka1</id>
    <published>2025-09-18T06:28:57Z</published>
    <updated>2025-09-18T06:28:57Z</updated>
    <content type="text/plain">This issue has only started occurring within the past week. Previously, Document Search allowed searching by name without needing the file extension and would return partial matches. Now, it requires the full document name including the extension, which is a frustrating and unwelcome change.</content>
  </entry>
  <entry>
    <title>Convertir directement pour Word ou Libre Office les données analysées</title>
    <link href="https://feedback.parseur.com/suggestions/666565/convertir-directement-pour-word-ou-libre-office-les-donnees-analysees"/>
    <id>sug_uslzewtdx7ni5o8</id>
    <published>2025-09-17T16:58:58Z</published>
    <updated>2025-09-17T16:58:58Z</updated>
    <content type="text/plain"/>
  </entry>
  <entry>
    <title>EXPORT EN MEME TEMPS DU FICHIER xlsx ET DES DOCUMENTS TRAITES DANS CE FICHIER</title>
    <link href="https://feedback.parseur.com/suggestions/666325/export-en-meme-temps-du-fichier-xlsx-et-des-documents-traites-dans-ce-fichier"/>
    <id>sug_dcmomjcd5yji6zo</id>
    <published>2025-09-16T17:01:51Z</published>
    <updated>2025-09-16T17:01:51Z</updated>
    <content type="text/plain">Il conviendrait de télécharger tous les documents en même temps que l'export du fichier de traitement de ces documents.</content>
  </entry>
</feed>
