Chart of Accounts are permission based
To update, your account must have one of the following roles enabled:
Role: Company Admin, Accountant
Custom role with: Accounting settings - Full access
Overview
With COA Mapping you can create a translation layer between your production company's COA and a 3rd party's or studio's COA — automatically, without manually reconciling them in a spreadsheet.
When a 3rd party uses different account names or numbers than your company COA, COA Mapping creates a bridge so you can generate reports in either format without re-keying any data or touching the underlying transaction coding.
Who this is for: Production accountants and company-level finance administrators whose productions are required to report in a 3rd party's or studio's COA format — for example, productions working with Netflix, Amazon, or other studio partners.
Prerequisite: A COA must be enabled at the company level before COA Mapping is visible. If you can't see the Chart Mapping tab, contact your Wrapbook Customer Success Manager or the Support Team to confirm a company-level COA is enabled for your company.
How COA Mapping works
Mappings are configured at the company level and inherited automatically by all new projects using that COA
You select a source COA (your production company's chart) and a destination COA (the 3rd party's or studio's chart)
Auto-mapping analyzes both charts and intelligently suggests account matches based on account descriptions and types — giving you a strong starting point without manual matching
You review every suggested match and can accept, modify, or override each one individually
Delta accounts — project-specific accounts not present in the company template — must be mapped manually, as auto-mapping only handles accounts present in both charts
Once activated, you can generate reports using your company's native account codes or the mapped COA view at any time, without changing how transactions are coded
Set up a company-level COA mapping
Only company-level users can create or edit company COA mappings. Project-level accountants cannot modify company-level mapping settings.
In the left-side navigation, click the dropdown and select All projects
Click Company settings
Click Production accounting chart templates
Open the Chart Mapping tab
Click Add mapping
Select a source COA (your production company's chart) and a destination COA (the 3rd party's or studio's chart)
Click Auto-mapping — Wrapbook suggests account matches based on descriptions and account types
Review the suggested matches and accept, modify, or override each one as needed
When your review is complete, click Activate
Note: You can create separate mappings for each 3rd party or studio you report to. Each mapping is one-to-one — one source COA to one destination COA.
Set up a project-level mapping
Mappings can also be created directly at the project level. If your project was created from a company COA template, any mapping already configured at the company level is inherited automatically and is read-only from the project view.
In the left-side navigation, click the dropdown and select the project
Click Project settings
Navigate to Accounting > COA mapping
Click Add mapping
Follow the same steps as the company-level setup: select source and destination COA, run auto-mapping, review, and activate
Apply a COA mapping to reports
When generating a Cost Report, General Ledger, or Trial Balance, you can apply a COA mapping to view or export the report in a 3rd party's format:
In the left-side navigation, click the dropdown and select the project
In the left-side navigation, expand the ACCOUNTING menu, and then click Account reports
Click the Create report button next to the report you want to generate
In the report settings, locate the Show account codes in toggle
Switch from Project COA to your mapped COA
Generate or export the report — transaction amounts remain unchanged; only the account names and codes reflect the mapped COA
Show native account codes in a mapped cost report
When generating a Cost Report with a COA mapping selected, you can display your native (project) account codes and descriptions alongside the mapped accounts in the exported PDF. This lets you trace costs back to your internal GL structure and identify coding issues in the report.
To enable this view:
Follow the steps to generate a Cost Report and select a COA mapping
In the Report settings, select the option to Show native accounts
When enabled, the exported PDF displays the underlying native COA codes and descriptions beneath the mapped account sections
Totals continue to roll up at the mapped account level
When this is useful:
Spotting costs hitting the wrong native account before finalizing GL coding
Confirming that coding aligns with your internal GL structure before submitting a mapped report to a studio
Supporting tax credit audits where both mapped and native account codes may be required
Note: This option appears only when a COA mapping has been selected while generating the report. The setting applies per report/export and resets when the page is refreshed. If you want to reuse the setting, create a report template.
Mapping limitations
One-to-one only: Each mapping connects one source COA to one destination COA. You’ll need to create a separate mapping for each 3rd party or studio you report to.
Directional: A mapping from COA A to COA B does not automatically work in reverse
Not transitive: If you have A → B and B → C, Wrapbook does not automatically produce an A → C mapping
Clearing a mapping: You can clear and restart a mapping at any time — this does not affect historical report data