Skip to content
Nappai Documentation

Agente Auditor ICJCE

This component acts as an intelligent auditor assistant within your Nappai automation workflow. It is designed to review financial documents and records against Spanish accounting standards (such as ICJCE regulations). By using this component, you can automate the verification of compliance, detect potential errors or irregularities, and receive structured audit reports with actionable recommendations.

It serves as a critical checkpoint in your data management processes, ensuring that your financial data meets regulatory requirements before further actions are taken.

How it Works

When you execute this component, it performs the following steps internally:

  1. Receives Instructions and Data: You provide the component with specific instructions about what to audit, along with the relevant financial documents or data packages.
  2. Analyzes Against Standards: The agent applies knowledge of Spanish accounting norms and legal requirements to the provided data. It checks for consistency, validates entries, and looks for deviations.
  3. Generates Findings: Based on the analysis, it identifies compliant items and flags any irregularities or non-compliance issues.
  4. Outputs Results: The component returns a structured report containing the audit findings, a detailed explanation of the reasoning behind the conclusions, and metadata about the execution status.

This process helps you automate repetitive audit tasks, reduce manual review errors, and maintain accurate compliance records.

Inputs

The following fields are available to configure this component.

  • Pregunta o Instrucción de Auditoría: Specific instruction, query, or scope definition that tells the agent what to review and what outcome to expect.

    • Visible in: All operations

  • Documentación de Soporte: Financial data packages, balance sheets, accounting books, notes, or legal norms required for the analysis. The quality and completeness of this input directly impact the accuracy of the audit.

    • Visible in: All operations

  • Parámetros de Restricción: Configuration settings such as accounting periods, deadlines, materiality criteria, or specific standards (e.g., PGC, LSC, NIC/NIIF) that guide how the agent performs the audit.

    • Visible in: All operations

  • Historial de Interacción: Record of previous steps, decisions, or iterations. This helps maintain continuity and context when running multi-step or iterative audits.

    • Visible in: All operations

Outputs

The component produces the following outputs, which can be connected to other nodes in your workflow:

  • Informe de Auditoría: A structured report containing findings, compliance status, and recommendations for adjustment or corrective actions.
  • Razonamiento Técnico: A detailed explanation of the criteria applied, legal/accounting references, and the logic behind each conclusion. This helps you understand and verify the audit results.
  • Metadatos de Ejecución: Operational data including validation status, confidence levels, execution times, and alert flags. This metadata can be used to trigger downstream actions based on risk or success.

Output Data Example (JSON)

json { “Informe de Auditoría”: { “resumen”: “La auditoría de los gastos operativos del ejercicio 2023 se completó. Se identificaron 3 partidas con incumplimiento leve de la norma PGC.”, “hallazgos”: [ { “cuenta”: “620 - Servicios exteriores”, “desviación”: “Falta de soporte documental en 15% de las transacciones”, “nivel_riesgo”: “Medio” } ], “recomendaciones”: “Se sugiere solicitar a los proveedores las facturas faltantes y ajustar el provisionado de gastos pendientes.”, “cumplimiento_general”: “Parcialmente conforme” }, “Razonamiento Técnico”: “El análisis se basó en el Plan General de Contabilidad y las NIC aplicables. Se compararon los registros contables con la documentación proporcionada. Se detectaron inconsistencias en la conciliación de cuentas de gastos menores, lo que afecta la confiabilidad del reporte final en un 85%. Se aplicaron criterios de materialidad del 5% para la clasificación de las desviaciones.”, “Metadatos de Ejecución”: { “estado”: “exitoso”, “nivel_confianza”: 0.85, “tiempo_ejecucion_s”: 3.2, “alertas”: [ { “tipo”: “falta_documentacion”, “descripcion”: “Documentación insuficiente para el 15% de las transacciones revisadas” } ], “dependencias_salida”: [ “requiere_revision_humana” ] } }

Connectivity

This component is typically used in financial audit and compliance workflows.

  • Typical Predecessors: Connect to nodes that extract financial data, parse documents, or retrieve accounting records from your data management systems.
  • Typical Successors: Connect the outputs to nodes that generate final reports, send notifications to auditors, update compliance databases, or trigger remediation actions for identified issues.
  • Logic: The component acts as a processing hub where raw financial data is transformed into audited, actionable insights. Its outputs often feed into reporting or decision-making nodes that require verified financial information.

Usage Example

Scenario: Automating the monthly review of operating expenses.

  1. Setup: You have a workflow that collects your company’s expense logs and invoices for the current month.
  2. Configure Inputs:
    • In Documentación de Soporte, connect the output of your expense data node.
    • In Pregunta o Instrucción de Auditoría, enter: Verify compliance of operating expenses against PGC standards and identify missing documentation.
    • In Parámetros de Restricción, set the accounting period to 2024-01 and materiality threshold to 5%.
  3. Execute: When the workflow runs, the component analyzes the expenses.
  4. Use Outputs:
    • Connect Informe de Auditoría to an email node to send a summary to the finance team.
    • Use Metadatos de Ejecución to check if nivel_confianza is below a threshold; if so, route the workflow to a manual review step.

Tips and Best Practices

  • Be Precise with Instructions: Clearly define the scope and specific rules in the Pregunta o Instrucción de Auditoría field to ensure the agent focuses on the relevant aspects of the audit.
  • Provide Complete Documentation: Ensure all necessary financial statements, books, and supporting documents are included in Documentación de Soporte for accurate analysis.
  • Leverage Metadata for Automation: Use the Metadatos de Ejecución outputs to create conditional branches in your workflow, such as triggering alerts only when risk levels are high.
  • Review Reasoning for Verification: Always check the Razonamiento Técnico to understand the basis of the findings. This helps you validate the agent’s conclusions and address any questions during audits.
  • Use History for Complex Audits: If your audit process involves multiple steps, pass the Historial de Interacción to maintain context and ensure consistency between iterations.
  • Adjust Parameters as Needed: Modify the Parámetros de Restricción to reflect specific accounting periods, regulations, or materiality criteria relevant to your audit requirements.

Security Considerations

  • Data Privacy: This component processes sensitive financial information. Ensure that you only pass authorized and secure data to this node.
  • Access Control: Restrict access to workflows containing this component to authorized personnel who handle financial audits and compliance.
  • Compliance: Verify that the data inputs comply with your organization’s data retention and privacy policies before processing.
  • Output Handling: Be cautious when connecting outputs to downstream systems, especially if they contain detailed audit findings or flagged irregularities. Ensure appropriate access controls are in place.