Thunes | Documentation | Reporting
Account statement extract between two payouts:
Introduction:
Account statement extract between two payouts permits marketplace or vendors to have a unique and consolidated .csv file which resumes all financial operations on a dedicated account between two payouts.
File recovery:
File is setup to be retrieved by email, in the morning, the day after a payout occurs. It could also be retrieved on Thunes Collections back-office.
Important remarks
The entry corresponding to the payout involving the account statement extract is integrated to this export. The entry corresponding to the previous payout is not included.
If there is no payout triggered, file is not generated!
Account state:
First and last two lines of the line permit to have a complete view of account state at the beginning and at the end of period (period is defined by two payouts made).
State at the beginning of the period:
| Cell's description | |
|---|---|
| Account | Account number concerned by this report |
| StartDate | Beginning date of the period |
| StartBalance | Amount balance on account at the beginning of the period (StartDate). |
| Currency | Account currency |
State at the end of the period:
| Cell's description | |
|---|---|
| Account | Account number concerned by this report |
| EndDate | End date of the period |
| EndBalance | Amount balance on account at the end of the period (EndDate). |
| Currency | Account currency |
Statement description:
You will find below different columns of the account statement extract between two payouts. You will find on it all operations made during the concerned period, explained at the beginning and at the end of the file.
Note
Debit or credit entries could be lie to an order. That's why we will repeat in several columns information about orders.
| Cell's description | |
|---|---|
| CounterpartAccount | Counterpart account. If operation is a debit, it will be account where money was settled on, and vice versa for a credit. |
| Label | Text description of the financial operation. You could have the label POid : PaymentOrderId (cf: column with the same name). |
| FinancialOperationId | Thunes financial operation id |
| OperationDate | Operation date of the financial operation |
| EntryDate | Value date of the financial operation taken into account by Thunes |
| DebitAmount | If it's a debit entry, amount will be added here (always positive). If not, amount will be 0. |
| CreditAmount | If it's a credit entry, amount will be added here (always positive). If not, amount will be 0. |
| PaymentOrderId | Lie to an order - Thunes payment order id |
| MerchantId | Lie to an order - Thunes merchant id lie to the payment order (and order) |
| MerchantOrderId | Lie to an order - Merchant order id lie the Thunes payment order |
| OrderAmount | Lie to an order - Total amount charged of the payment order |
| Currency | Lie to an order - Currency lie to the payment order |
| OrderDate | Lie to an order - Order date |
| PaymentPageId | Lie to an order - Payment page requested when the payment order was created |
In order to go further
Don't hesitate to contact us to get further information and the specification guide.
Other reports:
We also allow different reporting for vendors and marketplace:
- Account statement: .pdf file sent by email each month
- Statement of the annual fees: .pdf file sent by email each year
Updated about 1 month ago