American Express Card In-Store Reconciliation

Cointab helps finance teams reconcile American Express card in-store transactions by matching internal sales records with settlement and bank data. Instead of checking store reports, deductions, and bank entries manually in spreadsheets, teams can upload files, map fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped transactions in one place.

What American Express card in-store reconciliation covers

In-store card reconciliation compares the transactions recorded at the point of sale with the amounts received through the payment processor and bank statement. For finance teams, the goal is to confirm that each card sale has been settled correctly and that any deductions, timing differences, or missing entries are easy to spot.

A typical workflow may include:

• Internal client sales or store sales report on Side A
• American Express settlement or payment report on Side B
• Bank statement for final receipt validation
• Optional supporting data such as store mapping or deduction logic

This helps merchants review both individual store performance and consolidated reconciliation across all stores.

Why this reconciliation is important

American Express in-store settlements often need to be reviewed alongside other payment methods, store-level reports, and bank receipts. When this is handled manually, finance teams can spend a lot of time comparing files, checking deductions, and resolving open items.

Cointab helps teams reduce that effort by:

• Matching transaction records using structured logic
• Highlighting sales variance, settlement differences, and missing receipts
• Separating fully matched, partially matched, unmatched, and skipped records
• Keeping each reconciliation available for future reference
• Supporting audit-ready Excel report downloads

This is especially useful during month-end close, store-level reporting, and partner follow-up.

Typical data sources used in the reconciliation

Cointab supports a flexible Side A and Side B setup, so the exact reports can vary by business process.

Optional supporting data can be uploaded to enrich the main files, such as store masters, mapping files, deduction rules, or reference tables.

How the reconciliation workflow works

1. Upload files

Users upload the required CSV, XLS, or XLSX files into the reconciliation workspace. Multiple files can be added when the same format is used across stores or periods.

2. Map required fields

The user maps the important columns for each report, such as:

• Transaction date
• Amount
• Store ID
• Card reference or payment reference
• Settlement ID
• Any other identifier needed for matching

3. Add supporting data or derived columns

If a field needs to be cleaned, combined, or calculated, Cointab supports supporting datasets and derived columns. Finance users can also use AI to generate Excel-style formulas for derived values.

Examples include:

• Cleaned reference number
• Normalized store code
• Net amount after deductions
• Settlement amount for comparison

4. Run reconciliation

The reconciliation engine applies structured matching logic across the uploaded reports. It can handle one-to-one, one-to-many, many-to-one, and partial matching scenarios.

5. Review the report

Once the run is complete, users can review the report dashboard and inspect different transaction groups:

• Fully matched transactions
• Partially matched transactions
• Unmatched transactions
• Skipped transactions

6. Download the output

The report can be downloaded in Excel format for review, audit support, or follow-up with internal teams and partners.

What finance teams can review in the output

A well-structured in-store reconciliation report helps teams see both the high-level summary and the transaction-level details.

Common summary fields include:

• Total card sales
• Card sales by store
• Settlement received
• Deductions and fees
• Sales variance
• Bank variance
• Net received amount

Transaction-level views help teams drill into the exact records that need attention. This is important when the totals look close but one or more store-level exceptions remain open.

Store-wise and consolidated reconciliation

Cointab supports both individual store reconciliation and consolidated reconciliation across all stores.

Individual store reconciliation

This view helps teams understand how each store performed and whether the settlement received for that store matches the sales recorded internally.

It is useful for:

• Store-level close reviews
• Exception tracking by branch or location
• Identifying missing or delayed settlements
• Reviewing deductions at the store level

Consolidated reconciliation

This view combines the data from all stores and compares the overall totals against the settlement and bank statement.

It is useful for:

• Month-end financial review
• Summary reporting for controllers and CFOs
• Tracking aggregate settlement differences
• Checking whether any store-level gap is still open

How exceptions are handled

Not every transaction will match on the first pass. Some records may require partial matching, manual review, or additional supporting data.

Cointab helps teams handle exceptions by clearly separating:

• Fully matched records, where amount and identifiers match as expected
• Partially matched records, where the relationship is identified but amounts differ
• Unmatched records, where no valid counterpart is found
• Skipped records, where the row could not be used because of missing or invalid data

For unresolved items, AI can assist with open-item analysis and suggest likely reasons, such as missing files, deductions, timing differences, or incomplete references. If the evidence is not strong enough, the item remains unmatched.

Manual review and missed file refresh

Finance operations often depend on late-arriving reports from payment partners or banks. If a file was missed, users can upload it under the same reconciliation and refresh the report.

Cointab also supports manual match for cases where the system cannot confidently match records but the finance team has enough business context to resolve the item. Manual matches are clearly marked for audit visibility.

Reusable setup for recurring periods

Once the reconciliation is configured, the same setup can be reused for future periods. Teams do not need to rebuild the mapping and matching logic every month.

This makes recurring card reconciliation easier for:

• Monthly closes
• Store-wise reporting cycles
• Quarterly reviews
• All-time or lifetime tracking
• Custom settlement periods

Automation for recurring reconciliation

For teams that handle the same workflow repeatedly, Cointab can automate the data flow through email, SFTP, or API.

That means the reconciliation can be configured once and then run on a schedule such as:

• Daily
• Weekly
• Monthly
• End of day
• After all required files are received

After reconciliation is completed, Cointab can also deliver the output back to internal systems through email, SFTP, or API.

Team workspace and audit readiness

Cointab is designed for finance teams that need shared access, visibility, and control. Multiple users can work in one team workspace instead of passing spreadsheets around.

Teams can review:

• Who ran the reconciliation
• Which files were used
• What matched and what did not
• Which rows were skipped or manually matched
• What report was generated for audit or follow-up

This creates a clearer audit trail than spreadsheet-based reconciliation.

When to use this reconciliation workflow

American Express card in-store reconciliation is a good fit when your team needs to compare:

• Store sales vs payment processor records
• Settlement reports vs bank receipts
• Card sales vs deductions and fees
• Store-wise totals vs consolidated monthly values

It is especially helpful for merchants and multi-store businesses that want a more structured process for transaction matching, settlement reconciliation, and financial close support.