Skip to content
QUANDIS

Solutions · Compliance automation

Every check run. Every decision recorded. Ready for the exam.

Compliance automation, built into the workflow: QBO puts military status and bankruptcy checks at the steps that require them, enforces your rules on every save, and keeps a dated audit trail of who did what. When an examiner asks, the evidence is already on the record.

For compliance directors, risk managers, and CCOs · Since 2003

Independently audited · SOC 2 Type 2 report · ISO 27001:2022 certified ISMS · Trust Center ↗

Audit defensibility

The examiner’s questions, answered from the record.

Audit findings rarely come from a rule nobody knew. They come from a check that was skipped, a result nobody kept, or a change nobody can explain. QBO keeps that evidence as a side effect of doing the work.

  1. 01

    Was the check run before the action?

    The check is a step in the workflow, and the action step depends on it, so the action can’t start until the check completes. Each step keeps its actual start and completion dates.

  2. 02

    Against what source, and as of what date?

    Military status is stored on the person with its source and the date it was verified, and the DoD certificate can be kept with the record. Bankruptcy filings are stored with their court, chapter, case number, and dates.

  3. 03

    Who changed the process, and why?

    Restarting a workflow or skipping it forward requires permission and a reason, and the reason is written to the record as a message.

  4. 04

    Who could see this customer’s data?

    Partner access is granted record by record and enforced on every screen and API call. Revealing a full Social Security number requires a specific permission and writes a security log entry naming the user and the person.

  5. 05

    How do you know the work was done correctly?

    Completed work is sampled by rule, at the rate you set, and the sample is routed to an audit worklist for review.

Verification checks, built in

The check runs at the step that needs it, every time.

A check that depends on someone remembering will eventually be missed. In QBO the check is a workflow step, the action waits for it, and the workflow branches on the result: continue, or route to a person.

SCRA · MLA

Military Search

Verify active-duty status directly from the Department of Defense (DMDC): SCRA status as of the date that matters, and MLA covered-borrower status when credit is extended. Run one search in real time, a batch file, or recurring checks across a portfolio.

  • Status, source, and verified date stored on the person
  • DoD status certificates kept as evidence
  • Name variations searched so aliases aren’t missed
Explore Military Search →

Bankruptcy filings · dockets

Bankruptcy Search

Check federal bankruptcy court records before you act, and monitor accounts for new filings and docket changes, so a filing that lands after your last check still reaches the right person.

  • Court, chapter, case number, and filing date on the record
  • Discharge, dismissal, and key bar dates tracked
  • Monitoring lists, with new filings and docket changes reported

See how Bankruptcy Search works.

Workflow · before the action

  1. 1 Verify military status
  2. 2 Check bankruptcy filings
  3. 3 If/then: covered or filed?
  4. true → exception worklist, assigned to a reviewer
  5. false → proceed with the action
Illustrative. Which steps run, and in what order, is defined in your workflow template.

Both checks are B2B services for organizations with a permissible purpose. They are not available to consumers.

Policy, enforced

Your rules hold, whoever enters the data and however it arrives.

Validation on every save

Validation rules run on the server whenever a record is saved. They can block the save with an error or allow it with a warning, and they apply the same way to a person on a screen, a spreadsheet import, and a partner calling the API.

Required and hidden fields by rule

A rules matrix can make a field required or hide it, without editing the form, so a policy change is a configuration change.

Approvals with separation of duties

A form’s state diagram lists each allowed status move and the role or permission it requires. QBO enforces it on every save, including imports and the API, and moves the work to the next reviewer’s worklist.

Imports checked before they land

Incoming files are staged and validated before anything is imported. A file that fails its checks imports nothing, and every row is tracked.

For how validation rules and rules matrices are built, see Business Rules in the QBO documentation.

Audit trail

A history you don’t have to reconstruct.

The workflow, the security system, and the data itself each keep their own record, so you can answer for the work, the access, and the exceptions.

How workflows record every step →
Dated workflow history
Every step records its estimated and actual start and completion dates, its status, and, for if/then steps, the result. Holds record how long work waited and why.
Corrections with a reason
Restart and Skip Forward require permission and a reason, and add a message to the record so the correction is part of the history.
Security log
Sign-ins, failures with their reasons, lockouts, impersonation, and API key resets are written to the security log. Impersonation can be turned off entirely.
Sensitive data, logged
Social Security numbers display masked. Each reveal requires the Unmask SSN permission and is logged against the user and the person.

Third-party risk

Vendors and outside counsel see only their part.

Partners who work in your system are a risk to manage, not a reason to email spreadsheets. QBO’s extranet security filters every screen and API call by record. Assigning a partner to a case grants that case and what’s beneath it, and nothing beside it. Click a party below to see what they see.

Viewing as
Which records each party can see on Account 1042
RecordYour teamField inspectorAppraiserCollection agencyLaw firm
Account 1042VisibleVisibleVisibleVisibleVisible
InspectionVisibleVisibleHiddenHiddenHidden
ValuationVisibleHiddenVisibleHiddenHidden
CollectionsVisibleHiddenHiddenVisibleHidden
LitigationVisibleHiddenHiddenHiddenVisible
Settlement quoteVisibleHiddenHiddenHiddenVisible
Internal reviewVisibleHiddenHiddenHiddenHidden
How partner security works →

Exceptions & oversight

Every exception gets an owner. Every sample gets a reviewer.

Exception worklists

When a check result needs a person, the workflow adds an exception item to a worklist, assigned by rule to a team and person, with a due date, and tracked to resolution.

Quality sampling

Sample completed work by percentage, with minimums and maximums set by rule, such as a higher rate for higher-risk work. Samples route to an audit worklist like any other task.

Reporting

Bundle saved queries into Excel reports that run on a schedule and arrive by email with secure download links, or build ad hoc reports for a specific request.

Notices from templates

Generate letters and notices from approved templates and your data, filed on the record. Send certified mail and track delivery and return mail.

Compliance in your industry

The same controls, in the vocabulary of your operation.

  1. 01

    Compliance for credit unions

    Member checks at the steps that need them, with partners seeing only the accounts they work.

  2. 02

    Compliance in mortgage servicing

    SCRA and bankruptcy checks before referral, sale, and other actions, with attorneys working in the same system.

  3. 03

    Compliance in insurance

    Claims and policy work as tracked cases, with every document, decision, and deadline on the record.

Your vendor review

Our own controls are independently audited.

Our controls are independently audited. The QBO platform has a SOC 2 Type 2 attestation report, and our information security management system holds an ISO 27001:2022 certification, both from A-LIGN. Our security documentation and policies are in the Quandis Trust Center, so your vendor risk review can start without waiting on us.

Trusted in regulated operationsSince 2003HousingWire TECH100Independently auditedSOC 2 Type 2 reportISO 27001:2022 certified ISMSVisit the Trust Center ↗

FAQ

Compliance and risk questions

Does QBO make us compliant?

No software does that on its own. QBO enforces the rules, checks, and approvals you configure, and keeps the evidence that they ran. Your compliance team and counsel decide what those rules should be.

Who can use Military Search and Bankruptcy Search?

Both are business-to-business services for organizations with a permissible purpose, such as lenders, credit unions, servicers, collectors, law firms, and property managers. Neither is available to consumers.

Does AI decide military status or bankruptcy status?

No. Military status comes from the Department of Defense’s Defense Manpower Data Center, and bankruptcy information comes from federal court records. AI in QBO assists the work around the checks, such as reading incoming documents or drafting review memos, and its output lands on the record for a person to review.

Do the rules still apply to data that arrives by file or API?

Yes. Validation rules and form state diagrams run on the server, so a spreadsheet import or a partner’s API call is held to the same rules as a person using the screen.

Can we check a whole portfolio, not just new records?

Yes. Military status checks can be queued for any set of people, and Military Search can re-check a portfolio on a schedule and report what changed. Bankruptcy Search can monitor accounts and report new filings and docket changes.

Where are your SOC 2 report and security policies?

The QBO platform has a SOC 2 Type 2 attestation report from A-LIGN, and the information security management system that protects it is certified to ISO 27001:2022. Security documentation and policies are available in the Quandis Trust Center at trust.quandis.com.

Show us your next exam. We’ll show you the evidence trail.

Walk through your checks, approvals, and exception handling running in QBO.

Request a Demo