7. Optional columns

Extra fields your accounting system supports but doesn't require — Project, Area, Agent, currency rate. Set these up only if your accounting setup uses them.

Admin only, at Settings → Export target (/settings?panel=target), below the credentials.

Which columns are available depends on your export target. If your books don't use project or area coding, skip this page entirely.

Three ways to fill a column

Off — the column is left out of the export. The default, and correct for most organizations.

Fixed value — the same value on every document. Use when your setup requires the field but the answer never varies: one location, one default project code.

From master data — the value is looked up from a reference list you maintain. Use when the value varies per document and you want a controlled set rather than free text.

Setting up a reference list

Bind a column to master data and a new card appears under Settings → Master data for that column. Populate it like any other list — CSV import, live sync where supported, or by hand. See Import your master data.

Each entry is a code and a value. Once populated, the column can be set from that list during review.

A common use is a currency rate list: codes for each currency and their rates, so foreign-currency invoices carry the right rate without anyone typing it.

Advice

Start with everything off. Add a column when an import actually fails without it, or when your accountant asks for it. Every column you turn on is another field someone has to think about on every document.

Prefer fixed values where the answer never changes. A fixed value costs nothing at review time; a master-data list adds a decision per document.

Changing columns later

Changing a column's setting affects exports produced from then on. Documents already exported or pushed aren't retrospectively changed — re-export them if you need the new column on them.