Posted on — Leave a comment

What We Chose Not to Build Into ID Verification

Most identity-verification platforms quietly collect more than they advertise: IP address, device fingerprint, browser fingerprint, even behavioral telemetry like how long you hesitated filling out a form. It’s standard practice, and there’s a real fraud-detection argument for it.

We looked hard at adding it to NEXIOS AML/KYC’s remote verification flow — the one your customer uses from their own phone, from wherever they are, to submit an ID photo and a selfie. We decided against it.

That flow exists specifically because the person being verified is remote and never physically present — the exact context with the most real legal exposure around biometric data and consent. Our protocol makes an explicit promise: no device identifiers, no IP, no geolocation, nothing beyond the document and the selfie someone actually agreed to submit. Adding invisible tracking on top, even well-intentioned, would mean quietly breaking that promise.

We kept what already does real fraud-detection work without that tradeoff: on-device liveness detection that catches a photo-of-a-photo or a virtual-camera replay, MRZ and barcode cross-checks against what the customer typed, a tamper-evident hash-chained audit log, and sanctions/PEP watchlist screening with a staleness policy that actually gates the verdict.

We also just shipped a real partner API — bearer-token auth scoped per firm, idempotent writes, the same audit trail, self-service token management, no engineering ticket required.

None of this is a pitch dressed up as a principle. It’s what we actually built, and the tradeoff we actually chose, when a faster path was sitting right there.

— Norman Fuchs, NEXIOS

Posted on — Leave a comment

The ERP for Companies That Have Outgrown QuickBooks

There’s a real gap in the market nobody talks about: a company outgrows QuickBooks — multi-entity, real inventory, a finance team that needs actual BI — long before it’s ready for a six-figure NetSuite implementation and the system-integrator relationship that comes with it.

We built NEXIOS ERP for that exact gap.

Real multi-entity consolidation (schema-level isolation per company, not row filtering a bug could leak).

Real BI — trend forecasting with confidence bands, a 13-week cash forecast that places receipts at each customer’s actual payment-lateness date, and now an AI assistant that narrates it, grounded against the real numbers.

A real QuickBooks migration path, not a slide. We tested it ourselves this week: uploaded an export, watched it correctly flag three account collisions (never silently merged, each one reviewed), confirmed it, and watched everything post as fully balanced double-entry journal entries.

We’re not claiming NetSuite-grade depth — twenty years of edge cases isn’t something any product closes overnight. We’re claiming the honest step up from QuickBooks.

— Norman Fuchs, NEXIOS

Posted on — Leave a comment

The Net Capital Squeeze: Why Small BDs Are Rethinking Their Back-Office Stack

Net capital rules (SEC Rule 15c3-1) haven’t changed dramatically for most small broker-dealers in years, but the cost of staying compliant with them has. Between rising vendor fees for fragmented point solutions, the compliance headcount needed to manage three or four separate systems, and the operational risk of manual reconciliation between them, a lot of firms in the 5–100 rep range are quietly running tighter margins on compliance overhead than most people realize.

This isn’t a story about regulation getting harder — net capital computation itself is the same math it’s always been. It’s a story about tooling not keeping pace with firm size. Enterprise broker-dealers can absorb the cost of custom-built, fully staffed compliance operations. A 20-rep independent BD generally can’t, and often ends up buying smaller, cheaper versions of enterprise tools that still require the same manual stitching-together.

The shift worth watching: firms consolidating what used to be three or four vendor relationships — back-office accounting, AML/KYC onboarding, communications archiving, sometimes a separate WSP/manual builder — into fewer, connected systems. Not because the regulations demand it, but because the operational overhead of fragmentation has become the real cost center, more than the compliance requirements themselves.

If you’re a 5–100 rep BD and haven’t actually added up what your compliance stack costs in logins, support tickets, and reconciliation time — not just subscription fees — it’s worth fifteen minutes to do that math.

— Norman Fuchs, NEXIOS