This article explains how RedTeam Flex works with Sage 100 through hh2: linking control accounts, and sending vendor commitments and vendor invoices to Sage.

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 forces account coding for the transactions RedTeam Flex sends to Sage. RedTeam Flex company divisions can be connected to specific Sage 100 department accounts for direct costs.

Link the Control Accounts to your Sage 100 General Ledger accounts

Step 1: Click Apps, then click the hh2-Sage100 app card.

Step 2: Expand Control Accounts. For each Control Account, click the Edit (pencil) icon, select the Sage GL account, then click Save.

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

Link the direct cost accounts for each company division

Step 1: Click Configuration, then click Company Divisions.

Step 2: Click the tools icon next to a division, then click Edit.

Step 3: Scroll down to Sage 100 Revenue and COGS Accounts, select the Sage GL account for each cost type, then click Save.

The Company Division accounts are critical for direct cost accounting. They make sure invoices for each cost type send to Sage with the correct account. If the GL account has sub-departments, you must select a sub account. Several divisions can use the same accounts, or each can use different department entries.

Set up in Sage: Contact Sage for instructions.

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

RedTeam Flex sends Commitments to Sage (including the AP Vendor, Job and Job Cost Codes, as required) once they are executed, as long as their Commitment Forms are configured in RedTeam Flex with the type they post as in Sage (Subcontract or Purchase Order).

The Sage 100 integration restricts how Subcontracts and Purchase Orders are configured. For Purchase Orders to send as Purchase Orders, they must use Units Delivered as their progress metric. They can use any cost type. If PO commitments won't be sent to Sage, they can use the Amount Billed progress metric in RedTeam Flex, but their Sage Commitment setting should be Do Not Send.

If you need to send commitments to Sage 100 as Material type but also use Amount Billed, send the Commitment to Sage as a Subcontract.

RedTeam Flex does NOT support importing Commitments from Sage. If a commitment already exists in Sage, the RedTeam Flex version can't be linked to it, and later invoices go to Sage independent of the commitment. We recommend creating Commitments in RedTeam Flex to avoid entering them in both systems.

To synchronize Commitments between RedTeam Flex and Sage, you need the Job Cost module in your hh2 account.

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

Create, Commit and Execute Vendor Commitments in RedTeam Flex

See Manage Buyout Commitments.

When you create Commitments in RedTeam Flex, you can specify your Commitment Number.

If a vendor commitment or vendor change fails to post

You can send it again yourself with Retry. Click Apps, open the hh2-Sage100 app card, then click Transactions Log. Fix the cause shown in the Message column, then click Retry on the failed row and Accept the warning. No message appears; click Refresh after a minute or two to see the result.

Check Sage before you retry: Retry doesn't replace a record that already exists in Sage. For the full steps, see Retry a Failed Vendor Commitment, Vendor Change or Vendor Invoice.

In Sage 100, these are known as AP Invoices.

RedTeam Flex sends Vendor Invoices to hh2 and posts them to Sage when they are Executed in RedTeam Flex. When entered against a linked Commitment, the invoice posts to hh2/Sage against that Commitment. If it isn't entered against a linked Commitment, it still posts to hh2/Sage. RedTeam Flex sends all job cost items ("distributions" in hh2) and amounts, along with the Project Cost Code and Category.

Transactional Post: When the Vendor Invoice is Executed in RedTeam Flex, it is 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 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 means that for a Sage-linked database, RedTeam Flex cannot have a vendor invoice that both releases retainage and bills against a line item at the same time. When it's time to release retainage, handle it separately in each system. Track the release in RedTeam Flex with an invoice used only for retainage release. That invoice is not sent to Sage, because of Sage's separate release process. Release the retainage in Sage through your normal procedure.

If a vendor invoice fails to post

You can send it again yourself with Retry, the same way as a commitment: click Apps, open the hh2-Sage100 app card, then click Transactions Log. Fix the cause shown in the Message column, click Retry on the failed invoice and Accept the warning. No message appears; click Refresh after a minute or two. When the new transaction shows Successful Post, the invoice is in Sage.

If the invoice is already in Sage, the retry can fail again. Check Sage first. For the full steps, see Retry a Failed Vendor Commitment, Vendor Change or Vendor Invoice.