VSN|CONNECT · Future finance, made simple. · Prelaunch r2
VSN|CONNECT FDMS · Finance & Data Management System

Future finance,
made simple.

Finance,
made simple.

Keep your provider.
Or use VSN Pay.

Being built as one system for your organization's payments, records and data. Keep your payment provider, or use VSN Pay when it opens.

Request early access

Prelaunch · Not live yet · Opening to a first group of verified organizations

A new era of finance and data.

FINANCEFinancial workflows and payment-provider connections.
DATARecords, evidence and source history.
MANAGEMENTTeam coordination, permissions and approvals through the XFO Workroom.

VSN|CONNECT is being built as a Finance & Data Management System. Teams work through the XFO Workroom, connecting financial workflows with records and evidence in the VSN Registry, while payments are executed through authorized payment providers.

How it will work

Five steps. Then it runs quietly.

  1. 01 Install Add VSN|CONNECT to the way you already work. Web and phone.
  2. 02 Pick your field Choose your field of work, so everything fits from day one.
  3. 03 Sign up your organization Your team and their roles, set up once.
  4. 04 Your workroom opens Payments and records, side by side, for the whole team.
  5. 05 COMING
    Meet Vyen Your guide to navigating the network.
VSN Pay

Keep your provider. Or use VSN Pay.

Already paid through a provider you trust? Keep it. Each payment is designed to get its record in your workroom, whichever provider executes it.

RECORDS ONLY · YOUR PROVIDER

Keep your provider.

Payments stay where they are. VSN|CONNECT is designed to keep the record beside each one.

Paymentvia your provider · example
RECORDED
VSN PAY · PROVIDER RAIL · PLANNED

Or keep it simple with VSN Pay.

Payments and their records in one place, from the first invoice to the last. When it opens, licensed payment providers will execute every payment.

Paymenton VSN Pay · example
RECORDED

Designed so the record keeps itself, quietly in the background. Your people approve what moves.

Settlement

Programmable Settlement Infrastructure

Designed to connect settlement terms, supporting evidence, rules and required approvals in one traceable workflow. Authorized financial providers execute payment movement; the outcomes they confirm stay linked to their records.

INTENDED WORKFLOW · CONCEPT
  1. 01Obligation recordedWhat is owed, and on what terms.
  2. 02Evidence reviewedWhat was supplied, and what is missing.
  3. 03Action approvedThe required people sign off.
  4. 04Payment confirmedThe provider reports the payment outcome.
  5. 05Settlement closedA separate governed decision, linked to its record.

Five different states, each shown on its own. A payment confirmation doesn't close a settlement.

The Workroom

Everything behind a payment, in one record.

What was agreed, what was paid and the evidence behind it, kept together where your whole team can see it.

PLANNED XFO WORKROOM AREAS
TodayPaymentsClients & VendorsRecordsReview & EvidenceClose & Year EndSettings

Work in the XFO Workroom, or later connect your own systems through approved APIs. API access is under development.

Workroom ILLUSTRATIVE · SYNTHETIC DATA
Search records
Rivera kitchen · line rebuild $9,600.00 Rivera Homes SETTLED
Cabinet install · Unit 4B $3,240.00 Harbor & Pine PAID
Quarterly retainer · Q4 $6,000.00 Marlow Group AGREED
Roof inspection · Elm Street $450.00 Coastline Realty AGREED
RECORD Rivera kitchen · line rebuild With Rivera Homes · Oct 14
$9,600.00
EVIDENCE
Signed agreement Invoice 1042 12 site photos
AgreedOct 2
Payment reportedOct 12
Evidence verifiedOct 13
Settlement confirmedOct 14

Corrections are added with who, when and why. Nothing is overwritten.

Evidence up front.

Sources traced.

Changes attributed.

The XFO Workroom, from Xaelis

VSN Registry

One central Registry. One lasting number per record.

Each accepted Payment Record, and each eligible Settlement Record, is designed to get its own permanent number on the central VSN Registry. Ordinary workroom tasks don't get numbers. The Registry isn't issuing or publishing records yet.

Append-onlyCorrections are added, never written over.
One identityThe number stays with its record as status changes.
Private by defaultKnowing a number doesn't grant access.
HOW A VSN NUMBER READSSPECIMEN · NOT ISSUED
VSN · R001 · 0123 4567 89AB CDEF GHJK MNPQ · FSXY
VSNThe public namespace.
R001The Registry format.
RECORD24 random symbols. No names, dates or amounts.
CHECKCatches typing mistakes.

A number or its check doesn't prove a payment succeeded, confirm identity or grant access. Lookup isn't available yet.

Coming to the workroom

Help when you need it. A finished year when you don't.

VYEN BY XAELISCOMING

Meet Vyen, your guide.

Ask about any record and she'll find it and explain it. Available 24/7 when she arrives. Vyen helps; only people approve payments.

YEAR ENDCOMING

Your year, ready for your CPA.

An annual portfolio with every figure traced to its record. The advice stays with your CPA.

DIGITAL SIGNATURESCOMING

Signed where the work lives.

Agreements, approvals and printed records for clients or patients, signed inside the workroom.

Who it's for

Built for any organization.

Contractors & tradesBids, change orders, draws and final payment.
Insurance & claimsClaims, supplements and payouts, each with its evidence.
Professional servicesRetainers, milestones and invoices.
Property & real estateDeposits, inspections and closings.
NonprofitsGifts, grants and how every dollar was used.
HEALTH & SCIENCE · WITH XYVELORCOMING

Hospitals, practices, labs and research.

Xyvelor will bring VSN|CONNECT to healthcare and science: practices and hospitals, laboratories, research facilities and public agencies.

Security

Quiet by design. Careful by default.

Access by roleEach person sees what their role allows.
Every change attributedWho, when and why, on every record.
Nothing overwrittenCorrections are added beside the original.
People approve paymentsAI can explain. Only your people approve and release.

Not a bank. Not a processor. The record.

VSN|CONNECT is designed never to hold your funds. Payments are executed by licensed banks and payment providers, under their own controls. Provider payment status and governed Settlement closure are separate decisions.

These are design commitments for launch, not certifications. Security implementation and independent verification remain in progress.

For payment providers

Your rails. Our records.

We're exploring integrations with payment providers: records and settlement workflows beside the payments you already process. Any integration is proposed and subject to agreement.

FAQ

Good questions.

Not yet. It's in prelaunch. We're opening early access to a first group of verified organizations. This design preview does not submit requests. A verified early-access contact path will be added before registration opens.

No. Keep your provider, or use VSN Pay once it opens. Either way, payments are executed by authorized payment providers, and each payment is designed to get its record in your workroom.

What was agreed, what was paid and the evidence behind it, in one place. It's verification and audit evidence about the recorded activity. On its own, it doesn't establish payment finality.

Where accepted Payment Records and eligible Settlement Records are designed to get their permanent numbers. Ordinary tasks don't. Corrections are added, never written over, and knowing a number doesn't grant access. The Registry isn't issuing or publishing records yet.

Vyen by Xaelis is your guide to the network. She's coming soon, and she'll be available 24/7. She finds and explains; she never moves money.

No. It hands your CPA a finished year of records. The advice stays with them.

Early access

Be among the first.

We're opening VSN|CONNECT to a first group of verified organizations. Tell us a little about yours.

{{ formErr }}

DESIGN PREVIEW · NOTHING IS SENT FROM THIS PAGE
PREVIEW · NOT SENT {{ thanks }}

This preview doesn't send or save anything, so you're not on a list yet. Early access will open through a verified contact path.