# Build onchain balance reporting for your institution.

Stream balance changes with GraphOps Substreams into your reporting database and re-read any figure with RPC at its block. Scope the integration with your engineering and supplier-review teams.

[Discuss your project](https://graphops.xyz/contact#enterprise) [Explore Substreams API](https://graphops.xyz/services/substreams#service-example) 

European institutions 

Worked example 

## Show where every figure in the report came from

Your finance team reports two EURC balances at month end. Internal audit asks where each figure came from, and supplier review asks who handled the data on the way.

At stake 

The report is accepted only if both questions have a documented answer.

Built with 

- GraphOps Substreams

- GraphOps RPC

### Month-end EURC balances

Block 1,100 · hash 0x9f…2c  

- Public network 

- SourceSelected network  

HandlesBlock 1,100 and its hash

You can checkThe same hash from any node

- Operated by GraphOps 

- IngestionChain nodes  

HandlesBlocks served to Substreams and RPC

You can checkRe-read results at the same block

- IndexingSubstreams  

HandlesEURC transfers for your addresses

You can checkBlock, transaction, and event index on every record

- Operated by your institution 

- StorageReporting database  

HandlesStored output, cursor, and retention

You can checkYour access controls and logs

- ReportTreasury balances  

HandlesFigures, lineage, and approval

You can checkYour approval record

#### Report figures and their lineage

- Operating0xa1…03 125,000 EURC  Block 1,100 0x9f…2c 0x4e…a1 / event 2  RPC re-read at block 1,100: 125,000

- Reserve0xc2…08 75,000 EURC  Block 1,100 0x9f…2c 0x7b…d9 / event 0  RPC re-read at block 1,100: 75,000

Report total200,000 EURC

### How it comes together

- GraphOps service

- Your systems and team

- GraphOps Substreams 

#### Stream balance changes into your database

Your consumer stores EURC transfers for both addresses with block, transaction, and event index, and saves the cursor after each commit.

- Your reporting system 

#### Compute figures with their lineage

Balances at block 1,100 carry the block hash and the last movement behind each figure.

- GraphOps RPC 

#### Re-read at the same block

Balance reads at block 1,100 return 125,000 and 75,000 EURC under the same block hash. Reads at older blocks need archive state on that network.

- Your reviewers 

#### Accept the evidence by owner

Engineering accepts measured behavior. Security reviews request fields, credentials, and logs. Procurement assesses locations, contracting entity, support, and exit terms.

ResultAudit gets a lineage for each figure, supplier review gets an operator for each stage, and a re-read at block 1,100 returns the same values.

European operation alone does not establish EU-only processing or regulatory compliance. Request workload-specific answers for your review.

Related workflows 

## Institutional workloads to evaluate

- ### Internal asset reporting

Read balances at explicit blocks for internal reports.

[GraphOps RPC](https://graphops.xyz/services/rpc)

- ### Client and operations applications

Build asset activity and position views from an indexed schema.

[GraphOps Subgraphs](https://graphops.xyz/services/subgraphs)

- ### Data integration and retained history

Retain package output in your storage under your data policies.

[GraphOps Substreams](https://graphops.xyz/services/substreams)

- ### Existing system integration

Connect node responses to a customer-run reporting integration.

[GraphOps RPC](https://graphops.xyz/services/rpc)

Evaluate with your data 

## Connect acceptance to a deployment decision

A technical result and supplier approval answer different questions. Record each decision with its owner so open terms stay visible.

- Test 01 

### A report operations can verify

Compare reference balances at the same block, including a failed request and a missing observation. Decide whether the report waits, marks a value unavailable, or carries an approved value with its original timestamp.

- Test 02 

### A data flow security can inspect

Document request fields, credential handling, application logs, and destination storage. Start from the company and privacy information, then request workload-specific processing and contractual details.

- Test 03 

### A scope procurement can assess

List required data locations, contracting entity, support, availability, and exit arrangements, and obtain scoped answers before approval.

### Bring to the first conversation

- Report format

- Network requirements

- Request volumes

- A data-flow diagram

- Your supplier questionnaire

[Explore current pricing](https://graphops.xyz/pricing)  

## Scope your institutional data requirements.

Work with GraphOps to define the technical approach, responsibilities, and service scope around your data flows and supplier requirements.

[Discuss your project](https://graphops.xyz/contact#enterprise)[Create account (opens in a new tab)](https://platform.graphops.xyz/auth/register)