Eway Payment Gateway Reconciliation Automation

Australian finance teams that accept payments through Eway often need to compare internal sales records with gateway settlements, refunds, bank entries, and ERP data. Cointab helps structure that work into a reusable reconciliation workflow so teams can review matched, partially matched, unmatched, and skipped transactions in one place.

What Eway payment gateway reconciliation means

Eway payment gateway reconciliation is the process of comparing your internal records against Eway reports to confirm that orders, payments, settlements, fees, refunds, and reversals are recorded correctly. In practice, finance teams may need to reconcile:

• Sales or order data from the business system
• Eway settlement and payment reports
• Refund or chargeback data
• ERP or accounting exports
• Bank statement entries

This is often more than a simple one-to-one match. A single sale may link to a settlement after fees, refunds, or partial adjustments. A reconciliation platform needs to handle those differences clearly so finance teams can review the right exceptions.

Common Eway reconciliation scenarios

Finance teams typically use Eway reconciliation to answer questions such as:

• Which orders were paid but not settled yet?
• Which settlements do not match the order value?
• Which refunds were processed in Eway but not reflected internally?
• Which bank entries relate to Eway settlements?
• Which transactions need manual review because the amounts do not align?

Typical mismatch patterns include:

• A payment is present in Eway but missing in the website or ERP report
• The internal order amount is higher or lower than the Eway settlement amount
• A refund, adjustment, or fee explains part of the difference
• A bank receipt exists, but the matching Eway record is missing
• A transaction is present on one side but not the other

Cointab keeps these outcomes visible as fully matched, partially matched, unmatched, and skipped records so finance teams can focus on exceptions instead of checking every row manually.

How Cointab handles Eway reconciliation

Cointab uses a structured Side A and Side B model for reconciliation.

• Side A can be your internal sales, order, ERP, or books data.
• Side B can be your Eway settlement, refund, or payment report.

That means the workflow can support both simple payment matching and more complex finance reviews where multiple files need to be compared.

1. Upload and map the required reports

Users upload CSV, XLS, or XLSX files and map the key fields needed for reconciliation, such as:

• Transaction date
• Amount
• Order ID or payment reference
• Settlement ID
• Bank reference or other identifier

If the same report is used each period, the setup can be reused instead of rebuilding the workflow every month.

2. Add supporting data when needed

Supporting data can be used to enrich or prepare the primary reports before reconciliation. For Eway workflows, this may include:

• Product master data
• Order metadata
• Fee rate files
• Refund reference files
• Mapping files for internal IDs and partner IDs

Supporting data is not reconciled directly. It helps complete the main records so the reconciliation output is easier to review.

3. Create derived columns for cleaner matching

If the source files need cleanup or calculation before matching, users can create derived columns. These can help with tasks such as:

• Standardizing transaction IDs
• Calculating net amounts after fees
• Converting refund values to negative amounts
• Creating cleaned reference fields

Cointab also supports AI-assisted formula creation, which is useful when finance teams know the business rule but do not want to build the Excel formula manually.

4. Run structured matching

Cointab applies matching logic across multiple patterns, including one-to-one, one-to-many, many-to-one, and grouped matches. This matters in payment reconciliation because a single settlement may contain several transactions, fees, or adjustments.

The system first applies deterministic rules. After that, remaining open items can be analyzed with AI-assisted review where the evidence is strong enough to help, but not strong enough to force a weak match.

5. Review exceptions and manual matches

Once the run is complete, users can review the report by status and investigate the open items that need attention. If a transaction cannot be matched automatically, users can also perform a manual match when the values and business context support it.

This is useful for one-off exceptions, missing identifiers, or cases where partner data arrives in a different format.

6. Export reports and reuse the setup

After review, finance teams can download Excel reconciliation reports for internal review, audit support, and partner follow-up. The same reconciliation setup can be reused for later periods, which reduces repeat work and keeps the process consistent.

Why finance teams use Cointab for Eway reconciliation

Eway reconciliation is often part of a broader finance workflow, not a standalone task. Cointab helps teams manage that workflow in a more controlled and repeatable way.

Key benefits include:

• Reusable setup for monthly, quarterly, or custom periods
• Clear exception handling with matched, partially matched, unmatched, and skipped records
• Audit-ready reporting for internal review and follow-up
• Team workspace support so multiple users can work from a shared reconciliation history
• Recurring automation through email, SFTP, or API-based data flows
• Scheduled runs so reconciliation can happen daily, weekly, or after files are received
• Automated output delivery back to email, SFTP, or API for downstream systems

For finance teams that manage many reports, this reduces spreadsheet dependency and gives more visibility into what was matched, what was not matched, and what needs action.

What the reconciliation report shows

After the run completes, the report dashboard typically includes:

• Total summary
• Fully matched summary
• Partially matched summary
• Unmatched summary
• Skipped summary
• Transaction-level tables
• Filters for deeper analysis
• Detailed matched transaction views
• Downloadable Excel output

If a file was missed earlier, it can be uploaded later under the same reconciliation and the report can be refreshed. That is important for real finance operations, where settlement files or bank statements may arrive late.

Using Eway reconciliation in a broader finance workflow

Many teams use Eway reconciliation alongside bank reconciliation, ERP reconciliation, and refund review. That gives finance leaders a clearer view of cash movement, settlement timing, deductions, and open exceptions across systems.

A structured workflow is especially useful when:

• Sales and settlement reports follow different formats
• Refunds and fees create partial differences
• Multiple internal systems need to stay aligned
• Reconciliation needs to be repeated every period with the same logic
• Audit and review teams need consistent outputs

FAQs

What files can be used for Eway reconciliation?

Teams can use internal sales, website, ERP, bank, settlement, and refund files as long as the key fields needed for mapping and matching are available.

Can Cointab compare Eway with bank and ERP data?

Yes. Cointab is designed to compare two sides of financial data, so Eway reports can be reconciled against ERP, books, bank statements, or internal sales records.

What happens if a file is missed during the reconciliation cycle?

The missed file can be uploaded later under the same reconciliation and the report can be refreshed so the new data is included.

Can Eway reconciliation be automated for recurring runs?

Yes. Once the reconciliation is configured, data can be brought in through manual upload, email, SFTP, or API, and runs can be scheduled on a recurring basis.