Skip to main content

Statements

Generate a statement for one wallet over a date range, and set the cadence, sections and formats that apply to every statement the organisation produces.
Open it fromReportingStatementsRoles:OwnerPlatform administratorConsole address: /reporting/statements

Statements gives an organisation owner or a platform administrator two cards. Generate statement produces a statement for one holder wallet, the investor wallet that holds the assets, on the selected network over a date range. “Statement policy” sets the cadence, the sections and the file formats that apply to every statement the organisation produces. A statement holds the sections the policy lists, for the wallet and the period. The platform marks it reconciled only when the opening balances plus the movements equal the closing balances, a check of the statement's own figures and not a comparison with a bank or custody record.

Asking again for the same range returns the same statement. A policy change applies to statements produced afterwards, not to earlier ones.

The “Statements” page as an organisation owner sees it.

The Generate statement card holds the fields “Holder wallet address”, “First day” and “Last day” and the “Generate statement” button. The “Statement policy” card holds the “Cadence” list, the checkboxes under “Sections” and “Formats”, an optional reason, and the “Save policy” button.

Steps

Enter the holder wallet

On “Generate statement”, enter the wallet in Holder wallet address. The picker lists holder wallets only, never token contracts. You can still paste any wallet address. The Console refuses an address that is not a valid wallet address and says “Enter a valid wallet address, starting with 0x.”

Choose the days

Enter the First day and the “Last day”. Both days are part of the statement. The last day must not be before the first day, and a statement covers at most 366 days. The Console says “Choose a first and a last day.”, “The last day must not be before the first day.” or “A statement covers at most 366 days.” beside the dates.

Select Generate statement

Select Generate statement. The “Generated statement” card appears below the two cards. Changing the wallet or a date clears the card.

A statement covers only blocks that are final on the chain. When the last day is not final on the chain yet, the card reads “No statement can be produced for this range yet” and asks you to choose an earlier last day or to try again later.

Read and download the result

The card shows the “Holder”, the “Period” as “first day to last day”, the “Formats” the statement is available in, and “Generated at” in UTC. A Reconciled badge means the opening balances plus the movements equal the closing balances for every security.

When they do not, the card reads This statement is incomplete, with “Opening balances plus the movements listed do not equal the closing balances for every security. Do not rely on it.” Do not hand such a statement to a holder. Check the wallet and the period.

Select “Download CSV”, “Download XLSX” or “Download PDF”, one button for each format the statement is available in. The file name carries the wallet and the period.

Set the statement policy

On Statement policy, which applies to every statement the organisation produces:

  1. Choose the Cadence: “Daily”, “Weekly”, “Monthly” or “Quarterly”. After each period of that length closes, the platform produces a scheduled statement for every holder of the organisation's assets.
  2. Under Sections, tick what a statement holds: “Positions”, “Portfolio”, “Movements”, “Profit and loss”, “Fees”, “Deposits and withdrawals” and “Corporate actions”. Choose at least one section.
  3. Under Formats, tick “CSV”, “Excel workbook” and “PDF” as needed. Choose at least one format. “Excel workbook” downloads with “Download XLSX”.
  4. Enter a Reason (optional) if you want one recorded. It is recorded in the audit trail with the change, and takes up to 1,000 characters.
  5. Select Save policy. The button is unavailable until a section and a format are ticked and something changed. The Console confirms with “Statement policy saved”.

A change to the policy is recorded in Audit trail as a change to the Statement policy, with the earlier and the new values.

Troubleshooting

What you see
What it means and what to do
“Statements are managed by organisation owners and platform administrators”
You are neither an organisation owner nor a platform administrator. Ask one to change the policy or generate a statement.
The screen shows only its title
The deployment's Reporting and finance operations module does not allow changes, so neither card is offered. Ask the platform operator.
This statement is incomplete
The balances do not reconcile for at least one security. See Read and download the result.
The statement policy could not be loaded
The policy card could not read the current policy. Statements already produced are unaffected. Use the control to try again, or refresh the screen.
Save policy is unavailable
Either no section or no format is ticked, or nothing changed since the last save.
The statement is too large to produce
The range holds more than 120,000 rows. Choose a shorter range and generate again. Nothing was stored.
A generate or download request fails with a message
The Console shows the platform's reason. Read it, correct the wallet or the dates, and try again.

API routes

The two cards use these routes of the Platform API, which the investor statements guide describes. A caller can also generate a statement for a wallet they hold without the owner or platform administrator role:

  • GET /api/v2/reporting/statements/policy and PUT /api/v2/reporting/statements/policy read and change the policy.
  • POST /api/v2/reporting/statements generates a statement, and GET /api/v2/reporting/statements lists them.
  • GET /api/v2/reporting/statements/{statementId}/download returns a statement in one format.

Was this page helpful?