Treasury

See treasury clearly.

Understand where organizational funds sit, what is available for operating needs, and the movement and control context around each destination.

Get Started Discuss Treasury

Illustrative interface concept — not live account data.

Treasury overviewOrganizational view

Liquidity context

Primary reserve

AvailableReservedPending context

Vendor operationsInternal movement contextReviewed

Approved destinationExternal destination recordKnown

Treasury overview

Location before movement.

Operating fundsPrimary reserveWorking liquidity context

Committed fundsReserved contextObligations remain visible

DestinationsKnown endpointsAuthority travels with movement

Accounts and structure

Organize money by operating purpose.

A treasury view should explain the relationship between reserves, working funds and destinations without turning the page into a portfolio or performance screen.

Organization treasury

ReserveLiquidity context

OperationsWorking funds

DestinationsAuthorized context

Movement historyContextState

Reserve → OperationsWorking liquidityRecorded

Operations → DestinationVendor purposeUnder review

Destination updateAuthority changeRecorded

Movement visibility

Follow why money is moving.

Movement history should carry purpose and destination context, not just direction. Review lifecycle states separately so intent, authorization and downstream completion are never blurred together.

Authorized destinations

Destination context stays close.

Keep ownership, purpose, review status and changes visible around the endpoint a finance team intends to use.

Destination recordVendor operating destination

Purpose: Operating expense
Authority: Reviewed destination
Change record: History retained

Treasury

Know where the money is — and the context that governs it.

Get Started See Payments

Connect liquidity to the work it needs to support.

Treasury is the organization financial context within Neptlium. Its product direction connects operating funds, obligations, destinations and the people responsible for decisions.

Plan around obligations

Separate available liquidity, reserves, commitments and expected receipts. Consider timing, currency, entity and restrictions when assessing a funding need. An expected receipt should not be treated as available operating cash.

Keep responsibility attached

A useful payment review brings together purpose, counterparty, amount, destination and supporting records. Organization membership, permissions and any applicable approval policy must be established before an action can proceed. Personal account access does not grant authority over organizational funds.

Questions and next steps

How is Treasury different from Pay?: Pay concerns the payment interaction. Treasury concerns the organization’s financial position, obligations and the record of what happened to its money. A payment confirmation alone does not establish reconciled treasury proceeds.
Are all currencies, bank rails and stablecoins supported?: No universal support is implied. Confirm the specific currency, rail, network, jurisdiction, limits and fees for any service before relying on it.