Identity and access
Microsoft identity integration authenticates users. Tenant membership checks select the customer workspace, while Integration API keys are handled separately from user sessions.
Security and controls
Security for controlled finance operations.
Protecting the financial data and connections your organization relies on, with encrypted storage, authenticated access, and traceable review context.
Effective date: September 24, 2026
Security posture
How Reconcilia protects finance workflows
From signing in to connecting systems, security is part of how Reconcilia handles your financial data.
Traceability and audit context
Operational workflows preserve source lineage, citations, status, review decisions, and audit metadata so users can understand how a value or recommendation was produced.
AI boundaries
AI uses the provider and model configured for the workspace. Relevant workflow data may be sent to that provider to generate a response; users should review the results.
Integration safety
Integration API workflows use scoped keys, validation modes, idempotency, async job visibility, safe deactivation where supported, and clear boundaries around reconciliation visibility.
Encryption and credential protection
Azure PostgreSQL and Blob Storage encrypt stored data, while HTTPS and TLS protect connections. Provider credentials use Azure Key Vault or AES-256-GCM encryption, depending on the deployment configuration.
Data access and privacy
Workspace membership controls customer access. Reconcilia operators with privileged access can also access stored data; encryption does not remove that technical capability. Contact us to discuss your data-handling requirements.
Control model
Designed around reviewable finance decisions
Source records, processing status, and review context help finance teams understand the data behind their decisions.
Scoped user access
Roles and account/entity scope help limit which users can view, review, and administer finance data.
Review context
Review exceptions, source references, and generated outputs together to investigate differences and assess results.
Validation-first API ingestion
Integration API flows support scoped keys, validation modes, idempotency, and operational boundaries for source-data ingestion.
Execution boundaries
Reconcilia separates finance review assistance from money movement, destructive operations, and unrestricted production execution.
AI assists inside controlled workflows
AI can help summarize, explain, draft reports, and suggest actions. Its outputs should be checked against source records and your own review process.
No payment movement from AI chat
Reconcilia does not present AI chat as a shortcut for executing payments. Payment source records can be reviewed as data, but money movement belongs outside the public AI-assistance path.
Need a security review?
Discuss your access, privacy, and integration requirements with us. To report a security concern, contact support@reconcilia.ai without including passwords, API keys, or customer records.