Skip to main content
Version: Current

Understanding validation levels

Zudello uses different validation levels to provide feedback on document data quality and enforce business rules. Understanding these levels helps you identify issues and ensure documents are processed correctly.

Best practices​

  • Pay close attention to Error level validations, as they block processing.
  • Review Warning level validations to ensure data accuracy, even if processing isn't blocked.
  • Use Info level validations for informational purposes or non-critical checks.
  • Configure validation rules (via extensions or sentences) that align with your business needs and ERP requirements.

Validation levels explained​

When Zudello validates a document (either automatically during enrichment/saving or via specific validation extensions), issues are categorised into three levels:

  1. Error (Blocking):

    • Indication: Typically shown with a red icon or banner. Sets the document's validation level field to error.
    • Impact: Prevents the user from performing critical actions like Save and Submit or potentially Approve. The issue must be resolved before the document can proceed.
    • Examples:
      • Missing mandatory fields required by the ERP integration.
      • Document totals do not balance according to validation rules (e.g., validate purchase total).
      • Failing a critical compliance check (e.g., validate no new contact if enabled).
      • Item price exceeds a hard blocking limit (Configure item price blocking).

  2. Warning (Non-Blocking):

    • Indication: Typically shown with a yellow/orange icon or banner. Sets the document's validation level field to warning (if no errors are present).
    • Impact: Alerts the user to a potential issue or deviation but does not block submission or approval. Users should review warnings but can choose to proceed.
    • Examples:
      • Minor discrepancy in totals within an acceptable tolerance range.
      • ABN validation returns an inactive status (Configure ABN validation).
      • Bank detail comparison shows a mismatch (Configure bank detail validation).
      • A budget is exceeded, but the workflow allows submission with a warning.

  3. Info (Informational):

    • Indication: Typically shown with a blue or grey icon/banner, or just as informational text. Sets the document's validation level field to info (if no errors or warnings are present).
    • Impact: Provides helpful information or context without blocking any actions.
    • Examples:
      • Displaying the result of a successful ABN validation.
      • Showing matching bank details.
      • Indicating that a specific default rule was applied.

How validation levels are determined​

  • Validation Extensions: Many extensions (like validate purchase total, check contact ABN) have built-in logic to determine the appropriate level based on the outcome of their check.
  • Sentences: Automation sentences can check conditions and explicitly set the validation level field using the set field action, although this is less common for standard validation feedback.
  • Hierarchy: If a document has multiple validation issues, the highest severity level determines the overall validation level (error > warning > info).

Reviewing validation issues​

Users can typically see validation issues:

  • Via banners displayed at the top of the document viewer.
  • Through icons next to specific fields or sections.
  • In the "issues" column or icon in list/table views (see Review validation issues).

Need help?​

If you are unsure why a specific validation level is being applied or how to resolve an error, contact your organisation administrator or Zudello support.