For the revenue that arrives as a spreadsheet: distributor sell-through, marketplace statements, a usage export from billing.Not every euro a partner earns passes through your CRM. Distributors report sell-through monthly, marketplaces settle on their own statement, and usage-based revenue often lives in a billing database nobody has connected. That money still has to be paid on the same rules as the rest of the program. A File upload plan is where it goes: you map the columns of one sample file, and from then on each period is an upload, a short review, and a set of commission lines that behave like every other line in Introw.
What you’ll achieve
A commission plan that reads files, a mapping saved on it so nobody re-does the column work, and this period’s file imported into pending commission lines, each one traceable back to the row it came from.Before you start
1
Get write access to commission plans
You need permission to build plans and to run imports.
See Internal roles.
2
Have the partners in Introw
Rows match against partners that already exist. A row for a partner Introw does not know goes on hold, so import your partners first.
See Partner management.
3
Have a representative file
A CSV or
.xlsx up to 50 MB, with the columns a normal period carries. Use a real export rather than a hand-made example: the mapping you build here is the one every future file has to fit.Steps
Build the plan
1
Create a plan on the File upload source
Go to Commission plans and create a plan. Name it for the file it will read, such as “Distributor sell-through”, then on Data source choose File upload, described as “Import commission events from a CSV or Excel file”.A file plan skips two steps you know from CRM plans. There is no Conditions step, because the file is the filter: the rows you upload are the rows that earn. There is no Enrollment step either, because the plan’s partners are whoever its rows match.
2
Upload a sample and map the columns
Upload your sample file. Introw reads it, shows the worksheet and header row it used, and lists the columns it found. Nothing is imported at this point: a sample only builds the mapping.Map the columns that matter:
- Partner - the column that names the partner, plus Select how to match: Introw partner ID, Partner external ID, Partner name, Partner domain, or a CRM record through its record ID or one of its properties. Introw proposes a match field from the sample itself and shows how many sampled rows resolve, and to which partners, before you commit.
- Amount - the money the row is worth. Add a Currency column when the file mixes currencies.
- A date, so rows land in the right plan period.
- Description, which prints on the commission line and on the partner’s statement.
- Unique row ID - the identifier your source system already gives each row.
3
Set what a row pays
On Reward, pick one of three, paid once per row:
- Full amount pays the amount in the row as provided. Use it when the file already carries the commission.
- Percentage takes a percentage of the row amount.
- Fixed amount pays a set reward per row, whatever the row is worth.
Import a file
1
Upload the period's file
Go to Imports, start an import, and pick the file upload plan it belongs to. Introw uploads the file, reads it against the plan’s mapping, and checks every row. It runs in the background, so you can leave the page and come back.
2
Work the rows on hold
Rows arrive as Ready, On hold or Conflict, and every held row says why: no partner match, an ambiguous one, no rate that applies to that partner, a date outside the plan period, a currency that cannot be converted, or an amount too large to store.Assign a partner to a held row, or skip it, one row at a time or over a selection. Skipped rows create nothing. Needs attention filters the list down to the imports that still have rows waiting on someone.
3
Finish the import
Finish import books the commission. You can finish with rows still unresolved, and the button says how many you are leaving behind, so it is a decision rather than an accident. Lines are created in the background, and no payment is sent by finishing an import.
Verify it worked
The import reads Completed, and its rows read Imported. The commission lines are on Commission lines as pending lines against the matched partners, ready for your normal review and the next payout run, and each one carries the file, the worksheet, the row number and the row ID it came from. Partners see their share in the portal as they do for any other line.Good to know
- A wrong import can be corrected. On a completed import, select imported rows and skip them: their unpaid commission lines are voided and their row IDs are freed, so the corrected file imports them again. Rows whose commission is already paid cannot be skipped.
- Re-uploading is safe. With a Unique row ID mapped, a row that was already imported is skipped on the next file, and a row whose figures changed under an ID you already used is flagged for you rather than silently overwritten. Without one, Introw falls back to exact deduplication on the file name and row number.
- Negative amounts are credits. A clawback row reverses, so a correction file nets against what you already booked instead of needing a manual adjustment.
- The mapping is the plan’s, not the file’s. Editing it applies to future imports; imports that already ran keep the mapping and the rates they ran with.
- Every import is kept. A file that never created lines can be discarded; a completed one stays for the audit trail and for the duplicate check on the next file.
Related
Build and launch a commission plan
The CRM and billing version of the same wizard.
Commission lines
Review, adjust and approve what a plan produced.
Pay a payout cycle with Introw Pay
Turn approved lines into money in partner accounts.
Implementation reference
Data sources, rewards, versions and enrollment.