In Black & White

Freeing Finance, Budget, Audit & Treasury Departments from Drudgery One Article at a Time

Cashflow Confidence: The Surprising Opportunity For Finance

Cashflow Confidence: The Surprising Opportunity For Finance

  • Jamie Black
  • Automating Financial Reporting
  • minute(s)Cashflow Confidence: The Surprising Opportunity For Finance In an era of considerable challenge (seemingly un-fundable infrastructure deficits, an aging population which will require more services, and a turbulent global environment), many Canadian public sector organizations struggle to cope. The obvious options of raising rates, property taxes, tuition, etc., to generate revenue, or reducing services to control costs, or a combination of the two to address these challenges, are so unpalatable amongst constituents that they are usually non-starters. Too frequently, we overlook a key asset: cash reserves and investment portfolios. By refining cash management practices, finance teams can significantly boost returns on investments, turning idle funds into a powerful revenue source. This article explores a surprisingly overlooked way to boost investment returns while reducing risk —helping tackle big challenges without having to raise fees or cut services. Balancing Two Risks Capital Risk Investing in volatile assets exposes an organization to an increased likelihood that the initial investment may be lost, in whole or in part. To minimize this risk, public sector entities default to low-risk, low-yield options like short-term deposits. They trade higher returns for greater certainty. This strategy is codified in provincial regulations that limit diversification and emphasize capital preservation. These conservative strategies are mandated by various provincial frameworks: Ontario's O. Reg. 438/97, which restricts municipal investments to eligible assets like bonds, debentures, or promissory notes issued or guaranteed by Canada or its provinces. The regulation also enforces a prudent investment standard (Part III), requiring municipalities to adopt written policies that address diversification, liquidity, and risk management, while prohibiting investments in low-rated securities (e.g., below A-low for long-term debt). In British Columbia, the Municipal Finance Authority Act enables pooled investments through the Municipal Finance Authority (MFA), providing access to diversified, secure options for local governments. In Alberta, the Municipal Investment Regulation (Alta Reg 149/2022) offers additional investment opportunities, with specific provisions for major cities like Calgary and Edmonton, while still prioritizing prudent standards under the Municipal Government Act. Inflationary Risk Keeping too much cash in low-yield accounts exposes organizations to inflation risk. A simple example: a capital project budgeted to cost $100,000,000 in 2020 would require $120,000,000 in 2025, even if you only consider Consumer Price Inflation (Inflation Calculator - Bank of Canada). Thus, we “lost” $20 million in purchasing power in 5 years. Now that example assumes the return on our investment is zero. Erosion of purchasing power occurs if the rate of return is anything below the rate of inflation. In today's environment—with Canada's CPI hovering around 2% as of October 2025—a 1.5% yield on cash feels safe but delivers negative real returns. Thus, to effectively protect public funds, we need to mitigate both risks. Balancing Risks and Improving Returns Daily cash flow forecasting stands out as a foundational tool, shifting teams from reactive to predictive management. By anticipating cash needs more accurately, organizations can extend investment horizons and capture higher rates within regulated categories like fixed-income securities issued by Canadian governments. This directly supports the liquidity considerations required under O. Reg. 438/97, s. 7(2), ensuring investments align with an entity's written investment policy (s. 7(1)). Below, we outline two key strategies enabled by this practice, tailored to the realities of public sector teams: 1) Invest for Longer Terms Finance teams that do not dedicate time to daily cash flow analysis often default to short-term investments, as uncertainty about future cash needs makes longer commitments risky. However, with precise forecasting, entities can confidently allocate funds to longer-term eligible investments, which typically offer higher yields. This approach aligns with provincial regulations that permit such instruments while prioritizing capital preservation, allowing for improved returns without added risk. 2) Minimize Your Cash Buffer Without robust cash flow analysis, teams tend to maintain overly large buffers in low-yield bank accounts to hedge against unanticipated outflows or delayed inflows. Daily forecasting provides clarity, frequently enabling a reduction in these buffers while still ensuring liquidity. The excess cash can then be moved into even short-term regulated investments, yielding better returns. A Potential Hurdle - Banking Agreements Public sector organizations are often bound by banking covenants requiring significant amounts to be held in low-interest accounts to secure favorable loan terms or services. Daily cash flow forecasting provides the data needed to demonstrate stable liquidity, empowering teams to renegotiate these agreements for more flexibility. This could involve reducing minimum balance requirements or shifting funds to higher-yield options within regulatory limits, further enhancing returns. Real-World Benefits and Examples The improved return on investment delivered by these strategies can be substantial. Better returns have the potential to add millions to annual income, as demonstrated by entities that improved yields through enhanced forecasting, even under restrictive rules. Seizing the Opportunity Improved returns represent a "hidden" lever for fiscal health in Canadian public sector organizations, achievable within regulatory frameworks that prioritize safety and compliance. We urge finance professionals in municipalities, school districts, and higher education to assess their current practices and consider incremental improvements. By implementing strategic initiatives such as daily cash flow forecasting—reducing buffers, investing excess cash sooner, for longer enhance yields while balancing capital and inflationary risk mitigation—teams can generate additional revenue to assist in addressing pressing challenges like infrastructure deficits and an aging population. The challenge for most is how to find the time to do this daily work. As you heard Joe Sass from the City of Kelowna say, “what enabled all of this for us was having the people we could put to do this work on a full-time basis.” Often finance is trapped dealing with compliance work and can not prioritize this strategic work.
Public sector finance teams can unlock significant investment returns by refining cash management. Learn how daily cash flow forecasting helps reduce idle cash, extend investment horizons, and generate more income—without raising taxes or cutting services.
READ MORE
The Financial Process Maturity Model

The Financial Process Maturity Model

  • Jamie Black
  • Automating Financial Reporting
  • minute(s)The Financial Process Maturity Model A Practical Framework for Assessing and Improving Finance Operations Before choosing technology, assess the maturity of the financial process you want to improve. Should we automate reconciliations? Should we modernize reporting? Should we implement workflow? Should we replace spreadsheets? These questions are understandable. They are also often premature. Before deciding how to improve a process, organizations should first understand the maturity of the process they already have. Assessing process maturity helps organizations identify what needs to change first—and direct improvement efforts most effectively: automating before defining the work can leave required steps out of the workflow, extensively documenting and cross-training a manual process just before redesigning it can mean doing that work twice Assessment helps avoid omissions and rework—not simply choose software. Importantly, this model is not intended to measure technology maturity. It measures process maturity. A process can have modern software and still be immature. Likewise, a process may rely on legacy systems and still operate at a relatively mature level. The ultimate question is not what tools are being used. The question is whether the process is predictable, efficient, visible, resilient, and sustainable. Figure 1. A common six-stage model for assessing the management capability surrounding a financial process. Stage 1: Uncontrolled Objective: Existence Is the process occurring at all? At this stage, ownership is unclear, execution is inconsistent, and management has limited confidence that the process is being performed consistently. Typical symptoms Responsibilities are poorly defined Deliverables are frequently missed Work occurs inconsistently Knowledge resides with a small number of people Management lacks visibility into status Common statement: “I think somebody takes care of that.” Next objective: Establish ownership and ensure the process consistently occurs. Stage 2: Reactive Objective: Survival Are we constantly scrambling? Reactive organizations are capable of producing results, but success depends heavily on heroic effort. Deadlines are met through determination rather than design. Typical symptoms Recurring overtime Frequent fire drills Staff burnout during major cycles Continuous deadline pressure Heavy dependence on a few key individuals The critical distinction A single difficult year does not necessarily indicate a Reactive process. A new accounting pronouncement, ERP conversion, major reorganization, or unexpected vacancy may temporarily increase workload. The real test is whether extraordinary effort is the exception or the expectation. If overtime occurs every year, the process is likely Reactive. If overtime occurred because of a unique event, the organization may be Planned but temporarily disrupted. Figure 2. Recurring operating patterns are more diagnostic than one unusually difficult cycle. Common statement: “We always get it done somehow.” Next objective: Move from recurring fire-fighting to predictable execution. Stage 3: Planned Objective: Predictability Can we reliably execute the process? At this stage, organizations have moved beyond survival. Work is scheduled. Responsibilities are assigned. Procedures are documented. Reviews occur consistently. Success is repeatable. Typical symptoms Defined ownership Established schedules Documented procedures Consistent reviews Reasonable predictability Warning signs Even Planned organizations experience new regulations, major technology changes, unplanned staff departures, and significant organizational change. The difference is that these issues are disruptions, not normal operating conditions. Common statement: “We know what needs to happen and when.” Next objective: Reduce effort while maintaining consistency. Stage 4: Automated Objective: Efficiency Have we eliminated low-value manual work? Automation is not the objective. Efficiency is. Organizations at this stage deliberately reduce repetitive activities so staff can focus on analysis, review, decision-making, and risk management. Typical symptoms Reduced manual entry Less copying and pasting Data integration Workflow automation Reduced spreadsheet maintenance More time spent analyzing than assembling Warning sign Replacing ten spreadsheets with one enormous spreadsheet is not automation. If effort has not materially decreased, the process is probably not Automated. Common statement: “The team spends more time reviewing than preparing.” Next objective: Create operational visibility. Stage 5: Transparent Objective: Visibility Can leadership see what requires attention? The defining characteristic of this stage is visibility. Management can identify risks before they become problems and intervene before they become crises. That visibility also supports productivity: less effort is required to establish status, locate bottlenecks, and determine where to intervene. Typical symptoms Status dashboards Progress tracking Exception management Escalation procedures Early risk identification Bottleneck visibility Practical test Can leadership quickly answer the following questions? What is complete? What is overdue? What is blocked? What is at risk? Where should management intervene? If answering these questions requires several emails, meetings, or phone calls, the process is probably not yet Transparent. Common statement: “We know where the issues are before deadlines are affected.” Next objective: Create long-term organizational sustainability. Stage 6: Governed Objective: Sustainability Can the organization sustain and continuously improve the process? At the Governed stage, the focus expands from executing the process to sustaining and continuously improving it through personnel changes, technology changes, organizational restructuring, and future growth. Process governance Formal process documentation exists Procedures are maintained and version controlled Ownership and accountability are clearly defined Documentation reviews occur regularly Organizational resilience Cross-training programs exist Succession planning has occurred Knowledge transfer is intentional The process is not dependent on one individual Technology governance Approved and supported tools are used Security controls and access rights are reviewed Disaster recovery plans exist Business continuity considerations are documented Continuous improvement Post-cycle reviews occur Lessons learned are documented Successes and failures are evaluated Root causes are identified Processes and documentation are revised accordingly Practical test A Governed organization can answer “yes” to two questions: If our most experienced employee left tomorrow, would this process still operate effectively next year? Did we learn something from this year’s cycle that will measurably improve next year’s? Common statement: “The process is bigger than any individual employee.” Next objective: Sustain the process while learning, adapting, and improving. How To Use The Model The goal of this model is to identify the next practical step forward. Very few organizations operate entirely at one maturity level: Financial reporting may be Planned. Reconciliations may be Reactive. Cash flow forecasting may be Automated. Grants management may be Transparent. The model creates a common language for discussing operational maturity across finance functions. It also helps organizations avoid a common mistake: trying to automate a process that first needs to be planned. Automation rarely fixes an immature process. More often, it makes an immature process operate faster. Final Thought Technology projects often begin with discussions about software. Successful transformations usually begin with discussions about process maturity. Organizations improve by building capabilities that reinforce one another: planning makes execution predictable; automation reduces repetitive effort; transparency makes status and bottlenecks visible; and governance helps sustain and improve performance over time. Ultimately, maturity is not about technology. It is about creating financial operations that are predictable, efficient, visible, resilient, and continuously improving. That is the foundation upon which lasting transformation is built.
Technology won’t fix an immature process. Before you automate, assess your maturity. Use the six-stage Financial Process Maturity Model to identify your next practical step.
READ MORE
Where Is Your Organization on the Reconciliation Maturity Curve?

Where Is Your Organization on the Reconciliation Maturity Curve?

  • Jamie Black
  • Finance Evolved
  • minute(s)Where Is Your Organization on the Reconciliation Maturity Curve? A practical self-assessment for finance teams looking to improve productivity & internal controls. Most finance teams can answer whether reconciliations have ever been performed. Far fewer can say, with confidence, whether the process is timely, complete, visible, and strong enough to detect issues before they become control problems. That distinction matters. A reconciliation process may have been performed while still leaving management with limited visibility into overdue accounts, aging reconciling items, recurring discrepancies, review quality, and control effectiveness. A maturity model helps organizations place themselves on the journey from reactive reconciliation to governed, exception-based oversight. The Six Stages of Reconciliation Maturity Stage Core Question Common Symptoms Would we know if a material error, omission, or unreconciled balance existed? Reconciliations have stopped, ownership is unclear, and management has no dependable visibility into errors, unreconciled balances, or accumulating exceptions. Did we reconcile? Manual spreadsheets, inconsistent timing, limited review, high dependency on individual knowledge. Did we reconcile correctly? Standard templates, clear procedures, defined preparer and reviewer roles, but limited automation. Can we reduce manual matching and automate exception management? Automated data imports, automated matching (rules, faster based), exception identification. Do we know what requires attention? Dashboards, aging views, overdue-account reporting, automated escalation, and management visibility. How healthy is our reconciliation process? Continuous monitoring, trend analysis, risk-based frequency, exception ownership, and audit-ready evidence. Stage 1: Uncontrolled Due to staff turnover, conflicting priorities, or other causes, no reconciliations are occurring currently. The risks abound: Undetected errors: Material errors, omissions, or unreconciled balances may exist without management knowing. Financial reporting risk: Inaccurate balances may flow into internal or external reporting before they are identified. Fraud and misuse risk: Unusual or unauthorized transactions may go unnoticed because no regular control is operating. No clear ownership: No one can reliably confirm which accounts should be reconciled, who is responsible, or when the work last occurred. Loss of institutional knowledge: Staff turnover, undocumented routines, or competing priorities can prevent the process from restarting quickly. Unmanaged exceptions: Reconciling items may accumulate without aging discipline, escalation, or resolution. Audit and control failure: The organization may be unable to demonstrate that a key control exists, operated, and was reviewed. Stage 2: Reactive At the reactive stage, the organization is primarily concerned with whether reconciliations are getting done at all. The process may depend heavily on spreadsheets, email, undocumented routines, and the knowledge of a few experienced employees. The risk that reconciliations are not happening at all is reduced. Most other risks remain because the process is still manual, inconsistent, and dependent on individual effort. Stage 3: Disciplined At the disciplined stage, the organization has standardized templates, clearer procedures, documented review steps, and defined ownership. Reconciliations are more consistent and easier to review. This is an important improvement, but it does not automatically solve the visibility problem. A disciplined manual process can still be slow, fragile, and difficult to monitor across many accounts. We have also mitigated the continuity of operations risk somewhat in that procedures are documented, but transition may still be long and difficult. Stage 4: Automated At the automated stage, the organization begins reducing manual matching effort. Bank and general ledger activity can be imported, matching rules can identify routine activity, and exceptions can be surfaced more quickly. This stage is often where tools such as reconciliation automation and integrations with reporting platforms can create significant value. The objective is not simply to make accountants work faster. It is to focus their attention on exceptions, judgment, resolution and the beginnings of management visibility. Here then at stage 3 we have begun to drive significant productivity improvements, focusing our team on the important items and automating the repetitive. The automation also further mitigates the negative impact of losing key staff as the matching rules are a very explicit, formal documentation of how the reconciliation should be performed. Also, the matching can run daily and while not a complete reconciliation it does mean that the reconciliations waiting for the new hire are at least partially completed. Stage 5: Transparent At the transparent stage, management can see what requires attention. Leaders can view completion status, overdue accounts, aging reconciling items, recurring exceptions, and escalation needs without waiting for informal updates. This is the point where reconciliation begins to connect directly with continuous controls monitoring. The process becomes visible enough for management to monitor whether the control is operating, not merely whether staff believe the work is underway. Stage 6: Governed At the governed stage, reconciliation is treated as a management control, not simply an accounting task. The organization monitors process health, evaluates trends, uses risk to determine frequency, assigns ownership for exceptions, and retains audit-ready evidence. The question changes from “Did we reconcile?” to “How healthy is the reconciliation control, and where is risk increasing?” How to Move Up the Curve Progress does not require a single, enterprise-wide transformation. Many organizations begin by identifying high-risk accounts, standardizing procedures, reducing spreadsheet dependency, automating routine matching, and building dashboards that show completion, aging, exceptions, and review status. The organizations that move furthest up the maturity curve are not simply those that match transactions faster. They are the organizations that give management clear, timely confidence that a critical control is operating. As organizations mature, the focus shifts from completing reconciliations to governing the effectiveness of the process itself. The goal is not automation for its own sake. The goal is a reconciliation process that is faster, more resilient, easier to review, and more visible to management. A Useful Self-Assessment A simple way to start is to ask: Do we know every account that should be reconciled? Do we know which reconciliations are late? Do we know how old unresolved items are? Do we know whether exceptions are increasing or decreasing? Would management know if a reconciliation stopped happening? If these questions are difficult to answer, they are a useful starting point for a deeper conversation. F.H. Black works with public sector finance teams to assess reconciliation maturity, identify control gaps, and define a practical path toward more automated, transparent, and governed reconciliation. Contact us to explore a reconciliation maturity assessment for your organization.
Evaluate your reconciliation process with this six-stage maturity model. Identify gaps, improve visibility, and move toward stronger controls and higher productivity.
READ MORE
Reconciliation Delayed Is Risk Multiplied

Reconciliation Delayed Is Risk Multiplied

  • Jamie Black
  • Finance Evolved
  • minute(s)Reconciliation Delayed Is Risk Multiplied A control-risk perspective for finance leaders, treasurers, controllers, and audit committees. Most organizations know they should reconcile their bank accounts. The more important question is whether they are doing it often enough, completely enough, and with enough visibility. For many finance departments, reconciliations remain a manual process performed by a small number of experienced employees on a periodic basis. When workloads increase, vacancies occur, or key staff retire, reconciliations can quickly fall behind. That situation is more than an operational inconvenience. It is a control risk. Why Timing Matters Reconciliations are far more than merely an essential first step in financial reporting. They help identify fraud, bank errors, internal mistakes, and unexpected activity while giving management an accurate view of cash which is critical for accurate cash flow forecasting & investing. The longer the delay in reconciling, the greater the risk to the organization: Errors accumulate, Recovery opportunities diminish, Institutional knowledge fades, and Fraud related losses accumulate (Figure 1) Thus, the value of reconciliation is not simply confirming that most transactions are correct. It is finding the transaction that is not. That is why timing matters. A reconciliation performed weeks or months after the activity occurred may still identify a problem, but the organization may have already lost its best opportunity to correct, recover, or contain the issue. Turnover Is the Risk Nobody Plans For When finance leaders think about risk, they often focus on cyber threats, fraud schemes, or regulatory compliance. Less attention is paid to risk to operational continuity. In many organizations, only one or two employees truly understand the reconciliation process. If one of those individuals leaves, critical controls can stop almost immediately. Reconciliation is too important to reside in the knowledge of a single employee. If a critical control cannot survive the departure or absence of one person, it is not a resilient control. Reconciliation Modernization Solves an Oversight Problem The most overlooked risk may be management visibility. In an environment of manual, decentralized reconciliations most organizations cannot reliably answer basic governance questions: Which account reconciliations are overdue? How old are the exceptions? Are unresolved items increasing or decreasing? Would management know if a reconciliation stopped happening altogether? In that sense, reconciliation modernization is not only about matching transactions faster. It is about giving management timely evidence that a critical control is operating as intended. That ability creates what every CFO, Treasurer, Controller, and Audit Committee needs: confidence that controls are operating, not simply confidence that controls exist. A Practical Path Forward Organizations do not need to transform every reconciliation process at once. A practical starting point is to: Identify high-risk accounts, Increase reconciliation frequency where the risk warrants it, Standardize documentation and review, and Give management visibility into completion status and unresolved exceptions. For organizations already considering account reconciliation modernization, FHB’s broader resources on balance sheet account reconciliations, continuous controls monitoring, Workiva and Adra integration, and public-sector success stories provide useful companion perspectives. The conclusion is straightforward: reconciliation delayed is not risk postponed. It is risk multiplied.
Delayed reconciliations multiply risk. Discover why timing, staff turnover, and poor visibility create control gaps—and how finance leaders can fix them.
READ MORE
How Joint CIO–CFO Leadership Transforms Government Reporting

How Joint CIO–CFO Leadership Transforms Government Reporting

  • Jamie Black
  • Finance Evolved
  • minute(s)Beyond the Report: How Joint CIO–CFO Leadership Can Transform Government Reporting Productivity and Resilience Across state and local government, core financial and regulatory reporting outputs, such as the Annual Comprehensive Financial Report (ACFR), Schedule of Expenditures of Federal Awards (SEFA), GASB disclosures, and recurring interim financial reporting, remain critical to public accountability. However, the greatest operational risk and opportunity for improvement does not reside in the outputs themselves. It resides in the business processes, controls, and operating models required to produce them. CIOs and CFOs increasingly share accountability for these end-to-end processes. Modern government reporting is not a downstream document-assembly task; it is an enterprise workflow that spans data ingestion, governance, validation, review, audit support, and publication. The strength and efficiency of this workflow directly affect transparency, risk exposure, staff sustainability, and public trust. In California, this challenge intersects directly with the priorities of Envision 2026: California’s Technology Future: Goal 5 (Continually Future-Proof the Business of Government) emphasizes modularity, process consolidation, and emerging-tech readiness, while Goal 4 (Align Strategy Execution Across the State) calls for breaking down silos and improving performance excellence. Goal 2 (Secure California’s Technology Investments) further underscores the need for strong data governance, traceability, and cybersecurity in all enterprise workflows — including financial and regulatory reporting. Core Challenge: The End-to-End Reporting Process Most reporting challenges faced by governments are not driven solely by evolving accounting standards or disclosure requirements. The challenges posed by these changing standards are often exacerbated by fragmented, manual, and loosely governed processes used to assemble recurring reporting outputs. These operating models commonly rely on disconnected spreadsheet-centric calculations, informal review practices, late-cycle validation, and institutional knowledge concentrated among a small number of individuals. These fragmented approaches often result in thousands of hours of unnecessary effort, late nights during reporting season, heavy reliance on a few institutional knowledge holders, elevated risk of errors or control weaknesses during audits, and limited capacity for proactive analysis or strategic initiatives. In such environments, reporting outputs become point-in-time results produced through effort and heroics, rather than predictable outcomes generated by controlled and repeatable processes. What Modernization Really Means Modernizing government reporting is not only about changing report formats or accelerating publication timelines. It is about strengthening the end-to-end reporting solution so that compliant reporting outputs are produced reliably through disciplined execution. A modern reporting operating model emphasizes controlled ingestion of source data, governed transformations and calculations, defined review and approval workflows, continuous validation throughout the reporting cycle, and full traceability from source data through final publication. Add to these benefits a dramatic reduction in the manual effort required each cycle. Organizations that have modernized often report 30–50%+ reductions in preparation time for ACFR and interim reports, fewer last-minute adjustments, and greater staff capacity for value-added work such as forecasting, performance analysis, or process innovation. Standards and Governance Alignment A process-centric reporting solution aligns with GAAP and GASB requirements, GFOA best practices, audit expectations related to documentation, version control, and evidence retention, and enterprise IT governance policies governing access control, security, and data integrity. Perspective from F. H. Black & Company The optimal approach is to address government reporting through the lens of end-to-end business process improvement and automation. Having supported hundreds of public sector organizations in this journey, the focus should not be on the report as a document, but the operational system required to produce reporting outputs consistently, from data sourcing and validation through review, audit support, publication, and roll-forward to future periods. Key to the success of these projects is not merely IT expertise. Improving business processes also requires experience in conducting these processes. That is why all FHB engagements are led by Principal Consultants who are CPAs, with extensive experience working in and with public sector finance, budget, treasury & audit teams. This ensures accounting standards, compliance obligations, and audit expectations are embedded directly into process design while remaining aligned with CIO responsibilities for governance, security, and enterprise resilience. Closing Thought For California CIOs and CFOs, the future of government reporting lies in treating it as a strategic enterprise capability rather than a recurring deadline-driven exercise. When supported by disciplined processes, modern platforms, and close collaboration between finance and technology leadership, organizations can achieve substantial productivity gains, lower operational risk, improve staff sustainability and morale, enhance audit readiness, and ultimately strengthen public trust and accountability. Strong reporting outputs are achieved not by working harder at deadlines, but by building processes and systems that perform reliably year after year. To explore how your organization can modernize its end-to-end reporting processes while aligning with Envision 2026 priorities, contact F. H. Black & Company at www.fhblackinc.com or reach out directly to discuss a no-obligation process assessment.
Discover how joint CIO-CFO leadership can modernize end-to-end government reporting, reduce risk, cut preparation time by 30-50%+, and advance Envision 2026 goals.
READ MORE
[Workiva + Adra]: An Integration Powered by FHB

[Workiva + Adra]: An Integration Powered by FHB

  • Jamie Black
  • Workiva
  • minute(s)[Workiva + Adra]: An Integration Powered by FHB Adra is a leading software for the automation of the financial close process, while Workiva offers a cloud-based, collaborative platform connecting reports and data. Both solutions are known to save users time and money while improving accuracy and repeatability. And together, they equal more than the sum of their parts. FHB recognized that the combination of Workiva and Adra would offer a uniquely transparent, accurate, and controlled solution for financial close and statutory and regulatory reporting, while streamlining workflow across the entire record-to-report (R2R) process. So, we developed an integration tool to bring you the best of both worlds. Introducing: [Workiva + Adra] At FHB, we have one focus—streamlining and automating processes to lighten the workload of public sector finance and budget teams across North America. To that end, we partner with industry-leading software companies, providing custom implementation of the best available solutions to meet our clients’ needs. Workiva and the Adra Suite of Solutions by Trintech are two such valued partners. Learn more about [Workiva + Adra]. To find out how [Workiva + Adra] can work for you, schedule a call with our expert team. © 2025 FH Black Inc. All rights reserved. Content may not be reproduced, excerpted, distributed, or transmitted without prior written consent.
Reap the combined benefits of Workiva and Adra with FHB's integration tool.
READ MORE
Discovery as a Foundation for Success

Discovery as a Foundation for Success

  • Jamie Black
  • Best Practices
  • minute(s)Why Is Discovery Such a Crucial Step? Discovery sessions are key to ensuring that a project will result in the desired outcome for our clients, our partners, and ourselves. They provide a forum for all stakeholders to build a common understanding of the challenges of the current processes and tools; the needs that must be addressed by the solution; project objectives; and potential hurdles and pitfalls. A productive discovery session resolves misunderstandings and sets the tone for open, clear, and consistent communication. It is a critical first step to ensuring team buy-in and is essential to maximizing the benefit you receive from the project. Learn more about managing change. How Can We Ensure a Fruitful and Effective Discovery Session? Have the right people in the room. First and foremost, you must include those in the trenches who perform the process. The more people with this perspective you can include, the better. Only they can offer an intimate look at process details; practical feedback regarding shortcomings, nuances, and time involved in the current approach; and a thoughtful wish list of essential features in a new solution. They will ask the right questions, and their answers will provide invaluable insight. Next, be sure to include senior management and the business process owner(s). These are the people who understand the big picture—e.g., political implications, budget and time constraints, your organization’s vision, and overall goals. They can speak to how process challenges impact the execution of your organization’s strategy. Be completely candid. It’s important to make the discovery session a safe place to voice concerns and provide honest feedback, even if the conversation becomes uncomfortable. Are you short-staffed? Is your team relatively inexperienced? Are they lacking technological savvy? The more we understand your true challenges, the better we can design an implementation plan to tackle them. If We Don’t Include the Right People, What Could Go Wrong? In a word, everything. Without the right people in the room, you risk wasting countless hours, and losing hundreds of thousands of dollars. Failing to reveal key considerations up front can lead to process gaps you may not have the budget to fix. You might end up having to change or shrink the scope of your project. You might have installed the wrong software and be forced to start over. Worst case scenario, your implementation could result in complete failure. After all, a whopping 70% of IT projects fail. Change management research has revealed that making a decision about a significant change without input from your whole team will likely engender frustration and resentment, creating project adversaries instead of advocates. If We Prioritize Discovery, What Could Go Right? When all stakeholders have a voice in discovery and project goals are on target, everyone wins. As the US Navy Seals say, “Slow is smooth, smooth is fast.” When you focus on conducting each step of the implementation—starting with discovery—correctly and completely, you will see your desired results more quickly. In the words of our President, Jamie Black, “Take your time. Do it once, do it right.” "I have been involved with this kind of software implementation system upgrade for many, many years...when I started to go through the procurement process, I could never imagine it would have gone so smoothly, with this level of success." -Dongmei Li, Assistant Controller–Corporate Accounting at Chicago Public Schools © 2025 FH Black Inc. All rights reserved. Content may not be reproduced, excerpted, distributed, or transmitted without prior written consent.
Learn why discovery sessions are so important, who should attend, and what should be discussed.
READ MORE
Change Management: An Introduction

Change Management: An Introduction

  • Jamie Black
  • Best Practices
  • minute(s)Key Considerations for Managing Change The way our clients react to change and their level of change acceptance can influence their success as much as their budget, choice of software, or technical aptitude. How do we know? We’ve been helping public sector finance and budget departments across North America improve and automate their most time-consuming and tedious business processes for nearly 30 years. So, we thought it might be helpful to share highlights from research behind the importance and key features of change management. What Is Change? Change is both the process through which something is made different (a verb) and the result of that process (a noun). The adaptation, growth, and very survival of human beings has long depended on our ability to manage change. Consider the crucial advent of fire-building or weapon-making, or the more contemporary prerequisite of technological savvy for success in the modern workplace. Organizational Change Change management within an organization involves the activities, functions, and tools it uses to deal with something new. As an example, institutions of all kinds use the tools of training and development  to ensure their employees’ sustained competence and efficacy amid the ever-changing dynamics of the workplace. Global research and advisory company Gartner reports that today’s average organization has undergone five significant organizational changes in the past three years—and almost 75% of those expect to expand major change initiatives over the next three years. Change initiatives range in scope and complexity from process improvements to mergers and acquisitions. Timeframes for organizational change can range from slow and gradual, like rethinking each individual step in a process over time, to quick and total, like suddenly adopting an entirely new system or approach. As with individuals, an organization’s ability to survive, stay relevant, compete, grow, and last, depends on its ability to manage change—both internally and externally. WANT TO LEARN MORE? In his 1996 book, “Leading Change,” John Kotter was among the first to apply the academic theory of change management to the world of business. His eight-step change management process remains relevant to this day. Other notable change management models include  Lewin’s Change Management Model, and Prosci’s ADKARⓇ Model Change Is Difficult Despite the inevitability of change, people (by nature) prefer stability over anything new or unfamiliar. Known as cognitive bias, this tendency is thought to be an unconscious process, whereby people cling to a belief system despite being presented with a better solution. DID YOU KNOW? One 2019 study found that monkeys (capuchin and rhesus macaques) were “significantly more likely to adopt new and more efficient shortcuts to attaining their goals than humans.” The McKinsey consulting group reports that 70% of all change initiatives fail. The reasons for failure include: Misalignment of values reflected in the change itself and values of the people experiencing the change Failure to manage employees’ attitudes toward change Lack of awareness of change’s potential benefits Change is seen as unfair or punishment Staff members may fear: A shift in duties Losing their job to automation Revealing weakness/incompetence in technology or role Loss of control Ripple effects More work An unrealistic timeline or insufficient employee participation in training can further hinder the success of a change initiative. Unsuccessfully managing a workforce through change can be costly; dissatisfied employees are known to be less productive and are more likely to leave an organization. The development of negative attitudes and adverse reactions toward change is known as resistance to change. Research suggests that employees’ readiness for change strongly influences their resistance, by transforming their attitudes. In other words, change is more successful when employees are prepared for it, not surprised by it. DID YOU KNOW? The Society for Human Resource Management (SHRM) has identified six states of change readiness: indifference, rejection, doubt, neutrality, experimentation, and commitment. Change in the Public Sector Is Especially Difficult Government entities are typically slower to accept and adopt changes—like the introduction of new technology or business processes—than organizations in the private sector. Reasons include: Less funding Higher public scrutiny Lack of internal informational technology (IT) staff or capacity Siloed duties and departments Complicated contract processes For some public sector organizations, slow adoption of technology and process change has led to more expensive and burdensome service provision. When they embrace change, they: Help eliminate time-consuming, frustrating, and “glitchy” processes Can focus on the actual work of providing services Make their staff more accessible to the public Get help more efficiently to those who need it The benefits of change in the public sector are clear. The challenge is that government employees may be among the least comfortable or familiar with change. Consequently, greater change management support is likely necessary in those settings. To Be Successful, You Must Manage Change The Importance of Leadership Both a systematic approach (strategy) and effective leadership are critical to the success of any organizational change endeavor. A change management strategy provides leaders with steps to successfully guide an organization through change, while limiting disruption and unexpected consequences. The goal may be to change a process or approach, but the key to success is the ability to effectively lead people through the change. Keep It Human The fundamental common denominator among successful change initiatives is people. To effectively implement change, leaders must take its impact on people into account. The following steps can help garner stakeholder trust and promote acceptance (and even appreciation) of a proposed change: Clarify the desired end result in advance. Highlight pain points and the need for change. Make the change as specific as possible. Be transparent about its benefits and challenges. Listen to and address employees’ reactions. Establish their commitment to the initiative. Remember the study that found monkeys adapted to change more readily than humans? Turns out, when the benefits of using a new approach were made clear, “humans were more likely to get on board.” Why It Matters The importance and impact of effective change management cannot be overstated. Financial, cultural, institutional, and other factors make organizational change in the public sector particularly challenging. The right approach is vital to the success of any change initiative. Securing employee buy-in not only makes change easier, it establishes a relationship of trust, reducing resistance overall and minimizing the need to campaign for future reengagement and support. With the right combination of communication, preparation, planning, and support, a well-managed change can dramatically elevate both the quality of employees’ day-to-day experience and the focus of their work. Let Us Help Decades in the business of change have informed FHB’s successful approach to streamlining and automating even the most deeply ingrained and archaic business processes in the public sector. Schedule a meeting with us today to explore how we can help manage your organization’s need for change. © 2025 FH Black Inc. All rights reserved. Content may not be reproduced, excerpted, distributed, or transmitted without prior written consent.
Learn about organizational change, why it's particularly hard in the public sector, why it's important to manage it, and how to do so effectively.
READ MORE
Why focusing on simple can lead to catastrophe

Why focusing on simple can lead to catastrophe

  • Jamie Black
  • Best Practices
  • minute(s)For finance and budget professionals, optimizing how we complete our work can save time, mitigate the risk of error and make processes easier to delegate & manage. When improving a process requires new software tools, we recognize a common bias towards "simple" tools. It often begins with our client making a comment like: My existing solution is highly manual, time intensive, and has a high risk of error but it is easy/simple/straightforward. This new solution will likely save time and reduce the risk of error, but it seems too complicated. Initially, this may seem like a wise approach and an easy assessment. However, addressing it fully requires foundational concepts to be thoroughly flushed out. For example, what precisely do you mean when you say simple, easy, and complicated? An illustrative example Let's imagine we want to mount a new 60" TV on the living room wall. Let's also assume that we are not home renovation or carpentry experts. We arrange the supplied equipment from the mounting kit we bought on the table and review the instructions. Scenario 1: We have a very limited toolbox to use in the task. We have a hammer, some screwdrivers, and a tape measure. Scenario 2: We decide to invest in more tools. We get a laser level, a stud finder, cordless drill, drill & screwdriver bits, and screw anchors, as well as the hammer, screwdrivers, and tape measure we already had. Scenario 1 seems simpler. There are only three tools, and you already own them. They are basic tools you often use for minor tasks around the house so no learning is necessary. Scenario 2 is more complicated. It requires you to have: the additional tools, charged batteries for the laser level and drill (if not charged, we need to wait for them to charge), some understanding of home construction: Inside the walls are studs that are typically spaced every 16" and that, if you screw into them, they support mounting much heavier objects. If you do not mount it into a stud, you will also need to know that you need to use screw anchors, but even then, it may not hold the TV. Also, inside the walls are electrical wires and pipes that you must avoid. knowledge of how to use the laser level, stud finder and screw anchors. A more careful review reveals that you need to understand home construction in both scenarios. But if all you have is the simple tool kit, you might (unless you supplemented these tools with an expert's knowledge and experience) overlook the required home construction knowledge. In other words, the simple scenario is simplistic and omits some crucial considerations that may lead to long-term rework. In the mounting TV scenario, rework means: buying a new TV when the mount rips out of the wall and crashes to the floor, repairing drywall and repainting, repairing the floor where the falling TV damaged it. If you don't have time to do it right, when will you have the time to do it over? John Wooden Thus Scenario 2, while more complex and more expensive (in tools and time to learn them), dramatically increases the probability of properly meeting the goal both in the short and long term. In other words, these additional tools allows the non-expert home renovator to achieve results that a master might be able to achieve with the limited tools of Scenario 1. Clients often question the value of the greater expense of Scenario 2. Depending on the precise tools we are considering, once the investment in tools and the knowledge to use them has been made, you will likely use them on other projects (hanging pictures, mirrors etc.). Scenario 1 means these other projects are at equal risk of disaster as when we hung the TV. Our recommended approach: Considering the above, having this simple vs. complex conversation with clients, we suggest and assist with the following steps: Determine the necessary tools and knowledge to properly solve a particular problem. Assess current tools & knowledge to determine the investment necessary to achieve a solution you will be happy with both today and in the future. Consider the preferences & aptitude of the team that will complete the project. Some folks like learning new tools and see it as an opportunity to continue developing their skills. Others see "being forced" to learn new tools and approaches as an absolute negative. Evaluate the Return on Investment of various options, with specific consideration to long term re-use of the tools and knowledge in other areas. We also explicitly highlight the often-hidden future cost of the simplistic versus the upfront cost of the sophisticated. Ensure expectations are accurate about the path they choose. Some closing thoughts: We recommend avoiding unnecessary complexity. For example, in our scenario above, consulting an engineer, electrician & plumber, or welding a metal rack that bolts to the floor and ceiling would increase the cost for minimal benefit. The art is in differentiating between necessary and unnecessary. Simple is a magic term for sales & marketing departments. It is often used to accelerate and increase sales. If you were selling TV mounts, you might be tempted to minimize the "tools required" section of your manual so you do not scare away some potential customers. After all, when that TV falls on the customer's floor, you are not doing the repairs. © 2025 FH Black Inc. All rights reserved. Content may not be reproduced, excerpted, distributed, or transmitted without prior written consent.
When does focusing on simple software solutions result in catastrophe? When simple becomes the objective. Instead, finance and budget professionals should focus on what they want to achieve while avoiding unnecessary complexity. Learn how to evaluate what is and is not necessary for real success.
READ MORE
City of Greensboro Budget Book Automation Project

City of Greensboro Budget Book Automation Project

  • Jamie Black
  • Success Stories
  • minute(s)With a population of nearly 300,000 and growing, the City of Greensboro is the third-most populous in North Carolina. The City's 2020-21 adopted budget of $602 million spans 169 pages and was awarded the GFOA Distinguished Budget Presentation Award. Long-time Questica Budget users, the City is extremely happy with their processes for preparing the budget. The Budget Book however was another story. Like many finance departments, the City used Microsoft Excel, Word, and Publisher to prepare the book. The process was time-consuming, repetitive, resource-heavy, and disjointed; it was time to make a change. The team at Greensboro had heard about F.H. Black & Company Incorporated at a Questica conference and reached out for help to improve their budget book. Once the project was complete, we gave the City a little time to bask in their achievement before interviewing them about their journey. Here are the highlights of that interview with the City's Budget Database Specialist, Leah Price. The Old Way "We used a combination of Microsoft Excel, Word, and Publisher, and it was very time consuming for all staff members. The Budget Analysts had to manually enter all of their departments’ numbers line by line twice: once for the Manager Recommended version and again for the Final Adopted version. The Budget Database Specialist also had to make sure all of the formatting was correct in Publisher, and finally work with our internal print shop to make sure every page had the perfect amount of space between the text and the hole punches. When we heard there was a software that we could use to import the numbers from Questica directly into the budget document, we jumped on it." The Project "We sent our FHB consultants a copy of our former budget document and a copy of our budget data from Questica. The consultants built a template for us that was similar to the old format, and then worked closely with our staff to make sure that the budget data was going to the right places in the document. We have over 25 operating funds and many tricky aspects to our budget rules overall, so assigning the budget numbers and FTEs where they needed to go was the biggest struggle. However, it all came together in the end." The Benefits "The process is more streamlined and controlled. It probably saves the analysts a couple of weeks’ worth of time because they no longer have to do any manual data entry." "The budget analysts are an important resource to our departments, and their new found availability during the budget development process allows them to help out more with current year concerns." The Relationship "Our (FHB) consultants have always helped us meet our deadlines and make sure to work us into their schedule if we have last minute issues." "I have mainly worked with Joy, and I am so grateful to her for all of her help and expertise! I really appreciated that she wanted to make sure that I was learning how to do (almost) everything we needed her help with. It was my first year being responsible for the budget book and I had very little knowledge of CaseWare. I truly could not have done it without her." Considering a reporting automation project? Schedule a meeting with one of our experts to explore your options. © 2025 FH Black Inc. All rights reserved. Content may not be reproduced, excerpted, distributed, or transmitted without prior written consent.
The City of Greensboro implemented an automated budget book solution that pulled data directly from their Questica Budget software resulting in a better book in less time.
READ MORE