If your organisation uses Sage Intacct to manage accounting processes, you can connect it with your journal processes in Nomos One, to allow the platform to push lease accounting journal entries into Sage Intacct. This article will guide you through the set up process in both Sage Intacct and OneLease.
Please note: This functionality is an optional feature available to customers who use Sage Intacct, subject to request and additional cost.
Important Information
OneLease uses the Sage Intacct Rest API with OAuth 2.0 client credentials. It does not require Sage XML sender credentials, custom packages, smart events, custom fields, or custom reports for the current journal-entry workflow. You will not get charged by Sage for using the integration, because the OAuth Client ID and Client Secret are Nomos One's Sage credentials.
How It Works
| Area | Requirement |
| Authentication | OAuth 2.0 authentication is handled by OneLease. You will require your Company ID, a dedicated Web Services User, and optionally an Intacct Entity ID. |
| Read access | Active General Ledger journals and active General Ledger accounts, used to populate mapping choices in OneLease. |
| Write access | General Ledger journal-entry creation. |
| Posting state | OneLease can create records as Draft (pending) or Final (posted), depending on the option selected during the mapping step. |
Before You Begin
- Confirm that the Sage Intacct company (and optionally the entity) is the correct production or test entity that you want to connect to your OneLease organisation.
- Decide which Sage Intacct Web Services User OneLease should use for API activity. Note that the User ID is case sensitive.
- Find the Sage General Ledger and Chart of Accounts values that you wish to receive OneLease journal entries.
In Sage Intacct
Review IP Address Restrictions
If your Sage Intacct company enforces IP address filters, the OneLease outbound IP address must be allowed before the connection test will pass. Ask your Sage Intacct administrator if you are unsure. If your company does not enforce IP address filters, no change is required, and you can move to the next section. To allow the OneLease outbound IP address:
- Navigate to “Company”, then “Company Info”.
- Click “Edit” and open the “Security” tab.
- Review Enforce IP address filters. If filters are enabled, add the current OneLease production outbound IP address. You will need to contact OneLease support for this value, before enabling or tightening the restriction.
Create or update the OneLease API user
OneLease requests Sage access tokens using the Web Services User ID. That user must be active and have the minimum permissions required for the integration.
Role Based Security:
- Navigate to “Company”, then “Roles”.
- Create a role named “OneLease Integration”, or update an existing integration role.
- Grant the minimum security permissions listed in the permissions checklist below.
- Navigate to “Company”, then “Web Services” users. Create or update the OneLease user and assign the role on the “Roles” information tab.
User Based Security:
- Navigate to “Company”, then “Web Services” users.
- For the OneLease user, click “Subscriptions”.
- Grant the minimum permissions listed in the permissions checklist below.
Permissions Checklist
Exact permission names may vary based on the Sage Intacct configuration. The principle is least privilege: the user should only receive the access needed for OneLease to read setup data and create journal entries.
| Sage area | Access Needed | Reasoning |
| General Ledger journals | Read/list active journals | Allows OneLease to populate the General Ledger ID selection. |
| General Ledger accounts | Read/list active journals | Allows OneLease to populate Chart of Accounts mapping fields. |
| General Ledger journal entries | Create journal entries | Allows OneLease to push lease accounting journal entries. |
| General Ledger journal entries | Post or submit final entries, if Final (Posted) will be used | Required only if the organisation wants OneLease records created as Final (Posted). |
In OneLease
Connect Sage Intacct
- In OneLease, navigate to “Settings”. You will be directed to Integration, specifically Connected Platforms.
.gif)
- Click “Create Platform Integration”.
- Click “Connect Platform” and a pop-up window will appear.
- For Platform, “Sage Intacct” will be selected. Entity ID will display the Organisation you are currently working in.
- Enter the Sage Intacct Company ID, Sage Intacct Web Services Username, and optionally a Sage Intacct Entity ID. This information will be found in Sage. Find explanations for these fields in the table below.
- Click “Connect Platform”. This will prompt the two platforms to run the connection test. If the test succeeds, OneLease will store the connection details.
If you experience an error message after clicking “Connect Platform”, review the information entered for correctness. If the information is correct, but you are still experiencing an error message, reach out to our Support Team with details of the error.
Connection Fields
| OneLease field | Value to enter |
| Sage Intacct Company ID | Your Company ID provided by Sage. To find this, log into Sage Intacct and select the Company from the Applications dropdown. Navigate to Setup > Configuration > Company (or hover over Company and select “Company Info”). |
| Sage Intacct Web Services Username | The username of the user with Web Services privileges that OneLease will use for API operations. The username is case sensitive. |
| Sage Intacct Entity ID | If you would like to post journals to a particular Sage entity, rather than the top level company, enter the ID. To find your entity ID, go to the Root Level (top level) of your Sage Intacct company. Hover over Company on the top navigation menu, then select “Entities” (or go to Company > Setup > Entities). |
Complete Mapping Details
After the connection succeeds, OneLease will retrieve active Sage Intacct accounts, and the page will update to resemble the below screenshot. Open the Mapping Details section to complete the mapping connections before pushing journal entries.
To complete the Mapping Details:
- For General Ledger ID, select the Sage Intacct General Ledger that should receive OneLease journal entries.
- For Post Records in Sage as, select Draft (Pending) while validating the setup, or Final (Posted) once the process is approved.
- For the Chart of Accounts Mapping Detail section, map each OneLease account category to the corresponding Sage Intacct account. Find each OneLease account listed in the “Mapping Categories” table below.
- Click “Create Platform Integration”.
Mapping Categories
| Category | OneLease accounts |
| Assets | Cash, Right of Use Asset, Accumulated Depreciation, Accumulated Impairment, Accrual Prepayment, Security Deposits |
| Liabilities | Lease Liability, Make Good Provision |
| Equity | Asset Revaluation Reserve, Onerous Lease - Suspense Account, Retained Earnings |
| Income | Revaluation of Investment Property, Gain/Loss on Lease Event, Revaluation of Peppercorn Lease |
| Expenses | Depreciation Expense, Interest Expense, Impairment Expense, Gain/Loss on Surrender/Termination, Variable Lease Expense, Low-value Asset Lease Expense, Short-term Lease Expense, Operating Expenses Relating to Leases, Non-lease Component, Interest Expense on Make Good Provision, FX Movement on Lease Liability, Penalty - Surrender/Termination |
| Other | Direct Cost - Suspense Account, Prepaid Cost - Suspense Account, Accrued Rent - Suspense Account, Rent Equalisation - Suspense Account, Business Combination Gain/Loss, Finance Sublease Derecognised, Rounding |
Tip: Validate the connection before going live
- Use a Sage Intacct test company or a controlled production test before enabling regular journal-entry pushes.
- Start with Draft (Pending) so finance users can review the generated entries before posting.
- Push a small set of representative agreements and compare the Sage journal entry lines with the expected OneLease accounting outputs.
- Confirm that debit and credit totals balance, posting dates are correct, descriptions are meaningful, and mapped accounts are correct.
- Move to Final (Posted) only after finance users approve the draft output and the Sage permissions support final posting.
Pushing Data to Sage Intacct
- Navigate to “Settings”, then “Integration”, then “Integration Activity”.
- Click “Push Data To Integration Platform”.
- For the “Connected Platform”, Sage Intacct will be selected.
- Select to run the integration for all Agreements, or select specific Agreements.
- Enter the reporting period.
- Enter a journal-entry description that finance users will recognise within Sage Intacct.
- Click “Push Data To Integrated Platform”.
If any of the Agreements included in the data push have errors, or if no Agreements are ongoing during the selected reporting period, you will be unable to push the data to Sage Intacct. An error message will note what the problem is. Review the relevant Agreements and/or the selected set up of the report before trying again. To determine how to fix the Agreement(s) with errors, check out this article that lists each error message and its solution.
An error may also appear if the Mapping Details section has not been filled out with the necessary account mappings. An error message will note if this is the case. Review the Mapping Details section to ensure the necessary accounts have been mapped.
Once the data push has been prompted, you will see the push - and any previous data pushes - displayed on the Integration Activity page. You will see the integrated platform, details of the push, the date it was prompted, and the user who prompted it. If the push has worked successfully, the Status column will display “Success”. If not, the column will display “Fail” and the Message column will display the reason why it failed.
Troubleshooting
| Issue | What to check |
| Authentication failed | Confirm that the case-sensitive User ID, the Company ID, and optional Entity ID are correct with your Sage administrator. |
| Connection times out or is blocked | Check whether Sage IP filters are enabled and whether the current OneLease outbound IP address is allowed. |
| Journals or accounts do not appear in OneLease | Confirm the API user can read active General Ledger journals and accounts. Inactive Sage values are not returned for selection. |
| Cannot create journal entries | Confirm the API user has permission to create General Ledger journal entries and, if required, to post final entries. |
| Incorrect accounts on pushed entries | Review Chart of Accounts Mapping Detail in OneLease and update any incorrect mappings before pushing again. |
If setup does not complete successfully, provide OneLease Support with the Sage company/environment, the OneLease organisation, the Sage Web Services User ID, the step that failed, and the exact error shown in OneLease or Sage Intacct.
Nomos One does not provide or purport to provide any accounting, financial, tax, legal or any professional advice, nor does Nomos One purport to offer a financial product or service. Nomos One is not responsible or liable for any claim, loss, damage, costs or expenses resulting from your use of or reliance on these resource materials. It is your responsibility to obtain accounting, financial, legal and taxation advice to ensure your use of the Nomos One system meets your individual requirements.