Reporting

ICEPAY provides reporting exports that help you work with payment and financial data outside the ICEPAY Portal.

You can use these exports for tasks such as:

• reconciling ICEPAY statements with your accounting records;
• analysing payments and payment methods;
• matching payments with orders in your store;
• importing financial data into another system;
• building internal reports.

The most suitable export depends on whether you need a simple transactional dataset or a structured accounting format.

Available reporting formats

CSV

A configurable tabular export containing payment and transaction information.

CSV is suitable for spreadsheets, manual reconciliation, data analysis, and importing transactions into systems that support flat files.

CAMT.053

A standardized XML bank-statement format containing financial entries, balances, and account movements.

This format is intended for more structured or automated financial reconciliation.

Reporting is account-level

Reporting data is available independently of how your payments were created.

Whether you use a ready-made e-commerce integration or the Checkout API, the resulting financial activity can be included in ICEPAY reports.

CSV exports

CSV is the most accessible ICEPAY reporting format.

There are two places from which payment data can be exported.

Statement export

Exports the payments, refunds, and chargebacks that belong to a specific ICEPAY statement.

This is the recommended option when reconciling financial activity.

Payments export

Exports selected payments or payments from a chosen date range.

This is useful for quick transactional reporting, but the number of payments that can be exported is limited.

Use statement exports for reconciliation

When reconciling a payout or accounting period, start from the statement and export the transactions belonging to that statement.

This ensures that your exported data matches the financial period ICEPAY used for the statement.

Export from a statement

A statement export contains the transactions that contributed to that financial statement.

This includes:

• payments;
• refunds;
• chargebacks.

A typical reconciliation flow is:

1. Open the statement

   Go to Statements in the ICEPAY Portal and select the statement you want to reconcile.

2. Review the statement

   Check the processed turnover and other financial entries.

3. Export the transactions

   Use the payment export option on the statement.

4. Open the CSV

   Use the file in a spreadsheet, accounting system, or another reporting tool.

5. Match the transactions

   Use order references, payment identifiers, amounts, and other fields to match ICEPAY data with your own records.

Export from Payments

You can also export payments directly from the Payments page.

This is useful when you want to:

• investigate a specific set of payments;
• export a particular date range;
• create a quick operational overview;
• analyse payment methods or transaction details.

This export is less suitable for statement reconciliation because it is based on the payments you select rather than the financial transactions belonging to a specific statement.

Payment date and statement date can differ

A payment may be created or completed on one date but appear on a later statement.

This is one reason statement exports are more reliable when reconciling payouts.

Customise a CSV export

ICEPAY allows the CSV structure to be customised.

You can:

• choose which columns are included;
• change the column names;
• preview an example payment to see what the exported data will look like.

This makes it possible to tailor the export to your accounting or reporting workflow.

For example, if your accounting system expects:

OrderNumber
PaymentReference
Amount
Currency
PaymentMethod
PaymentDate

you can configure the export to contain only the fields you need and adjust their column names where appropriate.

CSV fields

The standard ICEPAY CSV export contains a broad set of payment information.

Common fields include:

Field	Description
PaymentID	Unique identifier for the ICEPAY payment
OrderTime	Time at which the order was created
Amount	Payment amount
Currency	Currency of the payment
Country	Country associated with the payment
OrderID	Order identifier
Reference	Reference associated with the payment
Description	Payment description
Checkout Reference	Reference associated with the checkout
Checkout Description	Description associated with the checkout
ProviderTransactionID	Transaction identifier from the payment provider
PaymentTime	Time at which the payment completed
CustomerAccountNumber	Customer account number, when available
CustomerName	Customer name, when available
MerchantDescription	Merchant name
MerchantID	ICEPAY Merchant ID
PaymentMethodDescription	Human-readable payment method
PaymentMethodCode	Payment method identifier
Issuer	Issuing bank or payment institution

The available data depends on the payment and payment method.

For example, customer bank details are not necessarily available for every payment.

Legacy status fields can appear in CSV exports

Some CSV reporting fields use older Portal reporting terminology such as OK, OPEN, ERR, or settlement descriptions.

These reporting values should not be confused with the Checkout API status values such as started, pending, and completed.

Choose useful reconciliation fields

When matching ICEPAY transactions with your own store or accounting system, some fields are especially useful.

Reference

Your payment or order reference can provide a direct link back to your own records.

Order ID

Can help identify the related order where an order identifier is available.

Payment ID

Identifies the payment within ICEPAY reporting.

Provider transaction

Can help trace the payment at the underlying payment provider where necessary.

Use a consistent reference

If you create payments through the Checkout API, use a reference that can be linked back to your own payment or order record.

A consistent reference makes later reporting and reconciliation considerably easier.

Reporting payments, refunds, and chargebacks

A statement export is not limited to successful payments.

It can also contain financial events such as:

Payments

Payments included in the statement.

Refunds

Funds returned to customers that affect the financial balance.

Chargebacks

Chargebacks associated with the statement period.

This is why the statement export is useful for reconciliation: it represents the financial activity associated with that statement rather than only the original incoming payments.

CAMT.053

ICEPAY also provides reporting in CAMT.053 format.

CAMT.053 is a standardized XML format commonly used for electronic bank statements and automated accounting processes.

ICEPAY currently generates files using:

camt.053.001.02

CAMT.053 is currently beta

ICEPAY currently documents the CAMT.053 export as a beta feature.

Review the generated files and your accounting integration carefully before relying on the format for fully automated processing.

CAMT.053 export options

There are two ways to export CAMT.053 data.

Single file

Generates one CAMT file containing all ICEPAY financial accounts within a single bank-to-customer statement document.

ZIP archive

Generates a ZIP archive containing a separate CAMT file for each financial account.

Both options contain the same underlying financial information but package the accounts differently.

Financial accounts in CAMT.053

ICEPAY models financial movements across three logical account types.

Transaction account

The transaction account represents merchant-facing financial activity.

Entries can include:

• payments;
• refunds;
• invoices;
• payouts;
• holdbacks;
• holdback releases.

For example, a simplified period could contain:

Incoming payments        +€250.00
Refund                   -€100.00
Invoice                   -€50.00
Holdback                  -€50.00
Payout                    -€50.00
────────────────────────────────
Closing balance             €0.00

The transaction account closes at zero because the funds available after the other financial entries are moved to the transit account when the statement is created.

Transit account

The transit account represents money moving between ICEPAY’s financial accounting and the external bank transfer.

Entries can include:

• the payout from the transaction account;
• successful bank transfers;
• older or delayed transfers.

Unlike the transaction account, the transit account can carry a balance from one statement to the next.

For example:

Opening balance             €500.00
Current payout             +€200.00
Completed bank transfer    -€500.00
─────────────────────────────────
Closing balance             €200.00

This helps represent funds that have been made available for payout but have not yet completed the external bank-transfer process.

Holdback account

The holdback account represents funds that ICEPAY temporarily reserves.

Entries include:

Holdback

Funds move from the transaction account into the holdback account.

Holdback release

Previously held funds move back from the holdback account and become available again.

The holdback account balance therefore increases when funds are reserved and decreases when those funds are released.

CAMT.053 transaction entries

A CAMT entry contains structured information about a financial transaction.

A simplified payment entry can look like:

<Ntry>
  <NtryRef>payment-123456789</NtryRef>
  <Amt Ccy="EUR">250.00</Amt>
  <CdtDbtInd>CRDT</CdtDbtInd>
  <Sts>BOOK</Sts>
  <BookgDt>
    <Dt>2025-04-11</Dt>
  </BookgDt>
  <NtryDtls>
    <TxDtls>
      <Refs>
        <PmtInfId>123456789</PmtInfId>
      </Refs>
      <RmtInf>
        <Ustrd>Description: Ice cream with sprinkles</Ustrd>
        <Ustrd>OrderID: ORD-16307</Ustrd>
        <Ustrd>Reference: ORD-16307</Ustrd>
      </RmtInf>
    </TxDtls>
  </NtryDtls>
</Ntry>

Important fields include:

Field	Meaning
NtryRef	Reference identifying the financial entry
Amt	Amount and currency
CdtDbtInd	Whether the entry is a credit (CRDT) or debit (DBIT)
Sts	Booking status; ICEPAY reports entries as BOOK
BookgDt	Booking date
PmtInfId	Identifier for the underlying payment, invoice, or other financial transaction
RmtInf	Additional information such as descriptions, order IDs, and references

The exact contents differ depending on the type of entry

Credits and debits

CAMT.053 represents incoming and outgoing financial movements explicitly.

CRDT

A credit entry increases the balance of the account represented in that part of the report.

DBIT

A debit entry decreases the balance of the account represented in that part of the report.

The meaning should always be interpreted in the context of the account.

For example, moving funds into the holdback account is a debit from the transaction account but contributes to the balance of the holdback account.

CAMT.053 summary values

A CAMT statement also contains summary information about its financial entries.

Common values include:

Element	Meaning
TtlNtries	Total number and amount of all entries
TtlCdtNtries	Total number and amount of credit entries
TtlDbtNtries	Total number and amount of debit entries
TtlNetNtryAmt	Net value of credits minus debits
CdtDbtInd	Whether the net result is a credit or debit

These values are useful when validating that all individual entries in an import were processed correctly.

CSV or CAMT.053?

Which format you should use depends on what you are trying to accomplish.

Use case	Recommended format
Open data in Excel or another spreadsheet	CSV
Manually reconcile payments	CSV
Analyse payment-method activity	CSV
Import selected payment fields into another system	CSV
Reconcile a specific statement	Statement CSV
Import structured financial movements into accounting software	CAMT.053
Track account balances and fund movements	CAMT.053
Build an automated accounting integration	CAMT.053

Start with CSV unless you need accounting-level structure

CSV is generally simpler when your goal is to inspect or match transactions.

CAMT.053 is more appropriate when your accounting software understands bank statement formats and you need structured account movements and balances.

Reporting and statements

Reporting and statements serve different purposes.

Feature	Purpose
Statement	Explains the financial balance for a particular period
CSV export	Provides transaction-level reporting data
CAMT.053	Provides structured accounting entries and balances

A statement tells you which financial period ICEPAY accounted for.

The report gives you the underlying data in a format that can be used outside the Portal.

For reconciliation, these are normally used together:

1. Start with the statement

   Identify the financial period you want to reconcile.

2. Review the statement balance

   Understand payments, refunds, chargebacks, invoices, holdbacks, and other adjustments.

3. Export the transactions

   Use CSV when you need transaction-level data.

4. Match your records

   Compare the exported ICEPAY transactions with your store or accounting system.

5. Use CAMT.053 when appropriate

   If your accounting system supports structured bank-statement imports, use CAMT.053 for automated financial reconciliation.

Reporting and your integration

You do not need to implement ICEPAY reporting as part of your checkout integration.

Ready-made integrations and custom API integrations are responsible for the payment flow.

Reporting happens afterwards at ICEPAY Account level.

Good payment data makes reporting easier

Even though reporting is separate from the checkout implementation, the data you provide when creating payments can make later reconciliation much easier.

Use meaningful and consistent order references and payment references wherever possible.

What to remember

• ICEPAY supports CSV and CAMT.053 reporting.
• Use statement CSV exports when reconciling a specific financial statement.
• Payments-page CSV exports are better suited to quick transactional reporting.
• CSV columns can be selected and renamed.
• Statement exports can contain payments, refunds, and chargebacks.
• Reporting CSV files can contain legacy Portal status terminology that differs from Checkout API statuses.
• CAMT.053 provides structured transaction, transit, and holdback accounting.
• ICEPAY currently documents CAMT.053 as a beta feature.
• CAMT.053 exports use the camt.053.001.02 standard.
• Reporting happens at ICEPAY Account level and does not need to be implemented as part of the checkout flow.

Continue reading

Statements & reconciliation

Learn how to reconcile payments, refunds, fees, holdbacks, and payouts using ICEPAY statements.

Payouts

Understand when available funds are transferred to your bank account.

Invoices & fees

Learn how ICEPAY costs are invoiced and how they affect your financial balance.

Payment lifecycle

Understand payment and financial statuses and when funds become cleared.

Troubleshooting

I cannot find a payment in my statement export

A statement export only contains transactions that belong to that specific statement.

The payment may have completed during a different period or may not yet have been financially available when the statement was created.

Check the payment in the ICEPAY Portal and review subsequent statements if necessary.

The statement CSV does not match my Payments export

The two exports are created for different purposes.

A statement export contains the payments, refunds, and chargebacks belonging to that financial statement.

A Payments export contains the payments you selected or the payments within the selected date range.

For financial reconciliation, use the statement export.

I need a column that is not in my CSV export

Review the CSV export configuration.

ICEPAY allows you to select the columns that are included and change their names.

Keep in mind that some values are only available when the underlying payment or payment method provides that information.

A CSV payment status does not match the Checkout API status

Some reporting fields use older Portal status terminology such as OK, OPEN, or ERR.

The Checkout API uses its own payment lifecycle values such as started, pending, completed, expired, and cancelled.

Do not treat these values as the same status model.

My CAMT.053 import fails

CAMT.053 is currently a beta feature.

Confirm that your accounting software supports the camt.053.001.02 format and check whether it expects one account per file or can process the combined export.

If the generated file appears incorrect, contact the ICEPAY team and include information about the export and the import error.

The CAMT.053 transaction account closes at zero

This is expected.

When a statement is created, the available funds are moved from the transaction account to the transit account.

The transaction account therefore closes with a zero balance.

The CAMT.053 transit account has a remaining balance

The transit account can carry a balance between statements.

This represents funds that have moved into the payout process but whose external bank transfer may not yet have completed.

Review the related payout and transfer information in the ICEPAY Portal.

I cannot match an exported transaction to an order

Start with the transaction’s reference, order ID, payment identifier, and provider transaction identifier.

If the payment was created through your own integration, compare these values with the identifiers stored in your application.

Using a consistent order or payment reference when creating payments makes this matching process easier.