Table of Contents

Handling POs

Jennifer Sneider Updated by Jennifer Sneider

If you received a message stating that POs were detected during ledger upload and were directed here, please ensure that the Asset report is exported with cost Transactions only. This article provides information on how to fix this.

Studio Managers, Series/Feature Owners, and Department Users (with Upload Ledgers permission) can access this feature. 

Handling PO-Coded Transactions in AssetHub

When a Transaction is coded as a PO on the Asset report ("ledger"), this is considered a "promise-to-pay." The assumption is that about 30 days after the Transaction is coded as a PO, it will be recoded as an AP. In your accounting software, this change takes effect directly on the Transaction; a copy of the Transaction is not made, it is simply updated on the record.

AssetHub is designed to import any new Transactions and ignore those that had been previously imported. In order for this to hold true, the information on a Transaction line must remain the same on every Asset report upload. If any piece of information on the line is changed, it results in duplicate Transactions.

Correcting Issues Resulting From PO-Coded Transactions 

To avoid duplicates as a result of PO re-coding, you need to exclude POs from your Asset report runs. This typically involves leaving the Include POs box unchecked, or Include Amounts that are Cost Only. Please see the manual for your accounting software for specific information on how to do this.

Note: If you have any questions about the message you received, please contact our Support team using the chat bubble in the bottom right corner of Asset Hub, emailing, or calling 310-451-1792 (M-F 6AM-6PM PST).

How did we do?

Matching Columns