Currently, when generating an invoice in Adagio Invoicing, the REFERENCE number field only allows you to input 12 characters. Will that amount ever be increased?

It's unlikely. What are you trying to use it for? Could you use one of the optional fields for the same information?

I use the reference field (and the PO# field) for my customers PO's, and some PO's are longer than 12 characters, therefore they don't print on the invoice completely. This transfers all the way to Receivables when I print statements. I never thought of using the optional fields. I will look into that.

Hi Andrew

I have a client complaining vociferously about the same issue - they do government contract work and the government PO's are 18 characters. The problem with the optional field idea (although it is what I suggested) is that it doesn't pass through to the customer's AR account and so it doesn't appear on customer statements.

If we could select the OE reference field AND the OE optional field, trimmed and combined, to pass through to the AR reference or description field, then the optional field idea would be more workable (although still not ideal).

Steve

Hi Steve,

QI Optional fields do pass through to the customer transaction if they are using Receivables 90A, and if AR is defined to use Batch Optional fields that use the same respective names as the Adagio Invoices optional fields. They will not pass through to ARTRANS if AR Batch optional fields are not defined as such.

So if this is the desired, as an example, define an Invoice optional text field (say #1) and call it something like 'PO#'. Then in AR9, define a batch optional text field (#1) to also be 'PO#'.

How about in OE? I just created an optional field called "Extended PO#"? If I create an identically named field in AR 9.0, will it get populated when the batch retrieved from OE during dayend is posted in AR? If not, I return to my suggestion above.

Steve

I think the answer is "yes", but you can confirm that with the sample data.

For OE to AR, the answer is Yes if OE Day end creates Direct batches in AR, and No if OE creates Retrieval batches for AR. You would be able to see the optional field value(s) on the created AR invoice batch prior to posting.

Again, you have to create a 'Batch optional field' in AR9 that has the same title and same optional field type/location as in OE. So the 'Extended PO#' would have to be Text 1 in both places, or Text 2 or Text 3. It cannot be Text 1 in one app and Text 2 in the other.