Out-of-the-box accounting integration — Excel copy/paste with project ledger apportionment

UniPhi 22 ships with a built-in, no-middleware accounting integration. If your finance system can export transactions to Excel, you can now bring actuals into UniPhi with a simple copy and paste — no custom connector build required.

Why it matters

Most project organisations run a corporate accounting system that has no concept of a project ledger — transactions are coded to GL accounts, not to project cost codes.

UniPhi 22 bridges that gap: where the source system does not support a project ledger, imported transactions can be apportioned to a project ledger in UniPhi (the UniPhi Chart of Accounts) as part of the import, so project managers see real actuals against their WBS without waiting for finance.

How it is configured

1.       Go to the main menu → Configuration → Accounting Integration → Settings.

2.       Set Source of Actuals — “the source of actuals for internal cost and revenue charts of accounts; select UniPhi if all actuals are generated by UniPhi claim documents”, otherwise select your accounting system.

3.       Set Accounting System has Project Ledger — this controls “whether transactions imported from the accounting system contain account codes belonging to a UniPhi chart of accounts; if No is selected then imported transactions can be manually mapped to UniPhi account codes”.

4.       With the integration configured, transactions are imported by copying rows from your Excel export and pasting them into the UniPhi import grid, where they can be split and apportioned across projects and cost codes.

Related change — MYOB Cost Centre IDs

For MYOB customers, exported invoices can now carry a Cost Centre ID derived from the project’s Sector Code, Project Type Code, Service Line Code or Location Code — or from the value of a List-type custom field. This lets MYOB cost centre reporting mirror your UniPhi portfolio structure automatically.