Beyond ARM is stable. Read what the contract lets the vendor do before you renew.
DAKCS has sold collection software from Ogden since 1981 and counts more than 200 active Beyond ARM installs, most of them small and mid-sized agencies with a healthcare tilt. Nothing about the vendor is in trouble. What deserves a look is the shape of the deal: a Linux server with a Windows thick client, integrations that run through the vendor's hub, a consumer payment portal that works only with the vendor's sister processor, and terms that allow unilateral fee increases, an early-termination fee and a bar on competing integrations.
- Accounts, debtors & balances
- Payment history, notes & activity
- Active payment arrangements
- Stored cards & ACH, via your processor
- Compliance flags & audit trail
Migrating from DAKCS Beyond ARM (DAKCS Software Systems, Ogden, Utah; a Beyond Investments company) → Resolvah
What is happening at DAKCS Beyond ARM.
Dated and sourced. The things a buyer should know before deciding whether to stay.
- 1981 to 2005
DAKCS Software Systems is founded in Ogden, Utah, around a UNIX terminal collection program. Kent Green runs it until 2005; Lex Patterson until 2020.
- 2003
Pay Data Center, later PDCflow, is founded as a sister company to carry PCI compliance for DAKCS. Both sit under Beyond Investments, an Ogden family office; DAKCS's own job postings describe it as the financial and administrative arm for its subsidiaries.
- 2016 to 2021
QwikDial replaces the VIC dialer (2016); a new consumer portal (July 2021) replaces QwikFund by 2022. Public release notes stop at version 2.13.5 in March 2021; later builds are documented only inside the login-walled help portal. SOC 2 Type 2 attestation is in place from December 2018.
- 2020 to 2022
Andy Shumway becomes president (February 2020). Legacy modules are retired on the vendor's schedule: QwikContact in March 2022, QwikFund in August 2022. The customer summit runs in 2017 and 2019 and again in 2024; the community forum on the help portal goes quiet in 2023.
- 2024 to 2026
A Dane County, Wisconsin bid waiver (October 2024) puts a ten-user Beyond ARM subscription on the public record. DAKCS launches Collect AI in January 2025 (template-only replies, no PII sent to the model); on the consumer portals we could see in September 2026 it was not yet enabled. Roles open in 2026 include an engineering manager for platform and AI. No summit is found for 2025 or 2026.
Why agencies leave DAKCS Beyond ARM.
Agencies do not leave Beyond ARM because the vendor is failing. They leave because the architecture and the contract were written for a different decade: a thick client with terminal remnants, integrations that go through DAKCS, payments that go through DAKCS's sister company, and terms that give the vendor the pricing pen. Read the schedule your agency signed; then decide.
A Linux server with a Windows .NET thick client; reviewers have noted terminal-era components, small fonts and field limits inside it (2018 to 2021).
Integrations go through the vendor's hub, and the contract bars competing integrations and bypassing the payment processor. The consumer portal's payment iframe is PDCflow, the sister company, and nothing else.
The terms allow unilateral fee increases and charge an early-termination fee; the base support plan is phone hours in Mountain time, with email support and password resets excluded and on-premises customers paying extra.
Legacy modules get retired on the vendor's schedule, and customers end up layering LiveVox, TCN, Skit.ai, Floatbot or Balto around the core to get modern outreach.
DAKCS Beyond ARM vs Resolvah
Both can collect a debt. The difference is how it feels to your team, your clients, and the person on the other end.
An Angular consumer portal per agency that takes payments through PDCflow. Plain-language resolution, plan building and AI conversation are not the design; Collect AI sends template-only replies and, on the portals we could see in September 2026, was not yet enabled.
A warm, self-serve resolution experience. Dee explains the balance in plain language, offers plans people can actually afford, and lets them resolve it 24/7 from any phone.
AWS-hosted or on premises, with a Windows thick client on every desk.
Fully cloud-hosted and always current — nothing to install, patch, or keep alive on a server in your office.
SOC 2 Type 2 since 2018; e-OSCAR through a partner; call-frequency and consent rules live in your process and your dialer.
FDCPA, Reg F, TCPA and state rules built into the everyday workflow, with a complete, exportable audit trail on every account and message.
QwikDial, DCS texting and email, and a vendor-hub integration model; customers add third-party dialers and bots for the rest.
Modern automation and AI assist draft outreach, summarize an account at a glance, and surface the next best step — without taking the human out of it.
Per-user SaaS with custom support billed monthly, one-time conversion fees, and a contract that permits unilateral increases and charges to leave early.
Transparent, predictable pricing. The features that make recovery humane aren't locked behind surprise modules or per-seat upcharges.
Phone support in Mountain-time business hours; email and password resets outside the base plan. Resolvah takes your data under your agreement's data-return terms and reconciles it with you.
A Resolvah onboarding team works with yours at every step: we map your data, move it, reconcile it against your old system, and work with your payment processor so active arrangements keep running. Four weeks to three months, and we stay on through go-live.
Comparison reflects general, publicly-observable platform characteristics and is provided to help you evaluate a switch. DAKCS Beyond ARM is a trademark of its respective owner; Resolvah is not affiliated with or endorsed by it.
A migration you barely feel.
Beyond ARM is hosted for most customers, so the export runs through Beyond ARM's reporting and the data-return terms of your SaaS agreement; on-premises customers have the server itself. We scope the return format with you, map it, move accounts, history, notes and arrangements, and reconcile every total against Beyond ARM before cutover. Four weeks to three months, and Beyond ARM stays your system of record until you sign off.
Prepare
We scope your portfolio, confirm the export path, and schedule a calm migration window.
Move
Your data comes across — accounts, history, notes and active plans — with a Resolvah specialist on it start to finish.
Validate
We reconcile every total with you against your old system before anyone relies on the new one.
Go live
Your collectors pick up where they left off, and your old system stays put until you're ready to retire it.
Worried about payment tokens? We work directly with your existing payment processor to re-point the vault to Resolvah, so stored cards and ACH come across and every active arrangement keeps running. Nobody re-enters a card, and no plan is interrupted.
The honest list for this system, so cutover day holds no surprises.
- Accounts, debtors and balances
Exported through Beyond ARM's reporting or returned under your agreement, and reconciled account by account.
- Payment history and notes
Transaction and note history come across; we check counts and totals against Beyond ARM's reports before cutover.
- Active payment arrangements
Scheduled arrangements continue on their cadence.
- Stored cards and ACH
Payments run through PDCflow. We work with PDCflow, or the processor you choose next, to re-point the vault to Resolvah, so every plan keeps running.
- Credit reporting history
e-OSCAR runs through a partner and credit reporting through the vendor hub; we carry the reporting state across so the next file is consistent.
- Vendor-hub integrations and dialer configuration
QwikDial campaigns and hub connectors are Beyond ARM's own. Each becomes a live integration in Resolvah, not a carried-over setting.
- Letters and call recordings
Held by your letter vendor and your dialer. We help you export them for retention.
- Read your support-services schedule for the early-termination fee, the notice period and the data-return terms before giving notice; the contract also permits fee increases, so check what your renewal price will be.
- Ask DAKCS for a full data return in a documented format and how many days it takes; the default backup retention in the terms is two days, so take your own export first.
- Tell PDCflow a re-point of the token vault is coming, and get any fee in writing; if you intend to change processors, plan the vault transfer as its own step.
- List what you have layered around Beyond ARM (LiveVox, TCN, Skit.ai, Balto, letter vendors); each is re-pointed to Resolvah rather than carried over.
Switching from DAKCS Beyond ARM
Is DAKCS going away?
No. It is a stable, family-office-owned vendor with more than 200 installs, a SOC 2 attestation and a forty-year history. This page is about the terms and the architecture, not the vendor's survival: what the contract lets DAKCS do, what runs only through its sister company, and what it takes to leave on your schedule rather than theirs.
Our consumer portal payments run through PDCflow. Can we keep it?
You can keep PDCflow as your processor if you like it; the vault re-point is the same work either way. What changes is that the portal and the platform stop being tied to one processor by contract.
How painful is moving our Beyond ARM data to Resolvah?
We make it as painless as we can, and we do it with you rather than to you. Accounts, balances, payment history, notes, active arrangements and compliance flags come across, and we reconcile the totals against Beyond ARM before anyone relies on Resolvah. Anything that cannot come across (call recordings held by a dialer vendor, for example) is identified up front, so nothing is a surprise on cutover day.
Will active payment plans keep running when we switch from Beyond ARM?
Yes. We work with your existing payment processor to re-point the vault to Resolvah, so stored card and ACH tokens come across, scheduled arrangements continue on their cadence, and no consumer re-enters payment details.
How long does migrating from Beyond ARM take?
Four weeks to three months, depending on the size of the portfolio and how Beyond ARM stores its data. A Resolvah onboarding specialist scopes it with you first, so you get a date, not a range, before anything moves. Beyond ARM stays your system of record until the reconciliation is signed off.
Don't see your system? See every migration we support.
Leave DAKCS Beyond ARM behind — without leaving anything behind.
Book a 20-minute demo and we'll map your exact portfolio onto Resolvah, payment tokens and all.
