Skip to content
Nappai Documentation

Agente Auditor ICJCE V2

The Agente Auditor ICJCE V2 is a specialized automation component designed to audit financial accounts in Spain. It acts as an intelligent assistant that checks your accounting data against Spanish regulations (such as PGC or NIC standards). This component helps you ensure compliance, detect errors or inconsistencies in your financial records, and produce structured results that can be used for reviews, verifications, or regulatory decisions.

How it Works

This component functions as a processing node within your Nappai workflow. It automates the evaluation of your accounting data to verify accuracy and regulatory adherence.

Workflow Process:

  1. Data Ingestion: The component receives your financial data, such as transactions, account balances, or ledger records.
  2. Rule Application: It applies predefined Spanish accounting rules and validation criteria to the data.
  3. Analysis: The agent analyzes the data to identify discrepancies, missing information, or compliance issues.
  4. Result Generation: It produces a structured output containing audit findings, a status indicator, and a detailed report.

The component works internally within the Nappai engine, leveraging base audit logic to ensure consistent and reliable results without requiring external API integrations.

Inputs

The following fields are available to configure this component. You can map data from previous nodes or enter values directly.

  • data: The accounting or audit data you want to review. This should be structured information about accounts, transactions, or records. This field is typically required for the audit to function.
  • config: Settings that control how the agent performs the audit. Use this to adjust validation rules, risk thresholds, or specific compliance criteria tailored to your needs.
  • context: Metadata about the workflow execution, such as user identity or previous state information. This is usually managed automatically by the Nappai engine, but can be customized if needed.
  • schema: A structure definition used to validate the format of your input data. Providing a schema ensures strict validation and helps prevent errors caused by malformed data.

Outputs

This component generates comprehensive audit results that you can use in subsequent steps of your workflow. The outputs provide insights into compliance, highlight issues, and offer detailed reporting.

Output Data Example (JSON)

json { “audit_result”: { “compliance_status”: “Compliant”, “findings”: [ { “description”: “Transaction ID 12345 adheres to Spanish PGC standards.”, “risk_level”: “Low” }, { “description”: “Account classification for ID 67890 requires review.”, “risk_level”: “Medium” } ], “validation_score”: 95.2 }, “audit_report”: { “summary”: “Audit completed. Minor adjustments recommended for account reconciliation.”, “recommendations”: [ “Update documentation for transaction ID 67890.”, “Verify account 4000 classification against current regulations.” ], “risk_level”: “Medium”, “generated_at”: “2024-05-20T10:30:00Z” }, “status”: “success”, “logs”: [ { “level”: “info”, “message”: “Audit process initiated with Spanish ICJCE V2 rules.”, “timestamp”: “2024-05-20T10:30:01Z” }, { “level”: “warning”, “message”: “Potential inconsistency detected in financial record ID 67890.”, “timestamp”: “2024-05-20T10:30:02Z” } ] }

Connectivity

This component is typically used in financial or accounting workflows where regulatory compliance is essential.

  • Incoming Connections: Connect data sources (such as database connectors, spreadsheet parsers, or ERP integrations) to the data input. Ensure the data is formatted correctly before it reaches this node.
  • Outgoing Connections: Link the outputs to downstream components. For example:
    • Use the audit_report to send summaries to reporting tools or email notifications.
    • Route the status to decision nodes to separate compliant records from those requiring manual review.
    • Feed the audit_result into approval workflows or final accounting ledger updates.

Usage Example

Scenario: Monthly Spanish Financial Audit

  1. Data Extraction: You start a workflow that extracts monthly transactions from your accounting software.
  2. Audit Execution: You connect the extracted data to the Agente Auditor ICJCE V2. In the config field, you select the specific Spanish accounting rules (e.g., PGC) relevant to your business.
  3. Review and Action: The agent processes the data and outputs an audit_report. You can connect this report to a dashboard node to visualize compliance metrics. If the status indicates errors, you can branch the workflow to send an alert to your finance team for immediate correction.

Tips and Best Practices

  • Clean Data First: For the most accurate audit results, ensure your input data is well-structured and free of formatting errors before processing.
  • Customize Configuration: Use the config field to fine-tune risk thresholds. Adjust these settings if you need stricter or more lenient compliance checks.
  • Monitor Logs: Check the logs output to understand why specific flags were raised. This helps in troubleshooting and refining your data sources.
  • Use Status Branching: Leverage the status output to automate decision-making. For instance, route “success” outcomes to final storage and “warning” or “error” outcomes to a review queue.
  • Schema Validation: If you encounter recurring errors, define a schema to enforce strict data structures and catch issues early in the workflow.

Security Considerations

  • This component processes sensitive financial and accounting data. Ensure that the data flowing into this node is secured and that access to the workflow is restricted to authorized personnel.
  • Audit reports and logs may contain confidential information. Handle the audit_report and logs outputs with care, and ensure they are stored or transmitted according to your data protection policies.