A statement is an official summary of financial transactions that occurred within a given period for a bank account held by a person or business. Statements are commonly used by account holders to monitor cash flow, check for possible fraudulent transactions, and perform bank reconciliations. Most Galileo clients deliver statements electronically, with some offering a paper option. Issuers in the United States are typically required to send a statement for an account only if one transaction has been made on the account during the statement period.

## What's in a statement?

Because a statement is a report of account activity, statements should display activity summaries (debits, credits, fees) as well the details of each transaction that took place during the statement period. Statements should also display the account balance as of the statement date, fee totals, and any interest with the interest rate.

### Statement options

As a Galileo client you have these options to provide statements:

• **Create statements from the RDFs** — Use this option if you want to customize your statements beyond what Galileo offers or to provide statements for credit accounts. See <a href="doc:creating-statements-from-the-rdfs" target="_blank">Creating Statements from the RDFs</a> for guidelines.

• **Obtain JSON statement data from Galileo** — Use this option if you want to create basic statements for debit accounts using JSON files. Continue reading for instructions.

## Obtaining statements from Galileo

Galileo currently offers statement data for these account types:

• DDA plus overdraft

• Savings / Interest

• GPR

If account holders have all three account types, for example, then Galileo would generate three statements per month for them.

Keep the following in mind:

• Amounts shown are always in the currency in which the account is based, not the currency at the point of sale.

• Statement periods begin at midnight on the first day of the statement cycle and end at 23:59:59 on the last day according to <a href="ref:galileo-system-time" target="_blank">Galileo system time</a>.

• Galileo stores your statement data for two years.

### Retrieving statements on-demand

You can retrieve individual account statement data in your interface by calling Get Access Token and then assembling an HTTP call.

#### Get Access Token call

These parameters are required for the <a href="ref:post_getaccesstoken" target="_blank">Get Access Token</a> call:

• `accountNo` — Use the <<glossary:PRN>> of the account.

• `type` — Pass `1` (account)

Galileo returns these values:

• `token` — A case-sensitive alphanumeric string, for example, `hpSVyayQScHmhJS6_MVXT1WlsFRQoDJrRu_fi_JlX2Jo2dgg5p`

• `expires` — The date/time the token expires, formatted as `YYYY-MM-DD hh:mm:ss` The default expiry is 300 seconds and/or 3 attempts. You can change default token-expiry parameters with the TSECV and TUSEC product parameters.

#### HTTP request for the statement

With the token assemble an HTTP call to retrieve the statement data, as shown in the example. The URL in the example is for an AWS instance that Galileo provisions for each client. If you do not already have an AWS URL, request one from Galileo This example is for the <<glossary:CV>> environment. For <<glossary:Production>> change the `cv` in the URL to `pd`.

where:

• `clientname` — The name of your tenanted AWS instance

• `token` — The token returned by Get Access Token

• `config` — A value provided by Galileo

• `date` — Statement date in MMYY format. The month corresponds to the first day of the statement period.

• `statementType` — Type of statement to return:

  • `G` — GPR

  • `D` — DDA, including overdraft

  • `S` — Savings or interest-bearing account

• `output` — `json` <!--Legacy clients can use `pdf`, and for those who want both JSON and PDF versions, pass `json%2Bpdf`. -->

##### Example HTTP call

Galileo returns a JSON of the statement data, which you can present electronically or [merge into a PDF template](🔗). You can print the PDFs on paper for those account holders who have opted out of electronic statements.

Each JSON file name has this format, `stmt_PRN_mmyy[_esign].json`, where:

• `PRN` — The account's payment reference number

• `mmyy` — The month and year of the starting date of the statement

• `_esign` — Appended when the account holder has opted in to electronic statements

## JSON fields

The JSON file that Galileo returns for each statement contains the fields in the table below. Most of the data are formatted as strings (enclosed in double quotation marks), and within those strings are these data types:

• **alphanumeric** — A–Z, a–z, and 0–9

• **$decimal** – $999999999.99. Up to nine digits plus two decimal places, making 11 digits total. Specified as (11, 2). No comma separation for thousands. $1000 is formatted as `$1000.00` instead of `$1,000.00`, and a negative value is `-$1000.00`.

• **integer** — Whole number with no decimal.

• **list** — Nested JSON list. **long date** — A date with the month spelled out and the four-digit year: `November 01, 2023` or `November 2023`.

### `transactions` fields

These fields are nested in the `transactions` object for each transaction, when transactions are present.

### Example JSON statement

## Converting JSONs to PDFs

One way to convert JSON data to PDFs is to follow these steps:

1. Convert the JSON into a format that can be used by an HTML Jinja template.

2. Convert the Jinja template into raw HTML.

3. Use a third-party tool to convert the HTML to PDF.

You may find other ways to port JSON data to a PDF template as suits your use case. Your JSON-to-PDF conversion must include the following elements: header, footer, and legal disclaimers.