DotPe Transaction Reconciliation with Cointab

Offline businesses that use DotPe need a reliable way to reconcile daily transactions, settlement files, and bank credits. Manual checks in Excel can quickly become repetitive when the same sales, refund, fee, and remittance differences need to be reviewed across multiple stores or periods.

Cointab helps finance teams automate DotPe transaction reconciliation by comparing your internal records with DotPe reports and related external records. The workflow is built for structured review, exception handling, and audit-ready reporting.

Why DotPe transaction reconciliation matters

DotPe reconciliation is not just about confirming that a payment was received. Finance teams also need to verify:

• Whether the amount recorded in the POS matches the DotPe transaction amount
• Whether settlement amounts have been credited to the bank correctly
• Whether fees, deductions, refunds, or timing differences explain the gap
• Whether any transaction is missing from one side of the reconciliation
• Whether store-wise reporting remains clean across periods

For offline stores, restaurants, and multi-location businesses, these checks are important for month-end close, cash control, and exception follow-up.

Common DotPe reconciliation workflows

DotPe transactions vs POS reconciliation

This workflow compares your internal POS or order system on Side A with the DotPe transaction report on Side B.

Typical Side A data includes:

• POS order detail
• Store-wise sales report
• Order-level payment register
• Internal receipt or cashless transaction data

Typical Side B data includes:

• DotPe offline transaction report
• Payment reference data
• Transaction status report

The goal is to match each sale with the corresponding DotPe record using fields such as order ID, transaction ID, amount, date, store code, or other reference columns.

This helps finance teams identify:

• Fully matched transactions
• Partially matched transactions where identifiers match but amounts differ
• Unmatched sales that may not have a corresponding DotPe record
• Unmatched DotPe entries that may need review
• Skipped rows that were incomplete or invalid

DotPe settlement vs bank reconciliation

This workflow compares the DotPe settlement report on Side A or Side B with the bank statement on the opposite side.

Typical reconciliation checks include:

• Settlement credited to the bank on the expected date
• Amount differences caused by fees, reversals, or deductions
• Missing remittances
• Timing differences between settlement and bank posting

This is especially useful for finance teams that need to confirm that settlement reports translate correctly into bank credits.

How Cointab structures the reconciliation

Cointab follows a Side A and Side B model:

• Side A contains the records you expect to be correct, such as POS sales or settlement working data
• Side B contains the external records, such as DotPe transaction reports or bank statements

For each primary file, users map the relevant fields once:

• Header row
• Date column
• Amount column
• Reference or identifier column

Common identifiers can include order ID, transaction ID, settlement ID, store code, receipt number, or other business references.

If a file does not match the configured structure, the system can reject it with a clear error so the reconciliation remains auditable and consistent.

Supporting data can improve matching

Some DotPe workflows need additional reference files before the actual reconciliation run. Cointab supports supporting data for enrichment and preparation, not direct matching.

Examples include:

• Store mapping files
• Product or menu master data
• Tax or GST mapping files
• Fee or charge rate files
• Order metadata
• Lookup files used for enrichment

Supporting data is useful when the finance team needs to add missing context, normalize identifiers, or prepare derived fields before comparing the main reports.

Derived columns and AI formula support

In many DotPe workflows, the raw report columns do not line up perfectly with the internal books or POS system. Cointab allows users to create derived columns from existing fields.

Examples include:

• Clean transaction ID
• Normalized order reference
• Net amount after fees
• Amount excluding tax
• Store-wise payment amount
• Payment amount based on status

Users can also describe the logic in natural language and let AI generate an Excel-style formula for the derived column. That is useful when finance users know the business rule but do not want to build the formula manually.

Matching logic for DotPe records

Cointab uses structured reconciliation logic to match records across the two sides. It supports:

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

The system can compare records using rules such as equals, contains, and subset-based comparisons. This is helpful when DotPe references are split across multiple fields or when the same payment needs to be grouped before comparison.

After the rule-based matching completes, AI can help analyze the remaining open transactions where deterministic rules are not enough.

What finance teams see in the reconciliation report

Once the run is complete, Cointab shows a report dashboard with transaction-level detail and clear reconciliation outcomes.

Fully matched

These are transactions where the DotPe record and the internal record match according to the configured rules.

Partially matched

These are records where the reference matches, but the amount does not. In DotPe workflows, this may point to fees, deductions, underpayments, overpayments, or rounding differences.

Unmatched

These are transactions that appear on one side but not the other. For example, a sale may exist in the POS system but not in DotPe, or a settlement may exist in DotPe but not yet in the bank statement.

Skipped

Skipped records are rows that were not included in the reconciliation because of missing data, invalid values, duplicates, or other file issues. Showing skipped records helps teams understand what was excluded and why.

Manual review remains available

Some DotPe exceptions require business context that cannot be captured fully in rules. Cointab supports manual match for unresolved items when the finance team confirms that the totals and references are correct.

This is useful when:

• A file is incomplete
• A reference is missing
• A transaction is delayed
• The partner report uses a different format
• The matching rule needs a one-off exception

Manual matches are clearly marked so the audit trail remains visible.

Reuse the same DotPe reconciliation setup

Once a DotPe reconciliation is configured, finance teams can reuse it for future periods instead of rebuilding the workflow every month.

Typical recurring workflow:

1. Select the saved reconciliation
2. Choose the period
3. Upload the latest files or receive them automatically
4. Run reconciliation
5. Review the report and exceptions
6. Download the Excel output if needed

This reuse is useful for businesses that reconcile by store, by day, by week, or by month.

Automation for recurring finance operations

Cointab can also support recurring data flow through email, SFTP, or API integrations. That makes it easier to automate DotPe reconciliation once the workflow is configured.

Automation can help with:

• Receiving transaction or settlement files on schedule
• Running reconciliation after files arrive
• Notifying users when the report is ready
• Pushing output to downstream finance, accounting, or reporting systems

This is especially helpful for teams that want fewer manual uploads and more consistent reporting across periods.

Why this use case matters for finance teams

DotPe transaction reconciliation often sits at the intersection of sales, settlements, and bank postings. A structured workflow helps teams:

• Reduce spreadsheet dependency
• Spot missing settlements earlier
• Review exceptions faster
• Keep reconciliation steps consistent across users
• Maintain clear audit-ready records
• Close periods with greater confidence

Cointab is designed to make that process repeatable, transparent, and easier to review for finance and operations teams.