Problem How It Works Platform ROI Calculator Case Study Playbook
Book a Demo
Home/How It Works
How Fullcast Works

From processor file to agent statement in one controlled workflow.

Same six steps, every period. Each one is defined once, runs automatically, and leaves a record — so the monthly residual run becomes a review, not a rebuild.

Problem 2How It Works 3Platform 4ROI 5Case Study
1

Import reports

Upload any processor export.

2

Match MIDs

Map merchants to agents.

3

Apply rules

Splits & overrides.

4

Calculate

Payouts per agent.

5

Statements

Branded & itemised.

6

Approve

Lock & audit.

Step by Step

What happens in each stage.

1

Import processor reports

Upload exports from each processor — CSV, Excel or fixed-width. Saved mapping templates recognise each processor's format, so importing the next month's file is a single step instead of a manual cleanup.

Any format
2

Match merchants & MIDs

Each MID is matched to the right merchant, agent and reporting hierarchy. New and unmatched MIDs are flagged for review rather than silently dropped — nothing slips through unallocated.

No orphans
3

Apply split rules

Splits, manager overrides and partner shares are applied from rules you define once — by agent, merchant, product or BPS band — not from formulas copied down a column. Change a rule and it applies cleanly across every affected MID.

Rules, not formulas
4

Calculate payouts

Residual amounts compute per agent, per merchant, with every figure traceable back to its source line. Open any payout and see exactly which residual, rate and rule produced it.

Fully traceable
5

Generate statements

Branded, itemised statements are produced for every agent automatically — consistent, professional, and ready to send or share through a portal. No more hand-built PDFs.

Automatic
6

Review & approve

Approve the run, lock the period, and retain a complete audit trail of every import, rule change and approval. The cycle closes cleanly — and is fully defensible later.

Locked & audited
What Makes It Controlled

The difference is repeatability.

Same process every month

The workflow doesn't drift. Last month's rules, templates and hierarchy carry forward, so the run is consistent regardless of who presses go.

Review, not rebuild

Each cycle is a check-and-approve step on top of rules that already exist — not a fresh spreadsheet assembled under deadline.

Nothing lives in one head

Rules, mappings and history are in the system, not an analyst's workbook. The process survives leave, handovers and growth.

Next — Step 3 of 5

See the capabilities behind the workflow.