In Sage 100, these are known as Chart of Accounts.

For Sage 100 users, you must link RedTeam Flex Control Accounts to your Chart of Accounts in Sage. This is used to force account coding for transactions sent by RedTeam Flex to Sage. RedTeam Flex company divisions can be connected to specific Sage 100 department accounts for direct costs.

Link: Link the RedTeam Flex Control Accounts to your Sage 100 General Ledger Accounts.

Part 1: Log into RedTeam Flex > Apps menu > click hh2-Sage100 App card > click to expand Control Accounts > click the Edit (pencil) icon for each Control Account > select the Sage GL Account from the dropdown > Save.

Part 2: Configuration Menu > Company Divisions > Click the tools icon to the right of a Division > Click Edit > Scroll down to Sage 100 Revenue and COGS Accounts > select the Sage GL Account from the dropdown > Save

Records shown in red have not been linked to a record in Sage.

The Company Division accounts are critical for their direct cost accounting. Multiple divisions can be connected to an identical set of accounts, or to department entries.

Set up in Sage:

Contact Sage for instructions.

In Sage 100, these are known as Subcontracts or Purchase Orders.

RedTeam Flex supports sending Commitments to Sage (including insertion of AP Vendor, Job, Extra, Job Category, Job Cost Codes, as required) once they are executed so long as those Commitment Forms are configured in RedTeam Flex to indicate which type of Commitment they will post as (Subcontract or Purchase Order) in Sage.

RedTeam Flex does NOT support importing of Commitments from Sage to RedTeam Flex. Additionally, if the commitment already exists in Sage, the RedTeam Flex version will not be able to be linked to that existing entry, and subsequent invoices would go to Sage independent of the commitment. We recommend creating the Commitments in RedTeam Flex to avoid duplicate entry of Commitments into both systems.

In order to synchronize Commitments between RedTeam Flex and Sage, you will need to have the Job Cost module as part of your hh2 account.

Transactional Post: When the Vendor Commitment is Executed in RedTeam Flex it will be posted automatically to Sage with the Commitment ID entered when it was created.

Create, Commit and Execute Vendor Commitments in RedTeam Flex

See the Article: Manage Buyout Commitments

When you create Commitments in RedTeam Flex, you will be able to specify your Commitment Number.

In Sage 100 these are known as AP Invoices.

RedTeam Flex will send Vendor Invoices to hh2 and post to Sage when they are Executed in RedTeam Flex. When entered against a linked Commitment, it will post to hh2/Sage against that Commitment. If not entered against a linked Commitment, it will still post to hh2/Sage. RedTeam Flex will send all job cost items (“distributions” in hh2) and amounts and post along with the Project Cost Code and Category.

Transactional Post: When the Vendor Invoice is Executed in RedTeam Flex it will be posted to Sage with the Commitment ID.

Create, Commit and Execute a Vendor Invoice

There is no change to the RedTeam Flex workflow when executing an invoice for a Sage-connected database

For more information, see the RedTeam Flex Article: Manage Vendor Invoices

Retainage Release Invoices: RedTeam Flex uses a vendor invoice document to release retainage for commitments, whereas Sage tracks accrued retainage and releases it directly without needing an invoice. This difference means for a Sage-linked database, RedTeam Flex cannot have a vendor invoice which both releases retainage and bills against a line item at the same time. When it comes time to release retainage, it must be handled uniquely for each system. Retainage release can be tracked in RedTeam Flex by creating an invoice exclusively for retainage release, and that invoice will not be sent to Sage because of Sage’s separate release process. The retainage can be separately released in Sage via normal procedures.