gl-recon

GL to subledger reconciliation normalizes two data extracts to a common key, performs a full-outer-join, and categorizes amount, quantity, and timing breaks. It outputs a detailed break report and summary for audit-ready month-end close.

Reconciliation breaks are classified by likely causes including timing differences, FX rates, account mapping errors, duplicate or missing posts, fee accruals, and data quality issues. The full-outer-join isolates GL-only and subledger-only entries for targeted review.

Yes, the reconciliation process handles daily checks across asset classes as well as month-end closes. It requires GL and subledger extracts sharing a common key and comparison columns to normalize data and surface matching or breaking entries.

Identifying timing breaks requires a full-outer-join on a common key between GL and subledger extracts. The process classifies unmatched entries as timing breaks, GL only, or subledger only, assigning likely causes like timing differences or missing posts.

Yes, a common key is required to normalize the two extracts and execute the full-outer-join. Without a shared key and comparison columns, the reconciliation cannot categorize amount, quantity, or timing breaks between the general ledger and subledger.

Amount and quantity breaks occur when matched records have differing values in comparison columns. The reconciliation classifies these breaks by likely cause, such as FX rate differences, fee accruals, or data quality issues, and includes them in the break report.