FeaturesPricingWhat's newHelpLog inStart free
Help/Data Sources

Map report columns

Tell SplitRun which columns in a report hold Merchant ID, Name, Profit, Revenue, etc. — done once per report type, then reused automatically.

Every provider formats its report differently. Column mapping tells SplitRun which columns in a file mean what — Merchant ID, Merchant Name, Total Profit, Revenue, Volume, and so on. You set this up once per report type; after that, every future upload of that report type is parsed automatically.

When you'll see the mapper

  • The first time you upload a new report type.
  • Any time a provider changes their file layout and you need to remap. Open the source's page or the upload's detail and choose to edit the column mapping.

Steps in the column mapper

The mapper walks through a short sequence:

  1. Mode — how the file is laid out: a single table, multiple tables, or stacked sections. Most reports are single-table.
  2. Upload a sample — a real file to read the headers from.
  3. Sheet — pick the worksheet (multi-sheet Excel only).
  4. Header row — tell it which row holds the column titles (reports often have banner rows above the real header).
  5. Map columns — match your file's columns to SplitRun's fields:
    • Merchant ID and Merchant Name (which merchant the row is for)
    • Total Profit (the residual/profit figure)
    • Revenue (if the report includes a revenue figure)
    • Volume, Agent/Sales Rep, and others as available
  6. Custom fields (optional) — capture any other column from the file (see below).
  7. Options — how to read the period (manually, from a column, from the filename, or from the sheet name), whether to aggregate multiple rows per merchant, and whether to skip footer/total rows.
  8. Preview — a parsed sample so you can confirm it looks right.
  9. Save Mapping — you can optionally upload the month's file immediately afterward.
If that sample upload hits a month you've already loaded, the mapper offers Replace existing / Add alongside / Cancel — the same choice the Upload page gives you. See Upload a report.

Custom fields

Sometimes a report contains a figure you need that isn't Profit, Revenue, or Volume — a fee column, a gross-sales column, or a vendor-specific number you pay an affiliate on. Custom fields capture it.

Define them in the mapping step (click Add Custom Fields), where the file's real headers are on screen:

  • Name — what you'll call it (e.g. Reported Revenue).
  • TypeCurrency (converted using your exchange rates) or Number (used as-is).
  • Source column — picked from a dropdown of the columns detected in your file. You can select several columns to be summed into a single value.

A custom field is file-level: one value per merchant, shared across all the income types in that file. The data source page keeps a summary of what you've defined, and fields can be edited in place (name, type, source columns) — no delete-and-re-add.

The Custom Fields section names the data source it's writing to, and warns if the sample file you loaded is missing columns this source's fields map — a sign the file belongs to a different source. Watch for that: adding a field while previewing the wrong file is how a mapping ends up on the wrong data source.

Using a custom field in your calculations

Once defined, a custom field can be chosen as the base for a deduction — both on a deduction stage in the revenue flow and on an individual agent's deduction. That's how you say "the affiliate earns 10% of this reported column" instead of of profit or remaining. See Choosing the base.

Why the Profit vs. Revenue mapping matters

Whether a report has a mapped revenue column affects the revenue-flow waterfall: if a revenue number is present, SplitRun uses it as Company Revenue; if not, it derives revenue from Profit × your split %. This in turn affects which commission bases are valid for that income type. See Choosing the base.

Good to know

  • Aggregation. Some reports list a merchant across several rows (e.g. one row per device or per app). Turn on aggregation so SplitRun sums them into a single per-merchant figure.
  • Mapping is reused. Once saved, you don't touch it again unless the layout changes — normal monthly uploads just work.
  • Multiple report types per source. Map each one separately; they can even have different currencies.

Next