Skip to Main Content

Many institutions view CECL model validation and internal audit as interchangeable, but they answer different questions. Understand how these reviews differ, where they overlap, and how they work together to strengthen CECL governance and oversight.

Every parks and recreation agency wants a strategic plan that guides real decisions instead of an instruction manual that ends up sitting on a shelf. At the 2026 NRPA Annual Conference, BerryDunn and the Johnson County Park & Recreation District (JCPRD) shared how three recent plans were built to do exactly that: the 2024 Legacy Plan, the 2024 Children's Services Strategic Plan, and the 50 Plus Strategic Plan.

Their approach comes down to three ideas: A strong plan is mission-driven, data-led, and designed for action.

Start with mission

A good plan provides the framework for evaluating opportunities, setting priorities, and making decisions. For JCPRD's Children's Services team, that framework starts with the mission:

Our mission is to foster connections and support families through fun and engaging programs that prioritize well-being, character-building, and education to inspire a love of learning and curiosity.

JCPRD's Children's Services supports roughly 3,500 children every school day, 2,500 summer campers, and 66 enrichment and care locations across four school districts. When presented with a new opportunity or challenge, the team asks four questions:

  • Does it support families without impacting existing programs?
  • Does it advance education and child development?
  • Does it build on services we already know how to provide?
  • Does it advance a priority already established in the strategic plan?

Shared questions like these help keep decisions tied to the mission and give staff a consistent way to explain them.

Use data with purpose

Data works best when it answers a specific question. The planning process moves from "we think" to "we know" to "here's what the evidence suggests we should do."

For example, the 50 Plus Strategic Plan uses mapping to identify areas projected to have high concentrations of residents age 50 and older by 2029. These projections are cross-referenced with existing program locations and drive-time accessibility to identify areas where additional assistance or promotional outreach may be needed.

Data like this doesn't replace professional judgment, but it gives that judgment something solid to act on throughout the plan's lifecycle.

Design for action

A plan is only useful if the organization can carry it out. The 2024 Legacy Plan lays the foundation for successfully executing the district's previous individual plans. Let's take a look at two of the core elements from the Legacy Strategic Plan:

  1. Inspiring Play, Culture, and Education
  2. Advancing Organizational Readiness and Access

One of the main initiatives behind "Inspiring Play, Culture, and Education" is to expand outreach opportunities across program areas. The 50 Plus Strategic Plan's data-driven approach to monitoring population growth directly supports this goal. The population data it projects doesn't just inform the plan; it directs it, linking day-to-day decisions to the district's overall strategic priorities.

The second core element, "Advancing Organizational Readiness and Access," focuses on workforce development, volunteer use, succession planning, and expanded partnerships. The Children's Services Strategic Plan puts that readiness into practice with staffing guidelines for growth or service reduction. It recommends no more than 10 specialists assigned to each site, one new specialist for every seven sites added, and assistant manager workloads kept between 20 and 40 sites.

Specific guidance like this lets an organization adjust as programs and needs change.

Putting your strategic plan into practice

Whatever your agency's size, three questions can anchor your next planning effort:

  • Start with mission: What are you trying to accomplish?
  • Use data with purpose: What are you trying to understand, and what does the evidence tell you?
  • Be clear about your goals: What are you going to focus on?

The result is direction for today and a framework for tomorrow.

How we can help

BerryDunn's consultants work with you to improve operations, drive innovation, and identify service improvements based on community need, all from the perspective of our team's combined 100 years of hands-on experience. We provide practical park solutions, recreation expertise, and library consulting. Learn more about our team and services.

Article
Planning for impact: How to build a successful parks and recreation plan

Receiving Rural Health Transformation Program (RHTP) funding is an important milestone. But an approved plan is not necessarily an implementation-ready project. The level of planning needed to secure funding can be very different from the level of detail needed to successfully execute the work. As organizations move from application to implementation, that is the time to pause, validate the plan for execution details, and make sure the right people, resources, and processes are in place.

Here are six questions to consider before moving forward.

1. Is your idea ready to become a project?

While an application establishes what you want to accomplish, when you move to implementation, you must determine exactly how you're going to accomplish it.

That means translating your proposed initiative into a detailed project plan that identifies activities, responsibilities, timelines, milestones, dependencies, and decision-making processes.

Take action

Before launching:

  • Define key activities, milestones, and timelines.
  • Assign an owner to each major component of the project.
  • Identify dependencies that could affect your schedule.
  • Determine who needs to be involved in decisions.
  • Establish a process for escalating issues when they arise.

The goal is to make sure everyone understands what needs to happen next and who is responsible for making it happen.

2. Does your project clearly align with RHTP goals?

As implementation begins, it can be easy to become focused on completing activities, meeting deadlines, and spending funds as planned. But those activities still need to advance the outcomes RHTP is intended to support.

Key initiatives for RHTP funding from the federal level include:

  • Building the rural healthcare workforce: Supporting recruitment, training, and retention strategies to strengthen the pipeline of healthcare professionals serving rural communities.
  • Strengthening rural facilities and access: Supporting partnerships, operational improvements, and care-delivery changes that help rural providers maintain essential services and improve access.
  • Advancing innovative care and payment models: Supporting new approaches to delivery and financing designed to improve quality, strengthen primary care, and support sustainable rural healthcare.
  • Expanding community-based and preventive care: Investing in school-based care, mobile services, and other community strategies that improve prevention, address chronic disease, and expand access to care.
  • Modernizing rural healthcare technology: Expanding remote care and data-driven tools to improve coordination and extend healthcare services to rural communities.

Before implementation begins, confirm that your project still has a clear connection to the goals it is intended to advance at every level of the funding trail.

Take action

Write down the RHTP goal or goals your initiative supports. Then define how you will measure whether the project is actually advancing those goals. Throughout implementation, keep asking, “Is what we're doing still helping us achieve the outcome we set out to accomplish?” If the answer changes, it may be time to revisit the plan.

3. Do you have the people and capacity to do the work?

Funding provides resources, but it doesn't automatically create organizational capacity.

Consider who will be responsible for implementing the initiative and whether those people realistically have the time and expertise to take on the work.

You may have much of the expertise needed internally. Other areas may require project management, outside consulting services, additional technology, interoperability between systems, or other specialized support.

Take action

  • Build a resource plan that identifies:
  • Who will lead the initiative.
  • What responsibilities and tasks will be handled internally.
  • Where there are expertise or capacity gaps.
  • What external support may be needed.
  • When those resources need to be available.

Do this before implementation is underway. Discovering a significant resource gap halfway through the project can put the timeline, funding, and outcomes at risk.

4. Are your vendors and dependencies ready?

Many RHTP initiatives will involve multiple organizations (that may or may not have worked together previously), technologies, systems, and stakeholders. Your project's timeline may depend on all of them.

For example, a technology project may require hardware, networking, integrations, vendor resources, other technology suppliers, and support from internal IT teams. And due to the national outreach of the program, some national resources may already be stretched by other RHTP-funded initiatives. A delay in one area can affect several others.

Take action

Map your project's critical dependencies and ask:

  • What has to happen before each phase of work can begin?
  • Which vendors or outside organizations are involved?
  • Have their availability and timelines been confirmed and have contingencies been considered?
  • What internal resources do they depend on?
  • What happens to the project if one component is delayed?
  • Don't build your timeline around assumptions. Validate the dependencies that matter most.

5. What happens when the RHTP funding ends?

Implementation planning shouldn't stop at getting the project up and running.

Consider what it will take to sustain the initiative once the initial year's funding has been spent. That includes ongoing staffing and operating costs as well as assumptions about reimbursement, utilization, future funding, vendor costs, and other factors that affect long-term viability.

Take action

Develop a post-funding scenario before making major commitments.

Ask:

  • What will this cost to maintain?
  • Which costs continue after the funding period?
  • What assumptions does the business case depend on?
  • What happens if utilization, reimbursement, or another key assumption changes?
  • Are contracts structured with enough flexibility to respond if circumstances change?

A successful launch matters. So does having a realistic plan for what comes afterward.

6. How will you know if the project is getting off track?

Even a strong implementation plan will encounter change.

The goal shouldn't be to anticipate every possible problem. Instead, establish mechanisms for recognizing issues early and addressing them before they threaten the initiative.

Take action

Before launch:

  • Identify your biggest implementation risks.
  • Assign responsibility for monitoring them regularly to catch issues early.
  • Establish regular project checkpoints.
  • Define when and how problems should be escalated.
  • Create a communication structure for internal stakeholders, vendors, funding entities, and other partners.
  • Establish a process for revisiting the plan when circumstances change.

A project plan should guide implementation, not prevent the organization from adapting when new information emerges.

Key takeaways

Moving from funding to implementation requires a shift in thinking and actions. Before launching an RHTP-funded initiative:

Turn the proposal into an executable project plan. Add the details required to manage the actual work.

Keep RHTP outcomes at the center. Connect activities and investments to the goals the project is intended to advance.

Be realistic about capacity. Identify early where internal resources are sufficient and where additional expertise is needed.

Validate dependencies instead of assuming they're ready. Confirm vendor, technology, staffing, and other requirements before establishing your timeline.

Plan for sustainability from the beginning. Understand what happens operationally and financially after the initial funding.

Build in ways to identify and address problems early. Strong governance, communication, and risk management can help keep implementation moving in the right direction.

How BerryDunn can help

Moving a complex initiative from an approved proposal to successful implementation can require expertise and capacity across multiple disciplines.

BerryDunn can help organizations assess implementation readiness, strengthen project and program plans, establish governance and project management structures, identify risks and dependencies, evaluate technology and operational considerations, and plan for long-term sustainability.

Just as importantly, we can help connect those pieces. Large transformation initiatives rarely succeed in silos. Strategy, operations, technology, finance, grants management, and project execution need to work together toward the same outcomes.

Whether you're refining an implementation plan, preparing to launch a funded initiative, or encountering challenges after work has begun, BerryDunn can help you move from funding to action with a practical path forward.

Article
From funding to implementation: Is your Rural Health Transformation project ready to launch?

Independent Verification and Validation (IV&V) plays a critical role in helping public-sector organizations manage risk, strengthen governance, and improve outcomes for complex information technology initiatives. However, determining when IV&V is appropriate and how to procure it effectively can be challenging for procurement managers and project leaders. This article provides practical guidance for agencies developing a request for proposals (RFP), task order, or master agreement to procure IV&V services for large IT projects.

What IV&V is—and how it supports IT project oversight

IV&V is an independent, third-party assessment of a project’s processes, deliverables, and outcomes. Its purpose is to verify that project activities are being executed effectively and will meet business and operational needs. Unlike quality assurance or testing services, IV&V does not perform project work or remediate issues. Instead, it provides objective insight to help decision-makers understand risks, tradeoffs, and areas requiring attention before they impact cost, schedule, scope, or security.

An IV&V provider like BerryDunn can support your project by:

  • Reviewing RFP requirements and requested information to identify potential contract risks and help align the procurement with applicable guidelines and best practices.
  • Assessing key project domains such as governance, communications, schedule, budget, operations and maintenance, integrations, and security.
  • Providing unbiased status reporting to executive leadership.
  • Analyzing project risk and providing actionable recommendations.
  • Evaluating vendor deliverables for completeness, quality, and alignment with contract and requirements.
  • Establishing advisory check-in meetings with project management and key stakeholders.
  • Assessing project management performance against approved schedule, budget, and scope baselines, as well as industry best practices.
  • Reviewing decision-making processes and escalation pathways.
  • Verifying requirements traceability throughout the design, development, testing, and deployment lifecycle.
  • Supporting readiness assessments at major project milestones and go-live events.

When is IV&V appropriate?

IV&V is most commonly applied to large IT project oversight efforts but can also provide value in other complex, high-risk initiatives when appropriate. Projects that may benefit from IV&V often involve:

  • Significant cost or duration
  • Multiple vendors
  • Evolving requirements
  • Heightened public or legislative scrutiny
  • Replacing legacy systems
  • Federal funding
  • Extensive system integrations and data migration

IV&V is a tool to surface risks related to these factors early enough to influence decisions at critical milestones (e.g., procurement, requirements baseline definition, design approval, testing readiness, and deployment). This helps delivery teams achieve the outcomes leadership expects while reducing the likelihood of costly corrective actions.

Beyond supporting compliance, IV&V also strengthens governance by providing independent insight that helps leadership make informed decisions and promotes greater transparency throughout the project lifecycle.

How does IV&V support large IT project oversight?

Many federal agencies and several states require or recommend IV&V as part of oversight efforts for large IT projects involving high-cost, high-risk, mission-critical, or safety-critical initiatives. Examples include:

Federal Agency/State

IV&V Status

Trigger/Scope

NASA

Required1

Mission-critical, safety, complex, or cost

Health and Human Services including Medicaid, CHIP, and eligibility

Required2

Schedule, cost, risk, new, or redesigned

Department of Defense

Required3

IV&V or equivalent for major programs

Department of Homeland Security

Recommended; increasingly institutionalized4

DHS recommends IV&V for major IT investments;

Office of Management and Budget (OMB)

Strongly encourages (government‑wide)5

Recommends independent, risk-based oversight for high-risk projects

General Services Administration (GSA)

Required6

Requires verification and validation for performance and data reporting

Government Accountability Office (GAO)

Advocates / Best practice7

Large, complex, or high-risk

State of Arizona

Required8

$5,000,000 Total Project Cost

State of Georgia

Required9

$1,000,000 Total Project Cost

State of Maryland

Required10

$1,000,000 Total Project Cost

Procuring IV&V services is a governance decision as much as a procurement exercise. By emphasizing independence, an outcome-focused scope, and risk-based flexibility, agencies can structure IV&V engagements that deliver meaningful value. When applied judiciously, IV&V can improve project outcomes by enabling earlier, evidence-based decisions that protect cost, schedule, security, and user adoption. Thoughtful procurement sets the foundation for IV&V to support transparency, accountability, and successful project delivery.

Planning to procure IV&V services? Our IV&V Procurement Toolkit provides a practical framework to help agencies define requirements, evaluate vendor qualifications, and establish an effective procurement approach, including an RFP template. 

BerryDunn can help

With more than 20 years of experience, our team acts as a genuine partner rather than an auditor. We understand the messy realities of real-world IT deployments, allowing us to tailor our approach to your specific organizational needs. We work collaboratively alongside your team, helping you ask the right questions and giving you the peace of mind that your major investment is securely headed in the right direction. Learn more about our services and team.

Requirements for IV&V vary by agency, funding source, and jurisdiction. Organizations should consult applicable statutes, regulations, and procurement policies when determining oversight requirements.

Sources

  1. National Aeronautics and Space Administration (NASA). NASA Software Engineering Requirements (NPR 7150.2).
  2. US Department of Health and Human Services. 45 CFR §95.626, Independent Verification and Validation.
  3. Acquisition.gov. Department of Defense Acquisition Guidance.
  4. US Government Accountability Office. GAO-11-581: Department of Homeland Security IT Acquisition Oversight.
  5. Office of Management and Budget (OMB). Capital Programming Guide and Circular A-11 Oversight Frameworks.
  6. US General Services Administration. GSA Order 2170.1B.
  7. US Government Accountability Office. Federal IT Oversight and High-Risk Program Reports.
  8. State of Arizona. A.R.S. §18-104 and Statewide Policy P1020: Independent Verification and Validation.
  9. State of Georgia. SM-06-001 Independent Verification and Validation Policy.
  10. Maryland State Finance and Procurement Code §3A-301.
Article
Procuring IV&V Services: A Practical Guide

Who this applies to: Executive leadership, accounting professionals, and board members at governmental organizations that follow GASB standards.

Government leaders are making long-term operational decisions today that will shape their financial statements for years to come. While procurement decisions are often driven by service delivery needs, staffing challenges, regulatory requirements, or strategic initiatives, they frequently create accounting and reporting implications that emerge well after a contract is signed. Governments continue to modernize technology, invest in infrastructure and environmental initiatives, navigate fiscal uncertainty, and increase their use of financial services. These procurement trends provide valuable insight into the financial reporting challenges governmental entities are likely to encounter in the next three years.

1. Technology modernization will continue to create accounting complexity 

State and local governments continue to invest heavily in cloud computing, enterprise resource planning systems, cybersecurity solutions, and software modernization initiatives. While these investments can improve efficiency and service delivery, they also create important financial reporting considerations. Governments implementing subscription-based software solutions must evaluate whether arrangements fall within the scope of GASB Statement No. 96, Subscription-Based Information Technology Arrangements (SBITAs).

Under GASB 96, a qualifying arrangement generally results in recognition of an intangible right-to-use subscription asset and a corresponding subscription liability. The standard also established requirements for:

  • Determining the subscription term
  • Measuring the liability
  • Capitalizing eligible implementation costs
  • Providing related note disclosures

Finance teams should be involved early in procurement discussions to identify contracts that may require recognition of subscription assets and liabilities. Procurement documentation should clearly identify:

  • The noncancelable contract period
  • Renewal and termination options
  • Payment terms
  • Implementation activities
  • Date the underlying technology is placed into service

These provisions can directly affect the recognition and measurement of the SBITA amounts reported under GASB 96. Waiting until year-end often results in rushed analyses, data collection challenges, and increased implementation costs. Governments that establish accounting review procedures during the procurement process are generally better positioned to achieve compliance and avoid reporting surprises.

2. Infrastructure investments will require stronger capital asset management

Infrastructure spending continues to be a major focus for many governments, particularly in transportation, utilities, public works, and community development. As capital programs expand, governments face increasing challenges in tracking project costs, managing construction-in-progress balances, documenting funding sources, and maintaining accurate fixed asset records. New projects may also require consideration of grant compliance requirements, debt financing arrangements, and long-term operational commitments.

For many governments, the greatest risk is not the accounting itself but maintaining complete and accurate project documentation throughout the life of the project. Proactive coordination between finance, engineering, facilities, and project management personnel can help ensure that assets are reported appropriately once projects are placed into service. That same coordination will also support implementation of GASB Statement No. 103, which requires the Management’s Discussion and Analysis (MD&A) to address significant capital asset and long-term financing activity within its prescribed structure. Governments will therefore need not only reliable capital asset records, but also sufficient information to explain the underlying reasons for significant changes in capital and financing activity. GASB 103 requires MD&A to include five specified sections and emphasizes that detailed analysis should explain why balances and results changed, rather than merely reporting the amount or percentage of change.

3. Fiscal uncertainty will increase the importance of transparent risk communication

As financial pressures evolve, stakeholders increasingly expect governments to provide transparent information regarding significant risks and vulnerabilities. GASB Statement No. 102, Certain Risk Disclosures, reflects this expectation by requiring governments to evaluate whether concentrations or constraints make them substantially vulnerable to future impacts. For purposes of GASB 102:

  • A concentration is a lack of diversity related to a significant inflow or outflow of resources
  • A constraint is a limitation imposed by an external party or through formal action of the government’s highest level of decision-making authority

A concentration or constraint alone does not automatically require disclosure. Management must also assess whether an associated event has occurred, has begun to occur, or is more likely than not to begin within 12 months after the financial statements are issued, and whether that event could cause a substantial impact. Examples may include significant dependence on a single employer, major grant program, industry sector, or revenue source. Other potential considerations could arise from statutory tax or debt limitations, externally imposed spending restrictions, or workforce concentrations, depending on the government’s specific facts and circumstances. When the disclosure criteria are met, the notes should describe the concentration or constraint, the associated event that could cause a substantial impact, and actions the government has taken before issuance of the financial statements to mitigate the risk.

Governments should not view these disclosures as merely a compliance exercise. Instead, they provide an opportunity to communicate financial risks transparently while demonstrating how management is planning for potential challenges. Establishing a documented annual risk-assessment process involving finance, budgeting, grants management, legal, and operational leadership can help management identify potential GASB 102 matters before the financial statement preparation process begins.

4. Environmental and sustainability investments will expand reporting responsibilities

Governments continue to grow environmental and sustainability-focused initiatives, including renewable energy projects, energy efficiency programs, resiliency investments, and environmental remediation efforts. These projects often involve unique funding arrangements, complex financing structures, and long implementation timelines. As governments pursue these initiatives, finance departments will need to evaluate:

  • How expenditures should be capitalized 
  • Whether grant requirements affect accounting treatment 
  • What disclosures may be necessary to explain the financial impact of these investments 

Many sustainability projects also involve multiple stakeholders, funding sources, and long-term commitments. Maintaining clear documentation throughout the project life cycle can help ensure accurate reporting and support management's ability to communicate the project's financial impact to governing boards and taxpayers. These projects may also intersect with GASB 102 when a government becomes significantly dependent on a particular funding source, supplier, regulatory approval, or other concentration or constraint, and the remaining disclosure criteria are met. In addition, GASB 103 may affect how governments discuss significant capital investments, financing activity, and currently known conditions in MD&A.

5. Growing demand for financial services reflects increased expectations for financial stewardship

Governments have increased their procurement activities related to financial services and insurance. This trend suggests that many governments are investing in treasury management, investment oversight, debt management, pension administration, and financial consulting services to navigate increasingly complex financial environments. As governments leverage specialized advisors and external expertise, expectations for financial transparency and accountability continue to rise. Governing boards, taxpayers, bondholders, and regulatory agencies increasingly expect finance departments to provide meaningful analysis rather than simply reporting historical results.

This trend aligns with broader financial reporting developments, including GASB Statement No. 103, which places greater emphasis on helping financial statement users understand why financial results changed rather than simply presenting what changed. GASB 103 retains MD&A as required supplementary information but limits its content to five defined sections: 

  • An overview of the financial statements
  • A financial summary
  • Detailed analyses
  • Significant capital asset and long-term financing activity
  • Currently known facts, decisions, or conditions

The detailed analyses should explain the underlying causes of significant changes, avoid unnecessary duplication, and focus on relevant information rather than boilerplate discussion.

Governments that strengthen financial planning, forecasting, and communication processes today will likely be better positioned to meet these growing expectations. Finance departments should begin aligning budget narratives, variance analyses, capital planning reports, and debt information with the new MD&A structure so that meaningful explanations are developed throughout the year rather than reconstructed after year-end.

Connecting procurement decisions to financial reporting

Procurement decisions often provide an early indication of tomorrow's financial reporting challenges. Technology modernization, infrastructure development, sustainability investments, and evolving fiscal pressures are transforming how governments operate and, ultimately, how they report their financial position and results. For government finance leaders, the key takeaway is that accounting considerations should not begin after a contract is signed or a project is completed. By involving finance personnel early in strategic initiatives, governments can better anticipate reporting requirements, improve compliance, and provide more meaningful information to stakeholders. As the governmental landscape continues to evolve, organizations that proactively connect operational decision-making with financial reporting requirements will be best positioned to maintain transparency, strengthen accountability, and support informed decision-making.

Key takeaways

  • Involve finance teams early in procurement decisions to identify accounting and reporting implications.
  • Strengthen documentation and coordination for technology, infrastructure, and sustainability investments.
  • Assess fiscal risks and vulnerabilities to identify potential disclosure requirements.
  • Align financial planning and reporting processes with evolving transparency and reporting expectations.

BerryDunn can help

BerryDunn’s governmental accounting team approaches each new engagement with an open mind, assessing client needs objectively to inform clear, powerful, and actionable recommendations. We partner with clients to establish compliance practices, optimize processes, and enhance the overall financial reporting process. We provide an array of customized services to support each client. Our engagements are staffed by principals, senior managers, and managers who take the time to know and understand each client. Learn more about our team and services.

Article
Five procurement trends shaping government financial reporting

Who this applies to: Board members, finance professionals, and the leadership team at nonprofit organizations, housing authorities, municipalities, and other governmental entities.

When many organizations hear the term "related party," they immediately think of family-owned businesses. However, related party transactions can occur in nearly any organization, including housing authorities, nonprofits, municipalities, and other governmental entities. Because these transactions often occur outside of normal market forces and may involve individuals with influence over organizational decisions, they can create financial reporting, compliance, and governance risks if not properly identified and disclosed. Understanding what constitutes a related party and how auditors evaluate these relationships can help organizations strengthen transparency and avoid surprises during the audit process.

What is a related party?

Under GASB Statement No. 62, a related party is defined as a person or organization that can significantly influence the management or operating policies of the transacting parties (e.g., through imposition of will) or has an ownership interest in one of the transacting parties and can significantly influence the other to the extent that one or more of the transacting parties might be prevented from fully pursuing its own separate interests.

Common examples include:

  • Board members
  • Executive directors or senior management
  • Family members of key officials
  • Organizations controlled by board members or management
  • Parent organizations, subsidiaries, or affiliates
  • Joint ventures and partnerships
  • Component units in governmental reporting structures
  • State governments providing loans, advances, or guarantees to a component unit
  • Public authority
  • A state pension plan investing in an entity controlled by:
    • A board member or key executive
    • An affiliated organization
  • A state department and a related public authority sharing employees, payroll processing, information technology, legal services, or accounting staff

A transaction becomes a related party transaction when resources, services, obligations, or economic benefits are exchanged between related parties. Examples may include:

  • Leasing office space from a board member 
  • Purchasing services from a company owned by management
  • Loans made to or received from officers 
  • Shared employees between affiliated organizations 
  • Cost allocations among related entities 
  • Use of facilities or equipment without charge

Not all related party transactions are improper. In fact, many are entirely legitimate and beneficial. The key requirement is transparency and appropriate oversight.

Why auditors focus on related parties

Related party relationships present unique risks because transactions may not occur on arm's-length terms. For example, a housing authority may contract with a maintenance company owned by a commissioner, or a nonprofit may lease office space from a board member. Even when these arrangements are competitively priced, they warrant additional scrutiny because personal interests could influence decision-making.

Auditing standards recognize related party transactions as a potential fraud risk because they may be used to conceal financial difficulties, circumvent procurement requirements, shift costs between entities, misstate revenues or expenses, or enable self-dealing or conflicts of interest. As a result, auditors perform specific procedures designed to identify related parties and evaluate whether transactions have been appropriately accounted for and disclosed.

Related parties in governmental and nonprofit organizations

Governmental and nonprofit organizations often encounter related party considerations that differ from those seen in commercial businesses. Some industry examples of related party considerations are as follows:

  1. Public housing authorities frequently interact with affiliated nonprofit organizations, instrumentality corporations (a public or private entity created to carry out a specific government function, public service, or commercial task), development entities, and project partnerships. Shared staff, common board members, or intercompany transfers may create related party relationships that warrant disclosure. 
  2. Municipalities may have component units, economic development corporations, authorities, or commissions governed by overlapping leadership structures. Transactions among these organizations may require careful consideration.
  3. Many nonprofits operate through supporting organizations, foundations, or affiliated entities. Shared governance and common management can create related party relationships even when the organizations have separate legal structures.

Organizations should be alert for circumstances that may indicate undisclosed related party transactions, including: 

  • Vendors with names similar to board members or employees
  • Significant transactions outside normal business activity
  • Payments to individuals rather than organizations
  • Contracts awarded without documented procurement procedures
  • Unusual loans or advances
  • Shared office space, employees, or equipment
  • Repeated sole-source procurements involving the same parties

These situations do not automatically indicate a problem, but they often warrant further investigation.

Best practices for management and boards

Strong governance is the first line of defense against related party issues. Organizations should consider implementing the following practices:

  1. Maintain annual conflict-of-interest disclosures: Board members and key employees should annually disclose business interests and relationships that could influence decision-making.
  2. Document review and approval procedures: Any transaction involving a related party should be reviewed and approved by independent members of the board or governing body.
  3. Ensure competitive procurement: When possible, obtain multiple quotes or conduct a competitive procurement process, even when working with a related party.
  4. Maintain clear documentation: Organizations should retain documentation supporting pricing, approvals, and the business rationale behind the transaction.
  5. Communicate with auditors early: Informing auditors of potential related party relationships early in the audit process can reduce delays and facilitate efficient audit procedures.
  6. Prioritize transparency: The existence of a related party transaction is not necessarily a concern. The greater risk lies in failing to identify, document, and disclose the relationship appropriately.

Transparent reporting helps stakeholders understand the nature of transactions and evaluate whether resources are being managed in the organization's best interests. It also strengthens public trust, which is especially important for organizations that receive government funding, HUD assistance, federal awards, or charitable contributions.

Governance of related party relationships

Related party relationships are a fact of life for many organizations. Whether involving housing authorities, municipalities, nonprofits, or other entities, these relationships require thoughtful governance and clear disclosure.

Organizations that proactively identify related parties, establish strong conflict-of-interest policies, and maintain thorough documentation will be better positioned for successful audits and stronger stakeholder confidence.

Key takeaways

  • Identify related party relationships and transactions that may create financial reporting, compliance, or governance risks.
  • Recognize circumstances that may indicate undisclosed related party transactions and warrant further review.
  • Strengthen governance through appropriate oversight, documentation, approval procedures, and disclosure.
  • Communicate related party relationships to auditors early to help reduce delays and support an efficient audit process.

BerryDunn can help

BerryDunn’s Nonprofit Practice Group brings a clear understanding of nonprofit funding, in-depth knowledge of complex compliance requirements, and the industry-specific knowledge necessary for accurate, complete financial reporting. That knowledge informs our work—and enhances your performance by addressing your most important operational challenges. Learn more about our services and team.

Article
Related party relationships: Why transparency matters