Business
Treasury built for modern operations.
VaultRail brings treasury, payments, approvals, policies, risk, reconciliation and audit into one operating environment.
Treasury
Know where business liquidity stands.
Available, reserved, in-transit and pending-reconciliation states describe different financial realities. Wallet observation alone is not canonical treasury truth.
Explore TreasuryObserved wallet or provider state does not become canonical treasury truth by display convention.
- 01Draft
- 02Preflight
- 03Policy checked
- 04Awaiting approval
- 05Authorized
- 06Submitted
- 07Settled
- 08Reconciled
Payments
Move money through a controlled lifecycle.
A payment can be drafted, checked, approved, authorized, submitted, settled and reconciled without collapsing those stages into one optimistic status.
Approvals
Authority should be explicit.
Who requested a payment, who reviewed it, what policy applied and what remains outstanding should stay visible before financial authority is exercised.
Example logic only. Actual policy depends on the organization and configured authority.
Policies
Rules before money moves.
Deterministic controls can evaluate amount, wallet, asset, network, counterparty, department, risk context and time. AI should never become the source of payment authority.
Policy input stays explainable and reviewable before authorization.
Policy input stays explainable and reviewable before authorization.
Policy input stays explainable and reviewable before authorization.
Policy input stays explainable and reviewable before authorization.
- From
- Operations Treasury
- To
- Approved vendor
- Asset
- USDC
- Network
- Base
Illustrative workflow. Asset, network and execution availability depend on supported product state.
Preflight
Understand the transaction before signing it.
Source, destination, asset, network and expected effects should be inspectable before authorization. Simulation can inform a decision; it does not replace policy or approval.
Risk
Show the evidence behind risk.
New counterparties, unusual amounts, known contracts, simulation results and unexpected permissions are more useful when the underlying evidence remains visible.
Risk state should expose supporting evidence instead of relying on an unexplained score.
Receivables · Developing
Collect, match and reconcile.
Invoice, payment link, received funds, matching, reconciliation and receipt are the intended lifecycle. Public payment infrastructure is represented separately at pay.neptlium.com; availability remains product-state dependent.
Illustrative lifecycle state.
Illustrative lifecycle state.
Illustrative lifecycle state.
Illustrative lifecycle state.
Illustrative lifecycle state.
Wallets + accounts
Wallets are infrastructure. Treasury is the product.
Root Treasury, Operations, Vendor Payments and Web3 Operations can represent business purposes while signing technology remains a separate infrastructure decision.
Purpose-driven account context without implying a specific custody or provider relationship.
Purpose-driven account context without implying a specific custody or provider relationship.
Purpose-driven account context without implying a specific custody or provider relationship.
Purpose-driven account context without implying a specific custody or provider relationship.
- 01Payment created
- 02Policy evaluated
- 03Approval granted
- 04Wallet authorization
- 05Transaction submitted
- 06Settlement confirmed
- 07Reconciliation completed
Audit
Every important action should leave evidence.
Payment creation, policy evaluation, approval, wallet authorization, submission, settlement and reconciliation should remain explainable months later.
AI · Concept
Intelligence without authority.
Where intelligent assistance is introduced, its role must remain bounded. This is a product principle, not a claim that every capability shown is currently live.
AI may
- Explain
- Summarize
- Detect
- Prepare
- Recommend
AI may not
- Approve
- Sign
- Override policy
- Change ledger truth
- Modify audit history
Business treasury, payments, receivables and related capabilities are subject to product availability, eligibility, supported infrastructure and operating requirements. Illustrative workflows do not imply that every capability or rail is currently available.