Download Reconciliation Files

System-Level Reconciliation

File Retrieval Methods

Evonet provides two ways to retrieve reconciliation files:

1. Portal Manual Download Log in to the Evonet Merchant Portal, navigate to Report → Report List, select the desired file type and date range, and download the corresponding file.
   Can also click Merge Export to download multiple reports combined into a single file.

   

2. SFTP Automatic Retrieval Contact your Evonet account manager to request SFTP access. Once enabled, you will be provided with the SFTP address, account, key, and other parameters.

📘

Note

In the SFTP directory, an accompanying file with the .ok suffix may appear. This file contains no data and serves as a completion indicator, confirming that the associated reconciliation file has been fully generated and transferred.

Tip: System processing peak hours are 10:00 AM – 12:00 PM (UTC+8). It is recommended to retrieve files after 12:00 PM to ensure completeness.

File Level Selection

Evonet provides reconciliation files at different levels:

Reconciliation Files

Activity Detail File

• Contains all transaction statuses (Success, Failed, In-Progress) but does not contain settlement information.
• Mainly used for request-level verification and not as the final reconciliation source.

Settlement Detail File

• Contains only successfully settled transactions with full settlement details.
• Transaction types included: Payment and Refund.

Note: The table below lists key fields. The file contains more fields, but these are the most important for reconciliation.

Miscellaneous Detail File

• Contains non-merchant-initiated fund changes, mainly for handling abnormal transactions.
• Transaction types include: Chargeback, Deposit Collection/Return, Monthly Fees, Post-Settlement Adjustments.

📘

Note

Transfer Fee: Currently, this is not reflected in any file. Merchants can only view it in the agreement and portal. The final credited amount = (Settlement Detail NetMerchantSttlAmt + Miscellaneous Detail NetMerchantSttlAmt) - Transfer Fee.

Best Practices for Reconciliation

Handling Extra Transactions (in merchant’s system but not in Evonet)

1. Put unmatched transactions into a pending matching pool and continue automatic matching for the next N days (recommended: 5 days).

2. If still unmatched after 5 days, escalate to manual review.

3. To avoid discrepancies caused by file delays or reissues, mark transactions as “abnormally terminated” on day M (recommended: 8 days) and stop further matching.

   Typical scenarios:

   • Cross-day transactions (different cutoff times between merchant and EVOCloud)
   • File delays or reissues
   • Settlement time differences between channels

Handling Missing Transactions (in Evonet but not in merchant’s system)

• You can follow the same process as above or shorten the timeline by 3 days before moving to manual review.

Fund Reconciliation

Merchant Inbound Amount calculation:

Merchant Inbound Amount = 
    ∑SettlementDetail.NetMerchantSttlAmt 
    + ∑MiscellaneousDetail.NetMerchantSttlAmt 
    - TransferFee

Settlement Trigger Conditions:

Data from Different Integration Methods (Merchant Side Data)

During reconciliation, data can be sourced from Request, Response, and Webhook.

Direct API

LinkPay/Drop-in

📘

Note

• merchantTransID is used for uniqueness verification to identify a single transaction.
• merchantOrderReference refers to a single order in the merchant's system. The same order may have multiple payments (different merchantTransID values).
• For LinkPay and Drop-in orders, merchantTransID and evoTransID are key reconciliation fields.

Reference

Activity Detail File

Settlement Detail File

Miscellaneous Detail File