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.

A budget line belongs to one project

A cost value is placed per deal: the same accounting account can point at one project's budget line and, separately, at another project's. What it may never point at is a budget line belonging to a different project than the one you are placing it under. That is refused here, and refused on the match queue too when several suggestions are accepted at once.

The reason is arithmetic. A cost coded to another project's budget line appears on none of that project's rows, because the rows are its own codes, while still being counted into the Actual total at the bottom. The column then does not add up to the figure above it, and a number that does not add up is worse than one that is missing.

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.