Hi @LB-03061218-0 ,
Great answer from Adis above covering the general financial dimension mechanics , I'd add a couple of project-specific points since you mentioned invoicing and revenue recognition:
On already-invoiced/posted transactions: As Adis noted, historical postings keep their original dimension values — Dataverse/Finance doesn't retroactively rewrite ledger entries. If you truly need old transactions to reflect new dimensions (e.g., for a specific reporting period going forward), the standard way is a General Journal reclassification entry moving balances from old dimension combination to new, rather than trying to "correct" the original transaction. This keeps your audit trail intact.
On active projects with WIP/accrued revenue not yet invoiced: Be careful here, if you change the dimension on a project mid-stream and it has open/unbilled WIP, cost accruals, or revenue recognition not yet posted, those future postings will pick up the new dimension, but this can create a mismatch against already-recognized revenue on the same project under the old dimension. I'd recommend closing out any pending WIP/accrual postings before changing the project's dimension, so you don't end up with a split project history mid-lifecycle.
On T&M vs Fixed Price specifically: Fixed Price projects using POC (percentage of completion) revenue recognition are more sensitive to this — since revenue recognition is calculated based on project-to-date cost/completion, a dimension change mid-project won't affect the recognition calculation itself, but will affect which dimension the recognized revenue posts to going forward, which can distort trend reporting if not documented clearly.
Agree with Adis's suggestion, test this in a sandbox copy first, especially for a project with WIP and partial invoicing, so you can see exactly how the split looks in reporting before doing it in Prod.
Thanks!