Skrill Payment Gateway Reconciliation with Cointab
Businesses that process online payments through Skrill often need to compare multiple records before the numbers are ready for finance close. Sales data, settlement files, refund reports, ERP exports, and bank statements may all show the same transaction in a different format. Cointab helps finance teams reconcile those records in one structured workflow, so they can review matched, partially matched, unmatched, and skipped transactions without relying on manual spreadsheet checks.
What Skrill payment gateway reconciliation covers
In a typical Skrill reconciliation workflow, finance teams compare internal records with Skrill-related external records.
Side A: your records
Side A contains the records your business expects to be correct, such as:
- Website or order reports
- Internal sales data
- ERP exports
- Ledger or books data
- Refund or cancellation records
Side B: external records
Side B contains records received from Skrill or related finance sources, such as:
- Skrill settlement reports
- Skrill refund reports
- Bank statements
- Payout or remittance records
- Supporting partner files used for analysis
Cointab treats reconciliation as a comparison between these two sides, then applies structured matching logic to identify what matches, what differs, and what still needs review.
How Skrill reconciliation works in Cointab
Cointab is built for finance teams that want a repeatable process rather than a one-time spreadsheet exercise. The workflow is straightforward:
- Create a reconciliation in a team workspace.
- Choose a popular or custom reconciliation setup.
- Upload the required CSV, XLS, or XLSX files on Side A and Side B.
- Map fields such as date, amount, and transaction identifier.
- Optionally upload supporting data for lookup, merge, enrichment, or calculation.
- Create derived columns when a cleaned or calculated field is needed.
- Run reconciliation manually or schedule it to run automatically.
- Review the report dashboard and exception details.
- Download the Excel report for internal review or audit support.
This approach makes it easier to reuse the same setup every month or for every period, instead of rebuilding formulas and matching logic each time.
Files commonly used in Skrill reconciliation
The exact files vary by business model, but common inputs include:
| File type | Typical use |
|---|---|
| Skrill settlement report | Confirms transactions settled through Skrill |
| Skrill refund report | Shows refunded or reversed transactions |
| Website sales report | Lists the orders or payments expected by the business |
| ERP or books report | Captures accounting entries and internal posting data |
| Bank statement | Helps confirm actual credits and debits received |
Supporting files can also help finance teams prepare the data before reconciliation. For example, a product master, fee file, order metadata file, or customer mapping file may be used to enrich the primary reports.
Common scenarios Cointab helps identify
Skrill reconciliation is rarely limited to perfect one-to-one matches. Finance teams often need to investigate differences such as:
- A payment exists in the settlement report but not in the website report
- An order appears in the website report but has not been settled yet
- The Skrill amount differs from the sales amount because of fees or deductions
- A refund appears in one file but not in the accounting export
- A transaction is cancelled on the website but does not appear in settlement
- A bank statement entry is present, but the related ledger posting is missing
- One record matches by identifier, but the amount needs review
Cointab’s reconciliation engine is designed to support these real-world finance scenarios, including one-to-one, one-to-many, many-to-one, and partial matching.
What the reconciliation report shows
Once reconciliation is complete, users can review a report dashboard that separates transactions clearly.
Fully matched
Fully matched transactions are records where the identifiers and amounts align according to the configured logic.
Partially matched
Partially matched transactions are records where the related identifiers match, but the amounts do not. These cases often need review because they may indicate fees, deductions, split settlements, rounding differences, or data issues.
Unmatched
Unmatched transactions are present on one side but not found on the other side. These are important for identifying missing settlements, missing accounting entries, late reports, or exceptions that need follow-up.
Skipped
Skipped transactions are rows that were excluded because they were invalid, incomplete, duplicated, or did not fit the configured format. Skipped records remain visible so finance teams know exactly what was not included.
Handling exceptions and difficult open items
Cointab is not limited to exact matching. After structured rules run, the system can analyze remaining open items using AI-assisted review.
That helps finance teams look at:
- Unclear references
- Slightly different descriptions
- Missing or partial identifiers
- Complex grouping scenarios
- Possible reasons for a mismatch
- Recommended actions for unresolved items
If a match is not strong enough, the transaction can remain unmatched rather than being forced into an unreliable result. Finance teams can also use manual match when they know the business context and the totals tally.
Why finance teams use Cointab for Skrill reconciliation
Cointab helps reduce the work that usually slows reconciliation down:
- Manual Excel checks and VLOOKUP-heavy workflows
- Repeated file comparisons across the same reports
- Delays caused by missing or late partner files
- Inconsistent exception handling across team members
- Stress during month-end close and audit preparation
It also supports a more controlled finance process by making the logic visible, the report reusable, and the output audit-friendly.
Reuse and automation for recurring Skrill workflows
Once a Skrill reconciliation is configured, the same setup can be reused for future periods. Finance teams do not need to rebuild the workflow every month.
Cointab also supports data automation through email, SFTP, or API integrations. That means recurring reports can be received or pulled automatically, validated, loaded into the correct reconciliation, and processed on schedule.
The output can also be sent back through email, SFTP, or API to downstream systems such as accounting, ERP, analytics, or internal reporting tools.
When a custom Skrill reconciliation is useful
A custom reconciliation is useful when the business has its own reporting structure or needs to compare Skrill with multiple internal and external data sources. Examples include:
- Website sales vs Skrill settlement
- ERP sales vs Skrill payout data
- Books vs bank statement
- Refund data vs payment records
- Order report vs settlement report with supporting mapping files
This flexibility matters when reconciliation is not a simple bank-style comparison and needs more than one report on either side.
What finance teams gain from a structured approach
A structured reconciliation workflow helps teams:
- Save time on repetitive matching work
- Improve consistency across periods
- Focus on exceptions instead of every transaction
- Keep an audit trail of matched and unmatched items
- Reuse the same setup for recurring close cycles
- Reduce dependence on fragile spreadsheet formulas
For finance leaders, that means better visibility into cash movement, settlement timing, refunds, and outstanding exceptions without losing control over the underlying logic.
Frequently asked questions
What reports can be used for Skrill reconciliation?
Common inputs include Skrill settlement reports, refund reports, website sales data, ERP exports, books data, and bank statements. Supporting files can also be added for lookup or enrichment.
Can Cointab handle refunds and cancellations?
Yes. Refunds and cancellations can be included in the reconciliation workflow so finance teams can see whether they were settled, reversed, or still open.
What happens if a required file is missing?
If a file arrives late, it can be uploaded under the same reconciliation and the report can be refreshed. This is useful when partner or bank files are received after the initial run.
Can the same Skrill reconciliation be reused every month?
Yes. Once configured, the workflow can be reused for future periods, which reduces repeat setup and helps keep matching logic consistent.
Can the reconciliation output be shared with other systems?
Yes. Cointab can deliver reconciliation output through email, SFTP, or API so downstream systems can be updated automatically.
