Map an accounting file to your budget
Point each deal-naming value at a project and each cost value at a budget line.
An accounting file divides work up in its own vocabulary. This page is where those values are pointed at yours: each value that names a deal points at a project, and each cost value points at a budget line.
The roles, meaning which dimension is the cost code and how the file divides into deals, are chosen on the settings row for the connection. This page is the layer under that, where the values themselves get placed.
Unmapped values
Unmapped values are listed first, because those are the work. A value left unmapped simply does not count toward a budget, which is the right answer for the accounts a developer does not track as job costs. It is a decision you can leave made.
Who can
- Settings & people at edit or better: anyone who can change settings and invite people.
How to
The step-by-step walkthrough for this page comes from the in-app guide, which is not on this release yet. Everything above describes what the screen does and who can open it.
Related pages
Known limits
Mapping needs settings at edit. Somebody who cannot edit settings is sent back rather than shown a page of selects they cannot use.
The mapping and the roll-up it feeds run against real data. The sync that pulls from a live company file, and the bill it would write back, have been exercised against staged files rather than against a customer's own company.