Eway Payment Gateway Fee Verification
Cointab helps finance teams verify Eway payment gateway charges by comparing expected fees, taxes, and settlement amounts against the records received from the gateway, bank, and internal systems. Instead of checking spreadsheets line by line, teams can upload the required files, map fields once, run reconciliation, and review differences in a structured report.
This use case is useful when you need to confirm whether gateway fees were charged correctly, whether tax amounts align with the configured rules, and whether the final settlement received in the bank matches the amount expected after deductions.
What payment gateway charge verification covers
Payment gateway charge verification is the process of checking whether the gateway has billed your business correctly on each transaction or settlement cycle. For a workflow such as Eway reconciliation, finance teams usually compare:
- The internal sales or transaction report
- The payment gateway payment report
- The gateway rate card or fee schedule
- The settlement report
- The bank statement
The goal is to confirm that the fee, tax, and settlement deduction logic is consistent and that any mismatch is clearly visible for review.
Typical reports used in the workflow
| Report | Purpose |
|---|---|
| Internal sales report | Acts as the business record of expected transactions |
| Eway payment report | Shows the payment activity and gateway-side transaction details |
| Rate card | Defines the expected fee structure and charge logic |
| Settlement report | Shows the net amount after fee and tax deductions |
| Bank statement | Confirms whether the settlement was actually received |
If needed, teams can also use supporting data such as refund files, order metadata, or mapping files to enrich the primary reconciliation before matching begins.
How Cointab handles Eway charge verification
Cointab uses a Side A and Side B model for reconciliation.
- Side A contains your internal records, such as sales, ledger, or expected settlement data.
- Side B contains the Eway report, settlement file, or bank record that needs to be checked against your books.
A typical workflow looks like this:
- Upload the required files.
- Map fields such as date, amount, and transaction or settlement reference.
- Add supporting data if needed.
- Create derived columns if values need to be cleaned, normalized, or calculated.
- Run reconciliation manually or on a schedule.
- Review fully matched, partially matched, unmatched, and skipped records.
- Download the Excel report for review, follow-up, or audit support.
If a file was missed, it can be added later under the same reconciliation and the report can be refreshed.
Common checks in payment gateway reconciliation
Finance teams often review the following scenarios during charge verification:
Fee correctly charged
The gateway fee matches the expected amount based on the configured rate card.
Fee overcharged
The actual fee is higher than the expected fee and may require follow-up or dispute review.
Fee undercharged
The actual fee is lower than expected. This still needs review because it may indicate a data issue or a billing difference.
Tax correctly charged
The tax amount matches the expected calculation in the configured reconciliation logic.
Tax difference
The tax amount is higher or lower than expected and should be flagged for finance review.
Settlement amount match
The settlement amount matches the expected net amount after fees and taxes are deducted.
Settlement amount mismatch
The settlement amount does not match the expected value and needs exception handling.
Settlement found in bank
The settlement reference or UTR appears in the bank statement.
Settlement not found in bank
The settlement appears in the gateway report but has not yet been matched in the bank statement.
Why structured reconciliation is better than Excel-only checks
Many finance teams start by using formulas, filters, and VLOOKUPs to verify gateway charges. That works for small files, but it becomes difficult to audit and repeat as transaction volume grows.
Cointab helps teams move from manual checks to a reusable reconciliation workflow that makes the process easier to review and repeat.
Benefits include:
- Consistent matching logic across periods
- Clear separation of matched, partially matched, unmatched, and skipped records
- Audit-ready Excel export
- Reusable setup for future reconciliation runs
- Faster exception review for fee, tax, and settlement differences
- Manual match support for edge cases that need human review
Where AI helps in this workflow
Cointab also supports AI-assisted finance work in a controlled way.
- AI formula builder: Create derived columns using natural language when a field needs to be cleaned or calculated.
- AI-assisted open-item analysis: Review difficult unmatched transactions after structured matching is complete.
- AI reason analysis: Understand why a record may be open, such as a missing file, a refund, a deduction, or a settlement timing difference.
AI supports the review process, but it does not replace finance controls. Weak matches should remain unmatched until there is enough evidence.
Reusable setup for recurring gateway checks
Eway charge verification is rarely a one-time task. Most finance teams need to run it every day, week, or month.
Once the workflow is configured, teams can reuse it for future periods without rebuilding formulas or file logic every time. That makes it easier to handle:
- Monthly fee review
- Settlement verification
- Period-end close support
- Partner dispute preparation
- Bank matching for received settlements
The same setup can also be extended to other payment gateways or internal settlement workflows when needed.
What the reconciliation report shows
After reconciliation runs, users can review a report dashboard with:
- Total summary
- Fully matched items
- Partially matched items
- Unmatched items
- Skipped items
- Transaction-level detail
- Filters for deeper analysis
- Downloadable Excel output
This gives finance teams a clear view of what matched, what did not match, and what needs follow-up.
Why this matters for finance teams
For CFOs, controllers, and reconciliation teams, gateway charge verification is not only about spotting an overcharge. It is also about making sure the billing, settlement, and bank receipt trail is complete and reviewable.
A structured workflow helps teams:
- Reduce manual spreadsheet effort
- Catch discrepancies earlier
- Support month-end close with cleaner data
- Review exceptions faster
- Keep a clear audit trail of what was matched and why
FAQ
What data is needed for Eway payment gateway fee verification?
Typically, teams use an internal sales or transaction report, the Eway payment or settlement report, the rate card, and sometimes the bank statement. Supporting files can also be added when they help with enrichment or mapping.
Can Cointab verify both fees and tax amounts?
Yes. Finance teams can configure the workflow to compare expected fees and tax amounts against the records received in the gateway or settlement file.
What happens if the settlement amount does not match the expected value?
The transaction is shown as a difference or mismatch so the finance team can review the cause, such as a fee variation, tax difference, refund, or timing issue.
Can this workflow be reused for future periods?
Yes. Once configured, the same reconciliation setup can be reused for future runs without rebuilding the workflow from scratch.
Can missed files be added later?
Yes. If a required report arrives later, it can be uploaded under the same reconciliation and the report can be refreshed.