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 process within OneLease to push journals into Sage Intacct.
Please note: This functionality is an optional feature available to customers who use Sage Intacct, subject to request and additional cost.
Push Data to Sage Intacct
Once your Platform Integration between Nomos One and Sage Intacct is set up (find instructions for doing so in this article) you will be able to push journals from OneLease to Sage Intacct whenever needed. To do so:
- 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.