If an export failure is encountered, this could caused by a crucial mismatch between the Xero Account Code Type and the UniPhi Tax Rate Type. Error Cause: Xero sees Account Code 412 as an Expense (a cost contract) and expects a GST Input tax rate. However, the transaction was assigned a tax rate that resolved to the taxType code 'OUTPUT' (typically for revenue). Step 4.1: Re-map the Tax on the Contract The solution is to correct the tax rate assigned to the contract line item

This section details specific considerations for tax rate mapping, particularly when working with custom tax codes and multiple Xero organisations. Advanced Tax Code Mapping Rules The UniPhi-Xero integration works by referencing an underlying TaxType code (e.g., OUTPUT for GST On Income, or INPUT for GST on Expenses), rather than the user-facing tax rate name. Tax Rate Type Basis of Mapping Rule for Integration System-Defined Rates (e.g., GST on Income, GST on Expenses) Mappe

How do invoices inherit an Orphaned status? AP invoices will inherit the Orphaned status if the contract's customer organisation is not linked to a Xero file. AR invoices will inherit the Orphaned status if the contract's supplier organisation is not linked to a Xero file. How do I fix the status? Delete the invoice (only System Administrators can do this) Check the contract customer and the UniPhi internal organisation is correct. What you select here is what will appear in

This article explains the end-to-end process for setting up Earned Value (EV) reporting in UniPhi. It is intended for Project Managers and Project Administrators who are familiar with Earned Value Management concepts, but who may be new to configuring UniPhi for EV reporting. Overvi ew: W hat UniPhi Uses to Calculate Earned Value To calculate Earned Value at all levels of the Work Breakdown Structure (WBS), UniPhi relies on three core data streams: A baselined Resource Plan (