Skip to content

What MySplitPay reads from your reports

Every line MySplitPay brings in from a report boils down to four pieces of information. Understanding what they are — and how they organize what you see — explains most of what happens in the app.

Whether a file is recognized automatically or through a custom mapping, each line is read for the same four things:

FieldWhat it isWhat it drives
MIDThe processing account numberWhich MID the line belongs to — created automatically if it’s new
DBA nameThe merchant’s business/location labelHow the MID is labeled everywhere in the app
CommissionThe residual/commission amount for the lineThe amount that’s split between you and the assigned rep
PeriodThe month the line belongs toWhere the line lands in ledgers, filters, and statements

The file itself is recognized by the way its columns are arranged — that’s how MySplitPay knows which processor a file came from without you telling it each time.

Everything is organized by MID and month: one MID’s activity in one month makes one commission line. That single rule has a few practical consequences:

  • Duplicates are ignored. If the same MID shows up for the same month in more than one uploaded file, it’s counted once — the most recent upload wins. That’s why re-uploading a corrected file is safe.
  • New MIDs create themselves. A MID that’s never been seen before is added to your book automatically, carrying the DBA name from the file. It arrives unassigned — link a rep to it and their split applies from there.
  • Commissions follow the period. A line’s period decides which month it counts toward in every view — so a rep’s ledger, the Commissions view, and period filters all agree.

Lines that can’t be read cleanly raise warnings on the report — you’ll see the count in the Reports list and the details on the report’s page, alongside the original lines exactly as they came in. Warnings don’t block the rest of the file; they flag the lines worth a second look.