Reconciliation

Note: The reconciliation service is currently available for card payments only. Support for additional payment methods will be added in future releases.

‍

Overview

The Precium Reconciliation Service provides automated transaction reconciliation between your payment processing activity and settlement data. This service generates daily report files that enable you to track card transactions through the complete payment lifecycle, from authorisation to bank settlement.

‍

Report Types

The reconciliation system produces three distinct report types:

‍

‍

Report Selection Guide

flowchart TD
    A[Transaction Processed] --> B{Reconciled with Provider?}
    B -->|Yes| C[MARKOFF FILE
Transaction activity]
    B -->|No| D[Not in any report yet]
    C --> E{Settlement Data Available?}
    E -->|Yes| F[RECON FILE
Ready for settlement]
    E -->|No| G[EXCEPTION FILE
Requires investigation]

‍

File Format

Common Specifications

‍

Data Formats

‍

Recon File Fields

The Recon File contains successfully reconciled transactions ready for settlement.

‍

Key Terminology

‍

Transaction Identification

‍

Payment Details

‍

Settlement Information

‍

Bank Reconciliation

‍

Accessing Reports

SFTP Delivery

Reconciliation reports are delivered automatically via SFTP to your designated location:

• Delivery Method: Secure SFTP transfer
• Location: Agreed upon during merchant onboarding
• Schedule: Daily, typically available by 06:00 UTC
• Format: CSV files as specified in this document

‍

Contact your account manager to configure or update your SFTP delivery settings.

‍

File Naming Convention

Reports follow this naming pattern:

‍

{report_type}_{merchant_id}_{date}.csv

‍

Example: recon_550e8400-e29b-41d4-a716-446655440000_2026-01-15.csv

‍

Report Availability

‍

Reconciliation Workflow

flowchart LR
    subgraph T0["T+0 Morning"]
        direction TB
        A1[Transactions processed]
        A2[Data captured]
    end

    subgraph Night["T+0 â T+1 Overnight"]
        direction TB
        B1[Gateway-provider recon]
        B2[Settlement processing]
        B3[Bank statement matching]
    end

    subgraph T1["T+1 Morning"]
        direction TB
        C1["ð Recon File"]
        C2["ð Markoff File"]
        C3["ð Exception File"]
    end

    T0 --> Night --> T1

‍

Settlement Timing

Settlement timing varies based on transaction characteristics and acquirer processing:

‍

Standard Settlement Timeline

‍

Important Considerations

Acquirer Fraud Review: Non-3DS transactions may experience delayed settlement (T+2 or T+3) as acquirers route these transactions through their fraud departments for additional clearance before releasing funds. This is standard industry practice for transactions without strong customer authentication.

‍

Factors Affecting Settlement Time

• 3DS Status: Authenticated transactions typically settle faster
• Transaction Amount: Higher-value transactions may undergo additional review
• Merchant Risk Profile: Settlement timing may vary by merchant category
• Acquirer Policies: Each acquirer has specific fraud review procedures
• Public Holidays: Settlement may be delayed around bank holidays

‍

Projected vs Actual Clearance

The projected_clearance_date field in the Recon File provides an estimate, while clearance_date reflects actual bank clearance. Discrepancies may occur due to:

• Acquirer fraud department holds
• Bank processing delays
• Weekend/holiday adjustments

‍

Settlement Amount Calculation

Understanding how net settlement is calculated:

‍

gross_settlement_amount
   - precium_settlement_deduction_incl_vat
   - settlement_provider_fees
   - acquirer_settlement_deduction_incl_vat
   âââââââââââââââââââââââââââââââââââââââââ
   = net_settlement_amount


‍

Example:

‍

Handling Refunds

Refunds are linked to original transactions:

‍

purchase_id,related_to_purchase,type,transaction_amount
original-uuid,,purchase,1000.0000
refund-uuid,original-uuid,refund,-500.0000


‍

Exception Handling

Transactions in the Exception File require investigation:

‍

Common Exception Causes:

• Settlement data not received from the provider
• Bank statement matching failure
• Data discrepancy between systems

‍

Resolution Process:

1. Check the Exception File daily
2. Investigate unmatched transactions
3. Transactions auto-resolve when settlement data arrives
4. Contact support for persistent exceptions (>3 business days)

‍

Integration Best Practices

1. Automate Downloads: Schedule daily report downloads
2. Match References: Use purchase_reference to link to your orders
3. Monitor Exceptions: Set up alerts for exception file entries
4. Reconcile Daily: Process files daily for timely issue detection
5. Archive Reports: Retain reports for audit purposes

‍

Coming Soon

The following payment methods will be added to reconciliation:

• Ozow
• Capitec Pay
• DebiCheck
• Debit Orders

‍

Contact your account manager for timeline updates.

‍

Support

For reconciliation questions or discrepancies:

‍

Email: support@precium.com

‍

Subject: [Recon] {Merchant Name} - {Issue Description}

‍

Include:

• Merchant ID
• Affected date(s)
• Purchase ID(s)
• Description of discrepancy

‍

Document Version: 1.0 | Last Updated: January 2026