Technically it could probably be done. While I have not installed the last couple of versions, I don't believe anything like this is in the canned reports. It would have to be completely custom written and would require the use of the Database Administration program (Connector or Advanced module) as well, not just the standard reporting module.

Depending on your Excel skills with MSQuery, you might be able to put together the data required from invoice lookup and customer history to put together a report as well. Any way you do it will take some time and effort.

If you do allocations to A/R, you can run two reports - an A/R aging and a Project Allocation report for account 1200.

With a bit of reworking you can get the Allocation Report whittled down to a list of invoices and the projects they relate to. Then use VLookup in Excel to put it together.

If you want an aging report by Project, once you have it all into a block of Excel data you can use a Pivot Table to rework it.

If you want to grab the data directly from the data tables with ODBC (MSQuery, Access, LibreOffice, Crystal Reports, etc.)

tItLU.bAlocToAll and tItLU.lProjID will get you the project ID, if the invoice has been allocated to exactly one project. If you use the Order Number field,

tItlu.LitRecid ->titrec.Lid will get you the invoice number in tItRec.sSource1 (assuming a straight-forward pay later invoice).

Sage 50 uses the same invoice tables for both Receivables and Payables. titRec.nJournal = 8 is the Sales Invoice table.

tCusTR and tCusTrDT All the invoices are in tCusTr, and tCusTrDT. If they're paid there is a matching payment in tCusTrDT. To find all the unpaid invoices you need to sum each tCusTR for all records in tCusTrDT - the ones that aren't zero aren't paid. If your company ever takes Sales Deposits you'll have to check how that is stored, too.

There is no direct link between tCusTR and tItrec, other than the invoice number with customer ID. Those two together are a compound key. If you're using a linked Access table you'll have to set that up in Relationships.

You may want to pick up the demo of XLGL, it may be easier to build a report in that tool than to tuck into the tables with SQL.