Skip to content

Column mappings for registers and bank statements

Tell the importer which column of your register or bank statement holds each field, how dates are written and how amounts are signed; a mapping whose headers match a file is then used automatically.

Registers and bank statements come in many layouts. Files that follow the platform template, or whose headers the importer recognises, need no mapping. For any other layout, save a column mapping once; every later file with the same headers uses it automatically.

Everyone can see the mappings. Managers, partners and firm admins create, change and delete them.

Create a mapping

Steps

  1. Open Data imports, then Column mappings, and choose New mapping (or start from a template button).
  2. Give it a Name and say what it is For (a purchase or sales register, or a bank statement).
  3. Paste the file's header row, one header per line, exactly as the file prints them.
  4. Under Which column holds each field, pick the column for each field. Required fields must all be mapped.
  5. Say how Dates are written as (day, month, year such as 31-03-2026, or another order) and the Signs of amounts (positive with the document type giving the direction, or signed as in the books).
  6. Tick Use as the firm's default for this kind of file if most of your clients' files look like this, and save.

When you upload a register you can also pick a mapping by hand under Column mapping.

Example

A synthetic client's purchase register has headers "Bill No", "Bill Dt", "Party GSTIN", "Taxable Amt", "IGST", "CGST", "SGST". You map them to document number, document date, supplier GSTIN, taxable value and the three tax heads, and choose "Day, month, year".

Last reviewed 27 October 2026