Match each source column to the job it does

Start with the five required meanings

On Match columns, select a source heading for every field marked with an asterisk. The reference should remain useful for finding the original transaction, and the item should describe the individual service or product. Earning staff member must identify the person whose rate applies. Blank staff cells become Unassigned and remain held even if a rule named Unassigned exists. Check the source, correct the earning person or exclude the line; the cashier or account owner does not automatically earn the sale. Use Change file when the export cannot provide the necessary itemised evidence.

Keep missing values distinct from zero

Signed tax amount and Reported commission may be set to Not in this file. A blank tax cell means no explicit tax was supplied; an explicit zero remains zero. Under an exclusive basis, missing tax uses the configured inclusive tax rate, while supplied tax is subtracted directly. A blank reported commission means no source comparison is available. Mapping a column full of zeroes instead asserts that the source actually reported zero for every line.

Give service and retail their own classification

Map Service or retail when the file contains a category column. Recognised service labels include service, services, treatment and booking; retail labels include retail, product and products. Other mapped values become unresolved categories for review. If you leave the category unmapped, All rows are starts at Require category review, holding those rows until you check each category. Choose Services or Retail products only when the entire file fits that category. Do not use a service default for a mixed file simply to avoid category questions: the wrong selection can choose the wrong percentage.

Remove date ambiguity before the preview

Dates with slashes defaults to DD/MM/YYYY (Australia), with MM/DD/YYYY (US) available. Under those options, 09/10/2026 means 9 October or 10 September respectively. YYYY-MM-DD avoids that ambiguity and is accepted directly. The parser checks actual calendar dates in the supported 2000–2100 range. It does not infer a timestamp’s timezone or choose between invoice date and payment date for you. Map the date field that your intended commission period actually uses.

Test the mapping with a known line

For a fictional service, Amount is $220.00, Tax is $20.00 and Reported commission is $80.00. With a later exclusive basis and 40% service rate, the expected commission is $80.00. Mapping the $20.00 tax column as sales would produce a very different input even though it is a valid number. Compare one sale, one refund and one retail line when those categories exist. Check references with leading zeroes against the original export too.

Save and apply a checked mapping

Only one compatible profile with exactly matching ordered headers applies automatically, before you edit the fields. Multiple exact matches require a choice. A profile with changed column order can be applied manually when its mapped columns remain available; missing mapped columns block it. The notice shows the applied name and version.

You can also create, edit or remove profiles under Settings & backups → Import profiles. Profiles store column choices, not sales, and are unavailable in the demo. Saving one does not import data or prove that later values beneath the same headings mean the same thing.

1. On Match columns in an account workspace, enter Mapping name and choose Save mapping.
2. For a later file, use Use a saved mapping and choose Apply mapping.
3. Check the selected columns, Dates with slashes and any category default before Preview import.
4. To update the applied mapping, save its existing name; a different name creates another mapping.