Skip to main content

Sage Intacct

The Sage Intacct integration pulls your general ledger from Sage Intacct into Una, so you can budget, forecast and report against your actuals without exporting or re-keying anything.

The integration is read-only. Una never writes back to Sage Intacct, and nothing is installed into your Sage company.

What it does​

  1. Prepare — you enable web services in Sage and create a read-only user for Una.
  2. Connect — you give Una that user's credentials.
  3. Configure — you choose which Sage dimensions map onto your Una model.
  4. Build and load — Una builds the model and loads your monthly balances into it.

Before you start​

Sage Intacct needs more preparation than most connectors, and most of it happens inside your Sage company. Work through Step 1 before booking time to do the rest — a Sage administrator needs to be involved.

You'll also need:

  • Admin access in Una, since you'll be configuring tenant-wide settings.
  • A start date — how far back Una should pull. Two to three years is typical. You can extend this later, but you can't shorten it.
warning

Check your fiscal calendar first. Una reads Sage's monthly reporting periods, and a period only counts if it starts on the first of a month and ends on the last day of that same month.

If your organisation uses a 4-4-5, 13-period or other non-calendar fiscal calendar, this integration cannot read your balances. Raise it with your Una contact before going further rather than working through the setup.

Step 1 — Prepare your Sage Intacct company​

This is done by a Sage Intacct administrator.

  1. Enable the Web Services subscription for your company.
  2. Authorise Una's Sender ID. Add unasoftwareMPP to your company's web services authorisations. This identifies Una as the calling application — it is not a password, and it is the same for every Una customer.
  3. Create a dedicated web services user. Set the user type to Business user. Use a dedicated integration account rather than a person's login, so the integration doesn't break when someone leaves. This user cannot sign in to the Sage web interface, and it is free of charge.
  4. Give that user a read-only role. Every permission is List and View only:
    • GL Accounts and Reporting Periods — always required
    • Departments, Locations, Classes — whichever of these you plan to report by
    • Consolidation books — only if you want Sage's own currency-translated figures
  5. Check your reporting periods. They must be calendar-monthly and flagged Budgetable, and your company must post to the accrual book.

The role does not need Platform Services, Journal Entries or Entities.

When this is done you'll have three values for the next step: the Company ID, the Web Services User ID, and that user's password.

Step 2 — Create the connection in Una​

  1. In Una, go to Settings → Integrations → ERP.
  2. Click Add New.
  3. Give the connection a name, and set Type to Sage Intacct.
  4. Choose Create a new connection.
  5. Enter the Company ID, Web Services User ID and Web Services Password, then save.

Una stores these encrypted.

Step 3 — Test the connection​

Click Test connection. Una signs in and then reads a single row from each object it needs, so this checks the permissions from Step 1 rather than just the password.

If the role is missing something, the message names exactly which objects Sage refused — hand that list to your Sage administrator and it maps directly onto the permissions in Step 1.4.

note

Run this test again after Step 4. Permissions on the dimensions you map can only be checked once the mapping is saved, so the first test doesn't cover them.

Step 4 — Choose the model and map your dimensions​

Click the connection's name to open it. You'll land on the Model Mapping tab.

  1. Under Model, leave the dropdown on <New Model> and give the model a name.
  2. In Dimension Mapping, map Account to Sage's Account.
  3. Use Add dimension for anything else you want to report by.

Sage Intacct offers four things to map: Account, Department, Class and Location.

warning

Entities are Locations. If your organisation is multi-entity, you won't find an Entity option — and that's expected.

Sage Intacct doesn't expose entities in a form Una can read directly. Your entities appear as top-level Locations, so for per-entity reporting you map Una's Entity role to Sage's Location.

Scenario, Time and Account are always present. Scenario and Time are built by Una automatically.

tip

Start small. Map Account plus one other dimension for your first load — it builds faster and makes it much easier to confirm the numbers are right.

Once you've saved the mapping, go back and run Test connection again so the dimension permissions get checked.

Step 5 — Load the data​

  1. Turn Load Data on. Without it, Una builds the model structure but loads no numbers.
  2. Set Update Mode to Snapshot for the first load.
  3. Set the Start Date — use the first day of a month.
  4. Leave Load Translated GL off for now. It is for organisations that want Sage's own currency-translated figures, and it needs a consolidation book chosen plus the matching permission. Get the base load right first.
  5. Click Save & Build.

The build runs in the background, reporting progress in the Messages panel, and usually takes a few minutes.

Watch for the line reading "Pulled N reporting period(s)". For a start date two years back, N should be roughly the number of months since then. If it says 0, no monthly periods matched — see the fiscal calendar warning at the top of this page.

note

Stay on the page while it runs. The progress messages are live only and are not saved, so if you navigate away you cannot get them back. The build itself carries on regardless.

warning

You can always come back and pull more history by choosing an earlier start date. You cannot shorten it by choosing a later one — Una ignores that deliberately, so that data you have already loaded is never deleted. If in doubt, start earlier than you think you need.

Step 6 — Check the numbers​

A completed build means the process ran, not that the result is what you expect. Before you rely on it:

  • Check the "Pulled N reporting period(s)" figure was not zero.
  • Open the model and confirm your real account names are in the Account dimension.
  • Compare one account for one month against the same figure in Sage. Do this for one balance sheet account and one P&L account — they are calculated differently.
  • Confirm the earliest month in the model matches your start date.

Balance sheet accounts should match the closing balance for that month. P&L accounts should match the movement in that month, not the year-to-date figure.

Day-two operations​

  • Refreshing data — run a data update from the connection to pull recent periods.
  • Adding a dimension — add it in Dimension Mapping, check the Sage role grants it, then Save & Build. A plain data refresh does not pick up structural changes.
  • New accounts in Sage — these arrive with a full Save & Build, not with a data refresh.
  • Changing the password — update it on the connection at the same time you change it in Sage, or the next refresh will fail.
  • Scheduling — to refresh automatically, add the ERP Integration activity to a workflow. See Workflow activities → ERP Integration.

Privacy and data sharing​

For the general ledger sync, Una reads your chart of accounts, your reporting periods, your monthly account balances, and the dimensions you choose to map. It does not receive:

  • Individual journal entries or transaction detail
  • Customer, vendor, employee, project or item records
  • Attachments or documents
  • Sage Intacct user or billing information

If you also turn on Additional Data, Una reads the specific Sage objects you select there — for example a vendor list or journal-entry detail — read-only, and only with the List and View permissions you grant for those objects.

Nothing is ever written back to Sage Intacct, and no package or customisation is installed into your company. All API usage is billed to Una, not to you. Within Una, data is stored per-tenant in your dedicated tenant database.

Troubleshooting​

The connection test names objects Sage refused. The read-only role is missing those permissions. Send the list to your Sage administrator — it maps onto Step 1.4.

The connection test fails without naming an object. Sign-in itself failed. Check the Company ID, user ID and password, and that Sender ID unasoftwareMPP is authorised.

"Pulled 0 reporting period(s)". No monthly periods matched. Either the fiscal calendar is not calendar-monthly, or the periods are not flagged Budgetable.

The build completes but the model is empty. Check the period count first, then that Load Data was switched on.

The build fails while loading balances. The role is likely missing permission on account balances — the one permission the connection test cannot check in advance.

There is no Entity option when mapping. Expected. Map Una's Entity role to Sage's Location.

The progress messages stop. The page can lose its live connection while the build carries on underneath. Wait a few minutes, then refresh and check the model.

"A run is already in progress". Something is already building on this connection. Wait for it to finish rather than starting another.

The numbers do not match Sage. Note the account, the month, both figures, and whether it is a balance sheet or P&L account, and raise it with your Una contact.