DotPe Transaction Reconciliation

Businesses using DotPe for in-store or cashless payments still need to match every transaction against internal sales records, POS data, settlement reports, and bank statements. Cointab helps finance teams automate DotPe transaction reconciliation with a structured workflow that shows what matched, what changed, and what needs review.

Why DotPe transaction reconciliation matters

Manual DotPe reconciliation usually means comparing multiple reports in Excel, checking order references line by line, and investigating differences across payment, settlement, and bank records. That becomes difficult when transaction volume grows or when reports arrive at different times.

Common issues include:

• Settlement amounts not matching the POS or sales record
• Underpayments and overpayments that need review
• Missing remittances or delayed bank credits
• Duplicate or incomplete rows in source files
• Different team members preparing reconciliation in different ways
• Month-end close and audit preparation taking longer than expected

Cointab replaces repetitive spreadsheet work with a reusable reconciliation setup that finance teams can run again for future periods.

How Cointab handles DotPe reconciliation

Cointab uses a Side A and Side B model for transaction matching.

• Side A is your internal record, such as POS order detail, sales data, or store-level transaction files
• Side B is the external record, such as the DotPe offline report, settlement report, or bank statement

A typical workflow looks like this:

1. Create a new reconciliation in a shared team workspace.
2. Choose a custom setup for the DotPe workflow.
3. Upload the required files for Side A and Side B.
4. Map the key fields such as date, amount, and reference columns.
5. Add optional supporting files for lookup or enrichment if needed.
6. Create derived columns when a calculated field is required.
7. Run reconciliation manually or schedule it for recurring periods.
8. Review fully matched, partially matched, unmatched, and skipped records.
9. Download the Excel reconciliation report for review and follow-up.

Common DotPe reconciliation workflows

DotPe POS reconciliation

This workflow compares your internal POS order detail or sales report with the DotPe offline report.

This is useful when your store or restaurant team needs to ensure every billed order is reflected correctly in the payment record.

DotPe settlement reconciliation

This workflow compares the DotPe settlement report with the bank statement.

This helps finance teams confirm that settlement amounts were received in the bank and that no transfer has been missed or delayed.

Fields and files commonly used in DotPe reconciliation

Cointab supports CSV, XLS, and XLSX files. For each primary report, users typically map:

• Header row
• Transaction date
• Amount
• Reference or identifier column

Useful identifiers may include:

• Order ID
• Transaction ID
• Payment reference
• Settlement ID
• Bank UTR
• Store code
• Invoice number
• Any business-specific reference used in your process

Supporting files can also be used to enrich the primary data before reconciliation. For DotPe workflows, that may include store mapping files, order metadata, fee or deduction files, or other reference data used for lookup and calculation.

How exceptions are reviewed

Cointab separates the reconciliation result into clear outcome groups so finance teams can focus on exceptions instead of reviewing every row manually.

Fully matched

The transaction appears on both sides and matches according to the configured logic.

Partially matched

The records are related, but the amounts do not fully match. This is useful for identifying short payments, overpayments, fees, deductions, or rounding differences.

Unmatched

The record appears on one side but not the other. This may indicate a missing file, a delayed settlement, an internal posting issue, or a partner-side exception.

Skipped

The row was not included in reconciliation because it was incomplete, invalid, duplicated, or excluded by rule.

AI-assisted work for difficult DotPe items

After structured matching is complete, Cointab can use AI to help finance teams review difficult open transactions. This is useful when references are inconsistent, descriptions are not standardized, or business context is needed to understand the difference.

AI can help with:

• Creating derived columns with Excel-style formulas
• Reviewing open items that do not match cleanly
• Suggesting possible reasons for an exception
• Identifying whether a missing file or delayed report may explain the mismatch
• Supporting conservative, reviewable matching decisions

If evidence is not strong enough, the record remains open rather than being forced into a weak match.

Reporting and audit readiness

Once reconciliation is complete, users can review a dashboard that shows the status of the run, the reconciliation summary, and transaction-level detail. Finance teams can filter results, inspect matched and unmatched records, and download an audit-ready Excel report.

The report history remains available for future reference, which is useful for recurring store operations, monthly close, and audit support.

Reuse and automation for recurring periods

A DotPe reconciliation setup does not need to be rebuilt every month. Once the workflow is configured, the same mapping and matching logic can be reused for future periods such as monthly, quarterly, yearly, or custom settlement cycles.

Cointab also supports automated data flow through:

• Email
• SFTP
• API

That means files can be received, validated, loaded into the correct reconciliation, and processed on a schedule. If a report arrives late, users can upload the missed file under the same reconciliation and refresh the report.

When a manual match is needed

Some DotPe exceptions require human review. Cointab provides a manual match option for transactions that the system and AI could not confidently resolve. This is useful when identifiers are missing, partner data is incomplete, or the finance team already knows the business context.

Manual matches remain visible in the report and can be undone if needed.

What finance teams gain from a DotPe workflow in Cointab

• Less time spent comparing reports in Excel
• Clear separation of matched, partial, unmatched, and skipped records
• A reusable setup for recurring store-level reconciliation
• Better visibility into settlement differences and bank credits
• Audit-friendly output for review and follow-up
• One shared workspace for the finance and operations team

Frequently asked questions

What reports are used for DotPe transaction reconciliation?

Most DotPe workflows use the internal POS or sales report on one side and the DotPe offline report, settlement report, or bank statement on the other side. Supporting files can be added when enrichment or lookup is needed.

Can Cointab handle both POS reconciliation and bank reconciliation for DotPe?

Yes. A DotPe workflow can be set up to compare POS data with transaction reports, or settlement data with bank statements, depending on the reconciliation objective.

What happens if a DotPe report is missing or received late?

The missed file can be uploaded under the same reconciliation and the report can be refreshed. This helps finance teams handle delayed partner files without rebuilding the workflow.

Can the same DotPe reconciliation be reused for future periods?

Yes. Once configured, the workflow can be reused for future runs by selecting the reconciliation, choosing the period, uploading the required files, and running the process again.

How does Cointab show exceptions in DotPe reconciliation?

Cointab separates records into fully matched, partially matched, unmatched, and skipped groups so teams can focus on the items that need review or follow-up.