Accounts Payable Aging Report

unknown

Our VP of Finance wants an AP Aging Report by Posting Date for a point in time.   He says that the AP250 is not what he needs since it is by due date.  He sometimes uses the AP136, but does not really get what he needs from that report.

Also, we always use the last day of the month as the posting date, to add an additional complication.

Does anyone out there have an AP Aging report that they use?  Is it Lawson or home grown?  Would you be willing to share with our organization how you handle this?

I can be reached by email at khamill@bklynlibrary.org.  Any help would be greatly appreciated.

Thanks.

 

Kay Hamill

Brooklyn Public Library

unknown

The AP136 ties to the General Ledger at month end.

The AP250 has aging buckets, by due date.

The most common AP aging I encountered was aging by invoice date. This can be significantly different from aging by due date when vendors have different payment terms.



Many years ago, a tech person from RPI Consultants did the COBOL coding to essentially use the AP136 selection with the AP250 aging, but aged by invoice date and that is the AP aging most commonly used. We have been able to carry forward this customization with little issue (and minimal COBOL knowledge).



Alternatively, we have a Crystal Report for other purposes that includes aging calculations:



Aging = {?CkRunDate}-{APINVOICE.INVOICE_DTE}

[?CkRunDate] is a Crystal parameter - entered by user when running report.



Using this Aging formula field, there are columns/buckets that evaluate where each invoice belongs:

if {@Aging}<=30

then {APPAYMENT.TRAN_PMT_AMT}



if {@Aging}>30 and {@Aging}<=60

then {APPAYMENT.TRAN_PMT_AMT}

else 0



... and so on.