How mrioan/transaction-reconciliation works
Project Type & Purpose
• This is a full‐stack Java web application (Maven multi‐module) for automatic financial reconciliation of two CSV files.
• The “core” module implements the CSV-processing pipeline in plain Java; the “web” module is a Spring Boot WebMVC layer (Thymeleaf + JS + Bootstrap + jQuery) that exposes HTML pages and JSON endpoints.
File Structure Analysis
• Top level:
• pom.xml (aggregator)
• modules: “core” and “web”
• core/src/main/java/com/mario/sample/reconciliation:
• config (ConfigProperties)
• exception
• filter (CSVLoadingFilter → IdenticalRecordRemoverFilter → SimilarRecordFilter → ResemblingRecordFilter → ReportDataOrganizationFilter)
• matching (field matchers, record matchers, revisitors)
• model (Record, RecordPair, etc.)
• processing (CSVParser, RecordStore abstractions)
• util
• web/src/main/java/com/mario/sample/reconciliation/web:
• Application (entry point)
• configuration (WebConfig)
• controller (HomeController, GlobalExceptionHandler)
• service (TransactionReconciliationService orchestrates core; StorageService)
• mapper (maps core FilterOutput → web ReconciliationResult)
• web model (DTOs)
• static (JS/CSS/images), templates (Thymeleaf)
Insights from README
• Core uses a filter‐pipeline architecture (extensible sequence of Filters).
• Web module relies on core, exposes:
• HTML UI (file upload form + results tables + animations)
• JSON API (multipart/form POST, returns JSON summary).
• Uses external config.properties for core; application.properties for web.