Here's what's new:
New Feature: Job Title Sync for Cast & Crew New Experience Project Users
What's New
Reporting+ keeps your production data complete and connected. When your team makes a change in the Cast & Crew New Experience, it flows through automatically, so your records are accurate from day one, without the back-and-forth.
When a project admin adds or edits a user through the Cast & Crew New Experience project workflow, the user's Job Title is now captured and synced to Reporting+ automatically
User records in Reporting+ will reflect the Job Title as entered in the New Experience. No manual re-entry or follow-up required
What We're Solving For
Previously, Job Title was not passed from the Cast & Crew New Experience to Reporting+ during user setup. You had to either fill in the gaps manually or go without the data entirely. On productions with large crews and frequent roster changes, this added up quickly.
Benefits
- Eliminates a duplicate data-entry step for project admins and payroll accountants on productions using the New Experience workflow
- Your records in Reporting+ are complete at the point of creation — no cleanup required
What You’ll Need to Do Differently?
| Previously | Now |
| Job Title had to be entered separately in Reporting+ after a user was added through the New Experience workflow. | Job Title entered in the New Experience automatically appears in Reporting+. No additional steps needed. |
New Feature: Incomplete PSL Reference Entries Excluded from PSL Ledger Bible Report
What's New
Every row in your PSL Ledger Bible now means something. Reporting+ automatically filters out incomplete entries, so your team is working with clean, trustworthy data. The report now reflects only fully entered, completed transactions. No manual cleanup, no second-guessing.
The PSL Ledger Bible report no longer returns rows for reference numbers that were started but never completed in PSL+. These are records with a reserved reference number but no associated GL transaction detail, which is typically the result of a user starting an entry and abandoning it before finishing.
What We're Solving For
When you start a transaction entry in PSL+ but doesn't complete it, a reference number gets reserved, but no GL detail is written. The PSL Ledger Bible was surfacing these stub records as rows in the report, creating noise that teams had to manually identify and filter out. During audits or end-of-project reconciliation, this added time and created confusion about whether those reference numbers represented real transactions.
Benefits
- Cleaner report data means less time spent auditing rows that shouldn't be there
- Reduces confusion during end-of-project reconciliation and financial close
What You’ll Need to Do Differently?
| Previously | Now |
| PSL Ledger Bible included rows for incomplete reference entries. You had to manually identify and disregard stubs during reconciliation. | Only fully completed transactions appear in the report. Incomplete reference entries are automatically excluded before the report runs. |