Westport, Connecticut waterfront
Case Study

Bedrock Communities

Custom Reporting, Account Trees & Managed Yardi Support

How BC Solutions helped a manufactured housing operator strengthen reporting, security, payment workflows, and weekly Yardi support across communities in Florida and Georgia

At A Glance

Client: Bedrock Communities
Project: Custom reporting, account trees & managed support
Industry: Manufactured housing
Timeline: October 2025 – Present
Location: Westport, CT
BC Solutions Lead: Joe Shamburg
Portfolio: Communities across Florida and Georgia
Outcome: Reporting and operational workflows stabilized
All Case Studies

What has impressed us most is the breadth of their Yardi knowledge and their ability to handle our needs with a small, responsive team.

Samantha Anderes, Chief Financial Officer, Bedrock Communities

About Bedrock Communities

Bedrock Communities is a manufactured housing operator headquartered in Westport, Connecticut, with communities across Florida and Georgia. The business depends on clear property-level reporting, disciplined payment workflows, and practical system controls that support site teams as well as finance leadership.

Manufactured housing operations create a different kind of Yardi demand than a conventional apartment portfolio. Lot waitlists, lot and home status tracking, non-tenant payments, check processing, deposit accounting, and community-specific reporting all need to work cleanly if operators are going to trust the system day to day.

For Bedrock, this engagement was about turning Yardi Voyager into a more reliable operating system for both financial oversight and community-level execution.

The Challenge

Bedrock needed support across a wide range of Yardi issues without losing momentum from week to week. The team needed better financial reporting through custom account trees, cleaner user and role permissions, resolution of AR and prepaid tie-out questions, help with payment-processing and CheckScan problems, and practical guidance on manufactured-housing-specific workflows such as lot statuses, waitlists, property builds, and move-out timing.

  • Build and refine financial account trees for MOR, Cash Flow MOR, Income Statement Summary, NOI Detail, and NOI Summary reporting
  • Investigate AR, prepaid, intercompany, and budget presentation issues affecting leadership visibility and tie-out confidence
  • Review and update user security, role permissions, RentCafe access, and document-related permissions across live environments
  • Troubleshoot CheckScan, payment processing, 1099/FinJournal, scheduler, and property build questions as they surfaced
  • Support manufactured-housing workflows around lot waitlists, lot occupancy, move-out timing, non-tenant payments, and community operations

This was not a single deliverable project. It was a structured managed-support engagement where reporting, workflow cleanup, and operational problem-solving all had to move together.

The BC Solutions Approach

Beginning in October 2025, with Joe Shamburg serving as the lead consultant, BC Solutions supported Bedrock through a steady cadence of weekly calls, targeted working sessions, and follow-up execution inside the client’s Yardi environment. The goal was to keep open items from piling up while also improving the reporting structure and permissions framework that Bedrock’s teams relied on every day.

Phase 1

Kickoff, weekly cadence, and issue prioritization

Held kickoff and recurring weekly calls with Samantha and the Bedrock team to review open items, priorities, and next steps
Created a structured support rhythm so financial, reporting, and operational questions could be handled without long delays
Used early working sessions to identify where Bedrock needed reporting changes versus security, payment, or workflow corrections
Kept issue tracking visible enough that small operational blockers did not become larger process problems
Phase 2

Financial reporting and account tree design

Built and refined MOR, CFMOR, ISSUM, NOIDETAIL, and NOISUM account trees for both consolidated and property-level reporting needs
Reviewed cash flow, income statement, and budget presentation issues so Bedrock leadership could trust the reporting outputs coming from Voyager
Troubleshot AR and prepaid tie-out discrepancies and identified where historical support documentation limited further tracing
Adjusted account tree signs, missing accounts, and summary structure so reporting could better match Bedrock’s review process
Phase 3

Security, payment workflow, and system administration support

Performed user security and role reviews, including read-only, A/P, PMS, marketing, and document-related access questions
Resolved or guided issues tied to CheckScan, payment methods, returned payments, non-tenant payments, and payment-processing workflows
Supported RentCafe administration, scheduler events, report packets, and related operational system settings
Helped Bedrock navigate 1099, FinJournal, interface, and Conservice configuration questions as they surfaced
Phase 4

Manufactured housing workflow refinement

Worked through lot waitlists, lot occupancy, and home payment scenarios, along with lot ready dates and move-in/move-out best practices specific to Bedrock’s communities
Supported property build questions, import issues, and community-level setup details as new needs emerged
Reviewed operational SOPs and client-side workflows so the system setup reflected how teams actually worked
Stayed available for weekly follow-up as Bedrock continued refining community operations inside Yardi

The Results

Bedrock gained more than isolated fixes. The team ended up with better financial reporting structures, a more dependable weekly support rhythm, stronger security and payment workflow controls, and a consulting partner that could move between manufactured-housing operational questions and Yardi administration details without losing continuity.

5 Account Trees Built

MOR, Cash Flow MOR, ISSUM, NOI Detail, and NOI Summary reporting structures delivered

Weekly Managed Support

A steady cadence of check-ins kept Bedrock’s open items moving instead of stalling

Security + Payments Refined

Role permissions, CheckScan, payment-processing, and admin workflows were cleaned up across the environment

MH Workflow Support

Lot, home, waitlist, property build, and move-related questions were addressed inside the same support engagement

Why It Matters

The Bedrock engagement shows why manufactured housing operators often need a broader kind of Yardi partner. Financial reporting, deposit and payment workflows, security settings, and community-specific operating questions all intersect, and they rarely arrive one at a time.

Manufactured housing operations need system support beyond standard apartment workflows.

Lot waitlists, home-related payment issues, property builds, non-tenant payments, and lot status logic create operational questions that require a support team familiar with how manufactured housing portfolios actually function.

Account trees can become a real management tool when they are built around the way leadership reviews performance.

Bedrock needed both consolidated and property-level reporting views. Custom account tree work gave the team more usable MOR, cash flow, and NOI visibility than a generic structure would have allowed.

Weekly managed support keeps small problems from turning into larger accounting and operations issues.

Because Bedrock had a regular support cadence, the team could address permissions, reporting, payment-processing, and budget questions as they surfaced instead of waiting for issues to compound.

One partner handling both financial and operational Yardi questions reduces friction.

Bedrock benefited from having one consulting team that could move between AR tie-outs, account tree design, CheckScan issues, user roles, and community workflow questions without splitting responsibility across multiple vendors.

Need Yardi support that actually fits manufactured housing operations?

BC Solutions helps manufactured housing operators improve reporting, tighten permissions and payment workflows, and stay ahead of the day-to-day Yardi issues that slow community operations down.