Back to InsightsAutomation

Reducing Month-End Close: What Worked in Multi-Entity Controllership

By Luis Alberto Rivera TurUpdated 7 min read

Real lessons from close acceleration, intercompany reconciliation, data cleansing and finance automation across multinational controllership roles.

Professional examples in this article refer to Luis Alberto Rivera Tur's employment and project experience. They are not presented as Rivera Enterprise Solutions client testimonials or anonymous client case studies.

There is no single script that fixes month-end close. The improvements I have seen came from combining process ownership, clean master data, reconciliation discipline, clear SOPs and automation where it removed repetitive work without removing accounting review.

Standardize recurring accounting before automating it

At Honeywell, SOPs for tax accruals and journal entries contributed to a 25% reduction in close time. Standardization came first: recurring work had to have a clear owner, timing, support and review expectation before automation could make it faster without making it harder to control.

Data quality is a close-speed issue

Vendor-record cleansing and rigorous data mapping at Honeywell reduced reconciliation errors by 40%. A close team loses time when the same master-data problems create exceptions every month. Fixing the source of those exceptions can be more valuable than adding another reporting layer.

Resolve intercompany differences closer to the source

Honeywell's redesigned intercompany reconciliation workflows contributed to a 30% faster close process. Later, at NOV, intercompany accounting had to operate across JD Edwards and NetSuite entities consolidated through HFM. The principle remained the same: identify differences early, assign ownership and avoid allowing unexplained balances to age across periods.

Use automation to reduce preparation, not accountability

At Nefab, AI-assisted ETL and automated workflows reduced manual preparation of migration-ready asset data by 65%, while Power BI and Power Automate improved same-day cost visibility. The same design principle applies to close automation: machines should prepare, match and surface exceptions; Controllers should retain ownership of material judgments and approvals.

Make operating information available before the monthly report

A finance function can be technically closed and still be too slow operationally. At Nefab, daily supply-chain-level cost-variance reporting replaced a corporate WD+3 view for plant management. At Forza Transportation, telemetry and cost data were combined to analyze routes, stops, maintenance and cost per kilometer. Faster information matters most when it changes a decision while there is still time to act.

The close objective

The objective is not the smallest possible day count. It is a close that is fast enough for management, controlled enough for audit, and repeatable enough that the team is not relying on heroics every month. Automation is valuable when it strengthens that operating model rather than disguising weak accounting processes.

Next step

Need help with your finance operations?

Rivera Enterprise Solutions provides fractional controllership, finance-led ERP transformation support and US GAAP financial-control services for U.S.-based companies.

Book a Consultation