Intercompany Utility Cost Reconciliations
An intercompany reconciliation should connect the providing and receiving records. Start with common references and agreed timing before comparing totals.
Intercompany Utility Cost Reconciliations
Separate timing differences from unmatched amounts or different classification. Each requires a different explanation.
Use a small cross-entity scenario to test the design. Follow the source event, approval, posting and reporting views for both sides. Include a correction or timing difference so the exception process is exercised. This reveals gaps that may not appear when each team tests only its own ordinary transactions.
Three useful steps
- Match transaction references.
- Compare periods and currencies.
- Assign unresolved differences to both relevant owners.
Keep inter-organization relationships explicit in the source and reporting design. A charge may need agreement between the providing and receiving teams, with appropriate evidence on both sides. Reconcile the relationship rather than assuming that one team's accepted record proves the other team's result is correct. Differences should have a defined owner and resolution path.
Consider a small example
One entity may record a charge before the receiving entity completes its process. Preserve the timing evidence rather than treating the difference as automatically erroneous.
Establish the organizational boundary before combining or comparing records. Legal entities, management units, utility services and reporting funds may answer different questions. Document which boundary applies to the current analysis. A shared name or common ownership does not make those dimensions interchangeable.
Where the approach can go wrong
Do not clear one side without considering the effect on the counterpart.
Separate common processing from common treatment. Organizations can share a system or support team while retaining different reporting requirements and approved policies. A standardized workflow should preserve those legitimate differences. Avoid using one convenient default merely because the technical platform can apply it everywhere.
Make the handoff easier
Distinguish creation, change and retirement of a record. The checks required for a new object may not be sufficient when an existing object changes ownership or becomes inactive. Preserve effective dates and historical relationships where the process needs them. Cleaning the current view should not make earlier transactions impossible to explain.
A reconciliation should separate missing data from data that has been classified differently. First compare the population of documents, then compare amounts, and only then investigate reporting categories. If those stages are mixed together, a changed filter can look like a mapping failure. Save the selection criteria with the evidence so another person can repeat the comparison using the same period and organizational scope.
Preserve the report selection along with the result. Period, organizational scope, currency and extraction time can explain a difference before any accounting issue is found. A workbook without those details is difficult to reproduce. Ask a colleague unfamiliar with the original preparation to repeat one check using only the saved evidence.
A usable result
Maintain a two-sided reconciliation with references, explanations and confirmed resolution.
Related reading
Municipal Utility Shared Service Reporting; Shared Utility Service Agreements and Cost Evidence; Utility Shared Asset Cost Reporting.