Project

General

Profile

Actions

Task #825

open

Epic #786: Square Payment Gateway Integration

Feature #821: Transactions & Reconciliation

Discrepancy Handling

Added by Redmine Admin about 2 months ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
-
Start date:
04/22/2026
Due date:
% Done:

0%

Estimated time:

Description

Create mechanism to flag, log, and optionally alert on discrepancies between system records and Square reports.

Actions #1

Updated by Deeksha Singh about 1 month ago

Module: Discrepancy Handling (Transactions)

TC_ID_DISCREPANCY_01
Title: Verify discrepancy is flagged when amount mismatch occurs
Preconditions: Transaction exists in both systems
Steps:

Create mismatch (Square = 100, DB = 90)
Run reconciliation
Test Data: Different amount
Expected Result: Transaction is flagged as discrepancy

TC_ID_DISCREPANCY_02
Title: Verify discrepancy is flagged when status mismatch occurs
Preconditions: Same transaction exists
Steps:

Set status mismatch (Square = SUCCESS, DB = FAILED)
Run reconciliation
Test Data: Different status
Expected Result: Discrepancy detected and flagged

TC_ID_DISCREPANCY_03
Title: Verify discrepancies are logged properly
Preconditions: Logging enabled
Steps:

Create mismatch
Run reconciliation
Check logs
Test Data: Any mismatch
Expected Result: Discrepancy details logged with transaction info

TC_ID_DISCREPANCY_04
Title: Verify alert is triggered for discrepancy (if enabled)
Preconditions: Alert system configured (email/notification)
Steps:

Create discrepancy
Run job
Test Data: Mismatch transaction
Expected Result: Alert/notification is sent to configured user/system

TC_ID_DISCREPANCY_05
Title: Verify no alert triggered for matched transactions
Preconditions: Matching records exist
Steps:

Run reconciliation
Test Data: Same data in both systems
Expected Result: No discrepancy flagged, no alert triggered

TC_ID_DISCREPANCY_06
Title: Verify handling of missing transaction discrepancy
Preconditions: Transaction exists only in Square or DB
Steps:

Run reconciliation
Test Data: Missing record
Expected Result: Missing transaction flagged as discrepancy

TC_ID_DISCREPANCY_07
Title: Verify duplicate discrepancy entries are not created
Preconditions: Same mismatch processed multiple times
Steps:

Run reconciliation multiple times
Test Data: Same mismatch
Expected Result: Discrepancy logged once or updated, not duplicated

TC_ID_DISCREPANCY_08
Title: Verify discrepancy records are stored for audit tracking
Preconditions: Discrepancy detected
Steps:

Run reconciliation
Check DB/log storage
Test Data: Mismatch transaction
Expected Result: Discrepancy stored with details (type, time, transaction ID)

TC_ID_DISCREPANCY_09
Title: Verify system handles high number of discrepancies
Preconditions: Multiple mismatches exist
Steps:

Run reconciliation
Test Data: Bulk mismatches
Expected Result: All discrepancies processed without failure

TC_ID_DISCREPANCY_10
Title: Verify error handling during discrepancy logging/alerting
Preconditions: Simulate logging/alert failure
Steps:

Create discrepancy
Trigger logging/alert failure
Test Data: System failure
Expected Result: Error handled gracefully, system continues processing

Actions

Also available in: Atom PDF