TemplatesGet a demo →Book a meeting

Bank operations, with the working shown

13 flows for the work a bank’s or credit union’s staff do every day: policy questions, regulator notices, call disclosures, statement breaks, vendor reviews and the questionnaires examiners and partners send. Every figure comes from your own systems and is quoted exactly, and anything that leaves the team waits for a person.

Your core and ledger, read-onlyYour policies and proceduresEvery run recorded with its steps, time and model costA person approves what reaches a customer or examiner

The work, template by template

Open them in the catalogue

Each opens in the builder as a working flow. Point it at your policies, procedures and exports, and press Test.

Where they land in a bank

Six of the thirteen, mapped to the queues compliance, operations and servicing teams already work.

Policy answer desk
Staff ask whether a fee can be waived, what a Reg E notice must say or which BSA procedure applies, and get the clause quoted, or a plain statement that policy is silent.
Regulator notice watcher
Reads the OCC, FDIC, Federal Reserve, NCUA or CFPB pages you choose every morning and posts to the compliance channel only when something affects you.
Call compliance check
Checks recorded servicing and collections calls against the disclosures your scripts require, and lists what was missed.
Statement reconciliation
Compares a correspondent, card or processor statement with your own records and lists only the breaks, computed in a table step rather than by the model.
Supplier risk scorer
Scores a vendor or fintech partner submission against your third-party risk criteria and sends anything below the bar to a person.
Ageing report
Groups open exceptions, disputes or tickets by age and owner and says what is oldest, from an export or a ticket API.

What your model risk and compliance teams will ask

Answered from how the product works, not from a slide. The full list of controls is on the security page.

Every figure comes from your systems
Reconciliation and reporting steps query your own ledger or exports, and the totals are computed in a table step in code. The model explains the result and is told never to state a number the table does not hold.
Nothing reaches a customer or examiner unapproved
Replies, escalations and anything sent outside the team stop at an approval step, which says what approving will do before anyone decides.
Only the records the reader may see
Each knowledge source carries its own access rules, applied in the retrieval query before any passage reaches a model, and database steps use a read-only connection you set up and can revoke.
Every run on the record
Its input, each step's output, how long it took, what the model cost and who decided, kept with the run and in an append-only audit log. Administrators can export records with an Ed25519 signature anyone can check offline.
Evidence for model risk review
Under SR 26-2, the April 2026 model risk guidance from US banking agencies, validators want to see what a tool was given, what it returned and who approved it. The run record and signed export are that evidence.
Your data boundary, your choice
Run it in Sphere's cloud, in a single-tenant environment in your own AWS account, or privately in your own cloud. SphereIQ does not train models on your data, and it is SOC 2 Type II certified, with the report shared on request.

Asked in every evaluation

Does it replace our core or our loan system?
No. It reads from your core, ledger and document stores through read-only connections, and those systems stay the systems of record.
Will it make credit or dispute decisions?
No. The templates are written to find, check, compare and draft. Decisions that affect a customer stay with your staff, and anything that leaves the team waits at an approval step.
Is this the same as Palladium?
No. SphereIQ is for your staff: policy answers, reconciliation, compliance checks and reviews. Palladium, also from Sphere, is customer-facing and resolves requests such as Reg E disputes and fee waivers end to end.
Our data is not laid out like the template.
The database steps carry example queries, and you point them at your own tables. The checks, the approvals and the write-up stay as they are.
Can we see it on our own policies and data?
Yes. We open a template in the builder, connect it to a sample of your documents and data, and run it with you.

Start with the queue that costs your team the most time

Bring one process, such as policy questions, statement breaks or vendor reviews, and we run the nearest template against your own material.