Back to Solutions Library
Solution 14 of 25PWS · Data Review/ValidationFO · Accounting
Cross-System Reconciliation Between RD Loan Systems and Treasury
RD must reconcile transactions across PLAS, DLS, CLSS, GLS, LoanServ, AMAS, ECMS, FMMI, NFC, and Treasury systems (CARS, GTAS, ASAP, G-Invoicing, IPAC, Fund Balance with Treasury) every month, and timing differences, transposition errors, mis-coded TAS, and pending Treasury settlements drive a stream of reconciling items.
Why It Matters
Treasury reconciliation breaks at month-end propagate into the Department-level USDA Consolidated Financial Statements and into OIG / GAO audit work papers. Smooth Treasury reconciliation is the foundation of clean audit opinion, accurate Fund Balance with Treasury, and on-time GTAS reporting.
HSG's Approach
- 1Stand up an automated multi-source reconciliation engine pulling from each loan system and reconciling to FMMI, NFC, and Treasury reporting (CARS, GTAS, ASAP) on a daily cadence.
- 2Tag every reconciling item to its USSGL account, TAS, cohort year, and Treasury reporting category for full lineage.
- 3Use AI tooling to auto-categorize reconciling items into proposed-correction templates with USSGL journal entry text.
- 4Stand up a 'ten-day-close' target with an exception aging dashboard.
- 5Document Treasury TFM Volume 1 Part 2 Chapter 4600 traceability and TFM Volume 1 Part 2 Chapter 4700 (intra-governmental) for every entry.
Expected Deliverables
- Multi-source reconciliation engine with documented lineage
- USSGL-tagged exception register
- Auto-generated journal entry package
- Exception aging dashboard
- Monthly close-by-day-10 SOP
Expected Outcome
Cut Fund Balance with Treasury reconciling-item population by 60% and accelerate monthly close by 5 business days.