"Ready to invoice" button not working in Actuals

(2) Share

Report

Posted on by TA-13061442-0

Currently, any time I try to generate an invoice I get the following error:

There are no past dated transactions for project-based contract lines that are in status ready to invoice. No invoice was created. Ensure that there is at least one transaction on a project-based contract line that is past dated and has Billing status value "Ready to invoice". Billing backlog links in the Billing section of Sales area can be used to mark transactions as "Ready to invoice".

I have a list of Actuals which all have an empty Billing status. From my understand, I need to use "Ready for invoice" button so that these transactions can be picked up when generating an invoice. My problem is that nothing happens whenever I click the "Ready for invoice" button. What am I missing?

All responses (2)

Answers (0)

Brittany W 7 on at

Like (0)

Report
"Ready to invoice" button not working in Actuals

A couple of other things to look at beyond what Erica suggested is:

Document Date - make sure they actually are today's date or older. Sometimes users accidentally forward-date transactions.

Other information: it is possible to accidentally make actuals that are missing a contract, contract customer, contract line, or contract line customer reference which makes them unable to pull into an invoice.
Erica J Ellis 71 on at

Like (0)

Report

"Ready to invoice" button not working in Actuals

Your understanding of how it should work is correct. If you mark the Actuals as Ready to Invoice, then they will go into the Invoice when you choose to Create Invoice.

Have you tried to open one of the transactions and manually select Ready to Invoice in the Billing Status field? I am wondering if that might produce an error that the button is failing to produce, so that you can see the problem.

Are you choosing Ready to Invoice on Unbilled Sales transactions? I have accidentally clicked Ready to Invoice on Cost transactions before, and it just does nothing. It didn't give an error or anything to indicate my mistake.