Connector Details

Name	Value
Platform	Sage 300 CRE
Auth Type	On-Premise
Direction	Bidirectional
Tap Metrics	Usage:
Target Metrics	Usage:

Overview

Sage 300 CRE (Construction and Real Estate), formerly Timberline, is on-premise accounting software for construction and property management. It is a distinct product from Sage 300. The hotglue Sage 300 CRE connector is an installed Windows program (.exe) that runs on the same machine as Sage 300 CRE. While it is running, you can read and write data the same way you would with a cloud connector.

Read can sync any table exposed by the Sage 300 CRE ODBC database. Common objects also have friendly stream names (for example vendor, job, bill).
Write supports creating (and in some cases updating) vendors, jobs, cost codes, categories, journal entries, bills, and commitments.

Tenant setup guide

Use the guide below to configure the Sage 300 CRE connector.

Initial credential configuration

Before installing the connector locally, gather the following:

Username and password: Sage 300 CRE credentials for the company. Empty values are valid for open or sample companies that do not require a login. For production companies, create a dedicated integration user rather than using an active interactive login.
Company path: The full path to the Sage 300 CRE company data folder. Example:

C:\\ProgramData\\Sage\\Timberline Office\\Data\\Construction Sample Data

tsObject.exe path: Path to Timberline tsObject.exe, used for writing transactional and job-cost objects. The default install location is:

C:\\Program Files (x86)\\Timberline Office\\Shared\\tsObject.exe

Once you have these credentials, provide them to support. In return, you will get the connector file, which is an exe Windows program that you will run, and a connector password.

Sample config

Tenant config is stored in hotglue and pulled down by the connector on each cycle. A typical config looks like:

{
  "company_path": "C:\\ProgramData\\Sage\\Timberline Office\\Data\\Construction Sample Data",
  "username": "",
  "password": "",
  "ts_object_exe": "C:\\Program Files (x86)\\Timberline Office\\Shared\\tsObject.exe",
  "read_frequency": 60,
  "tables": {
    "vendor": {
      "sync": true,
      "replication_key": ["VDSTMP", "VTSTMP"],
      "columns": ["VENDOR", "VNAME", "VDSTMP", "VTSTMP"]
    },
    "job": {
      "sync": true,
      "replication_key": ["JDSTAMP", "JTSTAMP"]
    }
  }
}

Field	Required	Description
`company_path`	Yes	Full path to the Sage 300 CRE company data folder.
`username`	No	Sage username. Leave blank for open/sample companies.
`password`	No	Sage password. Leave blank for open/sample companies.
`ts_object_exe`	For most writes	Path to `tsObject.exe`. Defaults to the standard Timberline Shared folder.
`read_frequency`	No	Seconds between read cycles. Defaults to `30`.
`tables`	For read	Map of stream / table names to sync settings. Friendly names (for example `vendor`) or raw Sage ODBC table names are both valid.

Table options

Each key under tables is either a friendly stream name (see Read) or a raw Sage ODBC table name.

Field	Required	Description
`sync`	Yes	Set to `true` to include the table in read syncs.
`replication_key`	No	Column(s) used for incremental reads. Pass a string for a single column, or an array of columns (for example `["VDSTMP", "VTSTMP"]`).
`columns`	Recommended	Explicit list of fields to sync. Sage tables often have 100+ columns; omitting this can make reads very slow. If you set a `replication_key`, include those columns here. Use Sage dictionary field names (for example `VENDOR`, `VNAME`).

Run the connector

Now you have all you need to run the connector.

Download the Connector launcher file.

The Sage 300 CRE connector is packaged as an .exe file. Read and write run in the same process.

Run the launcher .exe file as administrator. This registers the connector as a service and starts setup.
The connector will open a pop-up requesting your connector password. Enter your connector password and click OK.

That’s it. The connector is now running and ready to sync your Sage 300 CRE data. Config and logs live under C:\Program Files\hotglue by default.

Supported Objects

Write

The Sage 300 CRE connector supports writing the objects below. Writes are dispatched by the payload filename (for example vendor.json or bill.json). Objects are processed in dependency order: vendors and job-cost setup first, then journal entries, commitments, and bills.

Object	Payload file	Create	Update
Vendors	`vendor.json`	Yes	Yes
Jobs	`job.json`	Yes	—
Cost Codes	`cost_code.json`	Yes	—
Categories	`category.json`	Yes	—
Journal Entries	`journal_entry.json`	Yes	—
Bills (AP invoices)	`bill.json`	Yes	—
Commitments	`commitment.json`	Yes (including change orders)	Yes

In addition to the fields listed below, all objects support the optional externalId field. This is used to associate the created record in Sage with your own id. This field is not mapped to Sage 300 CRE, and only persists within hotglue.

When writing data to Sage 300 CRE, ensure that the .json files are written to the etl-output folder in your jobs. Otherwise the connector will not process them. The filename prefix must match the stream name exactly (for example vendor.json, not vendors.json).

Vendors

Payload file: vendor.json Vendors can be created or updated. Field names use Sage dictionary names.

Include VRWID to update a specific existing vendor by row id
Otherwise, if VENDOR already exists it is updated; if not, a new vendor is created

Field	Required	Description
`VENDOR`	Yes (for create / update by vendor id)	Vendor ID. Max 10 characters.
`VNAME`	Recommended	Vendor name. Max 30 characters.
`VRWID`	For update by row id	Existing Sage row id
`VADDR1`	No	Address line 1
`VADDR2`	No	Address line 2
`VCITY`	No	City
`VSTATE`	No	State
`VZIP`	No	ZIP / postal code
`VCCODE`	No	Country code
`VPHONE`	No	Telephone
`VFAX`	No	Fax
`VCNAME1`	No	Contact 1 name
`VCTELE1`	No	Contact 1 telephone
`VCEML1`	No	Contact 1 email
`VTYPE`	No	Vendor type
`VGLEXP`	No	Default expense account

Additional vendor fields are available — see the AP vendor field list.

Sample payload

[
  {
    "externalId": "vendor-2000",
    "VENDOR": "2000",
    "VNAME": "Vendor 2000",
    "VADDR1": "34092 Euclid Ave.",
    "VADDR2": "",
    "VCITY": "Cleveland",
    "VSTATE": "OH",
    "VZIP": "45800",
    "VCCODE": "US",
    "VPHONE": "(857) 555-0744",
    "VFAX": "(857) 555-9999",
    "VCNAME1": "John Doe",
    "VCTELE1": "(857) 555-8888",
    "VCEML1": "john.doe@example.com"
  }
]

Jobs

Payload file: job.json

Field	Required	Description
`id`	Yes	Job ID. Must match the company’s job format (for example `26-010`).
`description`	Yes	Job description.
`address.street`	No	Job street address
`address.city`	No	City
`address.state`	No	State
`address.zip`	No	ZIP
`customer.name`	No	Customer name on the job
`customer.address.*`	No	Customer address fields
`size.quantity`	No	Job size
`size.unit`	No	Size unit (for example `sqft`)

Sample payload

[
  {
    "externalId": "job-010",
    "id": "26-010",
    "description": "University Apartments",
    "address": {
      "street": "335 Spicer St.",
      "city": "Akron",
      "state": "OH",
      "zip": "45904"
    },
    "customer": {
      "name": "MidWest RE",
      "address": {
        "street": "34092 Euclid Ave.",
        "city": "Cleveland",
        "state": "OH",
        "zip": "45800"
      }
    },
    "size": {
      "quantity": 150000,
      "unit": "sqft"
    }
  }
]

Cost Codes

Payload file: cost_code.json Cost codes belong to a job. The job must already exist, or be created in the same write job first. Set extraId to attach the cost code to a job extra.

Field	Required	Description
`jobId`	Yes	Parent job ID
`costCode`	Yes	Cost code. Must match the company’s cost code format.
`date`	Yes	Date. Accepts ISO `YYYY-MM-DD` or `MM/DD/YYYY`.
`description`	No	Cost code description
`extraId`	No	Parent extra ID
`productionUnits.quantity`	No	Production units
`productionUnits.unit`	No	Production unit of measure

Sample payload

[
  {
    "externalId": "cost_code-001",
    "jobId": "26-010",
    "extraId": null,
    "costCode": "3-104",
    "description": "Concrete Forms",
    "date": "2026-09-28",
    "productionUnits": {
      "quantity": 5,
      "unit": "ea"
    }
  }
]

Journal Entries

Payload file: journal_entry.json Each entry must balance (total debits = total credits). Every line needs exactly one non-zero debit or credit.

Field	Required	Description
`id`	Yes	Journal reference. Max 10 characters. Shared across all lines in the entry.
`date`	Yes	Accounting date. Accepts ISO `YYYY-MM-DD` or `MM/DD/YYYY`. Must fall in an open period.
`journal`	No	Journal number (max 2 digits)
`description`	No	Entry description. Max 30 characters. Line-level values override this.
`reference2`	No	Secondary reference. Max 10 characters. Line-level values override this.
`basis`	Conditional	`"accrual"`, `"cash"`, or `null`. Required only when the company accounting method is Both.
`lines`	Yes	Array of journal lines
`lines[].account`	Yes	GL account
`lines[].debit`	One of the two	Debit amount
`lines[].credit`	One of the two	Credit amount
`lines[].description`	No	Line description override
`lines[].reference2`	No	Line reference override
`lines[].basis`	No	Line basis override

Journal entries written through this stream do not update Job Cost. Use bills or other job-cost objects when the entry should hit a job, cost code, or category.

Sample payload

[
  {
    "externalId": "je-1003",
    "id": "JE1003",
    "date": "2022-07-28",
    "journal": 21,
    "description": "Insurance allocation",
    "reference2": "ref2",
    "basis": null,
    "lines": [
      {
        "account": "6200",
        "debit": 400.00,
        "credit": 0
      },
      {
        "account": "6210",
        "debit": 350.00,
        "credit": 0
      },
      {
        "account": "6220",
        "debit": 250.00,
        "credit": 0,
        "reference2": "lineref2"
      },
      {
        "account": "1400",
        "debit": 0,
        "credit": 1000.00,
        "description": "Prepaid insurance"
      }
    ]
  }
]

Bills

Payload file: bill.json

Invoice header

Field	Required	Description
`Vendor`	Yes	Vendor ID. Limited to 10 characters.
`Invoice`	Yes	Invoice number. Limited to 15 characters.
`Amount`	Yes	Invoice total.
`Description`	No	Invoice description. Limited to 30 characters.
`Tax`	No	Tax amount.
`DiscountOffered`	No	Discount amount.
`MiscDeduction`	No	Misc deduction.
`InvoiceDate`	No	Invoice date. Accepts `MM/DD/YYYY` or ISO `YYYY-MM-DD`.
`DateReceived`	No	Date received.
`DiscountDate`	No	Discount date.
`PaymentDate`	No	Payment date.
`AccountingDate`	No	Accounting date.
`InvoiceCode1`	No	Invoice code 1.
`InvoiceCode2`	No	Invoice code 2.
`SmryPayeeName`	No	Summary payee name. Limited to 30 characters.
`SmryPayeeAddress1`	No	Payee address line 1. Limited to 33 characters.
`SmryPayeeAddress2`	No	Payee address line 2. Limited to 33 characters.
`SmryPayeeCity`	No	Payee city. Limited to 30 characters.
`SmryPayeeState`	No	Payee state. Limited to 4 characters.
`SmryPayeeZIP`	No	Payee ZIP. Limited to 10 characters.
`distributions`	Yes	Array of distribution lines. At least one is required.

Distribution lines

Field	Required	Description
`Amount`	Recommended	Distribution amount.
`ExpenseAccount`	Recommended	Expense account. Limited to 14 characters.
`APAccount`	No	Accounts payable account. Limited to 14 characters.
`Job`	No	Job ID
`Extra`	No	Extra
`CostCode`	No	Cost code
`Category`	No	Category
`Commitment`	No	Commitment number
`CommitmentLineItem`	No	Commitment line item
`Units`	No	Units
`UnitCost`	No	Unit cost
`Retainage`	No	Retainage
`1099Exempt`	No	1099 exempt flag
`DistCode`	No	Distribution code. Limited to 10 characters.
`Description`	No	Line description. Limited to 30 characters.
`Authorization`	No	Authorization. Limited to 10 characters.
`JointPayee`	No	Joint payee. Limited to 30 characters.
`Draw`	No	Draw
`TaxGroup`	No	Tax group
`Equipment`	No	Equipment
`EQCostCode`	No	Equipment cost code
`PMProperty`	No	Property. Limited to 10 characters.
`PMUnit`	No	Unit. Limited to 10 characters.
`PMLease`	No	Lease. Limited to 15 characters.
`PMLeaseRevisionNum`	No	Lease revision number.
`PMTenant`	No	Tenant. Limited to 10 characters.
`PMChargeType`	No	Charge type. Limited to 10 characters.
`PMChargeDate`	No	Charge date.
`PMItemID`	No	Item ID. Limited to 20 characters.
`PMChargebackDescription`	No	Chargeback description. Limited to 30 characters.
`PMMarkupPercent`	No	Markup percent.
`PMMarkupAmount`	No	Markup amount.
`PMMarkupChargeType`	No	Markup charge type. Limited to 10 characters.
`DefaultPaymentType`	No	Default payment type.

Sample payload

[
  {
    "externalId": "bill-2003",
    "Vendor": "2000",
    "Invoice": "HG-TEST-2003",
    "Description": "Hotglue import test",
    "Amount": 500.0,
    "InvoiceDate": "07/28/2026",
    "DateReceived": "07/28/2026",
    "AccountingDate": "07/28/2026",
    "distributions": [
      {
        "Job": "26-010",
        "CostCode": "3-104",
        "Category": "L",
        "ExpenseAccount": "10-5100",
        "Amount": 500.00,
        "1099Exempt": "t",
        "DistCode": "parts"
      }
    ]
  }
]

Commitments

Payload file: commitment.json Commitments support create, change orders, and updates to existing commitments.

Create a commitment

Use type: "subcontract" for a new commitment.

Field	Required	Description
`number`	Yes	Commitment number
`type`	Yes	Commitment type. Use `subcontract`.
`description`	Yes	Commitment description
`date`	Yes	Commitment date. Accepts ISO `YYYY-MM-DD` or `MM/DD/YYYY`.
`vendor.id`	Yes	Vendor ID
`project.number`	Yes	Job / project number
`status`	No	Status. Use `executed` for an executed commitment.
`retainage_percent`	No	Retainage percent
`items`	Yes	Commitment line items. At least one is required.
`items[].number`	Yes	Line item number
`items[].description`	Yes	Line description
`items[].cost_code`	Yes	Cost code
`items[].category`	Yes	Category
`items[].amount`	Yes	Line amount
`items[].project.number`	No	Overrides the header project for this line

Sample payload (new commitment)

[
  {
    "externalId": "commitment-2000",
    "number": "CO-2000",
    "type": "subcontract",
    "description": "Interior Painting",
    "status": "executed",
    "date": "2026-09-15",
    "retainage_percent": 10.0,
    "project": {
      "number": "26-010",
      "name": "University Apartments"
    },
    "vendor": {
      "id": "2000",
      "name": "Vendor 2000"
    },
    "items": [
      {
        "number": 1,
        "description": "Mobilization and prep",
        "cost_code": "3-104",
        "category": "L",
        "amount": 8500.00
      },
      {
        "number": 2,
        "description": "Interior finish painting",
        "cost_code": "3-104",
        "category": "L",
        "amount": 40000.00
      }
    ],
    "total": 48500.00
  }
]

Change orders

Send type: "change_order" against an existing commitment.

Field	Required	Description
`number`	Yes	Change order number
`type`	Yes	Must be `change_order`
`description`	Yes	Change order description
`commitment.number`	Yes	Existing commitment number
`date`	No	Change order date
`status`	No	`not_issued`, `pending`, `approved`, or `denied`
`items`	Yes	Change order lines
`items[].commitment_item` / `items[].number`	Yes	Commitment line item number
`items[].amount`	Yes	Amount
`items[].description`	No	Line description
`items[].units`	No	Units

Sample payload (change order)

[
  {
    "number": "001",
    "type": "change_order",
    "description": "Added scope",
    "status": "approved",
    "date": "2022-05-20",
    "commitment": {
      "number": "HG0001",
      "description": "Job Signage"
    },
    "items": [
      {
        "commitment_item": 1,
        "description": "Additional painting",
        "amount": 750.00
      }
    ],
    "total": 750.00
  }
]

Update an existing commitment

To update an existing commitment, send the lookup key plus the fields to change:

SRWID to update by Sage row id, or
SUB to update by commitment number

Field	Required	Description
`SRWID`	For update by row id	Existing Sage row id
`SUB`	For update by commitment number	Commitment number
(other fields)	Yes (at least one)	Fields to update (for example `SDESC` for description)

Sample payload (update)

[
  {
    "externalId": "commitment-2307",
    "SRWID": "eaa28b63-ee3f-e711-8bef-0019b9211094",
    "SDESC": "Updated by row id"
  },
  {
    "externalId": "commitment-2308",
    "SUB": "2308",
    "SDESC": "Updated by commitment number"
  }
]

Read

Read syncs any table you enable under tables. You are not limited to a fixed catalog — the connector can query any table exposed by the Sage 300 CRE ODBC database. Configure reads with either:

Friendly stream names (recommended for common objects)
Raw Sage ODBC table names when you need something outside the aliases below

Field names in results (and in columns / replication_key) use Sage dictionary names (for example VENDOR, VNAME, VDSTMP).

Common stream aliases

Stream	Suggested `replication_key`	Field reference
`account`	`["ADSTMP", "ATSTMP"]`	GL accounts
`vendor`	`["VDSTMP", "VTSTMP"]`	AP vendors
`job`	`["JDSTAMP", "JTSTAMP"]`	JC jobs
`cost_code`	`["PDSTAMP", "PTSTAMP"]`	JC cost codes
`standard_cost_code`	`["SPDSTMP", "SPTSTMP"]`	JC standard cost codes
`category`	`["CDSTAMP", "CTSTAMP"]`	JC categories
`standard_category`	`["SCDSTMP", "SCTSTMP"]`	JC standard categories
`journal_entry`	`["TDSTMP", "TTSTMP"]`	GL journal entries
`ar_transaction`	`["TDSTAMP", "TTSTAMP"]`	AR transactions
`ap_transaction`	`["TDSTAMP", "TTSTAMP"]`	AP transactions

Use the field-reference PDFs to pick columns and understand stamp / id fields. To sync any other table, use its Sage ODBC table name as the tables key — contact support if you need help identifying the right fields.

Example table config

{
  "tables": {
    "vendor": {
      "sync": true,
      "replication_key": ["VDSTMP", "VTSTMP"],
      "columns": ["VENDOR", "VNAME", "VADDR1", "VCITY", "VSTATE", "VZIP", "VDSTMP", "VTSTMP", "VRWID"]
    },
    "job": {
      "sync": true,
      "replication_key": ["JDSTAMP", "JTSTAMP"]
    },
    "ap_transaction": {
      "sync": true,
      "replication_key": ["TDSTAMP", "TTSTAMP"]
    }
  }
}

If you omit columns, reads can be very slow on Sage tables with a large number of fields. Prefer listing only the fields you need.

Getting Started

Key Concepts

Managed authentication

Transformation

Custom Connectors

Composite MCP

Unified Schema

Environment Settings

CLI

Connectors

Sage 300 CRE

Connector Details

Overview

Tenant setup guide

Initial credential configuration

Sample config

Table options

Run the connector

Supported Objects

Write

Vendors

Jobs

Cost Codes

Categories

Journal Entries

Bills

Invoice header

Distribution lines

Commitments

Create a commitment

Change orders

Update an existing commitment

Read

Common stream aliases

​Connector Details

​Overview

​Tenant setup guide

​Initial credential configuration

​Sample config

​Table options

​Run the connector

​Supported Objects

​Write

​Vendors

​Jobs

​Cost Codes

​Categories

​Journal Entries

​Bills

​Invoice header

​Distribution lines

​Commitments

​Create a commitment

​Change orders

​Update an existing commitment

​Read

​Common stream aliases

Connector Details

Overview

Tenant setup guide

Initial credential configuration

Sample config

Table options

Run the connector

Supported Objects

Write

Vendors

Jobs

Cost Codes

Categories

Journal Entries

Bills

Invoice header

Distribution lines

Commitments

Create a commitment

Change orders

Update an existing commitment

Read

Common stream aliases