COA Mapping (PAS)

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.

1. In the left-side navigation, click the dropdown and select All projects

2. Click Company settings

3. Click Production accounting chart templates

4. Open the Chart Mapping tab

5. Click Add mapping

6. Select a source COA (your production company's chart) and a destination COA (the 3rd party's or studio's chart)

7. Click Auto-mapping — Wrapbook suggests account matches based on descriptions and account types

8. Review the suggested matches and accept, modify, or override each one as needed

9. 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.

1. In the left-side navigation, click the dropdown and select the project

2. Click Project settings

3. Navigate to Accounting > COA mapping

4. Click Add mapping

5. 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:

1. In the left-side navigation, click the dropdown and select the project

2. In the left-side navigation, expand the ACCOUNTING menu, and then click Account reports

3. Click the Create report button next to the report you want to generate

4. In the report settings, locate the Show account codes in toggle

5. Switch from Project COA to your mapped COA

6. Generate or export the report — transaction amounts remain unchanged; only the account names and codes reflect the mapped COA

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