Unbilled item is generated upon receipt.

One RFO item can have multiple unbilled item.

❌ Users can only bill for the exact amount that is received. In order to bill for 10 quantities in the same bill, users will need to add all 3 unbilled items to the bill.
​

Unbilled item is generated upon PO creation.

One RFO item can only have one unbilled item.

✅ Users can bill up to the purchased quantity within the same bill. In order to bill for 10 quantities in the same bill, users can adjust the billable quantity.

❌ Users cannot see the received date of each receiving action anymore from this aggregated view.

⚠️ Users will have to cross reference PO page to see the received date of each receiving.
​

✅ Allow for multiple bill drafts for the same unbilled item to be created at once.

✅ Users are able to add unreceived items to the bill.

❌ Resulting in multiple draft bills with the same unbilled item. Users need to keep track of which draft bill contains the right information for processing.

❌ Users are not aware if the unbilled items are billed, they only see an error message when trying to submit the bill.

✅ Great for physical goods that are received by quantity.

❌ Not suitable for items that are not required to be received or service-type spending

❌ Users need to do ad hoc calculation or adjust the unit cost to achieve the billing amount.

✅ Gives flexibility to users to accurately represent what is billed.

✅ Supports BPO received by cost scenario well

❌ Once users decided to Bill-by-cost for an unbilled item, they are not able to switch to Bill-by-quantity afterwards.

✅ Helps users to keep an audit trail of when each receiving is made.

❌ Users need to keep track of all the unbilled items each time when they’re received.

✅ Users only need to keep track of one unbilled item and its most recent received action.

❌ Users can’t see received date of each unbilled item in the unbilled item page.

⚠️ Users can still retrieve an audit trail of the receiving history in the PO Receive but they will need PO permission.

✅ Users are able to ‘split’ an unbilled item and apply different tax codes

❌ Users need to keep track of the multiple copies of the unbilled item with different received quantities each time they ‘split’ the item.

❌ Users are able to bill over the received items costs by adjusting the unit cost.

✅ Users have the flexibility for editing the quantity they need to bill for without the need to be restricted by the receiving action.

✅ ability to apply different tax/unit cost on different unbilled items from the same RFO item on the same draft bill.

⚠️ Unable to apply different tax/unit cost on the same RFO item.

❌ inaccurate representation of deposit billed.

❌ does not follow common finance practices.

✅ Users are able to assign proper prepaid account code to deposit unbilled item.

✅ Deposit credit is available for sub-sequential billing to avoid any over billing.

✅ For companies with strict receiving policies prior to invoice processing, their users can guarantee that all items available during bill creation are received.

❌ Users are bottlenecked and have to wait for the items to be received before starting their invoice processing.

❌ Not suitable for invoices with items that are not required to be received. (ie: subscription, rent, contracts)

❌ Users would do ad hoc receiving to see items during invoice processing, resulting in an inaccurate representation of what is actually received.

✅ Users are able to start invoice processing by selecting draft bill prepared for that invoice.

✅ Users do not need to manually input invoice data.

✅ Invoice data are digitally recorded into Procurify for more accurate 3-way matching.

✅ Automatically create invoice line item ready for matching.

✅ For companies with strict receiving policies prior to invoice processing, their users can guarantee that all items available during bill creation are received and unbilled.

❌ This workflow is not suitable to bill for items that do not require receiving.

❌ Users do not have an invoice preview while editing item details.

✅ Automated matching reduced the need for users to manual match between invoice and PO items.

✅ Utilizing invoice data for matching instead of the duplicated PO data which reduces the need for users to manipulate the bill item.

✅ Bill items are created based on the invoice items. Users no longer need to manually remove unbilled PO items that are not ready to be billed.

✅ Users can see an invoice preview while editing item details

❌ Users would not know what are the discrepancies at a glance.

❌ Users will need to dig around for information to see why there are discrepancies.

✅ Users can hover over the highlighted areas to gain more context
Users can quickly identify discrepancies at a glance, with contextual information provided to explain the differences.

✅ Users quickly select specific unbilled items from another PO into the bill without selecting the entire PO.

❌ Users need to select POs in order to see the unbilled items for it.

✅ For companies with strict receiving policies prior to invoice processing, their users can guarantee that all items available during bill creation are received.

❌ Users are bottlenecked and have to wait for the items to be received before starting their invoice processing.

❌ Not suitable for invoices with items that are not required to be received. (ie: subscription, rent, contracts)

❌ Users would do ad hoc receiving to see items during invoice processing, resulting in an inaccurate representation of what is actually received.

✅ Users are able to start invoice processing by selecting the purchase order.

✅ Users are able to bill for service-based items that do not require receiving.

✅ Users do not need to do ad hoc receiving.

✅ For companies with strict receiving policies prior to invoice processing, their users can guarantee that all items available during bill creation are received and unbilled.

❌ This workflow is not suitable to bill for items that do not require receiving.

❌ Users do not have an invoice preview while editing item details.

✅ After adding items to bill, users see an item summary stating the unbilled item received status and previously billed amount.

✅ All items related to the PO that are not fully billed will automatically show up in the bill table.

❌ Users who only need to bill for received and unbilled items will need to manually remove items that are not ready to be billed.

❌ Users would not know what are the discrepancies at a glance.

❌ Users will need to dig around for information to see why there are discrepancies.

✅ Users can hover over the highlighted areas to gain more context
Users can quickly identify discrepancies at a glance, with contextual information provided to explain the differences.

✅ Users quickly select specific unbilled items from another PO into the bill without selecting the entire PO.
​

❌ Users need to select POs in order to see the unbilled items for it.

✅ Users get high-level PO details and invoices for reference.

❌ Users need to dig around to understand what has been approved previously or what has been received.

✅ Users get received quantity and previously billed context before approve / deny a bill.
​

​

✅ Act as an accrual report, which helps users to understand how much they still owe the vendors.

✅ Each item has its own received date.

✅ Item is consolidated by RFO item instead of receipt.

✅ More receive and billing data included in the export for user to manipulate and conduct more comprehensive analysis.

✅ Received date filter for user to user to manipulate the data for the accrual purpose. Received quantity, Received cost, Received and unbilled quantity and Received and unbilled cost data should be reflected by the received date filter selected.

Please note that individual received dates based on specific receiving actions will no longer be displayed. Instead, the latest received date will be shown. This update can be accessed through the new Receiving Log export feature

✅ Users can understand how much they still owe the vendors.

✅ Each item has its own received date.

✅ Receiving and billing data are on the same export

The Unbilled Item Export unintentionally served as a receiving log, and users had to consolidate the unbilled items manually.

✅ The receiving log export is organized and clear, intended solely for the purpose of maintaining accurate receiving records

Users will need to manually cross-reference the receiving log export and the unbilled item export by PO ID and PO Line Number to consolidate both sets of data into a single export