This Card is intended to compare whether the selected fields in a document are equal/not equal, greater than... or less than... .

Compare two fields with tolerance

This card should automatically compare whether the fields, for example between net amount and gross amount, are within the specified tolerance. For example, you then enter the percentage of the VAT in the tolerance amount and enter percent in the tolerance type. The workflow can check whether the amount is correct.

Tolerance type: percent or value

Purpose

This workflow card manages the execution of operations based on whether a task or document is assigned to a particular user or set of users. It employs conditional logic to either trigger or prevent specific actions, making it ideal for workflows that require user-specific handling.

Components of the Card

1. Operator

   • Description: Defines the logical condition to apply to the user assignment.

   • Options:

     • IS: Triggers the operation if the assigned user of the document or task matches any user in the specified list.

     • IS NOT: Triggers the operation if the assigned user of the document or task does not match any user in the specified list.

2. User List

   • Description: A list or selection of users to compare against the assigned user.

   • Detail: This list can include one or multiple users, allowing the card to handle both singular and multiple user conditions effectively. The selection can be made through checkboxes, a multi-select dropdown, or similar UI elements.

Functionality

• User Assignment Identification: Automatically identifies the user or users assigned to a particular task or document within the ERP system.

• Condition Evaluation:

  • Using the IS operator, the card checks if the assigned user is among those listed in the User List.

  • Using the IS NOT operator, the card ensures the assigned user is not among those listed.

• Action Execution:

  • True Condition: If the user assignment meets the condition (either IS or IS NOT), relevant actions are triggered, such as notifications, task initiations, approvals, or other workflow steps.

  • False Condition: If the condition is not met, the document or task may pass through different routing, or alternative actions may be specified.

User Interactions

• Setup and Configuration: Users configure the card by selecting an operator and specifying the relevant users from the User List. Setup should be user-friendly and intuitive to accommodate selections from potentially large user bases.

• Monitoring and Reporting: The ERP system should provide functionality to monitor and report on the operations triggered by this card, offering insights into assignment accuracy and process efficiency.

• Error Handling and Notifications: Users should have options to receive alerts or notifications if there are issues with the assignments, such as unassigned tasks or errors in user selection.

Conclusion

The "Assigned User Condition" workflow card is a critical tool for managing document and task workflows that depend on user assignments. By allowing conditions based on whether a task or document is assigned to specific users, it ensures that workflows are only triggered by appropriate user interactions, enhancing both accountability and task alignment within teams. Clearly documenting this card will help users understand its significance and integrate it effectively into their workflows, ensuring smooth and efficient operations tailored to user roles and responsibilities.

Purpose: This Docbits card is designed to ensure that the confirmed delivery dates on invoices or shipping documents align with the accepted delivery dates as stipulated in the master data lookup table. It helps manage expectations and adherence to scheduled deliveries within the supply chain.

Functionality:

• Confirmed Delivery Date: This component of the card captures the delivery date as confirmed on the invoice or shipping documentation.

• Master Data Table Lookup: The card references a master data lookup table specified by the user (identified by the <Master Data Table> parameter). This table contains the accepted delivery dates for comparison.

• Operator Value: Users can specify how the confirmed delivery date should compare to the accepted delivery date from the master data table. Available operators include:

• • Equals (=): Ensures that the confirmed delivery date is the same as the accepted delivery date.

  • Not Equal (≠): Indicates a discrepancy between the confirmed and accepted delivery dates.

  • Before (<): Verifies that the confirmed delivery date is earlier than the accepted delivery date.

  • After (>): Checks if the confirmed delivery date is later than the accepted delivery date.

Usage: This card is invaluable for ERP Managers and financial accountants who need to monitor and ensure compliance with delivery schedules. It is particularly useful in sectors where timely delivery is critical, such as manufacturing, retail, and distribution.

Example Scenario:

• An invoice lists a confirmed delivery date of June 10th. The master data table, however, shows an accepted delivery date of June 15th. Setting the operator to "Before," the card confirms that the goods are scheduled for early delivery, allowing logistics planning to adjust accordingly.

By implementing the "Compare with Purchase Order: Confirmed vs. Accepted Delivery Dates" card, organizations can proactively manage their supply chain, ensuring that deliveries are planned and executed in accordance with agreed-upon timelines, thus enhancing operational efficiency and customer satisfaction.

\

Purpose: This Docbits card is designed to streamline the verification process of invoices by comparing the total calculated price from the invoice against the corresponding purchase order.

Functionality:

• Combined Price of Quantity Difference: The card calculates the total price by multiplying the quantity of each item listed on the invoice by the price per unit and then subtracts this total from the amount listed on the related purchase order.

• Operator Value: Users can set conditions to determine how the calculated total price difference should be compared to the purchase order amount. The following operators are available:

• • Equals (=): Checks if the total invoice amount is exactly the same as the purchase order amount.

  • Not Equal (≠): Verifies that the total invoice amount differs from the purchase order amount.

  • Greater Than (>): Ensures the invoice amount is greater than the purchase order amount.

  • Less Than (<): Confirms the invoice amount is less than the purchase order amount.

Usage: This card is particularly useful for ERP Managers and financial accountants who need to automate and error-proof the reconciliation of invoices against purchase orders, ensuring financial accuracy and preventing overpayments or underpayments.

Example Scenario:

• An invoice lists a total of 100 units of a product at $50 per unit, totaling $5000. The related purchase order authorized a purchase of $4500. Using the "Greater Than" operator, the card identifies and flags the discrepancy for review.

By using the "Compare with Purchase Order" card, users can automatically ensure that payments are consistent with purchase agreements, saving time and reducing human error in financial processing.

\

Purpose

This workflow card is designed to automatically compare the values of two specified fields within a document based on a defined operator. It's used to enforce data integrity and ensure that document data conforms to business rules or conditions.

Components of the Card

1. Field Names

   • Description: Specifies the names of the two fields within the document that will be compared.

   • Detail: Users must input the exact names of the fields as they appear in the system. These fields can be any data type that supports comparison, such as numeric, date, or text fields.

2. Operator

   • Description: The comparison operator used to evaluate the relationship between the values of the two fields.

   • Options:

     • Equal (==): Checks if the value of the first field is equal to the value of the second field.

     • Not Equal (!=): Checks if the value of the first field is not equal to the value of the second field.

     • Greater Than (>): Checks if the value of the first field is greater than the value of the second field.

     • Greater Than or Equal (>=): Checks if the value of the first field is greater than or equal to the value of the second field.

     • Less Than (<): Checks if the value of the first field is less than the value of the second field.

     • Less Than or Equal (<=): Checks if the value of the first field is less than or equal to the value of the second field.

Functionality

• Field Selection: Users input or select the names of the two fields to be compared. This is typically done through a form or a dropdown menu within the card setup.

• Operator Selection: Users choose an operator from a list of available options that define how the fields should be compared.

• Comparison Execution:

  • The system reads the values from the specified fields and applies the selected operator to evaluate the relationship between them.

  • Based on the result of the comparison (true or false), subsequent actions may be triggered. For example, if a comparison fails, the system might flag the document for review, block further processing, or notify responsible parties.

User Interactions

• Setup and Configuration: Users configure the comparison by entering field names and selecting an operator. This setup should be straightforward and guided, possibly with help text or examples.

• Monitoring and Reporting: The system can provide feedback on the results of comparisons, such as logging all comparisons made, their outcomes, and any actions taken in response to the comparison results.

• Error Handling and Notifications: Users receive alerts if the comparison cannot be executed (e.g., if one of the fields is not found in the document or is not in a comparable format).

Conclusion

The "Document Field Comparison" workflow card is vital for maintaining data accuracy and consistency across documents in an ERP system. It helps automate checks that would otherwise be manual, error-prone, and time-consuming, enhancing efficiency and reliability in document processing. Documenting this card clearly in your ERP system's manual will assist users in effectively employing this feature, ensuring that data across documents remains consistent and in accordance with business rules.

Understanding "And" Cards

Purpose of 'And' Cards:

• And cards serve as condition cards that specify criteria that must be met for the workflow to continue. They effectively act as logical "AND" operators, meaning all conditions specified in these cards must be satisfied for the subsequent action to be triggered.

Categories of 'And' Cards

From the screenshots, it's clear that these cards cover a wide range of conditions, which include:

• Compare with Purchase Order:

  • Conditions related to validation and comparison against purchase orders, such as comparing delivery dates, unit prices, or quantity differences. These are crucial for ensuring that transactions align with agreed terms.

• Document Field:

  • These involve conditions based on specific fields within documents, such as checkboxes being marked, comparison of field values, or ensuring a document field meets a specified tolerance. This is particularly important for data integrity and automated checks within forms or document management systems.

• Document:

  • Conditions based on document characteristics, such as type or association with a particular sub-organization. These conditions can direct workflows based on document categorization or departmental involvement.

• Logic:

  • Logical conditions that might involve evaluations like "Continue with a chance of X%" or executing HTTPS requests, which are vital for integrations and probabilistic decision-making within workflows.

• Status:

  • Focusing on the status of documents or tasks, these conditions ensure that only items in certain states trigger specific workflows, crucial for status-driven process management.

• Table:

  • These involve conditions based on table data, such as matching regex patterns or comparing values within a table. Such conditions are essential for validating and manipulating large data sets.

• Assignee:

  • Conditions based on task or document assignees. This ensures that actions are only taken when certain users are involved, enhancing accountability and task specificity.

Practical Application

These "And" cards are configured within the workflow to perform checks and validations that ensure the process adheres strictly to business rules and data integrity standards. For example:

• A workflow might use an 'And' card to verify that an invoice's total amount matches the purchase order before triggering payment.

• Another workflow could use an 'And' card to ensure a document is reviewed by specific team members before it progresses to the next stage.

Conclusion

"And" cards are a fundamental component of workflow systems that require precise control over process execution based on multiple conditions. They ensure that each step of a workflow only proceeds when all necessary criteria are thoroughly met, thus automating complex decision trees within business processes.

Understanding and configuring these cards correctly is crucial for leveraging the full capabilities of your workflow management system to enhance efficiency, accuracy, and compliance within organizational processes.

Purpose

This workflow card is designed to automate actions based on the state (checked or unchecked) of a checkbox within your ERP system. By evaluating the checkbox's condition, it facilitates the triggering of specific processes or the enforcement of certain rules within the application.

Components of the Card

1. Field Name

   • Description: Specifies the name of the checkbox field that will be evaluated.

   • Detail: This should match the exact field label or identifier used in the system. It determines which checkbox's state is being monitored.

2. Boolean

   • Description: Defines the condition that triggers the workflow.

   • Options:

     • True: The workflow triggers if the checkbox is checked.

     • False: The workflow triggers if the checkbox is unchecked.

Functionality

• State Detection: The card continuously monitors the state of the specified checkbox field.

• Condition Evaluation:

  • The system checks whether the checkbox is in the state (checked or unchecked) specified by the Boolean condition.

• Action Execution:

  • True Condition: If the checkbox’s state matches the specified Boolean condition (either true for checked or false for unchecked), the system initiates the associated actions. These could include enabling or disabling form fields, triggering notifications, starting workflows, or updating records.

  • False Condition: If the checkbox’s state does not match the condition, alternative or no actions may be taken, depending on the workflow setup.

User Interactions

• Setup and Configuration: Users configure the card by selecting the checkbox field from a list of available fields and setting the Boolean condition. This setup process should be intuitive, typically involving a simple dropdown menu for field selection and a toggle for the Boolean condition.

• Monitoring and Reporting: Provides functionalities for users to monitor the status of this condition, possibly through a dashboard that shows real-time updates on which conditions are active or triggered.

• Error Handling and Notifications: Ensures that users are notified if there are any discrepancies or errors in the condition checking process, such as system failures to read the checkbox state.

Conclusion

The "Checkbox Field Condition" workflow card is a fundamental tool for managing dynamic forms and documents within an ERP system, where user inputs can dictate subsequent data processes. By automating actions based on the state of a checkbox, this card enhances workflow efficiency and ensures that system behaviors align with user inputs. Clear documentation of this card will help users effectively implement it within their operations, allowing for better control over form behaviors and process automations.

Compare with Purchase Order:

In Order Confirmation Purchase Order

Logic Card: Quantity or Unit Price or Discount Match

This logic card is designed to automatically verify that the quantity, unit price, or discount detailed in an order confirmation matches the corresponding figures in the purchase order. This verification ensures consistency and accuracy between what was ordered and what the supplier confirms to deliver.

Trigger Condition

The logic is activated when any of the following conditions are met in an order confirmation relative to the original purchase order:

• Quantity: The quantity of items ordered matches the quantity confirmed by the supplier.

• Unit Price: The price per item agreed upon matches the supplier's confirmation.

• Discount: Any discounts applied are consistent between the purchase order and the order confirmation.

Outcomes

• Equals: If the order confirmation's quantity, unit price, or discount exactly matches the purchase order, the system considers the confirmation as valid and proceeds with the next steps in the procurement process.

• Not Equal: If there's a discrepancy in the quantity, unit price, or discount, the system flags the order confirmation for manual review. This ensures any mismatches are resolved before moving forward.

Benefits

• Accuracy and Consistency: Maintains accuracy in the procurement process, ensuring that payments and deliveries are made based on correct figures.

• Efficiency: Automates the verification process, reducing the need for manual checks and speeding up order processing.

• Cost Control: Helps prevent overpayments or incorrect deliveries by catching discrepancies early in the process.

1. Define Comparison Parameters: Set up the specific fields (quantity, unit price, discount) that the logic card will check for a match.

2. Automate Verification: Configure the system to automatically compare these details upon receipt of an order confirmation.

3. Customize Alerts: Decide on the workflow for handling discrepancies, including customization of alerts for manual review.

This logic card is vital for ensuring that the details of an order confirmation align with the original purchase order, safeguarding the integrity of the procurement cycle. ``

This card can check whether, for example, the total amount in a document corresponds to the specified value - equal/not equal, larger or smaller.

Purpose

This card is designed to manage actions on documents contingent upon their type, employing simple conditional logic (is/is not) to either trigger or prevent specific workflows. This enables precise control over how different types of documents are processed within the ERP system.

Components of the Card

1. Operator

   • Description: Determines the conditional logic applied to the document types.

   • Options:

     • is: The operation will trigger if the document's type matches one of the specified types in the list.

     • is not: The operation will trigger if the document's type does not match any of the types listed.

2. Document Types List

   • Description: Specifies a list of document types to which the condition will apply.

   • Detail: This can include a variety of document types such as "Invoice", "Purchase Order", "Contract", "Employee Record", etc., based on which the condition (is/is not) will be evaluated.

Functionality

• Document Identification: The system first identifies the type of each incoming or existing document based on predefined attributes or metadata.

• Condition Evaluation:

  • If the operator is is, the card checks if the document type is in the provided list.

  • If the operator is is not, the card checks if the document type is not in the list.

• Action Triggering: Depending on the result of the condition evaluation:

  • True: Initiates the associated operations or workflows if the condition is met.

  • False: The process is bypassed or an alternative operation is triggered if the condition is not met.

• Integration and Automation: Seamlessly integrates with other system components, ensuring that document handling is automated and adheres to organizational workflows and policies.

User Interactions

• Configuration: Users must specify the operator and list the document types when setting up the card. This setup may include interface elements like dropdowns or checkboxes to select document types and operators.

• Monitoring and Adjustments: Users can monitor the outcomes and effectiveness of this card through logs and reports generated by the ERP system. Adjustments can be made to the list or the operator based on evolving business needs.

• Error Handling and Feedback: Provides feedback mechanisms for errors encountered during operation. Users can set up alerts for when conditions fail, ensuring prompt attention to issues.

Conclusion

The "Document Type Condition" workflow card plays a crucial role in managing document-based operations with precision and flexibility. By using simple conditional logic, it helps ensure that documents are processed appropriately, enhancing efficiency and compliance. Documenting this card clearly will help users understand how to implement and utilize it effectively, making it a valuable part of your ERP system's documentation.

Purpose

This card is designed to control workflow actions based on the current status of a document, using conditional logic to either trigger or restrict certain processes. It ensures that documents only proceed through workflows when they meet predefined status criteria.

Components of the Card

1. Operator

   • Description: Determines how the document status will be evaluated against a specified condition.

   • Options:

     • is: Triggers the associated actions if the document’s current status matches one of the specified statuses.

     • is not: Triggers the actions if the document’s status does not match any of the specified statuses.

2. Status ( List )

   • Description: Lists the specific statuses against which the document’s current status will be compared.

   • Examples: "Error", "Export Error", "Ready in Validation", "Ready in Review", "Pending Approval", "Pending Second Approval". These represent different stages or conditions a document might be in within a workflow process.

Functionality

• Status Identification: Automatically identifies the current status of a document as it moves through the ERP system’s workflow.

• Condition Evaluation: Applies the chosen operator (is or is not) to the document’s status in comparison to the listed statuses:

  • If is, it checks whether the document’s status matches any status in the list.

  • If is not, it checks whether the document’s status does not appear in the list.

• Action Execution: Depending on the outcome of the condition evaluation:

  • True: Executes predefined actions or workflows if the condition is met.

  • False: Skips or triggers alternative workflows if the condition is not met.

• Workflow Integration: Integrates seamlessly with other workflow components, ensuring that document handling is coordinated across the system.

User Interactions

• Setup and Configuration: Users configure the card by selecting the operator and specifying the relevant statuses. This setup may involve simple dropdown menus or checkboxes for selecting statuses and operators.

• Monitoring and Management: Users can track the card’s activity via a dashboard, which provides insights into the status conditions being monitored and the actions being taken based on those conditions.

• Error Handling and Alerts: Supports setting up alerts for process failures or mismatches in expected document statuses, enabling quick responses to operational issues.

Conclusion

The "Document Status Condition" workflow card is vital for ensuring that documents are processed correctly according to their current status, enhancing control and efficiency within the ERP system. Clearly documenting this card in the system's manual will help users effectively implement and manage it, leveraging its functionality to maintain smooth and compliant document workflows. This card is particularly useful in managing document lifecycles and ensuring that only documents meeting specific criteria advance to subsequent stages of business processes.

Note: Not every customer has the checkbox, but it can be added if desired.

This card should automatically check whether the checkbox on the document has the same value as the condition on the card. Was the selected field checked (true) or not (false)

Purpose

This workflow card is tailored to manage operations on documents based on a single, specified document status. By simplifying the condition to one status, the card is focused on very specific workflow triggers, making it ideal for targeted document processing activities within an ERP system.

Components of the Card

1. Operator

   • Description: Specifies the method for evaluating the document’s status against the selected condition.

   • Options:

     • is: Triggers the operation if the document's current status matches the selected status.

     • is not: Triggers the operation if the document's current status does not match the selected status.

2. Status

   • Description: Allows the selection of a single document status to set the condition.

   • Examples of Statuses: "Error", "Export Error", "Ready in Validation", "Ready in Review", "Pending Approval", "Pending Second Approval".

   • Detail: Users choose one status from a dropdown or a set of radio buttons. This status then serves as the criterion for the card’s operation.

Functionality

• Document Status Identification: Identifies the current status of a document as it is processed through the ERP system.

• Condition Evaluation:

  • Based on the operator selected (is or is not), the card checks whether the document's current status aligns with the chosen status criterion.

• Action Execution:

  • True Condition: If the status matches (or does not match, based on the operator), the corresponding action is initiated. This could be routing for further processing, notification generation, or other predefined workflows.

  • False Condition: If the condition is not met, no action is taken, or an alternate pathway is triggered.

• Integration with Other Workflows: Even though it's designed for single-status evaluation, this card can be effectively integrated into broader workflow sequences to ensure precise document handling.

User Interactions

• Setup and Configuration: Users set up the card by selecting an operator and then choosing one status from the available options. This selection process is straightforward and designed to prevent confusion.

• Monitoring and Reporting: Enables monitoring through system-generated reports or dashboards that track the processing of documents based on their status, helping to oversee the effectiveness of the implemented workflows.

• Error Handling and Notifications: Configurable to alert users to any processing anomalies or to flag documents that do not meet the set conditions, ensuring prompt attention and resolution.

Conclusion

The "Single Document Status Condition" workflow card simplifies document management by focusing on individual status conditions. This specification helps in cases where precise control over document flows is necessary, especially in environments with stringent processing criteria. Documenting this version of the card clearly will ensure that users fully understand its application and can effectively integrate it within their daily operations, enhancing both compliance and efficiency in document processing.

Purpose

This workflow card facilitates operations based on the assignment of a task or document to a single, specific user. Using a direct conditional logic approach, it manages workflows that require targeted user engagement, ensuring precision in user-based task handling.

Components of the Card

1. Operator

   • Description: Specifies the logic to apply to the user assignment.

   • Options:

     • IS: Triggers the operation if the assigned user of the document or task matches the specified user.

     • IS NOT: Triggers the operation if the assigned user does not match the specified user.

2. User

   • Description: Allows selection of a single user against whom the assigned user will be compared.

   • Detail: This involves a simple dropdown or autocomplete field where one user can be selected at a time.

Functionality

• User Assignment Identification: Identifies the user currently assigned to a specific task or document.

• Condition Evaluation:

  • For the IS operator, the card checks if the assigned user is the same as the user selected.

  • For the IS NOT operator, it verifies that the assigned user is different from the selected user.

• Action Execution:

  • True Condition: If the assignment meets the set condition (IS or IS NOT), it triggers predefined actions, which could include moving forward with approvals, initiating further tasks, sending notifications, or other related workflows.

  • False Condition: If the condition fails, the system can reroute the task, hold it for review, or trigger alternative predefined actions.

User Interactions

• Setup and Configuration: Users set up the card by choosing an operator and selecting a user from the user field. This setup should be straightforward, ensuring easy user selection and configuration.

• Monitoring and Reporting: Offers tools for monitoring the card’s performance, such as tracking which tasks are triggered by specific user assignments and the outcomes of these triggers.

• Error Handling and Notifications: Provides mechanisms to alert users if tasks are incorrectly assigned or if operational errors occur due to assignment issues.

Conclusion

The "Single Assigned User Condition" workflow card is essential for precise, user-specific document and task management within an ERP system. It simplifies workflows by focusing on individual user assignments, thus ensuring that actions are only executed when appropriate, based on the user's role and responsibilities. Documenting this card clearly will assist users in understanding its application, allowing them to implement and manage it effectively within their daily operations. This documentation ensures that all potential users can easily grasp the card's purpose and integrate it seamlessly into their workflows.

Purpose

This Docbits card allows detailed comparison, comparing the supplier of the invoice and that of the order confirmation. It should be ensured that the supplier who issued the invoice is the same as the one in the order confirmation.

Functionality:

• Supplier on Invoice Supplier on Purchase Order: This card checks whether the supplier in the invoice is the same as in the order confirmation or not.

• Operator Value: Users can set specific conditions such as: Is the supplier who issued the invoice the same as in the PO or not. Available operators include:

  • Equals (=): Checks whether the supplier in the invoice matches the supplier in the order confirmation.

  • Not Equal (≠): Ensures that the supplier who issued the invoice is the same as in the order confirmation.

Usage: This Card is helpful to ensure the entire process is handled with the same supplier and everything fits together. This ensures that if there are discrepancies, attention is drawn to checking these discrepancies and not paying the invoice to an incorrect supplier who has nothing to do with the order and order confirmation.

Example Scenario:

• An order is placed, then the order confirmation comes and then the invoice is issued. The entire ordering process is carried out with one supplier. If this is not the case, the card can immediately determine that there are discrepancies between the suppliers and thus ensures that no incorrect payments are made and that the invoice is only made with the supplier who was also involved in the entire process.

By using the “Supplier on Invoice … Supplier on Purchase Order” card, companies can automate the verification of suppliers who issue invoices and the associated order confirmations.

Purpose: This Docbits card facilitates the detailed comparison of unit prices on invoices against those specified in the corresponding purchase orders. It enhances accuracy in financial reporting by ensuring adherence to agreed pricing.

Functionality:

• Unit Price Combined with Fields: This card calculates the total amount for a specific item by combining the unit price with additional specified fields from the invoice. The combined total is then compared against the purchase order's recorded unit price for that item.

• Operator Value: Users can set specific conditions for how the invoice's combined unit price should be compared to the purchase order's unit price. Available operators include:

• • Equals (=): Verifies that the combined invoice price matches the price on the purchase order.

  • Not Equal (≠): Ensures the combined invoice price does not match the price on the purchase order.

  • Greater Than (>): Checks if the combined invoice price exceeds the price on the purchase order.

  • Less Than (<): Confirms the combined invoice price is below the price on the purchase order.

Usage: This card is particularly valuable for ERP Managers and financial accountants tasked with maintaining stringent control over purchasing and payment processes. It ensures that invoiced prices conform to those agreed upon in purchase orders, thereby mitigating financial discrepancies.

Example Scenario:

• An invoice presents a unit price of $50 for a product. The "field name" specified includes an additional handling fee of $5 per unit. When combined, the total per unit amounts to $55. Using the "Equals" operator with a value set to $55, the card verifies that the invoiced price aligns with the purchase order, ensuring agreement compliance.

By deploying the "Compare with Purchase Order: Unit Price Combined" card, businesses can automate the verification of pricing accuracy against purchase orders, streamlining financial operations and safeguarding against overcharges.

\

This card is supposed to automatically check whether the text you are looking for is contained in the field in a document or not. If the entered text is not found, there are other options as to how to continue with the document. (“Then” workflow cards)

\