Reconciliation Software for Auditors: What They Check

November 17, 2026
Get advanced tips with our free guide
Get advanced tips:
Get advanced tips

What auditors actually need from reconciliation software

In regulated industries, the audit team is a veto holder in software selection. Questions like "can auditors get read-only access?" or "does reconciliation software support SOX?" are not plain curiosity. They are checklist items that kill a deal if the answer is not a confident yes, backed by a demonstration. This page covers what Solvexia provides across the five areas auditors check: reconciliation software audit trail completeness, segregation of duties, read-only access, data retention, and regulatory reporting support for APRA and XBRL.

Solvexia is a no-code finance automation platform now part of Ripple Treasury (formerly GTreasury), a platform trusted by more than 1,000 customers across 160 countries, including regulated financial institutions. 

This page is a starting point for your compliance review, not a substitute for one. Confirm current certification and regulatory support status directly with Solvexia before relying on this for a compliance decision.

Coming Up

    SOX compliance and reconciliation automation - what's required

    Reconciliation software does not hold a SOX certificate. What it provides are the controls a SOX-compliant process depends on:

    • Role-based access controls that limit who can access, modify, and approve reconciliations
    • Separation of preparation, review, and approval so no single user completes all three steps
    • Configurable approval workflows that enforce the sign-off chain required by your control framework
    • A complete audit trail with version history on matching rules, capturing who changed what and when with user ID and timestamp on every entry

    Solvexia provides all of these controls and supports a SOX-compliant reconciliation process. Your auditors can verify each one in a demo.

    Solvexia also holds a SOC 2 Type 2 report covering its own controls and operational processes against standards established by the AICPA. SOC 2 and SOX are different standards, and your auditors may ask for both. For full security and certification documentation, see Solvexia Security Architecture for IT Teams.

    What audit trail does reconciliation software need to provide?

    An audit trail that satisfies a compliance review captures two distinct layers, and the absence of either is a control gap.

    Output audit trail

    An output audit trail is a complete log of every transaction match, including which transactions were matched, when, using which rule, and who approved the result. This is the layer most reconciliation platforms provide.

    Process audit trail

    A process audit trail is a complete log of every change to the underlying matching logic, including who modified which rule, exactly what changed, and when, with user ID and timestamp on every entry. This is the layer many platforms do not provide, and the one auditors increasingly require. Without it, there is no way to verify that the matching rules in place during the period under audit were the correct ones, or that no unauthorized change was made.

    The two layers together answer the questions an auditor is actually asking, not just what matched, but whether the logic that produced the match was properly controlled throughout the period.

    Solvexia captures both layers as a single connected record rather than separate logs that require manual cross-referencing. Every match, approval, rule modification, and exception resolution is logged with user ID and timestamp, and the version history on matching rules means auditors can reconstruct exactly what logic was in place at any historical point.

    For how to evaluate audit trail completeness in a vendor demo, see How to Evaluate Reconciliation Software and the questions to ask about audit trails specifically.

    How segregation of duties works in automated reconciliation

    Segregation of duties for reconciliation software requires that different people prepare, review, and approve a reconciliation. No single user should be able to complete all three steps alone. How software supports this matters to auditors, and the honest answer is that platforms differ significantly between system-enforced separation and configurable separation.

    Solvexia's model works in two layers:

    • The first layer is account-level roles: Subscriber, Designer, and Client Admin. Client Admin has access to everything by default. Designer and Subscriber are assigned permissions per resource on top of their account role.
    • The second layer is per-resource permissions. Processes can be set to Reader, Executor, Editor, or Owner. Tables, reports, and dashboards can be set to Reader, Editor, or Owner. This means access can be scoped precisely to each reconciliation type rather than set as a single account-wide policy.

    Separation of duties in Solvexia is configurable rather than structurally enforced. The system does not contain a hard block preventing one user from completing an end-to-end workflow. Separation is achieved by assigning permissions so that no individual holds the combination needed to both prepare and approve the same reconciliation. Whether that configuration is correctly maintained is a controls question your team owns.

    How to give auditors read-only access to reconciliation records

    Solvexia does not have a dedicated auditor role. Auditors are provisioned as users with Reader permission on the specific processes, tables, reports, and dashboards in scope for the review. Reader is view-only and set per resource rather than account-wide, which means you can scope exactly what an external or internal auditor can see without granting access to unrelated reconciliation types or workflows.

    Two provisioning patterns work in practice:

    Temporary Reader account for an external audit engagement

    Create a user with Reader permission on the processes and reports in scope, grant access for the duration of the engagement, and remove the account when the review is complete. This is the appropriate model for annual external audits or regulatory examinations.

    Standing Reader account for an ongoing internal audit function

    Provision a permanent user with Reader permission scoped to the reconciliation types the internal audit team monitors on an ongoing basis. Because permissions are set per resource, this account can be scoped narrowly to relevant processes without granting visibility across the entire platform.

    In both cases, the Reader permission is view-only. Users with Reader access cannot modify matching rules, approve reconciliations, or change any configuration. Confirm the specific scope of Reader permission, including whether it extends to historical rule version records, directly with Solvexia during your security review.

    How long does reconciliation software need to retain data?

    Retention requirements vary by jurisdiction and industry, so Solvexia does not impose a single fixed period. Data retention is configured at the process level, which means each reconciliation can be retained on the schedule its regulatory obligation requires rather than forcing one policy across everything. Confirm the arrangement for your specific obligation as part of your review.

    What internal audit teams look for when reviewing reconciliation software

    Internal audit teams evaluate reconciliation software differently from external auditors and regulators. Where an external audit engagement focuses on whether controls existed and operated during a defined period, internal audit is typically assessing whether the control framework is robust, consistently applied, and actually being followed in practice rather than just configured on paper.

    Three areas internal audit teams commonly focus on that go beyond the external audit checklist:

    1. Consistency of control application across all reconciliation types

    Not just the highest-risk or most visible reconciliations, but whether the same access controls, approval workflows, and audit trail standards apply consistently across every process running on the platform. A strong control on bank reconciliation and a weak one on an intercompany process is not a well-controlled environment.

    2. Evidence that controls are being followed in practice

    Configuration is not the same as compliance. Internal audit wants to see the audit trail showing that approvals are actually happening, that no user is circumventing the permission model in practice, and that exception resolution is being logged rather than cleared informally outside the system.

    3. The ability to sample-test historical reconciliations on demand

    Internal audit needs to pull historical reconciliation records, match results, and approval logs without raising a support ticket or waiting for a vendor data extract. The ability to access this data directly, scoped to what the internal auditor needs to see, is a practical requirement that affects how efficiently a review can be conducted.

    How Solvexia supports internal and external audit requirements

    Solvexia addresses the five areas auditors check across both internal and external review contexts:

    1. Audit trail completeness

    Every match, approval, rule modification, and exception resolution is captured in a single connected record with user ID and timestamp on every entry. Rule change history is included, meaning auditors can reconstruct exactly what matching logic was in place at any historical point without cross-referencing separate logs.

    2. Read-only auditor access

    Auditors are provisioned with Reader permission on the specific processes, tables, reports, and dashboards in scope. Reader is view-only and set per resource, allowing precise scoping of what each auditor can see. Temporary accounts for external engagements and standing accounts for internal audit functions both work within this model.

    3. Segregation of duties

    Per-resource permissions allow separation of preparation, review, and approval to be configured precisely for each reconciliation type. Separation is configurable rather than structurally enforced by a system block.

    4. Data retention

    Configured at the process level, allowing each reconciliation type to be retained on the schedule its specific regulatory obligation requires.

    5. APRA and XBRL regulatory reporting

    For Australian regulated entities, Solvexia produces APRA Connect forms in Excel and XML, generates D2A-ready XBRL, and submits automatically via the APRA Connect API. Pre-submission validation runs through Vizor Software’s Reporting API using the same rules as APRA Connect, catching errors before submission rather than after.

    Solvexia reports 78% faster APRA returns. In one deployment, an Australian wealth manager with over a million member accounts submits more than 50 different forms each year; automating that process saves 20 days annually, with a working proof of concept delivered in four weeks and the production solution in two months.

    RequirementWhy Auditors Need ItSolvexia Capability
    Complete audit trail Regulators need to see who matched what, when, and using which rule; not just the output. Full log of matches, approvals, modifications, and rule changes with user ID and timestamp on every entry, captured as a single connected record.
    Segregation of duties Different people must prepare, review, and approve; no single user should complete all three steps alone. Per-resource permissions (Reader, Executor, Editor, Owner) assigned so no individual holds the combination needed to both prepare and approve the same reconciliation. Configured rather than structurally enforced by a system block.
    Read-only auditor access Auditors must be able to review records without being able to modify them. Auditors are provisioned with Reader permission on the specific processes, tables, reports, and dashboards in scope. View-only, scoped per resource rather than account-wide. No dedicated auditor role exists; access is granted via the Reader permission.
    Version control on matching rules Auditors need to verify which matching rules were in place at any historical point during the period under review. Complete version history on matching rules, captured as part of the audit trail with user ID and timestamp on every rule change.
    Data retention Retention requirements vary by jurisdiction and industry; a single vendor default rarely satisfies all obligations. Configured at the process level. Each reconciliation type can be retained on the schedule its specific regulatory obligation requires, rather than one account-wide policy.
    APRA, XBRL, and SOX Support Regulatory reporting is non-negotiable for banks, insurers, and public companies; SOX-regulated companies require specific access and approval controls. APRA Connect forms in Excel and XML, D2A-ready XBRL, automated submission via the APRA Connect API, pre-submission validation via Vizor Software's Reporting API. For SOX: role-based access, configurable approval workflows, and a complete audit trail with rule version history; the controls a SOX-compliant process depends on.

    Solvexia security: hosting, certifications, and data residency (IT section)

    For a compliance team conducting a vendor security review, the key facts are:

    • Hosted on Microsoft Azure, with data encrypted in transit and at rest within the client database
    • SOC 2 Type 2 report covering controls and operational processes against standards established by the AICPA
    • GDPR standards applied across all locations, not only for EU customers
    • Penetration testing carried out every four months by the security firm Division 5. Most vendors test annually and almost none name the firm. The cadence and named provider are both worth noting in a control assurance review.
    • Instances available in Australian, EU, and US regions. Confirm the specific region for your deployment directly with Solvexia as part of your review.
    • Part of Ripple Treasury (formerly GTreasury), a platform trusted by more than 1,000 customers across 160 countries, including regulated financial institutions.

    When to confirm real-time reporting requirements before committing

    The FCA's PS25/12 safeguarding regime, in force since 7 May 2026, requires payment and e-money firms to reconcile on every reconciliation day, both internally and against safeguarding bank statements. Solvexia supports daily reconciliation, and frequency is a function of how the process is scheduled rather than a platform limit. What to confirm before committing is genuine intraday or continuous reconciliation, if that is what your obligation requires. Discuss your specific frequency with the implementation team rather than assuming either way.

    Conclusion

    Passing an audit requires software that proves your financial controls are operating as intended. So, does reconciliation software support SOX? Not on its own, no platform holds a SOX certificate. What it can do is provide the controls your auditors test: role-based access, separation of preparation, review and approval, configurable approval chains, and complete version-tracked audit logs. Solvexia provides all of these, and your auditors can verify each one in a demo.

    Ready to streamline your next audit and give your team total control over financial workflows? Request a demo of Solvexia’s audit-ready reconciliation software today to see how our automated platform satisfies your internal and external compliance standards.

    FAQ

    What audit trail does reconciliation software need to provide?

    A complete log of who matched which transaction, when, and using which rule; who approved each step; and who modified any rule, with what changed and when, all with timestamps and user IDs attached to every entry. Solvexia captures rule-change history with user ID and timestamp as part of a single connected record rather than separate logs that have to be cross-referenced manually.

    Does Solvexia support SOX compliance?

    Solvexia does not hold a SOX certificate, no reconciliation software does. What Solvexia provides are the controls a SOX-compliant process depends on: role-based access, separation of preparation, review and approval, configurable approval workflows, and a complete audit trail with version history on matching rules. Solvexia also holds a SOC 2 Type 2 report covering its own controls against AICPA standards, which is separate evidence your auditors may ask for.

    Can auditors access reconciliation records without being able to modify them?

    Auditors are provisioned with Reader permission on the specific processes, tables, reports, and dashboards in scope for their review. Reader is view-only and set per resource rather than account-wide, allowing precise scoping of what each auditor can see. Confirm whether Reader permission extends to historical rule version records directly with Solvexia during your security review.

    What is segregation of duties in reconciliation software?

    Segregation of duties requires that different users prepare, review, and approve a reconciliation, and no single user completes all three steps alone. In Solvexia, this is achieved through per-resource permissions (Reader, Executor, Editor, Owner) assigned so that no individual holds the combination needed to both prepare and approve the same reconciliation. Separation is configurable rather than structurally enforced by a system block.

    Does Solvexia support XBRL and APRA regulatory reporting?

    Yes, Solvexia APRA and XBRL support is a core use case. Solvexia produces APRA Connect forms in Excel and XML, generates D2A-ready XBRL, and submits automatically via the APRA Connect API, with pre-submission validation through Vizor Software's Reporting API using the same rules as APRA Connect. Solvexia reports 78% faster APRA returns.

    Is Solvexia hosted on Azure?

    Yes. Solvexia runs on Microsoft Azure with data encrypted in transit and at rest within the client database. Instances are available in Australian, EU, and US regions. Solvexia is part of Ripple Treasury (formerly GTreasury), a platform trusted by more than 1,000 customers across 160 countries.

    What security certifications does Solvexia hold?

    Solvexia holds a SOC 2 Type 2 report against AICPA standards and applies GDPR standards in all locations rather than only for EU customers. Penetration testing is carried out every four months by the security firm Division 5.