ACSP Suggestion 2013.12: Persistent field for Purchase Order Number in Billing Information
Author: Jason Schiller
Submitted On: 23 April 2013
Description: Allow ARIN-online Billing information to include a persistent field for PO#, that will get printed on the invoice in the PO # filed automatically.
Status: Closed Updated: 15 September 2014
22 May 2013
Thank you for your suggestion to include a persistent field for a purchase order number that will get printed on the invoice in the purchase order # field automatically. During development we will likely allow both a persistent (static) as well as a dynamic PO # according to each organization’s specific needs. We will put this into the development queue as soon as possible, noting that we have a couple of significant development efforts underway for the next few months. Therefore it may be several months before we are able to move this into implementation.
This suggestion will remain open.
26 September 2013
As part of the ARIN 32 ACSP Consultation: Open Suggestion Review and Project Prioritization Survey, we’re providing feedback and estimates on the predicted work involved. For this suggestion, the following is noted:
This would require a comment field to add PO number or whatever else the customer wants to have on invoice, then customer can reprint with field completed (dynamic) or have a place in ARIN Online to add what should be included on invoice in comment field and then invoice will be generated with comment field data. Estimated staff effort to implement: Four person months, plus communications efforts.
For information about the consultation and how to participate in the survey, please see the 26 September 2013 announcement.
15 September 2014
Following further internal analysis of payments, ARIN has found that the number of purchase order (PO) related payments actually turns out to be low when compared to total volume of payments processed. Specifically, PO-related payments account for about 5% of total payments. Following discussions with you and the Financial Services Department team, it appears that the process we have today, i.e. putting the PO reference number in the address line, or similar field, works well for the customer.
As a result we will not be pursuing any automation of creating a persistent PO field within the ARIN Online system, and we are closing Suggestion 2013.12.