gl-recon

Automated GL reconciliation normalizes GL and subledger extracts to a common key, executes matching algorithms to surface transaction breaks, and tags discrepancies by likely cause. It outputs a break report and a summary with counts and totals for root cause analysis.

Subledger reconciliation matches subledger transactions against the general ledger to identify breaks. Automated classification tags these breaks by likely cause, including timing differences, FX adjustments, mapping errors, duplicates, fees, and data quality issues for targeted resolution.

Yes, automated normalization aligns financial extracts to common comparison columns and coerces data types for exact equality tests. This standardization allows matching algorithms to accurately compare transactions even from differing source formats.

The best way to generate a reconciliation report is to run automated data matching on your GL and subledger extracts. This produces a break report and a summary containing counts and totals, directly aiding in root cause analysis and operational resolution.

Yes, you need to provide both general ledger and subledger extracts as input files. The reconciliation process requires these extracts to execute data alignment, matching algorithms, and classification tagging for your financial operations.