Zettle Payment Gateway Reconciliation with Cointab

Cointab helps finance teams reconcile Zettle payment gateway data with internal sales records, ERP exports, and bank statements in a structured, audit-friendly workflow. Instead of handling repeated Excel checks, users can upload files, map the required fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped records in one place.

This is useful for teams that need to track settlement differences, missing payments, refunds, deductions, and other open items across multiple systems. The same reconciliation setup can be reused for future periods, which reduces repeat work and keeps the process consistent across runs.

Why reconcile Zettle data in a structured workflow

Zettle reports are often only one part of the finance picture. To understand whether transactions were settled correctly, finance teams usually need to compare Zettle data with:

• Internal sales or order reports
• ERP or accounting exports
• Bank statements
• Refund or returns data
• Supporting reference files such as product, tax, or mapping files

When these records are checked manually, teams often rely on formulas, lookups, filters, and repeated comparisons across large files. That makes it harder to trace exceptions, explain differences, and maintain a consistent audit trail.

Cointab gives teams a repeatable reconciliation process with clear outputs. You can see what matched, what did not match, and what requires review without rebuilding the workflow every month.

Common Zettle reconciliation use cases

Cointab can be used wherever Zettle data needs to be compared against another source of truth.

Zettle vs sales reconciliation

Use this when you want to compare Zettle settlement records against internal sales or order data. Finance teams typically check:

• Whether each sale appears in both sources
• Whether the settlement amount matches the expected sales amount
• Whether refunds, discounts, or fees explain any differences

Zettle vs ERP reconciliation

Use this to compare Zettle transactions with ERP or accounting records. This helps identify:

• Sales entered in the ERP but not settled through Zettle
• Settlement records that have not been posted correctly
• Amount differences caused by fees, refunds, or timing gaps

Zettle vs bank reconciliation

Use this when the goal is to confirm that settlement activity has actually reached the bank account. This is useful for spotting:

• Settlements that are still pending in transit
• Bank entries that have not been mapped back to Zettle records
• Deposits that do not line up with the expected settlement value

How Cointab handles Zettle reconciliation

Cointab follows a Side A and Side B model.

• Side A contains the records your business expects to be correct, such as sales, ERP, or internal order data.
• Side B contains the external records received from Zettle, such as settlement reports, payout files, or related statements.

The workflow is designed for finance teams, not developers. Users upload the required files, map key columns such as date, amount, and identifier fields, then run reconciliation.

Typical fields used in the setup

For a Zettle reconciliation, teams often map:

• Transaction date
• Settlement date
• Amount
• Order ID or reference ID
• Transaction ID
• Receipt number
• Bank reference or settlement reference
• Any business-specific identifier used to tie records together

If a file does not match the expected format, Cointab can reject it with a clear message so the team knows what needs to be corrected before the run continues.

Reconciliation outcomes you can review

After the run completes, Cointab presents the results in a report dashboard.

Fully matched

These are records where the expected identifiers and amounts align according to the reconciliation logic.

Partially matched

These are records where the system can see a likely relationship between the two sides, but the amounts do not fully match. For Zettle workflows, that may point to a fee, refund, discount, or timing difference that needs review.

Unmatched

These are records that appear on one side but not the other. Examples include:

• A sale recorded internally but not found in Zettle
• A Zettle settlement entry that does not appear in the ERP
• A bank receipt that cannot be tied back to a settlement record

Skipped

Skipped records are rows that were not included in the reconciliation because they were incomplete, invalid, duplicated, or excluded by rule. Showing skipped data helps finance teams understand what was ignored and why.

Supporting data and derived columns

Zettle reconciliation often becomes easier when teams enrich the main files with supporting data.

Supporting data can include:

• Product master files
• Tax mapping files
• Fee rate files
• Order metadata
• Customer or store mapping files
• Reference reports used for lookup-style enrichment

These files are not reconciled directly. They are used to prepare or enrich the primary data before matching begins.

Users can also create derived columns on both sides. For example, a finance team might want to normalize an order reference, calculate a net amount after fees, or create a matching field from multiple columns. Cointab supports AI-assisted formula creation so users can describe the rule in plain language and generate an Excel-style formula.

Matching logic for complex Zettle files

Not every transaction matches one-to-one. Cointab supports structured matching across common reconciliation patterns, including:

• One-to-one
• One-to-many
• Many-to-one
• Many-to-many
• Net-to-net
• Contra matching
• Partial matching

This matters when one Zettle settlement covers multiple sales, when one internal record is split across multiple external entries, or when amounts need to be netted before comparison.

The engine applies deterministic matching first. Remaining open items can then be reviewed with AI-assisted analysis where simple rules are not enough.

AI support for open items

Cointab uses AI in a conservative, reviewable way.

For Zettle reconciliation, AI can help finance teams with:

• Formula creation for derived columns
• Reviewing difficult open transactions
• Analyzing possible reasons for a mismatch
• Suggesting whether a missing file, refund, fee, or delay may explain the difference

If the evidence is not strong enough, the transaction remains unmatched. This keeps the workflow audit-friendly and avoids weak automatic matches.

Manual match and missed file refresh

Some exceptions require human review. Cointab includes a manual match option so users can match transactions themselves when they know the business context and the totals tally.

If a required file was missed, teams can upload the missing file under the same reconciliation and refresh the report. This is helpful in real finance operations where partner files or bank data may arrive later than expected.

Reuse and automation for recurring runs

Once a Zettle reconciliation is configured, the same setup can be reused for future periods. That means teams do not need to rebuild the workflow each month.

Cointab also supports recurring automation through:

• Email
• SFTP
• API

This allows data to be received or pulled on a schedule, reconciliation to run automatically, and output to be delivered back to internal systems when needed.

For recurring finance work, this turns reconciliation from a monthly spreadsheet task into a repeatable process that fits into daily operations.

Reporting and audit readiness

Once reconciliation is complete, users can review the dashboard and download Excel reports for internal review, follow-up, or audit preparation.

The report view typically includes:

• Summary counts
• Fully matched records
• Partially matched records
• Unmatched records
• Skipped records
• Filters for transaction-level analysis
• Detailed views for open items and exceptions

For finance teams, this makes it easier to trace discrepancies, explain variances, and keep a clear record of what happened in each run.

Team workspace and historical visibility

Cointab supports team workspaces so multiple users can work from the same reconciliation environment with roles and access control. That helps controllers, finance managers, and operational teams stay aligned without sharing spreadsheet versions over email.

Past runs remain available on the dashboard for future reference, which is useful for month-end close, partner follow-up, and audit review.

FAQ

What can be reconciled with Zettle reports?

Cointab can reconcile Zettle settlement data with internal sales reports, ERP exports, bank statements, and other finance or operational files that contain matching identifiers and amounts.

Can Cointab handle both Zettle-to-sales and Zettle-to-bank reconciliation?

Yes. The same platform can support different workflows, including sales vs Zettle, Zettle vs ERP, and Zettle vs bank reconciliation, depending on how your files are structured.

What happens if a transaction is partially matched?

Partially matched transactions are shown separately so finance teams can review amount differences. This is useful when identifiers match but the value differs because of fees, refunds, discounts, or other adjustments.

Can recurring Zettle reconciliation be automated?

Yes. Once the workflow is configured, data can be received or pulled through email, SFTP, or API, and reconciliation can be scheduled to run automatically.

Can finance teams add missing context before matching?

Yes. Supporting data and derived columns can be used to enrich the primary reports before reconciliation, which helps when the original files need cleanup, mapping, or calculation first.