Card Transaction Reconciliation in Stores

Reconcile in-store card transactions across store sales reports, bank statements, and settlement files in one structured workflow. Cointab helps finance teams compare Side A records such as POS or internal sales data with Side B records such as bank or payment settlement reports, so store-level differences, missing credits, and open items are easy to review.

This use case is especially useful for retail, restaurants, QSR, and other payment-heavy businesses that need to reconcile card sales across multiple stores, terminals, and settlement cycles.

Why in-store card reconciliation matters

Card payments are usually straightforward at the point of sale, but the finance work starts after the transaction is processed. Teams still need to verify whether the amount recorded in the store system appears correctly in the bank or settlement file.

Common reconciliation challenges include:

• Multiple stores reporting sales in different formats
• Settlement deductions, fees, or timing differences
• Missing or delayed credits in the bank
• Refunds, reversals, or partial settlements
• Manual Excel checks that take time and are difficult to audit
• Repeating the same reconciliation setup every month

Cointab gives finance teams a reusable workflow so they can upload files once, map fields once, and run the same reconciliation again for future periods.

How Cointab handles card transaction reconciliation

Cointab follows a simple Side A and Side B model:

• Side A: your internal store sales records, POS exports, or sales summaries
• Side B: external bank statements, acquirer reports, or settlement files

A typical workflow looks like this:

1. Create a popular reconciliation or set up a custom workflow.
2. Upload the required reports for each side.
3. Map fields such as date, amount, store ID, transaction reference, or settlement ID.
4. Add optional supporting data such as store masters, fee files, or mapping files.
5. Create derived columns if needed using AI-assisted Excel-style formulas.
6. Run reconciliation manually or on a schedule.
7. Review matched, partially matched, unmatched, and skipped records.
8. Download the Excel reconciliation report or send output to downstream systems.

Reports commonly used

For in-store card reconciliation, finance teams usually work with one or more of the following reports:

• Store-wise sales report from the POS or internal system
• Card sales summary by store or by terminal
• Bank statement showing card credits received
• Acquirer or payment settlement report
• Fee or deduction report
• Refund or reversal report
• Store mapping or location master data

Cointab supports CSV, XLS, and XLSX files. If a file does not match the configured structure, the system can reject it with a clear error so users know what needs to be corrected.

What Cointab matches

Card transaction reconciliation can happen at different levels depending on the data available.

Cointab supports structured matching across:

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

This is useful when one store summary matches several settlement lines, when multiple terminal entries need to be grouped, or when identifiers are present but amounts differ.

The engine first applies structured reconciliation rules. Any remaining open items can then be analyzed with AI, which helps finance teams understand why a transaction may still be open or whether a file may be missing.

Store-level and consolidated reconciliation views

In-store card reconciliation is often reviewed in two ways:

Individual store view

This view helps teams understand how much card sales were recorded for each store and how much was actually received in settlement or bank credit. It is useful for identifying location-level gaps, timing differences, or deduction issues.

Consolidated all-store view

This view combines all store activity into a single reconciliation summary. It helps controllers and finance managers see the total amount expected, the amount received, and the overall variance across the business.

Both views can be kept in the same reconciliation workflow, so teams do not need to rebuild reports for each period.

What users see in the reconciliation report

Once the run is complete, Cointab shows a reconciliation dashboard with transaction-level detail and summary totals.

The report typically includes:

• Total summary
• Fully matched summary
• Partially matched summary
• Unmatched summary
• Skipped summary
• Filters for deeper review
• Detailed matched transaction views
• Downloadable Excel report

This makes it easier to focus on exceptions instead of checking every row manually.

Fully matched records

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

Partially matched records

These are transactions where the references match, but the amounts do not. Finance teams can use these records to review deductions, short credits, rounding differences, or settlement timing issues.

Unmatched records

These are transactions that appear on one side but not on the other. For in-store card reconciliation, this often highlights missing settlements, missing bank credits, or records that need follow-up.

Skipped records

Skipped rows are records that were not included in reconciliation because of missing data, invalid amounts, duplicates, or other file issues. They remain visible so teams understand what was excluded and why.

Supporting data and derived columns

In many card reconciliation workflows, the primary reports are not enough on their own. Cointab allows optional supporting data to be added for enrichment, lookup, or calculation.

Examples include:

• Store master files
• Fee rate files
• Terminal mapping files
• Refund reports
• Sales metadata
• Identifier mapping files

Users can also create derived columns from existing fields. AI can help generate Excel-style formulas in natural language, which is useful when finance users know the business logic but do not want to write formulas manually.

Examples of derived values include:

• Clean store ID
• Net card amount
• Amount after fee
• Normalized transaction reference
• Combined settlement key

Manual match and missed file refresh

Some transactions may need a manual review when the system and AI cannot confidently match them. Cointab provides manual match controls so finance teams can match transactions themselves when the totals make sense and the business context is clear.

If a report was missed during the original run, users can upload the missing file under the same reconciliation and refresh the report. This is useful when late bank files or settlement files arrive after the initial run.

Automation for recurring store reconciliation

Once the reconciliation is configured, it can be reused for future periods without rebuilding the workflow.

Cointab also supports recurring automation through:

• Email
• SFTP
• API

That means a card settlement report can be received automatically, the reconciliation can run on a schedule, and the output can be delivered back to internal systems after completion.

This is useful for daily, weekly, monthly, or end-of-period reconciliation where teams want a repeatable process instead of manual file handling.

Why finance teams use Cointab for card transaction reconciliation

Cointab is designed for finance teams that want clarity, control, and audit-ready reporting.

It helps teams:

• Reduce repetitive spreadsheet work
• Reuse the same setup across periods
• Review store-level and consolidated variances
• Separate matched, partially matched, unmatched, and skipped items clearly
• Keep reconciliation logic transparent and reviewable
• Maintain a history of past runs in the dashboard
• Support team-based work inside a shared workspace

For businesses with multiple stores, terminals, or settlement cycles, this creates a more consistent reconciliation process and makes month-end review easier to manage.

FAQs

What reports are needed for in-store card transaction reconciliation?

Most workflows use a store sales report or POS export on Side A and a bank statement, settlement file, or acquirer report on Side B. Optional supporting files can be added for store mapping, fees, or refunds.

Can Cointab reconcile both individual stores and all stores together?

Yes. The same reconciliation can be reviewed at store level and also in a consolidated all-store summary, which helps finance teams compare location-level and business-wide variances.

How does Cointab handle unmatched or partially matched card transactions?

Cointab separates fully matched, partially matched, unmatched, and skipped records. Finance teams can filter exceptions, review open items, and manually match transactions where appropriate.

Can recurring card reconciliation be automated?

Yes. After the workflow is configured once, reconciliation can run on a schedule and data can be received or delivered through email, SFTP, or API integrations.