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 Type | Purpose | Settlement Required |
|---|---|---|
| Recon File | Primary reconciliation output with full settlement data | Yes |
| Markoff File | Transaction activity reconciled between gateways and providers | No |
| Exception File | Transactions that could not be reconciled within expected timeframe | Partial data |
Report Selection Guide
File Format
Common Specifications
| Attribute | Value |
|---|---|
| Encoding | UTF-8 |
| Delimiter | Comma (,) |
| Header Row | Always included |
| Line Terminator | CRLF |
| Timezone | UTC |
Data Formats
| Type | Format | Example |
|---|---|---|
| Date | YYYY-MM-DD | 2026-01-15 |
| Datetime | YYYY-MM-DD HH:MM | 2026-01-15 14:30 |
| Decimal | #.#### | 1234.5678 |
| UUID | 36 characters | a1b2c3d4-e5f6-... |
| Boolean | True / False | True |
| Currency | ISO 4217 | ZAR |
| Country | ISO 3166-1 alpha-2 | ZA |
Recon file fields
The field tables that were here described Recon File Specification v1.0.
The current file is v3.0, and almost every column was renamed between the
two. purchase_id is now gateway_transaction_id, auth_code is now
transaction_auth_code, and settlement_id and related_to_purchase no
longer exist.
The current schema, the parsing rules and a version mapping are on Reconciliation files.
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}.csvExample: recon_550e8400-e29b-41d4-a716-446655440000_2026-01-15.csv
Report Availability
| Report Type | Delivery | Contents |
|---|---|---|
| Recon File | T+2 morning | Settled transactions ready for reconciliation |
| Markoff File | T+1 morning | All reconciled transactions (settlement not required) |
| Exception File | T+1 morning | Unreconciled transactions requiring review |
Reconciliation Workflow
Settlement Timing
Settlement timing varies based on transaction characteristics and acquirer processing:
Standard Settlement Timeline
| Transaction Type | Typical Settlement | Notes |
|---|---|---|
| 3D Secure authenticated | T+2 | Standard processing |
| High-risk transactions | T+3 or longer | Extended fraud department clearance |
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_amountExample:
| Field | Amount |
|---|---|
| Gross Settlement | R1,000.00 |
| Precium Fee | -R25.00 |
| Provider Fee | -R15.00 |
| Acquirer Fee | -R10.00 |
| Net Settlement | R950.00 |
Handling refunds
A refund is a separate payment transaction. It gets its own
gateway_transaction_id, its own RRN and its own authorisation code, and it
appears as its own row with transaction_type of REFUND and a negative
transaction_amount.
Recon v2.1 carried a related_transaction_reference column linking a refund
back to the original purchase. That column does not exist in v3.0. If you
need the linkage, record it on your side when you make the refund call. See
Reconciliation files.
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:
- Check the Exception File daily
- Investigate unmatched transactions
- Transactions auto-resolve when settlement data arrives
- Contact support for persistent exceptions (>3 business days)
Integration Best Practices
- Automate Downloads: Schedule daily report downloads
- Match references: use
gateway_transaction_referenceto link to your orders - Monitor Exceptions: Set up alerts for exception file entries
- Reconcile Daily: Process files daily for timely issue detection
- 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