Frequently Asked Questions
We have our own xml formats we use. Can QDS adopt these xml formats?
Yes. QDS can transform our native QBO formatted data into your organization’s format. This is extra effort and will impact the implementation timeline.
We already expose various end points to accept data. Can QDS tap into these endpoints?
Yes. However there are two considerations: 1) if the current endpoint is not supported by QDS standard protocols then a custom Service Connector will need to be built. 2) Your current endpoint may require a certain xml format to correctly function. When QDS consumes a custom endpoint for a Service Connector, we generally transform the data from the QBO format to the required endpoint format. This is extra effort and will impact the implementation timeline.
Are results received from Quandis in a secure manner?
Yes, result files are built on the Quandis platform, and may be encrypted with PKI and/or transmitted securely via sFTP, FTPS or HTTPS to the client.
How do I know Quandis employees will not compromise my data?
Bankruptcy search is a completely automated process; Quandis employees are not involved with the mechanics of a Bankruptcy search. Quandis system administrators have access to the servers on which the data is processed, and are governed by our Security Policy and Procedures document.
Is the data that you process secure?
The request and result files are encrypted and/or transmitted via secure channels (sFTP, FTPS, or HTTPS). All data within Quandis for processing is stored in a secure SQL Server database, with SSNs being encrypted at rest. SQL backups are encrypted, and stored on RAID media in our alternate production data center. RAID media is physically destroyed upon disposal. We do not use tape backups or off-site storage of our backups. All access to RAID media is tightly controlled with a minimum of two-factor authentication, and employees with access are trained in accordance with our Security Policy and Procedures document.
How long do you retain the data?
We retain all data for 1 year by default. However, we can configure on a client-by-client basis different retention periods to comply with client retention policies. We recommend 1 year ensuring we can answer any questions that may arise concerning your data. The monitoring product requires that we retain the data for at least the duration of monitoring.
Is your system scalable? How many searches can you perform?
Quandis maintains two production SSAE 16 and SOC 2 certified data centers: one in CA and one in VA. Our Bankruptcy Search primary hosting location in our CA data center, with nightly backups transmitted to our VA datacenter. Each runs on load balanced web servers with SQL Server 2008 for back end data storage. The limiting factor in volume is the Pacer website.
When you run the Pacer search through your system is it running a local/district level search? Or National?
We offer both. The basic search is at the national level, but the advanced search also checks the regional court. The advanced search is recommended for near-real-time requirements like the morning of a foreclosure sale bankruptcy search, since regional courts do not deliver their data to the national database until the evening.
What time(s) do you run the search?
The searches are run against the Pacer web sites in near-real-time. If you request our Pacer service in real time, the screen scrape will typically happen within a few seconds. If you deliver a spreadsheet of data to search, we will queue each row and run them in near real time in order. For large spreadsheets, this may mean a delay of minutes or hours, depending on how many rows you’ve provided to us.
When is the data you run the search on valid. If you run the search today what time is that data valid from? What we are trying to figure out is if we run an in house search for 4pm today we know the search is valid as of 4pm today. Does your search have the same parameters or is the data valid from the earlier in the day or previous day?
The results are in real time as of the moment we execute the search. We do not cache Pacer data locally; we are screen-scraping Pacer in real time. If you issue a Pacer search request to us @ 4:02 pm, the results are the data reflected in Pacer as of 4:02 pm.