Investor and portfolio
Investor, folio, transaction, position snapshot, NAV, and statement-document records.
Normalize CAMS and KFintech reverse feeds into canonical transactions, positions, SIPs, commissions, exceptions, and batch summaries.
RTA Sync preserves source context while giving the rest of your product a common vocabulary.
Each report family stays meaningful instead of being forced into one generic row shape.
Investor, folio, transaction, position snapshot, NAV, and statement-document records.
SIP, STP, and SWP registrations, pauses, expiries, terminations, and rejections.
Exceptions, brokerage payouts, mandates, settlement issues, and unmatched source records.
RTA Sync does not execute purchases, redemptions, switches, SIPs, STPs, or SWPs. It keeps the records behind those workflows usable and current.
POST /v1/rta-sync/normalize
files=@kfintech-feed.csv
provider=auto
include_source=trueCAMS and KFintech reverse-feed files across investor, folio, transaction, position, SIP, NAV, exception, brokerage, mandate, and statement workflows.
CSV, XLS, XLSX, and DBF. You can submit one or more related files in a multipart request.
Start with direct file upload. Gmail, Outlook, and email-forwarding connectors can deliver RTA reports to the same engine.
No. It normalizes and reconciles the data behind distribution and wealth workflows; it does not execute orders.
Bring a CAMS or KFintech sample and the operating model behind it.