Compare
Continuousvs Callvu
Continuous automates bank and credit union back-office operations: nightly batch, ACH and file movement, plus validation of lending documents and HMDA, CRA and 1071 data already in your systems. Callvu is the Completion and Compliance Layer: it runs the regulated process itself, from the member's request through the back office to the core, enforcing compliance at every step while the work runs, so the data is right before it reaches the system of record. Validation after the fact and enforcement during the run solve different problems, and many institutions need both.
At a glance
Runtime compliance enforcement
Front-to-back-office handoff
The fair version
What Continuous is built for.Sourced from their own pages.
Continuous is the new name, since August 2025, of SMA Technologies [1], a Thoma Bravo portfolio company [2] that describes its platform as automation and orchestration built for banking [3]. OpCon orchestrates ACH, nightly processing, transaction posting and file movement across core and third-party systems, detects exceptions and resumes workflows once they are fixed [4]. Encapture, acquired in November 2024 [8], validates indirect auto, mortgage and commercial lending files [5][6] and checks HMDA, CRA and 1071 data against source documents [7]. Permission Assist, from the Sycorr acquisition, handles user access reviews and provisioning [9]. Continuous says more than 1,600 financial institutions use it [1] and integrates with cores such as Jack Henry Symitar, Fiserv DNA and Corelation KeyStone [10].
When to choose which
Two different jobs.Pick the one you need.
When to choose Continuous
Choose Continuous when the need is IT operations automation: scheduling and orchestrating nightly batch, ACH, posting and file movement with dependencies across the core and third-party systems [4]. It also fits when you want lending files and HMDA, CRA or 1071 data validated against source documents across the whole portfolio rather than by sampling [7], or help keeping user access reviews audit-ready [9].
When to choose Callvu
Choose Callvu when you want the regulated process itself run end to end, from the member's or customer's first request through the back office to the core and the loan system. Callvu orchestrates the work, routes it by work type, skill and due date, applies rules and policies and manages every decision, and it runs the handoff in the same process with five moves: it prefills from what the core already knows, classifies each request the moment it lands, chases and verifies documents from members and outside parties on a clock, routes decisions to the Decision Desk, and writes the result back by API. Back-office planning starts the moment the front end starts.
Choose Callvu when you want compliance enforced during the run, not validated afterward. Continuous describes closing a validation gap between the loan system, the core and imaging that teams otherwise fill by hand [7]. Callvu prevents that gap: a deterministic orchestrator runs every step of a defined workflow, Callvu Studio comes with most regulations already loaded as policies, and a step that fails a control does not run. Errors are stopped before data reaches the system of record, and every run leaves a Decision Trace and an Audit Trace, pushed in real time to your GRC and BI tools.
Side by side
The verifiable facts.Nothing else.
Every cell about Continuous is sourced from its own public pages. Runtime enforcement and the handoff lead the table because they are where the two differ most.
| Capability | Continuous | |
|---|---|---|
| Primary role | Completion and Compliance Layer between every front door and the system of record | Automation and orchestration for bank and credit union operations: IT operations, lending document validation, compliance data validation, access management [3] |
| Runtime compliance enforcement | Yes. A deterministic orchestrator runs every step; AI never runs the process. Every regulation and company policy is enforced on every step while the work runs, whether a person or an AI started it; a step that fails a control does not run. A Decision Trace and an Audit Trace for every run | Not a platform capability. Compliance logic is built into each workflow, and HMDA, CRA and 1071 data is validated against source documents throughout the year [7] |
| Front-to-back-office handoff | Yes, end to end: prefill from the core, classify the work, chase and verify documents, route decisions to the Decision Desk and write back to the system of record. Back-office planning starts the moment the front end starts | Works between the loan system, core and imaging after data arrives; no member-facing intake described [7] |
| Orchestration, routing, rules and decisioning | Yes: workflow orchestration, routing by work type, skill and due date, rules and policies, and human decisions in the Decision Desk | Yes for IT operations: OpCon orchestrates batch, ACH and file movement with dependencies and exception handling [4] |
| Lending documents | Requests each missing item from the borrower or outside party on a clock, reads it on arrival (OCR) and checks it against what the loan type needs before the loan moves | Encapture validates indirect auto, mortgage and commercial lending files and routes exceptions to staff [6] |
| Compliance data | Enforces the data each step requires while the work runs; a step that fails a control does not run, and every step is recorded in the Audit Trace | Validates HMDA, CRA and 1071 data against source documents, with exceptions logged [7] |
| Core integrations | Fiserv, FIS, Jack Henry, CSI, Corelation (KeyStone), Finastra and lending systems such as nCino and MeridianLink; more added per customer | 400+ banking integrations, including Jack Henry Symitar, Fiserv DNA and Corelation KeyStone [10] |
| Who builds it | Callvu builds every process, trains your team and stays through launch and ongoing management, included in the license; a proof of value on one real process comes first, in 4 to 10 weeks | IT defines workflows; business users trigger prebuilt workflows through OpCon Self-Service [4] |
Using both together
Keep what works.Add the layer that finishes it.
Continuous and Callvu work at different points. Continuous keeps orchestrating batch, ACH and file movement and validating data across systems. Callvu runs the member-facing process and the handoff, then writes complete, checked data to the core and the loan system by API, so less needs correcting downstream. Where you do not need IT operations automation, Callvu runs the whole process on its own.
Proof
Live in production.At regulated enterprises.
FAQ
The questions buyers ask.Answered plainly.
Does Continuous enforce compliance at runtime?
What are alternatives to Continuous for credit union back-office automation?
Continuous Encapture vs Callvu for loan document checks: which fits?
Can a bank use Continuous and Callvu together?
How fast can Callvu go live at a community bank or credit union?
Sources
Every claim,sourced.
- https://www.businesswire.com/news/home/20250820293174/en/SMA-Technologies-Evolves-into-Continuous-Expanding-Automation-Solutions-for-Financial-Institutions
- https://www.thomabravo.com/companies/continuous
- https://www.continuous.com/
- https://continuous.com/it-operations-how-we-help/
- https://continuous.com/lending-loan-operations/
- https://continuous.com/lending/
- https://continuous.com/compliance/
- https://www.businesswire.com/news/home/20241107663507/en/SMA-Technologies-Acquires-Encapture-Adding-Intelligent-Document-Processing-IDP-to-its-Automation-Capabilities
- https://www.businesswire.com/news/home/20250825504702/en
- https://continuous.com/credit-unions/
Last verified: 2026-11-04. Facts about other vendors come from their public pages, filings and press, as of that date. Vendor names are trademarks of their owners. To report an error, contact Callvu.
See it on your process.
Bring one regulated process. We will show you the handoff and runtime enforcement on it.