Eway Payment Gateway Fee Reconciliation

For finance teams using Eway, fee validation is more than a monthly check. It is part of payment reconciliation, settlement control, and audit-ready reporting. Cointab helps teams compare the records they expect to see against the reports they receive from Eway, their bank, and supporting files so that fee differences, tax issues, and settlement mismatches are easier to review.

What to reconcile in an Eway fee review

A typical Eway payment gateway fee reconciliation compares two sides of the same transaction flow.

• Side A: your internal sales, order, or books data, along with the expected fee calculation
• Side B: Eway payment reports, fee or rate card data, settlement information, and bank statement entries

Supporting files can also be used when needed, such as tax mapping files, order metadata, or reference files that help complete the review.

Common Eway reconciliation checks

Finance teams usually review three parts of the workflow:

1. Gateway fee verification

   • Confirm whether the fee charged matches the expected rate
   • Check fixed charges, percentage-based charges, and any additional deductions

2. Tax review

   • Verify whether GST or other taxes on fees have been applied as expected
   • Review differences where the tax amount does not align with the calculation used internally

3. Settlement review

   • Compare the expected settlement amount against the amount received
   • Check whether the settlement reference or UTR appears in the bank statement

Typical reconciliation outcomes

How Cointab handles Eway payment gateway fee reconciliation

Cointab gives finance teams a structured reconciliation workflow instead of repeated Excel checks.

1. Upload the required files

Users can upload CSV, XLS, or XLSX files for the primary reports. For an Eway fee reconciliation, that may include the payment report, rate card or fee file, settlement report, and bank statement.

2. Map the key fields once

Users map the important columns such as:

• transaction date
• amount
• fee amount
• tax amount
• settlement reference
• order ID or payment reference
• bank UTR or payout identifier

3. Use supporting data when needed

Supporting files can help enrich the primary reports before reconciliation. For example, a tax mapping file or order metadata file can help calculate the expected fee or settlement value more accurately.

4. Create derived columns

When a reconciliation needs calculated values, users can create derived columns using AI-assisted formulas. This is useful for:

• net settlement amount
• fee after tax
• amount after deductions
• normalized reference fields
• cleaned identifiers for matching

5. Run reconciliation

Cointab applies structured matching logic to compare the two sides. It can handle partial matches, one-to-many matches, many-to-one matches, and netted values where the business logic requires grouping.

6. Review matched and open items

The report clearly separates:

• fully matched transactions
• partially matched transactions
• unmatched transactions
• skipped rows

This makes it easier for finance teams to focus on exceptions rather than scanning every transaction line by line.

7. Download the reconciliation report

Users can download an Excel report for review, partner follow-up, internal control checks, and audit support.

8. Handle exceptions manually when required

If a fee or settlement cannot be matched automatically, the user can manually match the relevant rows when the totals make sense. This keeps the process practical while still preserving visibility and control.

Why this matters for finance teams

Eway fee reconciliation often sits across multiple files and multiple controls. A single mismatch can come from fee logic, tax treatment, settlement timing, or a missing bank entry.

Cointab helps teams manage this work more consistently by:

• reducing repeated spreadsheet work
• keeping matching logic reusable for future periods
• making exception review easier
• preserving an audit trail of matched, unmatched, partially matched, and skipped records
• supporting recurring reconciliation runs for daily, weekly, or monthly cycles

A better workflow for recurring fee and settlement checks

Once the reconciliation is configured, the same setup can be reused for future periods. That is useful when the finance team needs to review Eway fees regularly and wants a consistent process for each cycle.

A typical recurring workflow looks like this:

1. Select the existing reconciliation
2. Choose the period
3. Upload the latest files or receive them automatically
4. Run reconciliation
5. Review exceptions and download the report

For teams that receive reports by email, SFTP, or API, the workflow can be automated further so that the reconciliation starts when the required data is available.

When this use case is most useful

This workflow is relevant for teams that need to review:

• Eway gateway fees against their expected rate card
• GST or tax applied to gateway charges
• settlement values after deductions
• payment references against bank receipts
• missing or delayed settlement entries
• recurring reconciliation for finance close and audit preparation

Reconciliation output finance teams can rely on

The output is designed for practical review. Finance teams can inspect the transaction-level records, apply filters, and focus on the items that need action. That makes it easier to identify fee differences, investigate settlement issues, and maintain cleaner month-end reporting.

For Australian finance teams, this is especially helpful when gateway fees, taxes, and settlement timing all need to be checked in one place rather than spread across separate spreadsheets.