Settlement files

Settlement files are ledgers that provide details of all transactions at the close of a business day and are created for every payout. Settlement files are of CSV format and can be accessed in three different ways - using Klarna’s Merchant Portal, using the Settlements API or by using an SFTP.

Merchant Portal

Using the Merchant Portal to access your Settlement files is the simplest method of managing settlement files, as no technical setup or configuration is needed. The Merchant Portal allows for filtering by dates and currency and simple downloads of settlement files for desired transactions.

Report Configurator

Part of the Settlements App is a Report Configurator, that allows you to customise your Settlement Reports as it suits you.

Settlements API

The Settlements API allows for managing and gathering Settlement files using our predefined API. It requires technical configuration, but is a preferred method to manage larger volumes of settlement files. Click here for detailed information and API reference on the Settlements API.

SFTP Settings

A merchant SFTP account allows for access to the root folder that contains all merchant reports, i.e. settlement file and the merchant payout report.

Merchant reports are kept in the SFTP account for 90 days. After that period, they are deleted automatically.

Configuration

Use the below settings for connecting to Klarna SFTP.

OptionSetting
Option
Address
Setting
mft.klarna.com
Option
Protocol
Setting
SFTP
Option
Port
Setting
4001
Option
Username
Setting
Provided by account manager
Option
Password
Setting
Provided by account manager

File name

The file name of the settlement file from the SFTP includes the unique Payment Reference for the payout, and the report generation timestamp in UTC.

Example: 123456789.20180809T000226+0000.csv

Green part, i.e. 123456789, is the Payment Reference for this payout. This payment reference is also included in the settlement file’s header. Blue part, 20150724T000226+0000, is the timestamp of the report generation. It is in UTC.

Note: This naming convention is unique to the SFTP and is therefore not shared with other systems e.g. Settlements API or the Merchant Portal.

Header fields

FieldTypeDescription
Field
total_sale_amount
Type
Decimal
Description
Total of all “sale” events.
These are all captured orders that have been shipped to the customers.
Field
total_fee_amount
Type
Decimal
Description
Total of all “fee” events.
These are service fees charged by Klarna for the related sale transactions.
Field
total_return_amount
Type
Decimal
Description
Total of all “return” events.
These are refund transaction, registered by the merchant and indicating that the goods/services have been returned by the customer.
Field
total_reversal_amount
Type
Decimal
Description
Total of all “reversal” events.
These are refund transactions, registered by Klarna in disputed orders in favour of the customer. This contains fraudulent cases seen as merchant loss eg. due to missing tracking data.
Field
total_commission_amount
Type
Decimal
Description
Total of all “commission” events.
These are paid by Klarna to the merchant based on the contractual agreement regarding commissions.
Field
total_holdback_amount
Type
Decimal
Description
The amount is used as a rolling reserve, which covers for future refunds or other security reasons.
Field
total_repay_amount
Type
Decimal
Description
If the payout amount in a previous period was negative (due to more refunds than sales) it is carried to the next period as a repay amount and deducted from the payout.
Field
total_release_amount
Type
Decimal
Description
The amount reduces the rolling reserve (the opposite of a holdback). The credit that Klarna had set apart for a merchant, gets released and paid back to the merchant.
Field
total_settlement_amount
Type
Decimal
Description
Total amount of this payout (sales + release - fees - tax - returns - holdback - reversals - repay = total_settlement_amount)
Field
total_tax_amount
Type
Decimal
Description
VAT (Value added tax) on Klarna fees.
Field
payment_reference
Type
String
Description
Unique identifier of this payout, which is stated in the transfer note in your bank statement.
Field
settlement_currency
Type
ISO 4217
Description
Settlement Currency. Payouts in the following currencies are currently available: DKK, EUR, GBP, NOK, SEK, USD, CHF, CAD, AUD
Field
payout_date
Type
ISO 8601
Description
Indicates when Klarna initiated the payout (Coordinated Universal Time, UTC). Please note that it usually takes one banking day until the funds are credited to your bank account.
Example: 2018-08-10T07:45:00Z
Field
merchant_id
Type
String
Description
Unique Merchant Identification Number
Example: "K123456"
Field
merchant_settlement_type
Type
String
Description
Settlement type:
NET
Klarna service fees are deducted from the payout.
GROSS
Klarna service fees are invoiced separately.

Body fields

FieldTypeDescription
Field
type
Type
String
Description
Type of this event:
SALE
(+) captured order that has been shipped to the customer.
FEE
(-) Service fee charged by Klarna for the related sale transaction. Please note that according to your contract multiple fee transactions can be applied to one sale transaction, eg. fixed fees and percentage fees.
RETURN
(-) refund transaction, registered by the merchant and indicating that the goods/services have been returned by the customer.
REVERSAL
(-) refund transaction, registered by Klarna in disputed orders in favour of the customer. This contains fraudulent cases seen as merchant loss eg. due to missing tracking data.
REVERSAL_MERCHANT_PROTECTION
(+) net-amount of the order value (without VAT), credited by Klarna to the merchant due to Klarna’s merchant protection eg. in case of fraud. The amount is reducing the total_reversal_amount.
COMMISSION
(+) Paid by Klarna to the merchant based on the contractual agreement regarding commissions.
CORRECTION
(+/-) Certain corrections that are booked against specific orders according to a mutual agreement between the merchant and Klarna.
Field
capture_date
Type
ISO 8601
Description
Date when the event was registered in Klarna’s system (Coordinated Universal Time, UTC). In case of a SALE transaction it refers to the moment when you shipped the goods to the customer and captured/activated the order.
Example: 2018-08-10T07:45:00Z
Field
sale_date
Type
ISO 8601
Description
Date of the order creation (Coordinated Universal Time, UTC).
Example: 2018-08-10T07:45:00Z
Field
order_id
Type
UUID
Description
Unique identifier of the order. All related transactions in the life-span of an order are associated with this ID. eg. fees or refunds. It is therefore the recommended identifier for reconciling the report lines with your system.
Example: c504a9bb-1948-46d5
Field
short_order_id
Type
String
Description
Customer-facing order ID.
Example: 9875QW2
Field
capture_id
Type
String
Description
Unique identifier for every capture on an order and only provided for sale and fee transactions. In case of partial shipments an order is captured more than one time. Each related capture is relfected as a sale transaction with a unique capture_ID.
Example: 8e93b66-6ab1-4d3d-b60d-1cc4e24f4a99
Field
merchant_reference1
Type
String
Description
Your internal reference to the order, that has been submitted during order creation.
Field
merchant_reference2
Type
String
Description
Your internal reference to the order, that has been submitted during order creation.
Field
amount
Type
Decimal
Description
Amount of the related transaction.
Example: 100.00
Field
posting_currency
Type
ISO 4217
Description
Currency in which the order has been placed. The following currencies are currently available: DKK, EUR, GBP, NOK, SEK, USD, CHF, CAD, AUD
Field
refund_id
Type
String
Description
Unique identifier for Return and Reversal transactions. In case of partial returns, each return transaction is associated with a unique refund_ID. Note: By default, these are not included in the reports on FTP. They can be included by using the Report Configurator.
Example: 8e93b66-6ab1-4d3d-b60d-1cc4e24f4a99
Field
purchase_country
Type
ISO 3166-alpha-2
Description
Purchase country, as provided by the merchant. Note: By default, these are not included in the reports on FTP. They can be included by using the Report Configurator.
Example: US, GB, DE, SE

Sample file contents

Click here to look at example CSV