Fee files in
Agent Core takes its facts from the files the fund platform publishes each business day under the institution’s selling-agent code, and from the institution’s private-fund system. Every batch is landed as received, checked against its own header, and only then promoted. A batch that does not add up stops the day’s calculation.
Who may do it: the system pulls on schedule · Commission Admin (re-pulls, uploads, resolves) · System Admin (schedule and connection) · Compliance Viewer (reads).
What comes in
Section titled “What comes in”| File | What Agent Core uses |
|---|---|
| Allotted transactions | Transaction ID, status, type (subscription, redemption, switch-in, switch-out), AMC, fund, unitholder, allotment date, NAV, amount, units, fee and brokerage fee with their VAT and withholding, tax invoice number, IC licence and IC code, branch and channel, original transaction ID |
| Unitholder balances | Units, amount, NAV and NAV date per unitholder and fund, each business day |
| Account data | The unitholder-to-customer link already used by CDD Core |
| Dividends | Reinvestments, so they earn no upfront; cash dividends for statements |
| Private funds | NAV and holdings from the institution’s private-fund system, on the same daily rhythm |
Only transactions with status allotted earn anything.
How a batch lands
Section titled “How a batch lands”- Pull. After the fund platform publishes the business date’s files, Agent Core signs in, downloads each file and keeps it exactly as received, with its hash.
- Check. The record count and as-of date in the file’s own header are the control totals. Every row is validated.
- Promote. Rows that pass become transactions, balances and NAVs. A transaction already held, or a balance for the same unitholder, fund and day, is not loaded twice.
- Run. The day’s calculation starts only when every expected batch has passed.
Ingestion screen
Section titled “Ingestion screen”One line per batch: file, business date, received at, record count against the header, status. From here the Commission Admin can re-pull a date or upload the same files by hand, which serves the days the connection is down and testing before go-live. A re-pulled batch that is already loaded changes nothing.
Fee field and fee master
Section titled “Fee field and fee master”The fee on each transaction is the starting point. The fee master gives the expected fee for that fund and date: a difference beyond tolerance opens a FEE_MISMATCH exception, and a row with no fee falls back to the fee master. Which fee field is the distributor’s revenue is set per AMC.
What the system does or refuses
Section titled “What the system does or refuses”- A batch whose count does not match its header blocks the run and opens an exception. It never produces part of a commission.
- No manual transaction entry. Figures come only from the files.
- The original file is kept with its hash, so any figure traces back to the row it came from.