3rd Party Billing? Ship-to Not Unique to Customer?

I have a crude workaround to some needs -- but I wondered if anyone had any more elegant workarounds -- or even knew of some features I had not yet found! My needs are:

1. People we ship-to are not necessarily the same as those "who ordered" or "who will pay". There are N:N relationships between "Payer" and "Recipient", N:N between "Order Originator" and "Recipient", N:N between "Orderer" and "Payer".

2. "Ship To LOCATION" are not necessarily 1:1 with ANY of "person who's receiving", "who ordered" or "who's paying", but frequently "Ship To LOCATION" MAY BE 1:1 with "person who's receiving". Locations change. Affiliations change. Payers change. Orders follow people though the changes.

3. All transactions will be synced from another transaction-based system. About 50% of the transactions are adjudicated and payment scheduled through EDI transactions which are represented in xTuple. The other 50% need post-transaction consolidated billing. Monthly statement showing "all items", "all shipments", "all charges", and "all adjustments" for 100's of "Ship to" events for 1000's of "Recipients".

4. EDI transactions are backed up with monthly reports from Payer, with some payments coming via EDI and some coming via snailmail/check. ALL need to be reconciled back to each revenue event. This is done manually.

xTuple is used as a replacement for an archaic embedded acconting module in the EDI OLTP system.

Any thoughts?

Regards,
George