Infrastructure for Cash Flow Forecasting

Generally Accepted Accounting Principles (GAAP) require explicit accounting policies. Sarbanes-Oxley (for larger systems) drives internal control documentation. CMS cost reporting requires specific accounting treatment documentation. Budget policies defined. However, cost allocation methodologies sometimes opaque. Financial planning assumptions partially documented. Cost accounting complexity (especially in teaching hospitals). Budget process includes negotiation and politics (hard to fully formalize). Financial planning requires judgment. Revenue cycle complexity spans clinical and financial. Transfer pricing between entities sometimes ad-hoc.

ERP systems capture all accounting transactions systematically. Budgets entered and tracked. Payroll transactions comprehensive. Vendor invoices processed. Revenue cycle data captured (see Revenue Cycle function). CMS cost report data collected. However, budget assumptions and justifications poorly captured. Financial planning scenarios not systematically logged. Budget process includes conversations and negotiations not systematically captured. Financial planning scenarios spreadsheet-based (multiple versions, poor version control). Board financial discussions summarized but details lost. Capital project justifications in proposal documents, not structured system.

Chart of accounts highly structured and standardized. GAAP provides accounting taxonomy. CMS cost report structure defined. Budget hierarchies explicit. General ledger data elements standardized. However, cost allocation rules complex and institution-specific. Financial notes and assumptions often narrative. Healthcare cost accounting uniquely complex (direct vs indirect, patient care vs non-patient care, teaching costs, capital costs). Multi-entity structures create complexity. Grant and restricted funds each have unique rules. Transfer pricing between entities not fully standardized. Revenue cycle joins clinical and financial data (complexity).

ERP provides financial reporting interfaces. BI tools query financial data warehouse. Standard financial reports available. However, detailed GL data requires IT support to access. Budget planning tools often separate. External financial benchmarks (Vizient, Kaufman Hall) not integrated. ERP vendors limit direct database access (query through reporting layer). Budget tools separate from ERP. External benchmark vendors provide reports, not data feeds. CMS cost report preparation uses specialized software (HFMA MST). Multiple financial systems create access complexity. Self-service analytics limited for non-technical users.

Chart of accounts updated as needed (new programs, regulatory changes). Budget reforecasting mid-year. Monthly financial close ensures current data. Payroll rates updated with contract changes. However, cost allocation methodologies rarely updated. Budget templates not systematically improved. Historical budget assumptions not revisited. Monthly close takes priority over methodology updates. Cost allocation changes require physician buy-in (difficult). Budget templates familiar—change resists. Small finance teams focused on current reporting. No systematic process for validating prior assumptions. Accounting conservatism resists frequent changes.

Revenue cycle system posts to general ledger. Payroll system interfaces with GL. Accounts payable integrated with purchasing. However, clinical operations and finance weakly connected. Budget planning separate from ERP. External benchmarks not integrated. Forecasting tools disconnected. Clinical and financial systems historically separate. Budget tools (Adaptive Insights, Anaplan) separate from ERP. FP&A spreadsheet-driven. Multiple entities with separate GL systems. External data providers don't integrate. Clinical-financial linkage (cost per case, productivity) requires manual data integration. Organizational silos between finance and operations.