AP-C is date sensitive.. if you say the invoice date is for the 28th then all items received after the 28th are not on the list to pick from, that might be your issue, just a guess.
 

There are two dates in PO Invoices, the invoice date and the post date.  The invoice date is the date on the invoice, the post date is the date that can not be before the receiver date.  MY AP person always makes the post date the date of the receiver or later.

The invoice date is the date on the invoice.  The post date should almost always be the date it is entered into DBA unless you are facing an end of the year situation.
 
DBA ages from the invoice date when determining when to pay the bill.

Quote from wildco   on 10/05/06 at 08:52:52:

Maybe I'm just picky, but I like to be able to create any report on any data for any date range and know that it will be accurate. The fact you acknlowledge that at the end of year they should agree indicates to me that the concept applies any time.
 
Is there some reason why it's bad in DBA to enter the post date in the past?

Actually, that is no longer true. The limits on dates allowed in AP-B & AP-C as well as payment dates in AP-H will keep the aging and GL in agreement.

Quote from wildco   on 10/06/06 at 09:48:16:

 
I was under the impression that the Invoice Date is the date DBA uses to age the bill in AP-Aging, and transaction date is the date DBA uses to post the invoice to the General Ledger in RP batch. If a prior period date is used for posting the invoice, that would change the prior period General Ledger balance for Accounts Payable - would it not?  

Certainly the transaction goes into DBA on the date the transaction is posted in GL-O.  But, I am 99% certain when it posts the amounts to the income statement/bal sheet, it uses the invoice date, and not the post date.  
 
Maybe Lynn can verify this, I dont want to give out incorrect info.
 
If you have reset your period close date at the end of a fiscal year, you will be unable to enter a transaction with a prior date, hence my statement about running into trouble at the end of the year.  Of course, you can roll the date back, enter the invoice, and reset the date, but at some point you need to close the books so you can pay taxes, etc.  At that point, I think you are better off putting in the transaction on the first date of the new year.
 
kevind:  DBA does make a transaction to RNI and inventory when something is received, and you now have to pay for the goods (the accrual system).  Then, when the invoice is posted, it removes it from RNI and puts it into AP.  I should have been more specific.
 
We have always done our receiving/POs this way and do not experience any problems.

oops...After looking into this further, it appears that the transaction enters DBA on the post date, as mentioned earlier by David.
 
but...  since the item is on a PO, when it is received that is when you incur the expense under the accural accounting system.  You do not incur the expense until you receive the item, because if it is lost, broken, incorrect you do not owe the vendor for the goods (usually).
 
so...I think it is acceptable to use the post date as the date the invoice is entered, because as far as the IRS is concerned, you have already incurred the expense when you received the goods.
 
HOWEVER... with AP-B enter vouchers, to make the amounts come out properly you could enter the post date and invoice date at the same time, since there is no intermediate step (receiving) to accrue the expense on a particular day.
 
sorry if this is confusing.

I have noticed 2 reasons for this:
 
1.  Receipt date is after invoice date
 
2.  Sometimes DBA "burps" and a receipt is only half a receipt.  What I mean by this is we will see that inventory has been increased and the PO has 0 left on it, but it never makes it into RNI.  I have no idea why this happens, but our workaround is to receive the PO again, and then adjust out the inventory in question.  So far we have been lucky and it hasnt involved a PO for a non-inventory item.  I suppose you could delete the errant lines in the database, but I do not know the correct files to use.

Quote from wildco   on 10/06/06 at 11:42:13:

 
My work around is to not affect inventory, but enter the invoice in AP-B as a manual invoice with the offset to RNI account.  Our experience shows it is usually the AP aging and A/P-C that did not post properly when the po receipt transaction only partially processes.

Quote from wildco   on 10/06/06 at 11:42:13:

 
When is the Invoice Date ever AFTER the Receipt date?

Perfect, that will work great.  What about your totals for RNI account matching the RNI report?  Does this process throw you off?
 
The receipt date can be after the invoice date in event of a mistake (i.e. 2007 instead of 2006).  Also, I think it is actually receipt date after POST date, since it is likely that all receiving will be after the invoice date as in shipping time.

Quote from wildco   on 10/09/06 at 10:39:09:

 
Absolutely not, as long as you process the PO Receipt transaction and AP-B entry in the same period.
 
I balance the RNI report montlhy to open packing slips and General Ledger RNI. That is how I learned I must use the GL for RNI in order to process the invoice through AP-B.

If you reopened the PO, then it must have been closed via PO-K which would be the reason you couldn't invoice it in the first place.

Quote from cathyh on 10/05/06 at 07:08:17:

 
I bought an item from Amazon on 12-24-2015.  The dollars cleared the credit card on 12-24-2015.  Amazons' invoice date is 12-24-2015.
 
We received the item on 1-4-2016.  
 
What month and year should the expense be in?
 
Thanks,
Laura