Settings and activity
35 results found
-
1 vote
Cyril
shared this idea
·
-
1 vote
This has been deferred (not planned for the next 6 months).
Please continue to share this idea, we will continue to monitor for votes and comments!
An error occurred while saving the comment Cyril
supported this idea
·
-
25 votes
An error occurred while saving the comment Cyril
commented
When using document matching with fuzzy text matching or the threshold feature enabled, the returned values are highlighted in the same blue color as standard text snips. This can be confusing to users since these settings allow for slight variations, such as small misspellings or rounding differences, which wouldn’t match exactly without these features enabled. To improve clarity and transparency, we should differentiate these values by shading them in a different color, making it clear to users that these results were influenced by the specific parameters they set. For example, if a threshold of $1 is set, and the input is $3, a returned value of $3.12 should be highlighted in a different color to indicate it's within the allowed threshold.
Cyril
supported this idea
·
-
4 votes
This has been deferred (not planned for the next 6 months).
Please continue to share this idea, we will continue to monitor for votes and comments!
An error occurred while saving the comment Cyril
commented
Idea: Introduce an automated "Signature Detection" feature to validate the presence of signatures on documents like contracts and agreements.
Problem: Auditors currently have to manually verify the presence of signatures, a time-consuming process prone to errors, especially in documents requiring thorough validation.
Solution: Leverage computer vision techniques (Convolutional Neural Networks) to detect whether signature fields contain signatures, streamlining the validation process.
Benefits:
Automates the tedious task of signature verification, reducing audit times.
Ensures compliance by quickly identifying unsigned documents.Cyril
supported this idea
·
-
6 votesCyril
supported this idea
·
An error occurred while saving the comment Cyril
commented
Idea: Allow users to choose between static and dynamic data extractions.
Problem: Currently, snipped data does not automatically update when source documents change, leading to outdated information and time-consuming manual updates. This is especially challenging for auditors handling multiple drafts, like at Prospect Capital, where updating each snip individually is inefficient.
Solution: Provide an option for snips to dynamically update when source documents are modified. This feature would offer more flexibility, cater to specialized auditing workflows, and integrate well with our cloud collaboration suite (CCS) package.
Benefits:
1. Streamlines the process of updating snips across document versions.
2. Maintains data integrity by offering user control over static or dynamic updates.
3. Saves time by eliminating the need for manual resnipping. -
1 voteCyril
shared this idea
·
-
2 votes
An error occurred while saving the comment Cyril
commented
Users need a more explicit indication when data extraction fails. Rather than simply omitting the missing value, we should clearly communicate that it was unable to extract the desired information, whether that's through providing a low confidence score, replacing missing values with empty cells or null values, or Add a specific flag or indicator (e.g., "N/A", "Error", or a unique symbol) to mark missing values.
Cyril
supported this idea
·
-
6 votes
An error occurred while saving the comment Cyril
commented
Can we enhance the current "Edit Cell Value" feature to include a system for logging user comments on edits? This would ensure that all changes to cell values are documented, providing a transparent audit trail. Such a feature is important for audit managers, as it helps them detect any discrepancies between edited values and the supporting documentation, whether due to accidental errors or intentional actions. This transparency is essential for maintaining trust and ensuring the integrity of audits.
Goals:
1. Enhance data integrity and audit trail.
2. Increase reviewer confidence in data accuracy.
3. Address user demand for greater transparency in data handling.Functional Requirements:
1. Notification System - notify users of cell value edits via in-app notifications.
2. Logging System - Implement a logging system that records all cell value edits along with timestamps and user information.
3. Comments: Require users to provide comments explaining the reason for each edit.
4. Version Control - Maintain version history of cell values, allowing users to view previous values and the associated comments.Cyril
supported this idea
·
-
2 votes
This has been deferred (not planned for the next 6 months).
Please continue to share this idea, we will continue to monitor for votes and comments!
Cyril
shared this idea
·
-
1 voteCyril
shared this idea
·
-
5 votes
This has been deferred (not planned for the next 6 months).
The problem noted of removing duplicate sample pages for a more accurate document match is something we would like to consider solving. An option to remove documents with snips however introduces an option to essentially remove links for work performed with DataSnipper.
Please continue to share this idea, we will continue to monitor for votes and comments!
An error occurred while saving the comment Cyril
commented
Could we develop a feature to remove pages containing snips from combined PDFs? This would address a common issue faced by users, who currently have to manually remove unnecessary pages due to ERP export problems.
Cyril
supported this idea
·
-
2 votesCyril
shared this idea
·
-
9 votesCyril
supported this idea
·
-
4 votes
This has been deferred (not planned for the next 6 months).
The current implementation allows all documents within each folder to be imported (the highest level folder will be replicated within DataSnipper but all documents within subfolders will be imported into that 1 folder).
Please continue to share this idea, we will continue to monitor for votes and comments!
An error occurred while saving the comment Cyril
commented
Could we introduce subfolder functionality within the document organizer? This feature would help internal audit teams better organize multiple controls within a single workbook, avoiding the tedious process of separating each control into its own workbook. It would improve organization and navigation, particularly for complex projects with numerous controls.
Cyril
supported this idea
·
-
3 votesCyril
shared this idea
·
-
26 votes
This has been deferred (not planned for the next 6 months).
Please continue to share this idea, we will continue to monitor for votes and comments!
Cyril
supported this idea
·
-
1 voteCyril
shared this idea
·
-
11 votesCyril
supported this idea
·
-
34 votesCyril
supported this idea
·
An error occurred while saving the comment Cyril
commented
I'm looking to enhance our current document matching capabilities with a feature that closely resembles the VLOOKUP function in Excel but extends this functionality to search within documents. The feature would streamline the process of verifying numerical amounts or specific data points against those listed within a given document.
The envisioned feature would work as follows: A user would input a unique identifier (e.g., a policy number, transaction ID, etc.), and the system would then locate this identifier within a selected document. Upon successful identification, it would prompt the user to define the data extraction parameters, allowing for the automatic retrieval of associated figures or information adjacent to or linked with the identifier, such as amounts or dates.
This feature would not only expedite the verification process by combining two steps into one but would also enhance accuracy and efficiency across various types of documents and use cases.
Impact:
Streamlines data verification processes across different document types
Reduces the need for multiple manual checks
Ensures higher data accuracy and efficiency -
5 votesCyril
shared this idea
·
Currently, users with a View Only license are unable to export documents to make mark-ups independently. Enabling this functionality would allow auditors and other team members with view-only access to export files from the shared Excel document, mark them up externally, and then return them with comments or annotations.