---
title: HomeBuilder Release Notes - 27.5 2026-03-31
description: Discover the latest enhancements and fixes in HomeBuilder Release 27.5.20260331
---

[HomeBuilder Updates & News ](https://blog.suiteengine.com/homebuilder-updates-news)

# [HomeBuilder Release Notes - 27.5 2026-03-31](https://blog.suiteengine.com/homebuilder-updates-news/homebuilder-release-notes-27.5-2026-03-31)

 Written by [Suite Engine Support](https://blog.suiteengine.com/homebuilder-updates-news/author/suite-engine-support) | May 15, 2026 2:46:41 PM

## HomeBuilder Release  27.5

### Released 31st March 2026 · Build 27.5.20260331 

 Before you install, read the ["HomeBuilder Release Notes Testing Advisory"](https://archerp.sharepoint.com/sites/SuiteEngine/Shared%20Documents/Product%20Development%20(General)/HomeBuilder/HomeBuilder/Release%20Notes/HomeBuilder%20Release%20Notes%20Testing%20Advisory.docx)  for how to validate this release in your environment.

 Spotted an issue or have an idea? Email us at [homebuilder@suiteengine.com](mailto:homebuilder@suiteengine.com). 

### What's new for HomeBuilder users

#### Purchase Requests

##### Pull planning lines into a purchase request without retyping them

If you’ve been opening a purchase request and rekeying lines that already exist in planning, you can now bring them across in one step. The new **Populate from Planning Lines** action appears on the **Purchase Request Card** while the request is still Open and you haven’t yet created a Purchase Order or Credit Memo against it.

To use it:

1. Open the **Purchase Request Card** for the request you’re working on.
2. Run the **Populate from Planning Lines** action.
3. Set your selection criteria and confirm — the matching planning lines drop straight into the request.

##### Less typing in the Planning Line selection dialog on purchase documents

When you run **Populate from Planning Lines** from a purchase document, the dialog that gathers your selection criteria does more of the work for you.

The new **Vendor No.** field arrives pre-filled from the vendor on the purchase document, so you start scoped to the right vendor instead of typing it in.

When you change **Vendor No.** or **Phase Code**, the **Vendor Contract No.** updates itself — it picks up the matching contract if exactly one exists for that Vendor No. / Phase Code pair, and clears so you can choose if there isn’t a single match. That means fewer manual lookups and less risk of pulling lines against the wrong contract.

#### Other enhancements

##### Set pricing and upgrade context once, on the template

Two new fields on the **Construction Item Template Card** let you capture the pricing context for an item up front:

- **Price Group Code**
- **Upgrade Level**

Fill these in on the template and the construction items you create from it start out with the right price group and upgrade level — no after-the-fact corrections on each item.

##### Push an item to lots without leaving the card

Previously, if you wanted to push an item to lots, you had to back out to the **Construction Items** list to do it. The **Push to Lots** action now also sits on the **Construction Item Card**, so you can do it on the item you’re already looking at.

##### “Job Cost Ledger Entries” now reads as “Lot Ledger Entries”

The custom subledger you use to trace lot-level posting now goes by **Lot Ledger Entries**. The data and behavior haven’t changed — the name simply matches how the rest of the system (and most of your team) already talks about lots.

#### Corrections

##### Refund installments show the correct sign on Lot Installments

If you’ve been reconciling refund installments and the numbers haven’t been adding up, this one’s for you. The **Posted Amount** on the **Lot Installments** page now reflects the sign of the amount that actually posted to the G/L for refund installments, so refunds read the way you’d expect.

##### Cost Detail descriptions stay in sync on Lot Budget Lines

When you assign a **Cost Detail Code** to a Lot Budget Line, the **Cost Detail Description** used for Cost Detail lookups now copies consistently from the **Cost Detail Name**. You’ll see the same description in the lookup as on the source record — no more mismatched names when you go back to trace a cost.

## HomeBuilder Release 

### Released: March 2026

[View full post](https://blog.suiteengine.com/homebuilder-updates-news/homebuilder-release-notes-27.5-2026-03-31)

```json
{
  "@context" : "http://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Suite Engine Support"
  },
  "dateModified" : "2026-05-15T14:46:41.499Z",
  "datePublished" : "2026-05-15T14:46:41Z",
  "headline" : "HomeBuilder Release Notes - 27.5 2026-03-31",
  "image" : {
    "@type" : "ImageObject",
    "height" : 465,
    "url" : "https://engage.suiteengine.com/hubfs/HomeBuilder/HMB%20RELEASE%20NOTES.jpg",
    "width" : 850
  },
  "mainEntityOfPage" : "https://blog.suiteengine.com/homebuilder-updates-news/homebuilder-release-notes-27.5-2026-03-31",
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "height" : 60,
      "url" : "/hs/hsstatic/content_shared_assets/static-1.4092/img/default-amp-logo.png",
      "width" : 60
    },
    "name" : "HomeBuilder Updates & News"
  }
}
```