Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
DocBits seamlessly integrates with Infor LN/M3 through ION API, ION Desk, and Infor Standard BODs. Our API integration allows us to export data to Infor and perform master data validation in DocBits.
To identify the supplier or compare/match purchase order lines, we activate a trigger in LN/M3 that sends the Sync.RemitToPartyMaster, Sync.SupplierPartyMaster, and Sync.PurchaseOrder BODs to DocBits. We configure this process in ION Desk by defining the dataflow to a specific connection point to DocBits.
We use the ION API to send the PDF with attributes to IDM and the BOD Sync.CaptureDocument to ION Desk. In ION Desk, we transform the to the desired target BODs based on the document type being processed. These transformed Infor BODs are then automatically imported to LN or M3.
Export to
DocBits is a cloud-based document capture solution that harnesses the power of Artificial Intelligence (AI) and Machine Learning (ML) to effectively recognize, classify, analyze, and extract information from various types of documents, regardless of their format. Here’s a closer look at its key features:
Document Recognition_:_ DocBits employs AI algorithms to accurately identify and recognize documents, whether they are in paper form or electronic files.
Document Classification: It classifies documents into relevant categories, facilitating easy organization and retrieval.
Data Extraction: DocBits extracts critical data from documents, transforming unstructured information into structured data that can be integrated into your workflow.
Machine Learning: The system continually learns and improves its recognition accuracy with each processed document, making it more proficient over time.
Swarm Intelligence: DocBits utilizes swarm intelligence to enhance its learning capabilities, creating a self-improving system.
Sending Data to Infor On-Premise Customer
To send data to an Infor on-premise customer, we offer two ways: Site-to-Site VPN with IPsec.
IPSEC VPN Setup
Endpoint B
Customer
FELLOWPRO AG
Name of Contact
Daniel Lopez
Endpoint Hardware/Software
StrongWAN
Location of Firewall
Frankfurt
Endpoint IP
46.101.133.158
Network/Host 1
10.135.0.0/16
1. UDP port 500: Used for Internet Key Exchange (IKE) phase 1 and phase 2.
2. UDP port 4500: Used for NAT traversal (NAT-T), allowing VPN traffic to pass through NAT (Network Address Translation) devices.
• Authentication URL: https://inforos.CustomerXYZad.net/
• Data URL: https://inforos.CustomerXYZad.net:7443/
For setting up an IPsec site-to-site VPN, ensure the above ports and protocols are configured and open.
Use the provided URLs to access Infor OS for authentication and data.
To send data to Infor onPremise customer we offer two ways Site2Site with IPsec or
Filter Option for Email Import Log: Users now have the ability to filter the import logs and sort the table for a clearer, more efficient overview. This enhancement streamlines the process of identifying and managing email entries, improving troubleshooting and overall log management.
Multi-Language Support for List of Values : We've expanded multi-language capabilities to the List of Values feature. Administrators can now define labels in multiple languages, ensuring that the correct label is automatically displayed based on the user's system language settings. This enhancement promotes greater accessibility and localization, making it easier for users worldwide to interact with the platform in their native language.
User Detail Enhancements in Settings: The settings interface now displays comprehensive user information. Administrators can easily view group affiliations, sub-organization details, and additional key data, enabling better management of user roles and a clearer understanding of team structures.
Auto Accounting Information on the Approval Screen: The approval screen now presents auto accounting details alongside invoice information. This improvement provides deeper insight into transaction data, facilitating smoother review processes and more informed decision-making regarding invoices.
Task Counter for Documents on the Dashboard View: Documents on the dashboard can now indicate open tasks associated with them and display the total number of pending tasks. This feature provides users with a quick overview of outstanding actions, improving task management and workflow efficiency.
Enhanced Workflow Logs for Decision Tree Cards: The logs now display the output of the decision tree, making it easier to track and understand how decisions were made within workflows.
Introduction of New Auto-Testing Setup to Enhance System Functionality and Stability:
We are excited to announce the implementation of a new automated testing system designed to improve the overall functionality and reliability of our platform. This new setup will run consistent, thorough checks on our system to identify any issues before they impact your experience. By automating these tests, we can ensure faster responses to potential problems and maintain the highest standards of quality for our system.
Resolved an issue where tasks were not appearing on the validation/approval screen.
Fixed the positioning of the Next/Previous button so that it remains static.
Fixed scrolling issues in the script and decision tree views, ensuring that action buttons remain stationary during scroll.
Removed the origin country field from e-invoices.
Fixed an issue with the task counter displaying an inaccurate number of tasks.
Added missing translations.
Corrected custom fields to display descriptive names instead of IDs.
Resolved an issue where documents were downloaded with an incorrect file name.
Fixed sorting inconsistencies in the invoice line table within PO matching.
Fixed an issue affecting task creation functionality.
Fixed an issue in PO matching where the invoice table sorting would reset when matching a line.
Resolved auto accounting issues by ensuring booking references split correctly when an amount is divided.
Updated the ClickHouse host information.
Resolved an issue where duplicate documents were not recognized as duplicates.
Fixed export issues caused by booking references that were too long.
Resolved an issue where readonly checkboxes where not readonly
Fixed an issue where Users can be added to a sub-organization twice
Fixed an issue where changing the sub-organization for a document caused to reset the assigned user or group
Improved the shortcuts.
Improved Data Extraction: Added an option to extract the Purchase Order or Item Number from a line above or below.
Fixed an issue where users could not be added to a group.
Fixed an issue with email import failures.
Resolved an issue with the field training on documents with more than page
Fixed an issue where scripts didn’t work properly.
Resolved an issue where document data didn't get displayed correctly
Fixed an issue with the auto update purchase order setting
Fixed an issue where the subscription tokens got displayed wrong
Resolved an issue where the task screen displayed an outdated document version
Fixed an issue that caused documents to not change their status
Support for ISO-8859-1 for ZUGFeRD: Improved compatibility for invoices using ISO-8859-1 character encoding.
Optimized Logging System: Enhanced tracking and diagnostics for quicker issue identification and resolution.
DocBits now includes full support for ZUGFeRD versions 2.1 and above, enabling seamless handling and processing of ZUGFeRD-compliant electronic invoices. The integration ensures:
Compatibility: DocBits is capable of managing ZUGFeRD invoices in both their structured (XML) and unstructured (PDF) formats, maintaining compliance with EU standards such as EN 16931 for e-invoicing.
Efficiency: Users can effortlessly import, validate, and extract data from ZUGFeRD e-invoices, minimizing manual data entry and reducing processing time.
Flexibility: Whether you're working with basic, comfort, or extended profiles within the ZUGFeRD standard, DocBits provides tools to manage each level of invoice complexity.
Future-Proofing: With support for newer versions, DocBits ensures that businesses remain compliant with evolving e-invoicing regulations across EU member states and beyond.
DocBits introduces an advanced capability to leverage external APIs during document processing, enhancing the completeness and accuracy of extracted data. This feature significantly reduces manual input by populating missing fields with accurate, up-to-date information retrieved in real time from trusted sources. It ensures that documents are processed faster and with greater consistency.
DocBits introduces a powerful Sequential Workflow and Approval History feature, designed to enhance document processing efficiency and accountability. By enabling documents to follow a predefined decision tree, this feature ensures orderly review and approval while maintaining a complete record of actions taken. Sequential Workflow Management:
Documents can be assigned to multiple users in a predefined sequence, ensuring that each stage of review or validation occurs in the correct order.
Each user in the workflow is notified when it's their turn to act on the document, reducing confusion and delays.
Workflows can be customized to match specific business processes
Approval History:
A complete log of all actions taken on the document is available in the Validation and Approval views. This includes:
User actions (e.g., "approved" "rejected")
Timestamps for each action
Comments or notes added by users during review
This feature enhances tax handling capabilities by enabling detailed classification and export of tax information to Infor LN (Full Tax, Reduced Tax, Tax Free). This allows for better alignment with complex tax structures and ensures seamless integration with accounting systems.
Multiple Tax Sections per Type:
DocBits now supports the addition of multiple tax sections under each tax type, such as:
Full Tax: Standard VAT or sales tax rates.
Reduced Tax: Lower rates for specific goods or services (e.g., essential items).
Tax-Free: Exemptions for eligible transactions.
These sections allow precise categorization of tax amounts, ensuring compliance with tax regulations and accounting standards.
Dynamic Auto Accounting Integration:
Based on the data extracted during document processing, the relevant tax sections are automatically displayed on the Auto Accounting Screen.
This ensures that users can validate and adjust tax entries quickly without manual calculation or re-entry, streamlining the workflow.
Export to Infor LN:
The tax data, including all relevant sections and classifications, is seamlessly exported to Infor LN, ensuring consistency between document processing in - DocBits and the enterprise resource planning (ERP) system.
Exported data is linked to the respective cost lines in Infor LN, maintaining clear traceability and accurate financial reporting.
DocBits has introduced significant updates to the dashboard, focusing on usability, efficiency, and improved data visibility. These enhancements include a new "Assigned To Group" filter and an optimized UI for Document Logs, making it easier for users to interact with and manage their documents.
DocBits introduces several usability improvements to the PO Matching Screen, designed to streamline the process of matching purchase order (PO) lines with invoices. These enhancements offer more intuitive controls for multi-line selection and provide clear visual indicators for handling outdated PO data.
Ctrl + Click for Individual Line Selection:
Users can now hold the Ctrl key and click on specific lines to select multiple, non-contiguous rows on the PO matching screen.
Shift + Click for Range Selection:
Users can select a range of rows by holding the Shift key, clicking on the first row, and then clicking on the last row. All rows in between the first and last selection will be automatically selected.
Automatic Outdated Data Detection:
If the PO data associated with an invoice is old (based on system settings), an icon will be displayed to notify the user. This visual indicator ensures that users are aware of stale data that may not reflect the latest updates in the purchase order.
Resolved an issue to ensure all possible values are displayed correctly during auto-accounting processes
Improved the user interface of Workflow Logs to make navigation and usability more intuitive
Updated the document fields to display additional information, such as required and hidden flags, directly in the user interface
Added visibility of group descriptions in the group settings
Displayed length restrictions for group names during creation to prevent errors
Addressed issues in the decision tree testing functionality and resolved translation inconsistencies
Improved the search functionality in Workflow Logs for more accurate and effective search results
Fixed an issue to prevent users from inadvertently deleting e-document drafts
Resolved bugs in the email import process to ensure seamless integration and data handling
Fixed issues with saving AI-generated tags, ensuring consistent data retention
Corrected a sorting issue that occurred when applying sorting across different pages of the dashboard
Enhanced the document counter to accurately display the number of documents processed by DocBits
Improved translations throughout the application to enhance usability for different languages
Users can now seamlessly import XML and EDI files through the Email Import feature.
Optimised Saving Mechanism: The saving process has been streamlined to occur only after the user completes the matching, reducing redundant saves and improving efficiency.
Enhanced Asynchronous Export: Export functionality now runs asynchronously, ensuring smoother operations and an improved overall user experience.
The workflow functionality has been upgraded to provide a better user experience:
Improved Logs: Workflow logs now feature a cleaner, more intuitive interface, making it easier to review and understand process details.
Enhanced Responsiveness: Workflow execution processes are optimized for faster and more reliable performance, enabling quicker task completion and reduced delays.
We’ve implemented advanced caching strategies across the application to optimize data retrieval and reduce load times. These improvements enhance overall usability by ensuring smoother navigation and a more responsive user experience, particularly for frequently accessed features.
Dashboard Enhancements: The dashboard has been revamped with an improved layout and additional features to simplify navigation and enhance visibility of key metrics.
UI Improvements: The user interface across the application has been refined for a more modern, intuitive, and user-friendly experience, making it easier for users to accomplish their tasks with minimal effort.
Enhanced the fuzzy logic to ensure more accurate and reliable data population following extraction.
Fixed known bugs affecting groups and permissions, ensuring seamless access management and role functionality.
Addressed inconsistencies in translations across the application, improving clarity and localization.
Resolved layout-related issues, ensuring a consistent and optimized user interface across all configurations.
Corrected errors in master data lookup functionality, ensuring accurate and reliable data retrieval.
Resolved issues with email import functionality across all available options, ensuring smooth and error-free operations.
Configured IMAP email settings to automatically send notifications for import results. Successful import notifications will confirm the files processed, while failure alerts will include the filenames and specific error details for prompt troubleshooting.
Revamped the master data lookup settings with refined categorization, enabling faster and more precise retrieval of diverse master data types. This improvement streamlines data access by organizing master data into distinct categories, significantly boosting search efficiency and accuracy. Users can now locate the relevant data more quickly, enhancing productivity and decision-making across the application
Implemented a robust caching mechanism to significantly boost application performance, especially under high request loads. This improvement reduces server processing time by temporarily storing frequently accessed data, enabling faster response times and a smoother user experience. The new caching system efficiently manages increased traffic, ensuring reliable and scalable performance even during peak usage periods
Upgraded the document locking functionality to prevent simultaneous edits, ensuring data integrity and minimising conflicts. Now, documents are automatically locked during active editing, providing users with clear indicators when a document is in use and preventing others from making changes until the edit session is complete. This enhancement streamlines collaborative workflows and reduces the risk of data overwrites.
Breadcrumb Navigation: Added breadcrumb trails across application pages to enhance navigation, allowing users to easily track and return to previous sections for a more intuitive browsing experience.
Streamlined User Interface: Removed the "new version" pop-up notification to create a smoother, uninterrupted workflow, reducing distractions and improving overall usability.
Resolved user-specific problems, such as attachment failures from encrypted or signed emails.
Fixed card display and flow problems.
Corrected routing issues with Next/Previous buttons.
Addressed bugs related to decision tree tables.
Updated UI for the password field to improve usability.
Fixed issues with the task counter not displaying correctly.
Corrected a user interface problem with the AI table.
Resolved errors with document extraction during table training.
Added a warning when a PO is matched during reformatting, and ensured matched rows are removed.
Fixed date formatting, ensuring data loads correctly by day and week filters, and ensured document types are properly displayed.
Corrected the display of documents on dual monitors.
Fixed a problem where unlinking one PO line would remove all lines.
Resolved incorrect translations across the application.
Fixed the issue where lengthy descriptions in rule management caused scrolling on the list.
FeastRestored missing "Assign-To" functionality for non-admin users.
This feature allows users to identify if documents are duplicated across their system. This feature works by analyzing document fields that can be configured by the user. By selecting specific fields, users can customize the detection criteria to suit their needs, ensuring that only relevant duplicates are flagged. This helps to maintain data integrity and reduces the clutter of redundant documents, streamlining document management processes.
The decision tree is a tool used to automate decision-making in a workflow by mapping out choices and their outcomes. By integrating decision trees, you can ensure consistent decisions based on specific criteria, streamline processes, and reduce errors. This approach enhances efficiency by automating complex decision points within the workflow.
DocBits now allows users to switch between different AI models to better suit their needs. You can choose the AI model that best fits your specific use case, whether it's for document analysis, data extraction, or text classification. This flexibility enables you to optimize performance and achieve more accurate results, tailoring the AI's capabilities to your organization's unique requirements.
DocBits now offers the ability to change the OCR (Optical Character Recognition) version used within the platform. Users can select different OCR versions based on their specific needs, ensuring better accuracy and compatibility with various document types. This feature allows for more precise text extraction from images and scanned documents, improving overall data quality and workflow efficiency.
Rule Manager provides the flexibility to create and edit conflict resolution rules tialored for DocBits invoicing system. These rules are designed to automatically handle discrepancies between invoice details and purchase order (PO) data, ensuring accurate financial reconciliation. The system applies these rules to process invoice lines, charges, and taxes, and generates appropriate adjustments or notes when necessary.
BOD syncing from Infor utilizes AWS Stream for real-time data processing, enhancing efficiency and significantly reducing data syncing time.
DocBits now processes XRechnung (electronic invoices) seamlessly by first creating a user-friendly PDF, streamlining and simplifying the invoice processing workflow.
PO Match Button Visibility Issue: PO Match button is available when there is no table or the table is deleted. Status: On field validation, PO Match will be hidden if there is no table or the table is deleted
Table Drag & Drop Sorting Issue: Table Drag & drop for sorting on all Lists/Dashboards Resolution: User can now drag and drop to sort the table
Validation Screen Toolbar Issue: Validation screen: toolbar right side not scrollable Resolution: Fixed
Horizontal Scroll Issue: Horizontal Scroll on Approval Screen Resolution: Fixed
Approval Screen Decision Clearing Issue: Ability to clear the approve/reject decision on approval screen Resolution: Fixed
Task Display on Approval Screen Issue: Task shown on the Approval Screen Resolution: Toolbar is available which shows the tasks count of open/in progress
PO Match Table Size Issue: PO Match table gets smaller after matching a line Resolution: Fixed
Task Assignment based on Item Procurement Group Issue: Translation for procurement group assignment Resolution: Fixed
Supplier Name and Id in Task Creation Issue: Adding Supplier Name and Id in Task creation Resolution: Supplier Name and Id will be picked from the document
Document Subtype Copy Issue: Click on Copy Document Subtype from sub document type setting was not working Resolution: Fixed
New Label Field Issue: New Label field in list of values to add label along with value and synonym Resolution: Fixed
Country Origin Card in Workflow Issue: New Card in workflow that checks country origin of a supplier and create a task or continue porcessing docuemtn accordingly Resolution: Fixed
Dark Mode Fix on settings searchbar Issue: This issue was previously identified Resolution: Fixed
Extracted Table Column Visibility Indicator Issue: Indicator if Columns are hidden in extracted table on Field validation Resolution: Fixed
Dashboard Assignment for Admins Issue: Make Assign to on the dashboard only for admins Resolution: Fixed
Document Split Visibility Issue: Show Document split only when more pages Resolution: Fixed
Invoice Dashboard Columns Issue: Additional columns on invoice dashboard Resolution: Fixed
Field Validation Script Deactivation Issue: Field Validation- Deactivate script was not working correctly Resolution: Fixed
Approval Layout Button Customization Issue: Cannot change the button type and style on approval layout builder Resolution: Fixed
Data Sync Table Issue: Data Sync Table in settings Resolution: Fixed
Dashboard Analytics Total Display Issue: Dashboard Analytics- display wrong total number Resolution: Fixed
Line Charges Export to M3
• Export line charges to M3 with appropriate costing elements as per your business needs.
PO & Invoice Discrepancy Handling
• Smart handling of discrepancies in quantity, prices, charges, and tax.
• Issue: PO search was not working.
• Status: This issue has been identified and will not be addressed in this release.
• Issue: PO matching connection was not removing as expected.
• Resolution: Fixed to ensure seamless PO matching operations.
• Issue: Exported documents had alerts for costing elements even when the system was not set up for it.
• Resolution: Corrected to prevent unnecessary alerts, ensuring accurate document exports.
• Issue: Advance shipment EDI view showed IDs in the title.
• Resolution: Titles now display correctly, improving data readability.
• Issue: Calculation errors occurred when lines were split further.
• Resolution: Fixed to ensure accurate calculations in all scenarios.
• Issue: No table was showing on the PO screen.
• Resolution: Display issue resolved to ensure tables appear correctly.
• Issue: Auto export was not working.
• Resolution: Functionality restored to ensure automatic exports operate smoothly.
• Issue: Mismatch issue on PO showed despite everything being identical on the Delivery Note.
• Resolution: Resolved to ensure accurate mismatch detection.
• Issue: Reports were not downloading.
• Resolution: Fixed to enable seamless report downloads.
• Issue: Total and Net amounts were showing incorrect values.
• Resolution: Values corrected to ensure financial accuracy.
• Issue: Invoice Date column had wrong format values.
• Resolution: Dates now display in the correct format, enhancing usability.
• Issue: Workflow delays occurred at “Ready for Validation” until feedback from Doc2flow.
• Resolution: Workflow timing improved for faster validation processes.
The existing system lacks automated rules for accurately matching and processing invoice charges against purchase orders (POs). This manual process can lead to discrepancies, as illustrated in the screenshots, where invoice charges and POs need reconciliation for correct invoicing.
With the new Rule Manager in DocBits, launching in July, you can automate this process:
Define criteria (e.g., Quantity > PO Quantity) for invoice line items.
Map fields and actions to export data seamlessly to Infor.
Validate rules with sample data to ensure accuracy.
This update brings exciting new features and bug fixes to Junebug:
New Features:
Automated Charge Extraction: Junebug now automatically extracts and maps charges within your Docbit documents. This eliminates manual data entry and streamlines your workflow.
Portal Export to Infor IDM: The new Portal allows you to effortlessly export supplier documents directly to Infor IDM. This simplifies shipment processing and reduces manual intervention.
Origin Identification (AI): Junebug introduces a powerful AI feature that automatically learns the origin of documents. This saves you time and effort in document classification.
Bug Fixes:
QR Code Fix: An issue that previously caused problems with QR code processing has been resolved.
Non-EDI Document Handling: Junebug now handles non-EDI documents more effectively.
Sandbox Freeze - 3th June 2024
In the upcoming release, a significant enhancement to the classification and extraction capabilities will be introduced, specifically aimed at table lines within documents. This new feature allows users to define whether a line in a table represents a charge. This functionality is particularly useful in detailed financial documents, such as invoices, where distinguishing between different types of transactions—such as charges, taxes, or fees—is crucial for accurate processing and record-keeping.
Key Points for Release Notes:
Enhanced Table Line Classification: Users can now specify if a particular line in a document table is a charge, improving the accuracy and granularity of data extraction.
▪ Workflow Card Translation: Enhancements in the workflow, including card translation for better localization support.
▪ Email Import Logging: Added detailed logging for email imports to enhance troubleshooting and monitoring.
▪ Broken Fuzzy Screen Fix: Resolved an issue with broken fuzzy screen display across various interfaces.
▪ Accounting Updates: Enhanced the accounting process by removing outdated accounting methods and integrating charges more efficiently.
▪ Ruiz Workflow Enhancements: Fixed bugs related to workflow navigation, particularly involving hidden steps.
▪ User Interface Adjustments: Improved user interface elements such as cash discount terms under payment terms for better clarity and user experience.
▪ Performance Enhancements: Various backend improvements to enhance system performance and stability.
▪ Approval Stamp Issue: Fixed critical issues surrounding the approval stamp process to ensure compliance and correct functionality.
▪ Key Addition: Added necessary keys back to the system to ensure data integrity and system functionality.
▪ Master Data Field Adjustment: Addressed an issue in the master data field to align with user requirements.
▪ Version Updates: Routine updates to various system components to align with current standards and technologies.
▪ Merge Activities: Numerous merges to integrate features, fixes, and enhancements from multiple development branches into the main branch.
▪ Cache Management Enhancements: Updated the get_receive_delivery_cache to improve performance and reliability.
▪ New Features for Sales Orders: Introduced a preview feature for sales orders, enhancing the visualization and management of order data.
▪ Document Handling Improvements: Added automated test jobs for demotesting and sandbox environments to ensure robustness.
▪ Enhanced Cache Functionality: Added field_id to further enhance the caching mechanisms.
▪ Office Email Import Adjustments: Made necessary adjustments to the Office Email Import feature to enhance functionality.
▪ Development Enhancements: Multiple merges from dev to main branches ensuring synchronization and stability across environments.
▪ Configuration Updates: Various updates to the configuration files improving the system setup and parameters.
▪ Implemented a new workflow test that can now be enabled during import, allowing for more flexible testing scenarios.
▪ Enhanced the logging functionality for action cards, making debugging and monitoring more efficient.
▪ Improved compatibility for field comparison cards with date and enum types, ensuring smoother comparisons and validations.
▪ Updated the tax card and modified the return processes for action cards to streamline operations.
▪ Addressed issues with the document status updates, ensuring they are accurately reflected in the system.
▪ Fixed the calculation for the comparison card involving unit price and quantity to correctly handle discrepancies.
▪ Resolved multiple minor bugs and made stability improvements.
▪ Merged multiple development stages into the sandbox and stage branches, reflecting a significant integration of new features and fixes.
This international standard defines the requirements for establishing, implementing, maintaining, and continually improving an Information Security Management System (ISMS). It helps organizations protect data in a systematic and cost-effective way, including processes for risk management and information security controls.
Impact for Clients: Ensures that DocBits adheres to the highest standards of information security, providing confidence that sensitive data is well-protected.
SOC 1 reports are designed for organizations that need to demonstrate the effectiveness of internal controls over financial reporting. It is particularly relevant for service providers that affect their clients’ financial reporting.
Relevance to DocBits: Demonstrates our commitment to maintaining stringent internal controls over financial data, providing assurance to clients about the reliability of our processes.
SOC 2 focuses on a service organization’s controls relevant to security, availability, processing integrity, confidentiality, and privacy of data. It is crucial for technology and cloud computing companies that handle sensitive information.
Value for Clients: Provides an independent validation that DocBits has implemented effective controls to protect client data, ensuring trustworthiness in our software and services.
The GDPR is a regulation in EU law on data protection and privacy in the European Union and the European Economic Area. It also addresses the transfer of personal data outside the EU and EEA areas.
Client Assurance: Compliance with GDPR ensures that DocBits processes personal data in line with EU regulations, protecting user privacy and adhering to strict data handling guidelines.
Stay updated with the latest features, fixes, and configurations available for testing in the Sandbox environment. This dedicated environment allows for validation and function checks
Access the Sandbox:
Use your existing credentials to log into the Sandbox environment.
Ensure that you are using the correct URL for the Sandbox.
Testing Guidelines:
Follow the steps provided for each feature or fix.
Test Logs:
Monitor system logs for relevant test results or errors.
Document your testing process and results for review.
If you encounter any issues or have suggestions during testing, please contact the support team or use the feedback form provided within the Sandbox environment.
Note: This page will be updated regularly to reflect the latest information about testing availability and upcoming updates in the Sandbox environment.
We understand the importance of secure data transfer. That’s why we use open port 443, the standard port for HTTPS, ensuring that all data transferred is encrypted and secure. Our SSL-secured connections guarantee that your data is safe during every step of the process.
When it comes to database communication, we don’t take any chances. Our Kubernetes setup and databases reside within the same Virtual Private Cloud (VPC). This means we only access the database via local IP, ensuring that the transmitted data never leaves the local network. It’s like having a private highway just for your data.
Document handling is a breeze with Docbits. All uploaded documents are securely stored in a dedicated ‘Space’. We use SSL encryption for data traffic and require multiple keys for file access, making sure your documents are as secure as a vault.
We only allow HTTPS-secured connections for communicating with our servers. This ensures that all data transferred is encrypted, keeping your sensitive information safe and sound. It’s like having a security guard for your data, 24/7.
Flexibility is key, and we offer both cloud and on-premise solutions. With our on-premise option, there’s no need to open any ports, ensuring that your network security remains uncompromised. Whether you’re in the cloud or keeping things in-house, we’ve got you covered.
Supplier-Based AI Model Selection: Users can now select the AI model used for data extraction on a per-supplier basis. This enhancement allows for fine-tuned optimization, ensuring better extraction accuracy for different suppliers and improving overall data processing results.
Expanded Cross Sub-Organizations Access: Non-admin users can now also access the Cross Sub-Organizations feature.
By incorporating ZUGFeRD 2.1 and newer standards, DocBits simplifies cross-border transactions and aligns with modern business needs, making it an essential tool for organizations prioritizing digital transformation and regulatory compliance.
For organizations with multiple sub-organizations enabled, DocBits now introduces the Cross Sub-Organizations feature. This enhancement empowers administrative users to streamline their document management across all sub-organizations under a single umbrella. Admin users can now access and view all documents from every sub-organisation without needing to switch sub-organization. This centralized visibility enables admins to see all the documents for all the sub-organisations, making it easy to locate specific files while still maintaining a bird’s-eye view.
DocBits introduces enhanced document visibility controls, enabling more precise access management for non-admin users through group-based permissions. This feature allows administrators to define which documents are visible to specific users or groups, ensuring streamlined workflows and improved data security. Admin users can assign documents to specific groups, granting visibility only to users within those groups. This ensures that users see only the documents relevant to their role or team, reducing clutter and enhancing focus.
The history ensures transparency and provides an audit trail for compliance and troubleshooting.
The SFTP/FTP Documents Archive enhancement in DocBits builds on the existing import functionality, introducing a seamless method for archiving files after they’ve been processed. A new setting in the FTP import configuration allows users to enable or disable file archiving. Once files are successfully ingested and processed in DocBits, they will be automatically archived to a designated folder on the SFTP/FTP server if the option is enabled. This ensures processed files are preserved for record-keeping without cluttering the active import directories.
Hotfix - 5 Juni
Report any issues, unexpected behaviors, or feedback via
Support Contact:
Feature/Update
Description
Available for Testing Customer
Internal Testing
LN Customers & M3
Create Tax Amount per Table Line
12/13/2024
12/10/2024
Supplier Invoice
Sequential Workflows
12/2/2024
11/29/2024
Organisation
Showing All Sub Organisations for Unified View
12/2/2024
12/2/2024
Supplier Invoice - Import
SFTP/FTP Read Files as Archived
12/2/2024
12/2/2024
Supplier Invoice Report
Power BI (ClickHouse Data for Reporting)
2024-11-28
12/1/2024
If the table extraction training results are not good:
Open the OCR View by clicking on the magnifying glass icon with OCR written on it.
Review the extraction results and see if the OCR process can improve the data capture.
If the results still look bad, try a different document to verify if the issue is document-specific.
If the issue is document-specific, use another document for extraction.
If the issue persists, follow the next steps.
Check if the document has e-text available.
You can verify this using a tool like Adobe Acrobat.
If the document contains e-text, follow Step 3.
If the document does not contain e-text, follow Step 4.
If the document contains e-text, you have two options:
Turn on e-text extraction for just this supplier:
Go back to the Documents Field Validation.
Click the square with the three dots in the left-side toolbar.
Here, activate the Use E-text if available option to turn it on for just this supplier.
Turn on e-text extraction for all suppliers:
Go to Settings > Document Processing > OCR Settings.
In this section, you will find the Use E-text if available option and can turn it on for all suppliers.
After enabling e-text extraction, retry the table extraction training.
If the results improve, the issue is resolved.
If the results are still not good, proceed to Step 4.
If the document does not have e-text available:
Go to Settings > Document Processing > OCR Settings.
Change the AI OCR Version to a different version.
Go back to the Table Extraction Training and try again.
If the result is better:
Check other documents from different suppliers to ensure the extraction results for those suppliers are not impacted by this change.
Be cautious, as this change can affect other suppliers' extraction results.
This change can impact other suppliers, so make sure to verify the results thoroughly to ensure it does not negatively affect other suppliers’ document extractions.
If the result did not improve after changing the AI OCR version, please contact us for further assistance.
Log in to LN CE.
Navigate to the Options menu and select Run Program.
In the input field, type ACP Parameters and press Enter to open the program.
Click on the arrow next to the Actual Set field to expand the settings.
Go to the Matching section.
Check the Automatic Matching Setting:
If the Automatic Matching is set to Match to Purchase Receipt, proceed to the next step.
If it is not set to Match to Purchase Receipt, but you still got this error, please contact us.
If the Automatic Matching is set to Match to Purchase Receipt, proceed with the following steps in DocBits:
Open DocBits and go to the Settings section.
Navigate to Document Processing.
Select Export.
In the Export section, click on the three dots icon next to the export that is not working and select Edit.
In the Edit Export Settings menu, click Download the LN-Mapping file.
Open the downloaded LN-Mapping file.
Search for the field IRF_PackingSlip.
If the field IRF_PackingSlip is present and set to nothing (empty), update it to TF_packing_slip.
If the field IRF_PackingSlip is not present, add it to the file and set its value to TF_packing_slip.
For the field InvoiceReceiptFields add PackingSlip to the values.
It should look like the following:
Go back to the Export section in DocBits where you previously downloaded the LN-Mapping file.
Upload the edited LN-Mapping file with the new updates.
If you encounter the error message "Costing elements are not properly configured. Please ask your admin to configure it," it could be due to one of the following reasons:
Accidental Activation: The Table Extraction for Costing setting might have been turned on accidentally.
To resolve this, go to Settings → Document Processing → Classification and Extraction, and turn off the Table Extraction for Costing setting.
Missing Configuration: The costing elements have not been configured yet.
In this case, go to the configuration page and set up the required costing elements.
Configuration page:
The API mode allows users to access all features available to them from the IT tools already deployed within the partner structures. There are two integration methods:
APIs are integrated directly into information systems or management software for parties issuing and receiving invoices or their dematerialising operators (ODs). Users can thus directly access the solution’s features and their upgrades from their usual IT tools, internal or offered by their OD.
APIs can also be integrated into the IS of the PDPs to give them more flexibility (compared with EDI mode), with some APIs dedicated to their use.
Editors will be able to offer software based on the APIs. Depending on the mode chosen by the editor, connection can then be effected by the editor, or by the customer itself during installation or deployment in its IS. This third-party software will complement the customer’s information system by adding a communication layer to the PPF.
The hub provides its customers with a web or application solution to enable them to make the various API calls. It is thus the hub that makes API calls on behalf of all its customers. In this case, each partner must have a technical account, but only the hub needs an application under PISTE and a connection to the PPF.
Source: Article 91 of France’s 2024 Finance Law (summarized by EY) mandates e-invoices be sent via a certified PDP or the state portal . The French tax authority’s updates further clarify that after 2024 reforms, businesses must use a registered PDP for B2B e-invoicing (the PPF will no longer serve as a free exchange platform) . PEPPOL is being implemented to connect these PDPs, not as an alternate channel outside the system . This confirms that using the PEPPOL network alone is insufficient – compliance in France’s 2026 e-invoicing regime requires integration with the PPF or a certified PDP, with PEPPOL serving only as the underlying delivery network among those platforms.
DocBits Dashboard Guide
After logging in with your credentials, you will be redirected to the DocBits Dashboard homepage. This is the main page where you can see and manage all your imported documents.
Under France’s 2026 e-invoicing mandate, companies cannot rely solely on the PEPPOL network to exchange domestic B2B invoices. The law requires that all invoices between French VAT-registered businesses be routed through either a certified private platform (PDP) or the state’s public invoicing portal (PPF) to satisfy legal . In other words, businesses will no longer send invoices directly to customers – they must transmit them via an approved e-invoicing platform (a PDP) or via the government . This ensures the tax authority receives the required data in real-time. Simply exchanging invoices over PEPPOL without involving an accredited PDP/PPF would not meet the mandated reporting and transmission obligations.
France is adopting PEPPOL as part of its infrastructure, but only as a transport layer within the PDP framework, not as an independent compliance route. The French tax authority (DGFiP) is becoming the Peppol Authority to standardize how PDPs . All certified PDPs are required to interconnect via the PEPPOL network for exchanging . This means PEPPOL will facilitate interoperability between authorized platforms – not replace the need for those platforms. In practice, a company may use PEPPOL only by working through a PDP (or the PPF acting in its limited role) that uses PEPPOL to send or receive invoices. This has been confirmed in official guidance: the public portal is focusing on data collection, while invoice distribution will happen exclusively through PDPs, with those PDPs leveraging networks like for .
To the right of the search bar, you will find other dashboard tools.
Refresh List: This is used to update the dashboard without having to refresh your browser tab.
Advanced Settings: More information on this topic is available further down this page.
Analytics: This provides you with further insight about the documents you have uploaded to DocBits.
Upload: More information on this topic in the next section.
The advanced settings often contain additional configuration options and functions that enable more specific adjustments and fine-tuning.
More settings
Keyboard shortcuts
Import Log
Set PO Table columns for organization
Set dashboard sorting by organization
Filter documents by day, week, month, year or all. The filtering refers to the time at which the document is imported
On the next pages you will find further information about the individual settings.
While navigating your documents in DocBits, if you would like to return to the main area of the Dashboard, you can simply press the escape (ESC) button on your keyboard and you will be returned to the main Dashboard menu (on the page which you entered the document you just exited from).
Document merge documents
Document merging allows you to combine multiple documents.
First, you need to select the documents you would like to merge. This can be done by selecting the checkboxes of the documents. Once you have selected the documents, click on the icon with three dots.
A menu will then be displayed, select the “Merge” option which can be found at the bottom.
Document merging is an important feature in a document management system that allows users to combine multiple documents into a single document. Here are some reasons why document merging can be useful:
Organizing Related Documents: By merging multiple documents into a single document, users can organize and keep related information or files together. This can help improve efficiency in managing and accessing documents.
Creating reports or summaries: Merging multiple documents can be useful to create reports or summaries by combining data or information from different sources or documents. This allows users to create comprehensive reports or presentations without having to manually copy and paste the information.
Archiving documents: When multiple versions of a document exist, or when documents need to be summarized within a specific time period, merging documents can help ensure consistent archiving practices and optimize storage space.
Workflow optimization: Document merging can be part of an automated workflow where documents are automatically combined once certain conditions are met. This can be used, for example, in an approval process or when creating contracts or reports.
Combining Invoices: A business needs to summarize all invoices from a given month for accounting purposes. Individual invoices are uploaded as separate documents and then merged to create a consolidated overview.
Combining approval forms: An application approval workflow requires multiple forms to be merged before being forwarded to management. The different forms are automatically combined as they are completed and submitted by the parties involved.
Creating an Annual Report: Multiple departments in a company work together to create a comprehensive annual report. Each department prepares its own section of the report as a separate document. These documents are then brought together to create the final annual report.
By merging documents, organizations can streamline their document management processes, improve collaboration, and increase efficiency.
If you are looking for a specific document or documents, then you have the following available to you. Within the search bar we have provided you with various tools to find the document you are searching for, in order to access them, select the following icon.
The following filter options will become available to you.
We provide you with the option to filter by document type, status of the document, the assignee of the document and by the date.
If you would like to see a detailed log of all documents imported to your DocBits environment, then follow these steps.
From your DocBits Dashboard, select the Advanced Settings option.
After the Advanced Settings bar appears, select the Import Log button.
A table will then appear with all recently imported documents as well as other relevant information regarding them.
Login and Navigation: How to access Docbits and navigate through the interface.
Initial Configuration: Setting up Docbits for first-time use.
Document Submission: Instructions for submitting documents into Docbits.
Document Review and Approval:
Approving Orders: Steps for reviewing and approving order forms.
Processing Invoices: Guide on how to process incoming invoices for payment.
Search and Retrieve: How to find and access documents within Docbits.
Edit and Update: Editing documents and updating their status.
Common Issues: Solutions to frequent problems encountered by users.
: How to reach support for assistance.
Welcome to DocBits
Automatic Data Extraction
Utilizes AI and OCR (Optical Character Recognition) technology to extract data from various document types.
Supports over 120 languages.
Capable of extracting unstructured data at both header and line levels.
Swarm Intelligence
Leverages the power of AI swarm intelligence to deliver communal benefits across customers.
Enhances the training of classification and extraction models with input from a wide range of users.
Provides over 96% accuracy in data extraction and classification.
Automates the reconciliation of purchase orders with incoming invoices.
Ensures accurate financial transactions and promptly addresses discrepancies.
Supports matching of various document types, not limited to invoices.
Facilitates automatic booking to ledger accounts.
Allows splitting of amounts by department.
Supports the definition of ledger accounts by the accounts payable team.
Provides integrated validation processes to ensure data accuracy.
Seamless Integration
User-Friendly Interface
Offers a modern and simple UI that requires no IT resources for setup and maintenance.
Features an interactive dashboard with unlimited document types and custom extracted columns.
Secure Cloud-Based Solution
Hosted on a secure cloud in Germany, ensuring data privacy and security.
Facilitates easy migration from legacy solutions.
Benefits
Efficiency: Automates repetitive tasks, reducing manual entry and errors.
Accuracy: High accuracy in data extraction and document classification.
Scalability: Can handle unlimited document types and volumes.
Compliance: Maintains an audit trail for compliance and review.
Cost Savings: Reduces the need for physical storage and manual processing.
Use Cases
Suitable for a wide range of industries and document types, including invoices, delivery notes, order confirmations, and more.
Ideal for businesses looking to optimize their document capturing processes and enhance operational efficiency.
Welcome to DocBits, your comprehensive source for documentation strategies and insights. At DocBits, we are dedicated to providing clear, concise, and up-to-date documentation resources for , , and .
by is an advanced intelligent document processing (IDP) solution designed to optimize and automate the handling of business documents. Below is a summary of its unique features and benefits:
Integrated Validation and Processes
Features approval to streamline document handling.
Integrates seamlessly with Infor IDM (Intelligent Document Management) and Infor ERP (Enterprise Resource Planning) systems, including and .
Supports data import through or connection and export to relevant ERP modules.
For more information, visit or contact sales at sales@fellowpro.com. Follow us on .
If you’re using DocBits software for document processing, it’s essential to understand the different document statuses that your files can have. Here’s a complete list of all the possible document statuses in DocBits:
WatchDog Start: The Watchdog module is starting.
WatchDog Split: The document is being split in Watchdog.
WatchDog Upload: The document is being uploaded in Watchdog.
Upload: The document is being uploaded.
OCR: Optical Character Recognition (OCR) is currently running on the document.
Classification: The document is being classified.
Zugferd import: A Zugferd document is being imported.
Ready for Validation: The document is ready for validation.
Zugferd export: A Zugferd document is being exported.
Workflow: A workflow is currently running with this document.
Pending approval: The document needs to be approved.
Pending second approval: The document needs to be approved a second time.
Auto Accounting: Automatic accounting is running.
Export: The document is being exported.
Error: An error occurred in the document.
This page provides a graphical overview of the various steps a document has gone through up to this point.
Navigate to the actions column on the dashboard and click the three dots next to the document for which you want to view the document flow.
Select Document Flow.
Open the document you want to view the document flow for.
Click the three dots on the right side of the Field Validation.
Select Document Flow.
On the left side of the screen, you will see the individual steps of the document flow, listed from left to right.
Steps that initiate the document flow process (such as import or restart) will appear in green.
To navigate through the steps, simply drag and drop them on the screen.
When you click on a step, the name of the module and information about whether the step was successful or not will appear on the right side of the screen.
Welcome to the FAQ page! Below you will find links to various categories that can help you quickly find the information you need.
For common questions and guidance on how DocBits works, how to set up your account, and basic troubleshooting tips.
Everything related to the extraction, handling, and processing of documents in DocBits.
Guidelines and FAQs related to integrating DocBits with Infor LN, document imports, and specific configurations for LN.
Guidelines and FAQs related to integrating DocBits with Infor M3, document imports, and specific configurations for M3.
From the Dashboard, click on the Advanced Settings icon as shown below:
The following menu will then be displayed:
Select the button labeled “Set dashboard columns for organization” and a list of all the column names will be shown.
From this menu, you can select the column names and use the arrows to add and remove the columns you desire.
You can set the order of the columns by clicking on the dots next to the column name and dragging them to the appropriate position.
Another option also allows you to add fields of a document type:
Here you can choose from the different document types:
For each document type there are different fields that you can add:
Select the fields you need and click "Add to visible Columns", they will then appear in the column settings.
The second part of the dashboard is an overview of all the uploaded documents. You can view all documents or just the ones assigned to you. You can also search for documents by name.
Data will be extracted within seconds, and the status will change from “Running” to “Ready for Validation”.
The dashboard includes the following shortcuts to enhance navigation and interaction:
Control + K – Opens the keyboard shortcut menu, providing a list of available shortcuts within the application.
Control + Q – Refreshes the dashboard table, ensuring that the latest data is displayed without needing to manually reload the page.
Control + H – Opens the documentation page for more information and assistance.
Filters not applied correctly:
First, check the filter settings to make sure the correct filters have been applied and that they are displaying the desired data.
Make sure that filters are applied logically and consistently. Sometimes incorrect filter logic or incorrect combinations can produce unexpected results.
Provide users with guidance on how to use filters correctly to ensure they can use the filtering features effectively.
Delays in loading data:
Check the network connection to make sure it is stable and not causing delays.
Check the server load and the performance of the data source to see if that is the problem. You may need to optimize the data source or switch to a more powerful infrastructure.
Implement caching mechanisms to reduce loading times, especially for frequently accessed data. Encourage users to optimize their data queries by retrieving only the required data fields and using filters to reduce the amount of data.
Browser issues:
Make sure the browser they are using is compatible with the dashboard and has all required updates installed.
Recommend users to clear their browser cache regularly to avoid memory issues and ensure they are getting the most up-to-date data.
Check for extensions or plugins in the browser that might be interfering with the dashboard and temporarily disable them if necessary to isolate problems.
User-specific issues:
Offer individualized support for users who continue to have problems. You may need to check their specific settings, permissions, or network configuration to identify and resolve the issue.
By providing users with these specific troubleshooting tips, you can help them effectively resolve common issues related to dashboard settings and increase their productivity.
Here are best practices that can help you:
Custom views:
Make sure the dashboard is customizable so users can customize their own views and layouts. This can be done through the ability to add, remove, or rearrange widgets.
Automatic updates:
Implement automatic updates to ensure data is always up-to-date. This is especially important for high-use environments.
You can enable this auto-refresh tool in the settings.
User guidance and training:
Offer a user-friendly interface and instructions on how to use the dashboard.
Train users regularly to ensure they understand all the features and capabilities of the dashboard.
Filters and views:
Using filters can be very helpful when searching for documents, but also consider resetting filters to keep a consistent view of data.
Dashboard analytics:
Monitor dashboard usage and collect feedback from users.
Analyze which parts of the dashboard are used the most and what improvements can be made to further optimize the user experience.
Data visualization:
Use engaging and meaningful data visualizations to present information quickly and understandably.
Choose visualizations based on user needs and the type of data presented.
Security and privacy:
Ensure the dashboard adheres to security standards and sensitive data is adequately protected.
Implement access controls to ensure users can only access the data that is relevant to them.
By considering these best practices, you can create a dashboard that effectively aligns with users' daily routines and helps them make informed decisions.
This is where you can keep an eye on your tasks. You can pick between two different layouts – one is a bit more detailed than the other. You can also filter tasks by different criteria, like whether they're assigned to you or the status of the task.
1. Check the Purchase Order from the Dashboard
If the document status is Export Error:
Locate the document on the dashboard.
Click on it and then select the Fields Validation button to navigate back to the field validation screen.
If the document status is Ready for Validation:
Click on the document to proceed directly to the Field Validation screen.
If the document is in Pending Approval status:
Navigate to the Approval Screen.
Next to the Invoice Line Items, locate the Purchase Order Table.
Go to 3. Check for the Delivery Number step.
2. Verify the Purchase Order
On the Field Validation screen, ensure the correct Purchase Order is selected.
Once the correct Purchase Order is confirmed, click on the Purchase Order next to the extracted table, to open the Purchase Order Table view.
3. Check for the Delivery Number
In the Purchase Order Table, look for the Delivery Number column:
If a Delivery Number is present, proceed to the Approval Screen and check again if it is present, when present go to Step 3.
If no Delivery Number is present, follow Step 2 to address this issue.
Before sending the Purchase Order to DocBits, verify that the Delivery Number is correctly assigned in LN. Check the Purchase Order details in LN to ensure that it is complete and accurate. If the Delivery Number is missing or incorrect, this could be the cause of the export error.
If the Purchase Order appears correct and contains the necessary details, you can proceed to the next step.
Open DocBits and go to the Settings section.
Navigate to Document Processing.
Select Export.
In the Export section, click on the three dots icon next to the export that is not working and select Edit.
In the Edit Export Settings menu, click Download the LN-Mapping file.
Open the downloaded LN-Mapping file.
Search for the field IRF_ReceiptLine.
If the field IRF_ReceiptLine is present and set to nothing (empty), update it to TF_delivery_line.
If the field IRF_ReceiptLine is not present, add it to the file and set its value to TF_delivery_line.
For the field InvoiceReceiptFields, add ReceiptLine to the values.
It should look like the following:
Go back to the Export section in DocBits where you previously downloaded the LN-Mapping file.
Upload the edited LN-Mapping file with the new updates.
After confirming that the Purchase Order has a Delivery Number and ensuring the Export file is correct, follow these steps to retry the export:
Return to the Dashboard:
Go back to the dashboard and find the document with the export error.
Retry the Export Process:
Click on the document with the export error.
If the Purchase Order has a valid Delivery Number and the Export file is correct, proceed to retry the export.
Check the Export Result:
After retrying, check the export process again to see if the issue has been resolved and the document no longer shows as an export error.
If the export is successful, the issue should be resolved.
Further Investigation (if the problem persists):
If the issue persists after retrying the export, contact support for further investigation into possible configuration or system issues.
The task counter is located in the upper-right corner of the Dashboard home page.
This is where you can see how many documents are in your queue for processing
and how many documents are now ready for validation.
This section offers a detailed overview of all purchase orders. It includes a search bar with various filters that you can select to quickly narrow down your results. Additionally, you can customize the arrangement of the column headers by using the drag-and-drop functionality for a more tailored viewing experience.
The validation screen allows you to check, edit, and validate all the imported documents. You can see the name of the document, how many pages it consists of, the date it was imported, and its status. The actions button allows you to assign, restart, validate, or delete the document.
This section offers a detailed overview of all advanced shipments. It includes a search bar with various filters that you can select to quickly narrow down your results. Additionally, you can customize the arrangement of the column headers by using the drag-and-drop functionality for a more tailored viewing experience.
This section offers a detailed overview of all shipment orders. It includes a search bar with various filters that you can select to quickly narrow down your results. Additionally, you can customize the arrangement of the column headers by using the drag-and-drop functionality for a more tailored viewing experience.
To configure your settings, click on the User Icon located in the bottom-left corner of the screen. Here you can customize several options:
Language
Select Preferred Language: Choose your desired language from the available options.
Dark Mode
Switch to Dark Mode: Enable or disable Dark Mode for a more comfortable viewing experience.
User Settings
In this section, you can adjust the following preferences:
Date Pattern: Customize how dates are displayed.
Amount Formatting: Set your preferred format for numerical values.
Name: Update your name.
Password: Change your password for account security.
Font Size: Adjust the text size for better readability.
Dual Monitor Mode: Enable this feature if you’re using two monitors.
Logout
Logout: Click here to securely log out of your account.
This section offers a detailed overview of all invoices. It includes a search bar with various filters that you can select to quickly narrow down your results. Additionally, you can customize the arrangement of the column headers by using the drag-and-drop functionality for a more tailored viewing experience.
When working within the field validation section, users can utilize these shortcuts:
Enter – Moves the cursor to the next field in the validation sequence.
Tab – Validates the current field and automatically jumps to the next field that requires validation, skipping already validated fields.
Control + K – Opens the keyboard shortcut menu specific to the field validation section.
Control + H – Opens the documentation page for more information and assistance.
Space – Toggles a checkbox selection, allowing users to quickly mark or unmark options.
Control + G / Alt + G – Moves the focus to the next group of related fields, helping navigate structured input sections efficiently.
Control + F – Moves the cursor to the first field in the first group, allowing users to quickly return to the beginning of a form.
Control + S / Alt + S – Saves the document, ensuring all entered data is stored.
Options + R / Alt + R – Rejects the document, marking it as invalid or requiring further review.
Control + T / Alt + T – Jumps directly to the table section of the document.
Control + plus (+) / Alt + plus (+) Creates a new Table Line.
Step 1: Choose column names (tags)
Select column names: Review the column names of your table and decide which tags to add.
Step 2: Press "Apply" button
Press button: Once you have selected the appropriate tag for a column, press the "Apply" button next to the selected column and tag.
Step 3: Add tag to the table
Add tag: The selected tag will be added to the table as an additional column next to the corresponding column.
Step 4: Save or Delete Tag
Save Tag: Press the Save button to save the desired tag
Delete Tag: To delete the selected tag, press the Delete button
Description: Position or order of the item within the order.
Tag: Integer
Example: 1, 2, 3...
Description: Short description of the item.
Tag: Text
Example: Screw, Nut, Widget...
Description: The number of the associated order.
Tag: Alphanumeric
Example: PO12345, PO98765...
Description: Number of units ordered.
Tag: Number
Example: 100, 50, 200...
Description: Unit of measurement (e.g., piece, kilogram).
Tag: Text
Example: Pcs, kg, l...
Description: Price per unit of the item.
Tag: Currency
Example: €10.00, €5.50, €100.00...
Description: Total price before deductions and taxes (calculated as quantity * unit price).
Tag: Currency
Example: €1,000.00, €275.00, €10,000.00...
Description: Absolute discount amount applied to the net amount.
Tag: Currency
Example: €50.00, €20.00, €500.00...
Description: Discount percentage applied to the net amount.
Tag: Percent
Example: 5%, 10%, 15%...
Description: Amount of VAT applied to the item.
Tag: Currency
Example: €200.00, €55.00, €1,900.00...
Description: Final amount after discount is deducted and VAT is added.
Tag: Currency
Example: €1,150.00, €310.00, €11,400.00...
Description: Country where the item was manufactured or shipped.
Tag: Text
Example: USA, Germany, China...
Description: Unique identifier or SKU for the item.
Tag: Alphanumeric
Example: 987654, A12345, Z98765...
Description: Number of the associated delivery note.
Tag: Alphanumeric
Example: DN56789, DN12345...
Description: Additional comments, codes or relevant information.
Tag: Text
Example: Comment, Specification...
With this structure and tags, the table is more clearly defined and the information can be better categorized and processed.
The AI Extracted Table feature allows users to easily manipulate and customize the extracted data from the invoice document. Here are the key capabilities and usage instructions:
Deleting Columns: If certain columns in the extracted table are not needed, users can easily remove them by clicking the "Delete column" icon (represented by three vertical dots) next to the column header. This helps declutter the table and focus only on relevant information.
Changing Currency Format: The currency format can be changed by selecting the desired format from the dropdown menu next to the "Currency" field. This ensures that the currency values are displayed in the preferred format, making it easier to interpret and analyze the financial data.
Showing/Hiding Non-Mapped Columns: By default, only the mapped columns (columns with extracted data) are visible in the table. However, users can choose to show or hide the non-mapped columns by clicking the "Hide non mapped columns" or "Show non mapped columns" button at the bottom of the table. This feature is useful when users want to review all available columns, even if they don't currently contain data.
Changing Table Headers: The table headers (column names) can be modified by clicking on the header and entering the desired name. This feature allows users to customize the column names to better align with their terminology or preferences, making the data more readable and understandable.
These features provide users with flexibility and control over the extracted data, enabling them to tailor the information according to their specific needs and preferences. The AI Extracted Table aims to enhance the user experience by offering a seamless and intuitive way to interact with and analyze invoice data.
The validation screen in DocBits is designed to verify the accuracy and completeness of data contained within documents before they are processed or saved. This functionality is crucial for ensuring that all data is correctly read and processed, thereby maintaining data integrity and quality.
Ensuring Data Quality: The validation screen checks the accuracy and completeness of extracted data to prevent the entry of incorrect or incomplete information.
Data Integrity: It ensures that the data complies with specified requirements and standards.
Error Prevention: By facilitating early detection and correction of errors, the validation screen helps mitigate potential issues during subsequent data processing.
User Friendliness: The system provides immediate feedback to users when errors or inconsistencies are detected, allowing for prompt corrections.
Compliance: The validation screen helps ensure adherence to legal and organizational regulations and standards.
Efficiency: It reduces the effort required for future corrections and minimizes the need for manual checks.
Automatic Data Extraction:
Optical Character Recognition (OCR): Automatically reads text from scanned documents or images.
Structured and Unstructured Data: Processes data from various document types, including forms, invoices, and contracts.
Checking and Validating Data:
Format Validation: Ensures that data is in the correct formats (e.g., date formats, phone numbers, email addresses).
Required Fields: Confirms that all mandatory fields are completed.
Range Checking: Validates numeric data to ensure it falls within specified limits.
Consistency Checking: Verifies that related data fields contain consistent information (e.g., ensuring start and end dates align).
User Interaction and Troubleshooting:
Error Messages: Displays clear and actionable error messages when data does not meet validation requirements.
Manual Review and Correction: Allows users to manually review and amend data when automatic validations fail.
Data Cleaning and Standardization:
Automatic Correction: Suggests or performs automatic corrections when errors are detected.
Data Formatting: Standardizes data formats to ensure consistency across datasets.
Security and Access Rights:
Input Filters: Protects against malicious inputs through robust validation and filtering mechanisms.
Access Control: Ensures that only authorized users can access and modify sensitive data.
Data Consistency:
Cross Validation: Checks for consistency among related data fields (e.g., validating that start and end dates align).
Duplicate Entries: Prevents duplicate entries within the database.
User Guidance:
Error Messages: Provides specific and understandable error messages when entries do not comply with requirements.
Help and Hints: Offers help texts or tooltips to assist users in entering data correctly.
In summary, the validation screen in DocBits is instrumental in ensuring the quality of extracted data, facilitating early error detection and correction, and enhancing the overall efficiency of data processing workflows.
Save Button:
Purpose: Saves the current state of the document or script being worked on.
Use Case: After making changes or annotations to a document, use this button to ensure all modifications are saved.
Add Special Rules / Add Script in DocBits:
Purpose: Allows users to implement specific rules or scripts that customize how documents are processed.
Use Case: Use this feature to automate tasks like data extraction or format validation, enhancing workflow efficiency.
Fuzzy Fields:
Purpose: Helps in identifying and correcting fields where the data may not be a perfect match but is close enough.
Use Case: Useful in data validation processes where exact matches are not always possible, such as slightly misspelled names or addresses.
There are fields that are required for further editing, these can be edited in the settings.
Use the tool tip to find out if:
Is it a mandatory field (required)
Validation required
Low confidence
Full tax amount missmatch
Required Fields:
Purpose: Identifies mandatory fields within documents that must be filled out or corrected before further processing.
Use Case: Ensures that essential data is captured accurately, maintaining data integrity and compliance with business rules.
Magnifying Glass (Magnify Glass):
Purpose: Provides a zoomed-in view of a selected area of the document.
Use Case: Helps in examining fine details or small text in documents, ensuring accuracy in data entry or review.
Open New Window:
Purpose: Opens a new window for side-by-side document comparison or multitasking.
Use Case: Useful when comparing two documents or when referencing additional information without leaving the current document.
Keyboard Shortcuts:
Purpose: Allows users to perform actions quickly using keyboard combinations.
Use Case: Enhances speed and efficiency in document navigation and processing by minimizing reliance on mouse navigation.
To share internal information, you can create tasks and assign them to a specific employee or group within the company.
Tasks:
Purpose: Enables users to create tasks related to documents and assign them to team members.
Use Case: Facilitates collaboration and task management within teams, ensuring everyone knows their responsibilities.
Note: The approval history must be activated before it can be displayed here.
Approval History:
Purpose: Displays document approval history in field validation, with red indicating rejected and the app's color indicating approved.
Use Case: Useful for organizations that require a transparent record of approval actions during field validation.
You can leave annotations on a document. This can be helpful to leave information for other users who further edit this document.
Annotation Mode:
Purpose: Lets users leave notes or annotations directly on the document.
Use Case: Useful for providing feedback, instructions, or important notes to other team members who will work on the document later.
Documents can be merged here, for example if a page of an invoice was missing, these pages can be merged later in this way without the entire document having to be deleted or re-uploaded.
Merge Documents:
Purpose: Combines multiple documents into a single file.
Use Case: Handy in scenarios where parts of a document are scanned separately and need to be consolidated.
In the OCR view, the text is automatically filtered from the document. This is used to recognize relevant features, such as the postal code, contract number, invoice number and the sorting of a document.
OCR View:
Purpose: Automatically recognizes text within documents using Optical Character Recognition technology.
Use Case: Streamlines the process of digitizing printed or handwritten texts, making them searchable and editable.
Unlike tasks that are passed on internally within the company, this support ticket is important to notify us and to immediately create a ticket in the event of errors and/or discrepancies. This makes the process much easier because you can immediately send the bug with the appropriate document. There is also the option to set priority, take a screenshot of the document or upload one.
Create Ticket:
Purpose: Allows users to report issues or discrepancies by creating a support ticket.
Use Case: Essential for quick resolution of problems and bugs, helping maintain the integrity and smooth functioning of the system.
Scripts can be created in the settings under Document Types; this information will then be displayed here.
Document Script Logs:
Purpose: Displays logs related to scripts that have been implemented for different document types.
Use Case: Useful for tracking and debugging script actions on documents, helping users understand the automated processes and correct any issues.
There you will find the flow of the document
Purpose: Shows the sequence and progression of document processing within the system.
Use Case: Helps in tracking document status through different stages, ensuring that all necessary processing steps are followed.
With this option you will be redirected and can edit your layout or use the default template
Go to Layout Template:
Purpose: Redirects users to a layout editor where they can modify existing templates or apply a default one.
Use Case: Enables customization of document layouts to meet specific business needs or preferences, enhancing the document’s visual and functional alignment with company standards.
Purpose: Enables DocBits to use e-text for all documents from a specific supplier if available, improving extraction accuracy.
Use Case: Enhances text extraction by leveraging embedded text instead of OCR, which can lead to more precise results for this supplier.
Purpose: Allows selection between three different AI models to optimize extraction results for a specific supplier.
Use Case: Ensures better extraction accuracy by choosing the most suitable AI model for each supplier’s document structure and content.
See here add
A guide to uploading documents to DocBits.
The PO matching screen has dedicated shortcuts to streamline the matching process:
Tab – Moves between different menu points on the sidebar, allowing quick navigation without clicking.
Control + M – Moves between the buttons available in the PO matching section, helping users efficiently navigate action options.
Enter – Selects or clicks the currently focused button, confirming actions without needing to use the mouse.
Control + H – Opens the documentation for PO matching, providing immediate access to assistance.
Control + K – Opens the keyboard shortcuts menu, displaying all available shortcuts for this section.
Control + D – Enables or disables the purchase order training mode, allowing users to switch between normal and training modes.
Control + A – Performs automatic purchase order matching.
Control + S – Saves the document, ensuring all modifications are stored properly.
Control + R – Rejects the document, marking it for revision or additional verification.
Control + E – Exports the document, generating an export file based on the applied settings.
Control + F – Opens the purchase order search function, allowing users to quickly locate specific purchase orders.
Control + P – Selects the first row of the purchase order lines, making it easy to begin working with order data.
Control + L – Selects the first row of the invoice lines, allowing quick access to invoice details.
Control + Left Click – Selects or unselects rows of the purchase order, enabling flexible selection of multiple entries.
Control + C / Alt + C – Selects purchase order rows to begin mapping to invoice lines, setting up the mapping process.
Control + V / Alt + V – Maps the selected purchase order lines to the invoice lines, linking data efficiently.
Option + Shift + Left Click – Selects all purchase order lines between the first selected and the last selected row, simplifying the bulk selection process.
This document provides a comprehensive guide on how to use the Purchase Order Matching system within your ERP platform. The PO Matching system automates the reconciliation of purchase orders with incoming invoices, ensuring that financial transactions are accurate and discrepancies are addressed promptly.
To begin using the PO Matching system, ensure that you have the necessary permissions set up by your system administrator. You will need access to both the purchase order data and the corresponding invoice data within the system.
Access to purchase order and invoice modules within the ERP system.
Appropriate user permissions for viewing and matching financial documents.
Automatic Data Extraction: Automatically extracts and interprets data from digital invoices.
Data Comparison: Compares extracted invoice data against existing purchase order data.
Match Verification: Verifies matches based on predefined rules and tolerances.
Discrepancy Reporting: Identifies and reports any discrepancies between invoices and purchase orders.
Audit Trail: Maintains a log of all actions for compliance and review.
The PO Matching system interface typically includes the following components:
Dashboard: Overview of matching status and recent activity.
Search and Filter Tools: Capabilities to search and filter purchase orders and invoices.
Matched Records: Section displaying successfully matched records.
Discrepancies: Section showing records with discrepancies needing review or action.
Reports: Access to detailed reports and export options.
Navigate to the PO Matching module from the main menu of your ERP system.
Automated Import: If your system is set up for automated data capture, invoices will be imported automatically into the system.
Manual Upload: If necessary, manually upload invoice files into the system using the provided interface.
Review invoices that have been automatically matched with purchase orders.
Verify the details of the match, including item numbers, quantities, and prices.
Access the Discrepancies section to review any invoices that could not be automatically matched.
Manually adjust quantities or prices as needed, or flag the invoice for further review.
For invoices not automatically matched:
Use the search and filter tools to find the corresponding purchase order.
Ctrl + Click: Allows you to single-select multiple, non-contiguous lines one at a time. Each click on a line with Ctrl pressed toggles the selection of that line.
Shift + Click: Enables you to multi-select a range of lines. You Shift + Click on the starting line, then Shift + Click on the ending line, and all lines in between are selected.
Manually verify and match the invoice to the purchase order.
This feature helps you manage and reconcile item numbers between your system and your suppliers. Often, the item numbers you use internally may not match the item numbers your suppliers use. Docbits makes it easier to handle these discrepancies by creating a mapping between your item numbers and those of your suppliers.
Manual Matching:
The first time you encounter a discrepancy between your item number and your supplier's item number, you need to match them manually.
You can do this by entering the correct supplier item number corresponding to your internal item number.
Automatic Matching:
Once you have manually matched an item number with its supplier's item number, Docbits remembers this mapping.
The next time the same item appears, Docbits will automatically match it based on the stored mapping, saving you time and reducing errors.
Supplier ID: The unique identifier for the supplier.
Item Number: Your internal item number for the product.
Supplier Item Number: The corresponding item number used by the supplier.
Action: Options to manage the mappings, such as deleting incorrect mappings.
Efficiency: Reduces the need for repeated manual entry, making the process faster.
Accuracy: Minimizes errors by ensuring that item numbers are correctly matched.
Convenience: Simplifies the workflow by automating the matching process after the initial manual entry.
Docbits is an advanced system designed to automate the matching of purchase order data (POs) with incoming invoice documents. This tool is specifically designed for efficient management and processing of invoice data within ERP systems. This documentation explains the basics of automatic matching through Docbits and defines the specific rules required for successful matching.
Data Extraction: Docbits begins the process by extracting relevant data from digitized invoice documents. Typically, this data includes item numbers, quantities, and unit prices of each invoice line. The precision of this extraction is crucial, as it forms the basis for the subsequent matching process.
Comparison with PO Data: The extracted data are compared with the corresponding information in the stored purchase orders. Docbits checks whether the item numbers, quantities, and prices match those in the POs. For a successful match, the data in the invoices must correspond to the data in the purchase orders, considering defined tolerance thresholds.
Automatic Matching: Based on the comparison results, Docbits performs the matching. The system verifies whether the matching criteria fall within the set tolerance limits. If these criteria are met, the match is considered successful.
Reporting: After completing the matching process, Docbits generates reports that show the status of the matches. These reports inform about successfully matched invoices and identify those with discrepancies.
Item Number: The item number on the invoice must exactly match the item number in the purchase order. There is no tolerance for deviations in item numbers.
Quantities: The quantity of goods delivered on the invoice may vary within a predefined tolerance range. Typically, a tolerance of ±5% might be acceptable to account for minor differences in delivery quantities.
Prices: Price deviations are tolerable up to a set threshold. A common tolerance might be ±2% of the price to accept slight differences in price statements that arise from rounding differences or currency fluctuations.
Full Match: All data points (item number, quantity, and price) are within the set tolerance limits.
Partial Match: One or more data points deviate outside the tolerance limits, but the deviations are minimal and require manual review.
No Match: Significant deviations in one or more data points that require immediate correction or further investigation.
The precise definition of these rules and the setting of tolerance limits are crucial for the efficiency of the automatic matching and the reduction of manual interventions. Docbits allows for flexible configuration of these parameters to meet the needs of various businesses and industries.
Welcome to the Accounting for Cost Invoice and Indirect Sales module! This module is designed to help you efficiently manage and reconcile your financial transactions within your ERP system. With features like automatic data extraction, document matching, and detailed tracking, you can ensure that your financial records are accurate and up-to-date.
To start using the accounting module, make sure you have the necessary permissions set up by your system administrator. You will need access to both the cost accounting and sales accounting modules within the ERP system.
Access to the cost accounting and sales accounting modules within the ERP system.
Appropriate user permissions for viewing and processing financial documents.
Automatic Data Extraction: Automatically extracts and interprets data from digital invoices and other documents.
Data Comparison: Compares extracted invoice data against existing purchase order data.
Match Verification: Verifies matches based on predefined rules and tolerances.
Discrepancy Reporting: Identifies and reports any discrepancies between invoices and purchase orders.
Audit Trail: Maintains a log of all actions for compliance and review.
Document Training: Train the system to recognize new documents with minimal effort, typically only once.
Amount Splitting: Split amounts by department for detailed financial tracking.
Ledger Account Definition: The APS (Accounting and Procurement System) team can define the ledger account once the data is extracted.
The accounting module interface typically includes the following components:
Dashboard: Overview of invoice and sales status, and recent activity.
Search and Filter Tools: Capabilities to search and filter invoices and sales records.
Matched Records: Section displaying successfully matched records.
Discrepancies: Section showing records with discrepancies needing review or action.
Reports: Access to detailed reports and export options.
Navigate to the accounting module from the main menu of your ERP system.
Automated Import: If your system is set up for automated data capture, invoices will be imported automatically into the system.
Manual Upload: If necessary, manually upload invoice files into the system using the provided interface.
Review invoices that have been automatically matched with purchase orders.
Verify the details of the match, including item numbers, quantities, and prices.
Access the Discrepancies section to review any invoices that could not be automatically matched.
Manually adjust quantities or prices as needed, or flag the invoice for further review.
For invoices not automatically matched:
Use the search and filter tools to find the corresponding purchase order.
Manually verify and match the invoice to the purchase order.
For new document types, train the system to recognize them by providing a sample.
Typically, you only need to train the system once for it to accurately recognize similar documents in the future.
Navigate to the "Line items" tab to view and record bookings for each invoice.
Allocate the amounts to the appropriate accounts, cost centers, and dimensions specific to Infor LN/M3.
Select Line Item: Choose the line item for the cost invoice.
Assign Account: Assign the appropriate account, such as "71200 - Non-Operating Expense".
Set Dimensions: Set additional dimensions like cost center, product group, and project.
Split Amount: If necessary, split the amount by department for more detailed tracking.
Enter Amount: Enter the amount for the line item.
Once the data is extracted, the APS team can define the ledger accounts.
This ensures that each transaction is recorded under the correct account for accurate financial reporting.
Access the "Reports" section to generate detailed reports on financial transactions.
Use export options to save reports for further analysis or record-keeping.
Uploading Documents: Users can upload various documents (invoices, delivery notes, etc.) to the system.
Automatic Matching: The system automatically matches the uploaded documents with existing purchase orders.
Reviewing Matches: Users can review the matches, verify details, and see status indicators.
Resolving Discrepancies: Any mismatches or discrepancies are highlighted for the user to manually review and correct.
Exporting Data: Matched data can be exported for further processing or record-keeping.
\
See here the as well
With the Webhook API provided below, you can easily transfer documents directly to DocBits with a simple POST request. This API is designed to simplify the process of uploading files to DocBits, and all the necessary parameters are already filled in for you.
To get started, simply go to the following page (depending on the environment you are using):
PROD: https://api.docbits.com/docs#/document/process_documents_document_process_documents_post
SANDBOX: https://sandbox.api.docbits.com/docs#/document/process_documents_document_process_documents_post
STAGE: https://stage.api.docbits.com/docs#/document/process_documents_document_process_documents_post
Make a call to the API using your API key. You can also include the file you want to upload as a parameter in your call.
Here you just need to enter the required information for your email provider, encryption, server name, port, username, email address, password as well as the email folder.
Things to Note
Input all needed information into the UI. Other information like the server, port, etc. Depends on the host (a quick Google search should help).
Folder and Move-Imported have the same Function here. Folder can not be disabled, but will use Inbox by default if left empty.
If you would like to integrate your SFTP with DocBits in order to import documents.
Requirements
Correctly configured, Linux compatible SFTP Server
SFTP Hostname, Username and Password
Dedicated Import folder
Import Configuration
From the Dashboard, open Settings and navigate to Import. Under FTP Import, select to add a new configuration.
Enter SFTP credentials in the given spaces and select save (The API Key field will automatically be filled with the API Key of the environment you are working on).
Once you have entered all the necessary details of your SFTP, click SAVE.
Enable File Archiving
Locate the "File Archiving" option.
Toggle the switch to the "On" position to enable archiving.
Select the Archive Directory
Once the "File Archiving" switch is enabled, a field will appear allowing you to specify the directory path for archived files.
Select the desired folder path on the SFTP/FTP server where the archived files should be stored.
Save Changes
Click the Save button to apply the changes.
Go to the Settings menu and select “Import” under Document Processing.
Scroll to the bottom of the page and select the NEW button to create a new email import.
After pressing NEW, the following menu will be shown to you.
Here you can select which Protocol you would like.
Help icons have been placed all around DocBits in order to assist you in learning and understanding what a feature really does and how it can assist you with your document processing.
These help icons look as follows
This is a tool available to you, on the validation screen, in the event of some sort of issue occurring when validating your document in DocBits.
This feature is located in the menu above the document preview area, like below
Once clicked, the following ticket form will be displayed to you.
This is where you will fill in your details as well as describe the error. You can also ,if applicable, attach a screenshot of the issue and attach a relevant file.
Here you just need to enter your desired sub organization and press ‘Authenticate’
You will be taken to this Microsoft page and you will need to enter a code.
This code can be found by clicking back to DocBits and the code will be displayed there like below, simply copy the code and enter it into the Microsoft page. Thereafter you will need to enter your own Microsoft credentials.
Press the FINISH AUTHENTICATION button and you will be taken to this menu
Use Folder
If you are using a folder other than your inbox, enter the folder name after enabling the slider.
Use Shared Mailbox
If you want the email import to access an inbox or a folder of a shared mailbox, input the email address here after enabling the slider.
Move imported emails to trash
If you want to import all emails, not just the unread ones, and have them moved to trash then activate this. If not, it will only check for unread emails, import the documents, set the email to read and leave it in its current place.
In the event of you receiving an error message indicating you do not have the rights to establish such a connection, someone with admin rights within Azure would need to authorize this connection. For more information, visit the following page: https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/grant-admin-consent?pivots=portal#grant-tenant-wide-admin-consent-in-enterprise-apps
If you’re looking to import documents manually into DocBits, follow these simple steps:
Click on the Upload button on the DocBits Dashboard.
A window will appear where you can upload your documents via file browser or drag and drop. You can upload up to 10 documents at once.
To upload documents via file browser, click on the Upload Documents button and select the files you want to upload. Once you’ve selected the files, click on Confirm to start the upload process.
Alternatively, you can drag and drop your files onto the DocBits import window.
After the files have been uploaded, they will have the initial status of “Running”. During this time, the upload is being processed and editing the file is not possible. The processing time may vary depending on the size and complexity of the file.
Once the file has been processed, it will receive the status of “Ready For Validation”. You can now start the validation process.
This is a tool available to you, on the validation screen, in the event of some sort of issue occurring when validating your document in DocBits.
This feature is located in the menu above the document preview area, like below
Once clicked, the following ticket form will be displayed to you.
This is where you will fill in your details as well as describe the error. You can also ,if applicable, attach a screenshot of the issue and attach a relevant file.
Help icons have been placed all around DocBits in order to assist you in learning and understanding what a feature really does and how it can assist you with your document processing.
These help icons look as follows
Welcome to the DocBits Beginner Course, your comprehensive guide to revolutionizing document management for your business!
In today's complex financial environment, managing order confirmations, delivery bills, invoicing, and cost accounting is no small feat. That's where DocBits shines. With over 20 integrations and unparalleled compatibility with Infor CloudSuite, LN, and M3, DocBits stands apart from other solutions on the market.
In this comprehensive video guide, viewers are introduced to the DocBits dashboard and its array of functionalities. From filtering and managing open documents to importing attachments via various channels such as email, scanner, or API, the tutorial offers a step-by-step walkthrough.
Key features are highlighted, including how to filter documents by status or assignee, locate specific details like invoice numbers, and change the assignee for individual documents. The ease and efficiency of the system are demonstrated, emphasizing the control and customization it offers . The tutorial sets the stage for a deeper exploration of within DocBits.
In this video, viewers are introduced to DocBit‘s user-friendly interface, specifically focusing on document validation. The tutorial emphasizes the simplicity of the system, where no coding or complex formulas are required.
Thanks to AI and Swarm Intelligence, most fields are extracted automatically, allowing to easily extract information by clicking on values within the document. Additionally, viewers learn about the flexibility of extracting specific areas by double-clicking or drawing around the desired region.
Explore the revolutionary capabilities of DocBits, a state-of-the-art document handling tool that simplifies the complexities of table extraction, Purchase Order (PO) matching, and cost invoice management.
In this video, we delve into the unique features of DocBits, focusing on the AI table extraction that effortlessly handles even the most intricate table layouts. With an accuracy rate of up to 95%, the system automates extraction, allowing you to focus on what truly matters.
\
In our document processing system, we handle a large volume of documents from multiple customers daily. To ensure that every customer's documents are processed in a timely manner, we have implemented a sophisticated priority system. This system dynamically adjusts priorities based on the number of pending documents a customer has, ensuring fairness and efficiency. Let's dive into how this priority system works and when the task counter is reset.
Key Concepts of the Priority System
Our priority system revolves around a few key concepts:
Pending Documents: This is a count of the documents a customer has submitted but are yet to be processed.
Reset Interval: The system periodically resets the pending document count to zero to ensure that no customer can monopolize the processing resources indefinitely.
How the Priority is Determined
Here's a step-by-step explanation of how the priority for processing documents is determined:
Tracking Pending Docuemnts: Each customer has a count of pending documents. This count helps us know how many documents are waiting to be processed for each customer.
Resetting the Count: To maintain fairness, we reset the pending documents count to zero if a set amount of time (the reset interval) has passed since the last update. This interval is set to 1500 seconds (or 25 minutes) by default.
Updating the Count: If the reset interval hasn't passed, we reduce the pending documents count by one each time we check, simulating the processing of a document.
Setting Priorities: The priority for processing tasks is based on the number of pending documents. The fewer the pending documents, the higher the priority, meaning those tasks will be processed sooner. We have specific thresholds to assign priority levels from 1 (highest priority) to 9 (lowest priority).
Priority Levels
The priority levels are assigned based on the pending documents count as follows:
Priority 9: If the pending documents count is less than -20
Priority 8: If the pending documents count is less than -14
Priority 7: If the pending documents count is less than -12
Priority 6: If the pending documents count is less than -10
Priority 5: If the pending documents count is less than -8
Priority 4: If the pending documents count is less than -6
Priority 3: If the pending documents count is less than -4
Priority 2: If the pending documents count is less than -2
Priority 1: If the pending documents count is greater than or equal to -2
When the Counter is Reset
The pending documents counter is reset to zero if more than the reset interval (1500 seconds) has passed since the last update. This mechanism ensures that no customer can accumulate pending documents endlessly and hog the system resources. By periodically resetting the counter, we guarantee that every customer gets a fair share of processing time.
If you're using DocBits Supplier Portal, it's important that you understand the different statuses that your suppliers can have. Here’s a complete list of all the possible supplier statuses in DocBits:
Open: Existing supplier who has not yet been invited
Pending Registration: Supplier has been invited to the supplier portal
Pending Supplier Input: Awaiting changes from the supplier after he completed the registration
Pending Approval: Supplier has finished registration, is waiting for the first approval
Pending AP Approval: Supplier has been approved the first time, awaiting second approval
Approved: Supplier has been approved
Rejected: Supplier has been rejected
This document outlines the testing plan for invoice automation using DocBits with Infor LN or M3. It includes details of test cases, testing preparation, execution steps, and support processes.
1
Cost Invoices
Invoices with no purchase order are processed successfully in DocBits and exported to LN as “cost invoice”.
TO BE TESTED
2
Purchase Order Related Invoice with Perfect Matching
Purchase order-related invoices are processed successfully in DocBits with a perfect match from invoice to PO, since item number, quantity, and unit price match.
TO BE TESTED
3
Purchase Order Related Invoices with Different Quantity
Purchase order-related invoices are processed in DocBits but in the PO matching module, we have a mismatch on the quantity.
TO BE TESTED
4
Purchase Order Related Invoices with Different Unit Price
Purchase order-related invoices are processed in DocBits but in the PO matching module, we have a mismatch on the unit price.
TO BE TESTED
5
Purchase Order Related Invoices with Different or Non-Existing Item Number
Purchase order-related invoices are processed in DocBits but in the PO matching module, we have a mismatch or a non-existing item number.
TO BE TESTED
6
Purchase Order Related Invoices with a Mismatch within Tolerance
Purchase order-related invoices are processed in DocBits but in the PO matching module, we have a mismatch on quantity or unit price, but it’s within tolerance.
TO BE TESTED
7
Credit Notes
Credit notes are successfully processed in DocBits and exported to LN. Clarify whether amounts should be exported with a positive or negative sign.
TO BE TESTED
Initial Meeting: Schedule a kickoff meeting with the customer to explain the testing process and objectives.
Access and Permissions: Ensure the customer has all necessary access to DocBits and Infor LN or M3 for testing purposes.
Training: Provide comprehensive training to the customer’s team on how to use DocBits for invoice processing.
Documentation: Share detailed documentation on the testing procedures, including expected outcomes for each test case.
Testing Environment: Set up a testing environment that replicates the customer's production system as closely as possible.
Step-by-Step Testing: Work with the customer to execute each test case, ensuring they understand each step:
Process invoices through DocBits.
Verify the output in the PO matching module.
Check the export results in LN or M3.
Tracking: Use a tracking system (like Jira or a simple spreadsheet) to log any issues or mismatches that occur during testing.
Support: Provide immediate support to resolve issues and clarify any doubts.
Verification: After each test case, verify the results with the customer to ensure accuracy.
Feedback Loop: Collect feedback from the customer on the process and any improvements needed.
Documentation of Results: Document the results of each test case and provide a summary report to the customer.
Review Meeting: Conduct a review meeting to discuss the testing outcomes and any further steps required before going live.
Training Refresh: Offer a refresher training session if necessary.
Support Plan: Develop a support plan for the initial go-live phase to ensure smooth transition.
Supplier Details
Please verify that the Supplier name is correct. This is a critical detail for identity and legal purposes that cannot be changed. Please provide all applicable information including the required fields. When completed, click on “Next” to continue to the Address Data section. To save your progress and continue later, click on “Save.”
Address Data Please provide all applicable information including the required fields. When completed, click on “Next” to continue to the Supplier Contact section. To save your progress and continue later, click on “Save.”
Supplier Contact Please provide all applicable information including the required fields. When completed, click on “Next” to continue to the Supplier Financial section. To save your progress and continue later, click on “Save.”
Supplier Financial Please provide all applicable information. When completed, click on “Next” to continue to the Supplier Purchase section. To save your progress and continue later, click on “Save.”
Supplier Purchase Please provide all applicable information. When completed, click on “Next” to continue to the Supplier Certificates section. To save your progress and continue later, click on “Save.”
Supplier Certificates Please upload all certificates required (Tax, Insurance, Vendor Diversification). Please save your progress if you need to return to complete the registration process later. When completed, click on “Send for Approval.”
Please upload all certificates required (Tax, Insurance, Vendor Diversification). Please save your progress if you need to return to complete the registration process later. When completed, click on “Send for Approval.”
Please check your E-mail for a confirmation that you have completed the registration process.
Should you face any challenges or have inquiries when using DocBits, please consult this user manual or reach out to our support team for help. Our commitment lies in providing a seamless experience for all users. Simply click on the support button in your DocBits app and you can create a support ticket.
You can also contact us via our FELLOWPRO page:
Inside the Validation Screen you can directly create tickets for the particular document and include a screenshot of the issue. Simply click on the "Create ticket" button, the support window opens and you can get started immediately.
Discover in this video how to professionally handle discrepancies during PO matching with DocBits. We guide you step by step through what to do when numbers don’t align. Whether you’re an experienced ERP manager or an aspiring financial accountant, you’ll learn how to efficiently and securely manage discrepancies.
Learn how our special AI swarm intelligence in DocBits leads you through the entire process and how you can use our documentation to quickly find solutions to problems or uncertainties. Join the many satisfied customers who have optimized their processes with DocBits.
Global Settings:
Company Information: Define and edit basic details about the company, like name, address, and other identifiers.
Groups, Users and Permissions: Manage user roles and permissions, allowing different levels of access to various features within DocBits.
Integration: Set up and configure integrations with other software or systems, enhancing DocBits' functionality with external services.
Document Types: Specify and manage different types of documents that DocBits will process, such as invoices, orders, etc.
Email Notification: Configure settings for email alerts and notifications related to document processing activities.
Dashboard: Customize the dashboard view with widgets and metrics that are important for the users.
Document Processing:
Documents Expiry: Set rules for how long documents are retained before being archived or deleted.
Import: Configure how documents are imported into DocBits, including source settings and file types.
OCR Settings: Adjust settings for Optical Character Recognition (OCR) that converts images of text into machine-encoded text.
Classification and Extraction: Define how documents are categorized and how data is extracted from documents.
Master Data Lookup: Set up lookups for validating or supplementing extracted data with pre-existing master data.
List of Values: Manage predefined lists that are used in data entry and validation.
Export: Configure how and where processed documents and data are exported.
Module: Additional modules that can be configured to extend functionality.
API Licenses: Manage API keys and monitor usage statistics for APIs used by DocBits.
Supplier Settings: Configure and manage settings specific to suppliers, possibly integrating with supplier management systems.
Cache Management: Adjust settings related to the caching of data to improve performance of the system.
You will receive an invitation with a link via E-mail to begin the registration process. Please click on “Go to Registration,” submit the required information, and accept the terms and conditions to get started.
The role of an administrator is crucial for managing IT systems, networks and digital platforms in an organization. An administrator has advanced permissions and responsibilities that allow them to control various aspects of the technical infrastructure and ensure that it is operated efficiently and securely. Here are some of the main responsibilities of an administrator:
User management: Administrators manage user accounts, access rights and permissions. They create new user accounts, assign them the necessary permissions and manage access control to ensure that only authorized users can access certain resources.
Security: Administrators are responsible for the security of IT systems to protect against data loss and unauthorized access.
Troubleshooting and support: The administrator is often the first point of contact for technical issues. They help users troubleshoot and resolve problems and ensure that the system is running smoothly.
In addition to these responsibilities, administrators are also tasked with managing sensitive settings and ensuring that systems meet compliance requirements and information security best practices. This includes managing sensitive data, configuring access controls and permissions, and monitoring and analyzing system logs to identify and address potential security risks.
Security is an essential aspect of any organization, especially when it comes to managing user accounts and access rights. Here are some best practices to maintain a secure user management protocol:
Regular password updates: Encourage users to update their passwords regularly to keep their accounts secure. Establish password complexity policies and require the use of strong passwords that include a combination of letters, numbers, and special characters.
Monitor administrator actions: Implement mechanisms to monitor administrator activities to detect suspicious or unusual activity. Log all administrator actions, including access to sensitive data or settings, to ensure accountability and identify potential security breaches.
Limit the number of administrators: Reduce the number of administrators to a minimum and grant administrative privileges only to those who really need them. By limiting the number of administrators, you minimize the risk of security breaches and make it easier to manage and monitor user accounts.
Zwei-Faktor-Authentifizierung (2FA): Implementieren Sie eine Zwei-Faktor-Authentifizierung für Administratorkonten, um die Sicherheit zusätzlich zu erhöhen. Dadurch wird ein zusätzlicher Sicherheitsschritt eingeführt, der sicherstellt, dass selbst bei Kompromittierung eines Kennworts ein Angreifer keinen unbefugten Zugriff auf das Konto erhält.
Regelmäßige Sicherheitsüberprüfungen: Führen Sie regelmäßige Sicherheitsüberprüfungen und Audits durch, um potenzielle Sicherheitslücken oder Schwachstellen zu identifizieren und zu beheben. Überprüfen Sie die Zugriffsrechte und Berechtigungen von Benutzerkonten, um sicherzustellen, dass sie den aktuellen Anforderungen und Best Practices entsprechen.
Training and awareness: Regularly train employees and administrators on security best practices and awareness of phishing attacks and other cyber threats. Make them aware of the importance of security and encourage them to report suspicious activity.
By implementing these best practices, organizations can improve the security of their user management protocol and minimize the risk of security breaches and data loss. It is important to view security as an ongoing process and make regular updates and adjustments to keep up with ever-changing threats and security requirements.
Company Name: The legal name of the company as registered.
Street + Number: The physical address of the company's main office or headquarters.
Postal code: The ZIP or postal code for the company's address.
City: The city in which the company is located.
State: The state or region where the company is based.
Country: The country of operation for the company.
Company ID: A unique identifier for the company, which could be used internally or for integrations with other systems.
Tax-ID: The tax identification number for the company, important for financial operations and reporting.
Commercial Register ID: The registration number of the company in the commercial register, which could be important for legal and official documentation.
Official Company Phone Number: The primary contact number for the company.
Official Company Email: The main email address that will be used for official communications.
The information entered here can be crucial for ensuring that documents such as invoices, official correspondence, and reports are properly formatted with the correct company details. It also helps in maintaining consistency in how the company is represented in various external communications and documents. After entering or updating the information, the administrator needs to save the changes by clicking the "Save" button to ensure all modifications are applied system-wide.
Additionally, the section provides a view of the subscription plan, showing how many days are left, start and end dates, and a subscription usage meter that tracks the consumption of service tokens against what's allocated in the plan. This can help administrators monitor and plan for the subscription renewals or upgrades based on the usage trends.
The App Color setting allows administrators to define the color scheme of the application interface. This feature is particularly useful for distinguishing between different environments such as testing, sandbox, and production. By assigning distinct colors to each environment, users can easily identify which environment they are working in, reducing the risk of performing critical actions in the wrong environment.
Navigate to Company Settings:
From the main menu, click on the Company Information section.
Locate the App Color Section:
Scroll down to the App Color section within the Company Information settings.
Choose a Color:
Click on the color box or enter a hex code directly into the text field.
A color picker will appear, allowing you to select the desired color.
You can enter a specific hex code if you have a predetermined color for the environment.
Save the Color:
Once you have selected the color, click on the Save button to apply the change.
The application interface will immediately update to reflect the new color.
Reset to Default:
If you wish to revert to the default color, click the Reset button.
To avoid confusion, it is recommended to establish a standard color scheme for each environment:
Production: Use a neutral or default color, such as #FFFFFF (white) or #f0f0f0 (light grey), to indicate the live environment.
Testing: Use a bright or alerting color, such as #ffcc00 (yellow) or #ffa500 (orange), to indicate a testing environment.
Sandbox: Use a distinct color, such as #007bff (blue) or #6c757d (grey), to indicate a sandbox or development environment.
Under the App Color section, administrators will also see information related to the Subscription Plan. This includes the current plan, its status, and the remaining days of subscription.
The App Color setting is a simple yet effective tool to help users quickly recognize the environment they are working in. By carefully selecting and managing these colors, organizations can minimize errors and improve workflow efficiency.
User Settings is an area in a system where users can adjust personal preferences, account settings, and security settings. Typically, user settings include options such as password changes, profile information, notification preferences, and possibly individual permissions to access certain features or data.
In most organizations, only authorized people have access to user settings, usually administrators or system administrators. This is because the settings may contain sensitive information that could compromise the security of the system if changed by unauthorized persons. Administrators are able to manage user settings to ensure that they comply with organizational policies and requirements and that the integrity of the system is maintained.
Search Bar: Allows administrators to quickly find users by searching for their names or other details.
User List: Displays a list of users with the following columns:
Name: The full name of the user.
Email: The user's email address, which is likely used as their login identifier.
Admin: A checkbox indicating whether the user has administrative privileges. Admins typically have access to all settings and can manage other user accounts.
Actions: This column typically includes buttons or links for performing actions such as editing user details, resetting passwords, or deleting the user account.
Add User Button: This button is used to create new user accounts. Clicking on it would typically bring up a form where you can enter the new user's details, such as their name, email, and whether they should have admin rights.
Access User Management: Navigate to Settings - Global Settings - Groups, User and Permissions - User, where you can add new users.
Add new user: In the user settings, click on “Add user”
Filling out the form: A form will appear where you can enter the information for the new user. Typical information includes:
Username: Unique name for the user used to log in.
First Name and Last Name: Name of the user.
Email Address: The user's email address used for communications and notifications.
Password: A password for the user that should comply with security policies.
User Role: Set the user's role, e.g. B. Standard user or administrator.
Logging in as an administrator: Log in with your administrator privileges.
Accessing user management: Navigate to user settings where you can edit existing users.
Selecting users: Find and select the user whose details you want to change. This can be done by clicking on the username or an edit button next to the user.
Editing user details: A form will appear containing the user’s current details. Edit the required fields according to the changes you want to make. Typical details to edit include:
First and last name
Email address
User role or permission level
Saving Changes: Review any changes you made and click Save to save the new user details.
Review the impact of role changes: If you changed the user's user role, review the impact of that change on security access levels. Make sure that after the role change, the user has the permissions required to continue performing their duties.
Send notification (optional): You can send a notification to the user to inform them of the changes made.
After completing these steps, the user details are successfully updated and the user has the new information and permissions according to the changes made.
Selecting Users: Find and select the user whose access you want to remove. This can be done by clicking the user name or an edit button next to the user.
Removing Access: Click "delete" to remove the user.
Confirmation: You are asked to confirm the user’s removal.
Optional Notification: You can optionally send a notification to the user to inform them of the removal of their access.
Review Tasks and Documents: Before removing the user, review what tasks or documents are assigned to the user. Move or transfer responsibility for those tasks or documents to another user to make sure nothing gets lost or left unfinished.
Save Changes: Confirm the user’s removal and save the changes.
By following these steps, you can ensure that the user’s access is safely removed while properly managing all relevant tasks and documents.
Creating suborganizations within a document management system serves to further organize and differentiate the structure and management of user accounts, documents, and workflows within an organization. Here are some purposes and benefits of creating suborganizations:
Structuring and organization: Suborganizations make it possible to create a hierarchical structure within the document management system. This can help organize user accounts and documents by department, team, location, or other relevant criteria for clearer and more efficient management.
Permission management: By creating suborganizations, administrators can set granular permissions and access controls for different groups of users. This means that specific users or groups can only access the documents and resources relevant to their respective sub-organization, improving security and privacy.
Workflows and Collaboration: Suborganizations can facilitate collaboration and communication within specific teams or departments by centralizing access to shared documents, projects, or tasks. This promotes efficiency and coordination when collaborating on common projects or workflows.
Reporting and analysis: By organizing user accounts and documents into sub-organizations, detailed reports and analysis can be created on the activities and performance of individual teams or departments. This allows administrators and managers to gain insight into document management system usage at an organizational level.
Scalability and Flexibility: Sub-organizations provide a scalable structure that can grow with the organization's growth and changes. New teams or departments can be easily added and appropriately integrated into the existing sub-organizational scheme without affecting the overall structure of the document management system.
Overall, suborganizations enable more effective management and organization of user accounts, documents, and workflows within a document management system by improving structure, security, and collaboration.
In Settings, Global Settings → Groups, Users and Permissions → Sub-Organizations as shown below.
You will then be taken to a page that looks similar to this:\
This is where you will find your previously created sub-organizations, as well as where you can create new sub-organizations.
Overview: For organizations with multiple sub-organizations enabled, DocBits introduces the Cross Sub-Organisations feature. This enhancement allows users to manage documents across all sub-organizations under a single umbrella. Both administrative and non-administrative users can now access and view documents from every sub-organization without the need to switch between them individually.
Benefits:
Centralized visibility of all documents across sub-organizations.
Simplified navigation to locate specific files.
Maintains a comprehensive overview of document activity.
How to Use:
Enable Cross Sub-Organisations:
Navigate to the dashboard.
On the top-right corner, where sub-organizations can be switched, select Cross.
The page will reload, granting you access to all documents across all sub-organizations.
Disable Cross Sub-Organisations (if not needed):
Return to the top-right corner of the dashboard.
Deselect the Cross option to return to viewing a single sub-organization.
Navigate to Group Settings: Log in to your admin account and go to Group Settings in the admin panel.
This window will open:
Click the + New button: If you want to add a new group, click the + New button to start the process of adding a new group.
Fill out the table: Provide the group name and a description of the group.
Save the details: Once you have filled in the group and description, click the "Save" button.
Edit Groups: To edit groups, click on "edit", here you can change the group name
Enable Groups & permissions: To make the group visible, "Groups & permissions" must be enabled.
Check the results: After saving, review the results to make sure the group was successfully added, edited, or updated.
Click on the + NEW
button
The following menu will be displayed:
Enter the details of the sub-organization you want to create, the name and description, then click on the SAVE
button. You should then find your newly created sub-organization at the bottom of the list of existing sub-organizations.
Manage Users:
Adding Users: Administrators can create new user accounts and assign them to the appropriate sub-organization.
Assigning Roles and Permissions: Administrators can set the roles and permissions for users within a suborganization. This typically involves assigning access rights to specific documents, folders or functions in the document management system.
Manage profile details: Administrators can edit profile details of users within the sub-organization, such as: B. Contact information or department affiliation. This allows for updated and accurate management of user data.
You can add a new user to the organization and have the option of whether to remove the user from other groups.
Edit User:
Editing suborganization settings: Administrators can edit the settings and properties of a suborganization, including its name, description, or hierarchy level within the system.
Edit user details: Administrators can edit the details of individual users within a sub-organization, for example to adjust their access rights or update their contact information.
Delete User:
Deleting sub-organizations: Administrators may also have the ability to delete sub-organizations if they are no longer needed or if a restructuring of the organizational structure is required. When deleting a suborganization, administrators must ensure that all users and data associated with it are handled properly.
These management features enable administrators to effectively manage and adapt the user accounts and organizational structures within a document management system to meet the company's changing needs and processes.
Activate/Deactivate Groups and Permissions: A toggle that allows the system administrator to enable or disable the use of groups and permissions across the platform. When turned off, the system may default to a less granular access control model.
Group List: Shows the list of available user groups within the organization. Each group can be configured with specific permissions. Administrators can add new groups by clicking the "+ New" button.
Permissions Table:
Displayed once a group is selected or a new group is being configured.
Lists all document types recognized by the system (e.g., INVOICE, CREDIT_NOTE, DELIVERY_NOTE).
For each document type, there are checkboxes for different permissions:
View: Permission to see the document.
Update: Permission to modify the document.
Delete: Permission to remove the document from the system.
First Approval: Permission to perform the initial approval of the document.
Second Approval: Permission to perform a secondary level of approval (if applicable).
Groups and permissions allow administrators to control access to sensitive data and resources.
By assigning permissions at the group level, administrators can exercise granular control over who can access what information.
This helps prevent unauthorized access and data leaks.
The Least Privilege Principle states that users should only be given the permissions they need to perform their jobs.
By using groups, administrators can efficiently manage permissions and ensure that users can only access the resources relevant to their particular role or department.
Using groups makes it easier to manage user permissions in large organizations with many users and resources.
Instead of setting permissions individually for each user, administrators can assign permissions at the group level, simplifying administration and reducing administrative overhead.
Using groups and permissions allows organizations to monitor access activities and meet compliance requirements.
Logging access events allows administrators to perform audits to ensure that permissions are properly managed and that unauthorized access is not occurring.
Groups and permissions provide flexibility to adapt to changing needs and organizational structures.
Administrators can create groups based on departments, teams, projects, or other criteria and dynamically adjust permissions to ensure users always have access to the resources they need.
Overall, groups and permissions play a key role in increasing the security of IT infrastructure, improving operational efficiency, and ensuring compliance with policies and regulations. By managing groups and permissions wisely, organizations can effectively protect their data and resources while promoting employee productivity.
In a company with different departments such as finance, marketing, and human resources, employees in each department will need access to different types of documents and resources.
For example, the finance team needs access to financial reports and invoices, while HR needs access to employee data and payroll.
In a healthcare organization, different groups of employees will need different levels of access to patient data.
For example, doctors and nurses will need access to medical records and patient histories, while administrative staff may only need access to billing data and scheduling.
In an educational institution such as a university, different groups of users will need different levels of access to educational resources.
For example, professors will need access to course materials and grades, while administrators will need access to financial data and student information.
Companies may need to implement different levels of access to meet legal and compliance requirements.
For example, financial institutions may need to ensure that only authorized employees have access to sensitive financial data to ensure compliance with regulations such as the General Data Protection Regulation (GDPR).
In a project team, different members may require different levels of access to project materials.
For example, project managers may need access to all project resources, while external consultants may only have access to certain parts of the project.
In these scenarios, it is important that access levels are defined according to the roles and responsibilities of user groups to ensure the security of data while improving employee efficiency. By implementing role-based access control, organizations can ensure that users can only access the resources required for their respective function.
Enabling or disabling the permission system using the switch has various effects on the functionality in DocBits.
When the permission system is enabled, the access permissions for users and groups are applied.
Users are only granted access to the resources they are explicitly authorized to access based on the permissions assigned.
Administrators can manage the permissions for individual users and groups and ensure that only authorized people can view or edit the data.
The Only Assigned Documents toggle button controls the visibility of documents for users based on their group assignments. When enabled, users can only view documents that are specifically assigned to them or a group they belong to. When disabled, users with the appropriate view permission can see all documents, regardless of assignment.
Off State (Default):
When the toggle is off, users who are part of a group can view all documents if they have the appropriate view permission. Document assignment does not affect visibility.
On State:
When the toggle is on, users can only view documents that are explicitly assigned to them or a group they are a part of. This enforces stricter document visibility based on group assignments.
Default (Off State):
A user who is part of the "Sales" group can see all documents in the system that they have permission to view, even if they are not assigned to those documents.
Enabled (On State):
A user in the "Sales" group can only view documents that are assigned to them or the "Sales" group, restricting access to documents outside of their assignments.
When the permission system is disabled, all access permissions are removed and users typically have unrestricted access to all resources.
This can be useful when open collaboration is temporarily required without the restrictions of access control.
However, there may be an increased risk of data leakage or unauthorized access as users may be able to access sensitive information they are not authorized to access.
Enabling or disabling the permission system is an important decision based on the security requirements and the way the organization operates. In environments where privacy and access control are critical, it is common to leave the permission system enabled to ensure data integrity and confidentiality. In other cases, disabling the permission system may be temporarily necessary to facilitate collaboration, but should be used with caution to minimize potential security risks.
This guide explains how administrators can define access control settings for different user groups in DocBits. Each group can be configured with custom permissions at the document and field level.
The access control panel allows the admin to manage user groups and their respective permissions. Each group can have specific configurations related to:
Document Access: Whether the group can access a document type.
Field-Level Permissions: Whether the group can read, write, or view certain fields within a document.
Action Permissions: What actions the group can perform, such as edit, delete, mass update, and approve documents.
Navigate to Settings.
Select Document Processing.
Select Module.
Activate Access Control by enabling the slider.
Navigate to Settings.
Go to Global Settings.
Select Groups, Users and Permissions.
Select Groups and Permissions.
To manage permissions for a group, such as PROCUREMENT_DIRECTOR, click the three dots on the right side of the screen.
Select View Access Control.
Access Control Overview:
In this section, you can enable or disable access for all document types, such as Invoice, Credit Note, Purchase Order, and more.
You can define access levels such as:
Enabled: Grants access to the document type.
List: Defines whether the document type is visible in the list view.
View: Specifies the default view for the document.
Edit: Grants permission to edit the document.
Delete: Allows the group to delete documents.
Mass Update: Enables mass updating of the document type.
Approval Levels: Sets the group’s ability to approve documents (First and Second level approval).
Unlock Document: Defines whether the group can unlock a document for further use.
Permission Levels:
Normal: All users can perform this action.
Owner: Only the assigned user has permission to perform this action.
Admin: Only users with administrative privileges can perform this action.
Example settings for PROCUREMENT_DIRECTOR:
Invoice: Enabled for all permissions, including edit and delete.
Purchase Order: Enabled with normal permissions for all actions.
Field-Level Permissions:
Inside each document type, specific fields can be configured with different levels of permissions.
Permissions include:
Read/Write: Users can both read and write to the field.
Read/Owner Write: Only the owner of the document or field can write, others can read.
Read Only: Users can only view the field but not modify it.
Owner Read/ Owner Write: Only the owner of the document or field can write and read.
Approval: Changes must be approved by authorized users or admin.
None: No specific permissions are applied to the field.
Check the permission settings for the documents or resources in question to ensure that users have the necessary permissions.
Make sure that users have access either directly or through group membership.
Check that the affected users are actually members of the groups that have been granted access.
Make sure that users have not been accidentally removed from relevant groups.
Check that individual permissions have been set at the user level that could override group permissions.
Make sure that these individual permissions are configured correctly.
Make sure that permissions are inherited correctly and are not blocked by parent folders or other settings.
Check permission history or logs to see if there have been any recent changes to permissions that could be causing the current issues.
Try accessing the affected documents with a different user account to see if the issue is user-specific or affects all users.
Make sure users are getting accurate error messages indicating permission issues. This can help you pinpoint and diagnose the problem more accurately.
If all other solutions fail, try reconfiguring permissions for the affected users or groups and ensure that all required permissions are granted correctly.
By following these troubleshooting tips, you can identify and resolve permission-related issues to ensure that users have the required access rights and can work effectively.
The integration settings play a crucial role in the efficiency and functionality of Docbits as they allow to ensure seamless interaction with other tools and services. Here are some reasons why properly configuring the integration settings is important:
The integration settings play a crucial role in the efficiency and functionality of DocBits as they allow to ensure seamless interaction with other tools and services. Here are some reasons why properly configuring the integration settings is important:
Increased efficiency: Integration with other tools and services can streamline workflows and increase efficiency. For example, documents can be automatically exchanged between Docbits and a CRM system, reducing manual entry and increasing productivity
Data consistency: Integration allows data to be exchanged seamlessly between different systems, improving data consistency and accuracy. This avoids inconsistencies or duplicate data entry that could lead to errors.
Real-time updates: Integration enables real-time updates between different platforms so that users always have the latest information. This is especially important for critical business processes that require real-time information.
Task automation: Integration allows routine tasks to be automated, saving time and resources. For example, notifications can be triggered automatically when a certain event occurs in another system without the need for manual intervention.
Improved user experience: A well-configured integration ensures a seamless user experience as users do not have to switch between different systems to access relevant information. This improves user satisfaction and contributes to efficiency.
To properly configure the integration settings, it is important to understand the organization's requirements and ensure that the integration is seamlessly integrated into existing workflows and processes. This requires thorough planning, configuration, and monitoring of the integration to ensure that it works smoothly and delivers the desired value.
In document processing, APIs can be used to automate various tasks such as extracting text from documents, analyzing document contents, converting between different file formats, and more. Here are some examples of APIs in document processing:
OCR (Optical Character Recognition) API: This type of API allows you to extract text from images or scanned documents. For example:
NLP (Natural Language Processing) API: This API enables analysis of text content in documents, including keyword identification, entity recognition, sentiment analysis, etc. For example:
Conversion API: This type of API allows conversion between different file formats, for example from PDF to Word or from Word to PDF. For example:
Document Management API: This API allows you to upload, download and manage documents in a document management system. For example:
These examples show how APIs can be used in document processing to automate various tasks and improve efficiency. The exact functionality and syntax of the API depends on the particular API and its specific features.
Key: This is the unique identifier used by external applications to access DocBits' API. It is crucial for authenticating requests made to DocBits from other software.
Actions such as view, regenerate, or copy the API key can be performed here, depending on the specific needs and security protocols.
Entity ID: This is the identifier for DocBits as a service provider in the SSO configuration. It uniquely identifies DocBits within the SSO framework.
SLO (Single Logout) URL: The URL to which SSO sessions are sent to log out simultaneously from all applications connected via SSO.
SSO URL: The URL used for initiating the single sign-on process.
Actions such as "Download Certificate" and "Download Metadata" are available for obtaining necessary security certificates and metadata information used in setting up and maintaining SSO integration.
Tenant ID: This might be used when DocBits integrates with cloud services that require a tenant identifier to manage data and access configurations specific to the company using Docbits.
Upload file: Allows the admin to upload configuration files or other necessary files that facilitate integration with an identity provider.
Configure: A button to apply or update the settings after making changes or uploading new configurations.
Instructions for viewing, copying or regenerating the API key
API key management is an important aspect when it comes to the security of integrations and access to external services through APIs. Here are some steps to manage API keys and best practices for their security:
View and copy the API key:
Navigate to the API key settings in your DocBits account. Here you can find the API key, click "Copy" to copy the key.
Handling API keys with security in mind:
Treat API keys like sensitive credentials and never share them with anyone. Store API keys securely and use encryption if you need to store them locally. Update API keys regularly to ensure security and minimize the risk of unauthorized access. Avoid using API keys in public repositories or unsecured environments as they could potentially be intercepted by attackers.
Limit API key permissions:
Give API keys only the permissions required for the specific integration or service. Avoid excessive permissions to minimize the risk of abuse. Regularly review API key permissions and remove unnecessary permissions when they are no longer needed.
Logging and monitoring API calls:
Implement logging and monitoring of API calls to detect suspicious activity or unusual patterns that could indicate potential security breaches. Respond quickly to suspicious activity and, if necessary, revoke affected API keys to minimize the risk of further damage.
By carefully managing and securing API keys, organizations can ensure that their integrations and access to external services via APIs are protected and the risk of unauthorized access is minimized.