Evaluate · one agent, in depth

ETF basket creation process: how an agent builds and tests the basket

In the ETF basket creation process, a file of securities and cash is built for one creation unit, tested with the custodian and exchanged by an authorized participant for new shares. Fund Launch Management gives the build-and-test work to a Basket agent that reads every rejection and never changes what is in the basket.

Updated · 13 min read

The ETF basket creation process turns a portfolio manager's basket into new ETF shares: the fund publishes a file of securities and cash that make up one creation unit, its custodian must recognise and be able to settle every line, an authorized participant delivers that basket plus or minus a cash balancing amount, and the fund issues the creation unit in return. Redemption runs the same way in reverse. For a new ETF, the process has to work once in test before it works for real, because the seed money itself enters as the first creation. Botminds' Fund Launch Management gives that build-and-test work to one agent, the Basket agent, which builds the basket and test files, runs them with the custodian, reads each reject file and reconciles it against the security master, while the basket's composition stays with the portfolio manager.

The account below follows one night in a fictional sample launch, Quillfield Short Duration Muni ETF, seen through its fund operations lead for ETFs. The rule text comes from Rule 6c-11 and the SEC's 2019 adopting release.

The Basket agent's job, step by step, with what it may never do

  1. Agent

    Build the basket file

    From the portfolio manager's basket, the creation unit size and the administrator's prices; every line cited to its source.

    Never: add, remove or resize a line

  2. Agent

    Build and send the test files

    In the custodian's format, through the custodian file transfer.

  3. Agent

    Read the reject file

    Line by line, against the security master, the official statements and the custodian's own codes.

  4. Agent

    Find the cause

    Not set up, undeliverable quantity, identifier mismatch, stale price; states its confidence and asks a person below its threshold.

  5. A person decides

    Portfolio manager

    Decides any change to the basket, including cash in lieu of a security.

  6. Agent

    Retest

    Runs the next test file once the cause is fixed; records the result as evidence on the basket step.

    Never: mark the step done without an accepted file

  7. A person decides

    Authorized participant and operations lead

    Run the creation test on the accepted file; the seed follows under treasury policy.

The Basket agent's role and limits in Fund Launch Management. Its confidence threshold in the sample setup is 95%: below it, the agent asks a person instead of acting.

ETF creation and redemption process, explained

New ETF shares come into existence only in creation units, issued to authorized participants in exchange for a basket and, where needed, cash. Rule 6c-11 builds this into its definition of an ETF: a fund that "issues (and redeems) creation units to (and from) authorized participants in exchange for a basket and a cash balancing amount if any" (Rule 6c-11(a)).

Everyone else trades the shares on the exchange. The creation and redemption process is what keeps those market prices close to NAV: when shares trade rich, an authorized participant can deliver the cheaper basket and sell the new shares; when they trade cheap, it can buy shares and redeem them for the basket. The SEC's release describes authorized participants doing this both for their own account and on behalf of market makers and institutional investors, for a processing fee (SEC, Exchange-Traded Funds, 84 FR 57162).

Delivering securities rather than cash is the in-kind creation and redemption the ETF structure is known for. The fund does not have to sell holdings to meet a redemption, and it can hand appreciated securities to a redeeming authorized participant; the tax effect of that is a subject for the tax benefit of an ETF share class and the fund's tax counsel, not for the basket file. For the basket file, in-kind means every line must be something the custodian can receive and the authorized participant can deliver.

Creation unit size: what one unit is, and why it matters to the seed

A creation unit is "a specified number of exchange-traded fund shares that the exchange-traded fund will issue to (or redeem from) an authorized participant" for a basket and any cash (Rule 6c-11(a)). The rule leaves the number to the fund; it is set in the prospectus and the participant agreements.

The sample's creation unit is 50,000 shares, so at the launch price of $25.00 one unit is $1,250,000 and the $25.0 million seed buys 20 of them. The unit size also sets the basket's granularity. A $1.25 million basket of municipal bonds can carry only a sample of a 212-bond portfolio in deliverable sizes: $25,000 par of one bond, $20,000 of another. That is why the basket is designed by the portfolio manager rather than computed by scaling the portfolio down.

What happens when a basket test file fails? One night, logged

When the custodian rejects a test file, every step that needs an accepted basket waits: the authorized participant's creation test, the seed creation and the NAV dry runs on the seeded portfolio. In the sample, the reject file arrived at 6:42 p.m. on Monday, February 22, three weeks before first NAV.

One rejected basket, from reject file to retest: fourteen hours, logged

  1. 6:42 p.m.

    Custodian

    Reject file for basket test file 2: 3 of 58 lines, "security not found"

  2. 6:51 p.m.

    Basket agent

    Matches all three identifiers in the security master: new issues set up February 16 from the official statements; custodian setup never requested

  3. 6:51 p.m.

    Launch Conductor

    Tips the basket step: standard setup of 5 + 1 business days puts 6 at risk; first NAV would move from March 16 to March 24

  4. 7:02 p.m.

    Provider agent

    Asks the custodian's ETF team for the expedited channel, with a pre-filled setup file and the three official statements

  5. 7:20 p.m.

    Readiness agent

    Checks each bond on its own: official statement, security master and pricing vendor agree

  6. 7:48 a.m.

    Custodian

    Two of three set up; asks for the third bond's call schedule

  7. 8:02 a.m.

    Provider agent

    Answers from official statement page 3: callable on or after December 1, 2029 at par

  8. 8:36 a.m.

    Basket agent

    Runs test file 3: 58 of 58 lines accepted; four of six days recovered

  9. 8:40 a.m.

    Launch Conductor

    Two days still at risk: three options, with first NAV dates, to the Head of Product

Fictional sample launch in Fund Launch Management, February 22–23, 2027, as recorded on the slip. Each step carries its time and its source and can be replayed. 'Out' marks steps by outside parties.

The sample's operations lead for ETFs, Raj Malhotra, describes the old version of this night in one sentence: "A basket file fails on one CUSIP and the seed date is gone." Each retest round with the custodian used to cost days because the reject file arrived after hours, the security master and the custodian's file lived in different systems, and the person who knew the bonds were new issues was not the person reading the reject file. In the sample, by the time he started his day the cause was diagnosed, the custodian had been asked, a second check was done and the retest had passed.

The sample night in numbers

3 of 58

lines rejected in test file 2: new issues never set up at the custodian

6days

business days at risk when the basket step tipped

4days

recovered by 8:36 a.m., when test file 3 passed 58 of 58

Fictional sample data in Fund Launch Management. The remaining two days went to the Head of Product as options; she approved moving the seed wire from March 2 to March 9, and first NAV held on March 16.

Why the agent never changes the basket

The basket's composition is an investment decision and, under Rule 6c-11, a compliance one. The fund must have written policies for constructing and accepting baskets, and for custom baskets they must set "detailed parameters" and name the titles or roles of the adviser's employees "required to review each custom basket for compliance with those parameters" (Rule 6c-11(c)(3)). An agent that swapped a rejected bond for cash would be creating a custom basket outside the people the policy names.

So the Basket agent's limits are written into its role: it never changes basket composition, and cash in lieu needs the portfolio manager. In the sample, the cash-in-lieu option was still put to the Head of Product, as option B, with its consequences laid out: it would change the seed basket, which the portfolio manager decides, and the authorized participant needed two business days to load a custom basket, so it would not have held the original seed date anyway.

Fund Launch Management: what the agents did on their own, overnight

Slip screen, What the agents did on their own, overnight in 14 hours: 6:42 p.m. custodian reject file received, test file 2: 3 of 58 lines rejected; 6:51 p.m. Basket agent matched the 3 CUSIPs in the security master; 6:51 p.m. Launch Conductor tipped the domino, standard setup 5 + 1 business days, 6 days at risk, first NAV Mar 16 to Mar 24; 7:02 p.m. Provider agent asked the custodian for the expedited channel; 7:20 p.m. Readiness agent checked each bond on its own; 7:48 a.m. custodian 2 of 3 set up, asked for a call schedule; 8:36 a.m. Basket agent ran test file 3, 58 of 58 accepted, 4 of the 6 days recovered; 8:40 a.m. two days left for a person to decide. Below, the second check table: official statement, security master and pricing vendor agree for each CUSIP.
The fictional sample slip as the operations lead found it in the morning. The second check below the timeline is the Readiness agent's, made from the official statements and the pricing vendor without reading the Basket agent's working.

A second agent checks the fix, from different sources

A fix that the same agent proposes and verifies is not checked. In the solution, the Readiness agent re-checks every other agent's fix from independent sources and never reads the other agent's working. In the sample it checked each of the three bonds against its official statement and the evaluated pricing vendor at 7:20 p.m., before the custodian had replied, and found coupon, maturity and identifier in agreement with the security master.

That separation is the same one a fund already uses between people. The portfolio manager sets the basket, fund operations builds and sends it, and someone else confirms the prices. The design makes the agents keep it: the agent that builds the file cannot also be the one that says the file is right.

Build and check, kept apart

Basket agentReadiness agent
Does

Basket agent: Builds the basket and test files; reads reject files; reconciles each line to the security master

Readiness agent: Checks seed and first-NAV readiness; re-checks other agents' fixes

Sources

Basket agent: Portfolio manager's basket, security master, custodian reject files, administrator prices

Readiness agent: Official statements, the evaluated pricing vendor, the administrator's dry runs, the website file

Never

Basket agent: Changes basket composition; cash in lieu needs the portfolio manager

Readiness agent: Declares go-live; reads the other agent's working

Asks a person when

Basket agent: Its confidence is below 95%

Readiness agent: Its confidence is below 95%

Agent roles and limits as set in Fund Launch Management's sample configuration; the confidence thresholds are settings the Head of Product approves.

Who approves a custom basket, and who approves the re-plan?

A custom basket is reviewed by the people the fund's policy names, by title or role; that is the rule. A re-plan of the launch is approved by whoever the sponsor's own controls name; in the sample, a launch project manager proposes and the Head of Product approves with a reason code, and any seed movement needs the fund treasurer's second signature.

The sample's approval followed that chain. Option A, recommended: keep first NAV on March 16 by moving the seed wire from March 2 to March 9 and running the first NAV dry run on the test-file portfolio on March 4. The launch project manager submitted it as maker; the Head of Product approved it at 9:07 a.m. with reason code "Re-plan within float"; the treasurer confirmed the wire at 9:08 a.m. The agents did not move a date.

Fund Launch Management: the second check, the options and the decision

Slip screen sections 3 to 5. The second check: three CUSIPs with official statement, security master and pricing vendor values, all agree; test file 3 passed 58 of 58. The options: A, move the seed wire to Mar 9, recommended, first NAV Mar 16 holds, you approve and the treasurer co-signs; B, keep Mar 2 with cash in lieu for 3 bonds, first NAV Mar 16 not reachable because Kestrel needs 2 business days to load a custom basket; C, accept the slip, first NAV Mar 18. The decision: Tom Reyes maker submitted option A at 8:52 a.m., Nadia Okafor checker decides now, Claire Donovan second signer for the $25.0M wire.
The fictional sample's options, each with its first NAV date and who decides. Option B, cash in lieu, would have created a custom basket and needed the portfolio manager; the authorized participant's two-day load time meant it saved nothing.

Evaluating an agent for the basket process: what to ask

Any tool that touches the basket should be judged on what it refuses to do as much as on what it does. The SEC's examination priorities for fiscal 2027 note that registrants are adopting what the SEC calls "super intelligence" tools, and say the staff will look at whether firms continue to meet their existing, technology-neutral obligations (SEC, FY2027 Examination Priorities). For a basket, those obligations are the rule's: written basket policies, named custom-basket reviewers, and records of every basket exchanged.

Questions for any basket automation, before a launch relies on it

  1. Does it read your custodian's actual reject files?

    Line numbers, reason codes and formats, not a summary someone retypes.

  2. Can it see the security master and the custodian side by side?

    The sample's failure was visible only with both.

  3. Is basket composition outside its permissions?

    Including cash in lieu, which makes a custom basket.

  4. Is the check done by something other than the builder?

    From different sources, without reading the builder's working.

  5. Does it say how sure it is, and stop below a threshold?

    With the threshold a setting someone approves.

  6. Is every step logged with its time and source, and can it be replayed?

    So the next launch learns from this one, and an examiner can follow it.

  7. Does it keep the basket records Rule 6c-11(d) requires?

    Holdings, custom flag, cash balancing amount, authorized participant, five years.

Our evaluation list, from Rule 6c-11 and the fictional sample's failure.

What changes in the next launch

A slip that is only fixed will happen again. In the sample, once first NAV held, the Launch Conductor proposed a change to the series-trust ETF playbook: lengthen the custodian setup step for new-issue municipal bonds from three to six business days, so the next municipal launch asks a week earlier. It went to the Head of Product as a change request, because playbooks are settings a person approves.

That is where a basket agent pays back beyond one night: each reject file becomes a rule about when to ask, not just a fixed line. The portfolio composition file, field by field lists the other failure types to plan for, and the 485a filing and its evidence file applies the same idea of evidence on every step to the registration side. The solution is at Fund Launch Management.

Questions people ask

What is an in-kind creation?

An authorized participant delivers the securities in the fund's basket, plus or minus a cash balancing amount, and receives a creation unit of new ETF shares; an in-kind redemption returns securities instead of cash. Rule 6c-11 defines the ETF around this exchange of creation units for a basket.

How big is an ETF creation unit?

Whatever the fund specifies in its prospectus and participant agreements; Rule 6c-11 defines it only as "a specified number" of shares. The fictional sample fund uses 50,000 shares, $1.25 million at its $25.00 launch price.

Can an ETF's basket be all cash?

Yes, subject to the fund's basket policies. The SEC's 2019 release notes that an ETF may substitute cash for some or all of its holdings in the basket; a substitution that makes the basket non-representative is a custom basket and needs the custom-basket procedures and named reviewers.

Who builds an ETF's basket each day?

The portfolio manager decides what is in it; fund operations or a service provider builds the file, prices it with the administrator's sources and sends it out. In Fund Launch Management the Basket agent builds and tests the file and never changes its composition.

How long does a custodian take to set up a new security?

It depends on the custodian and the market; the sample's playbook assumed three business days for new-issue municipal bonds and, after this launch, proposed six. Sub-custodians in other markets take longer, which is why the sample's service levels allow 10 business days for them.

Fund Launch Management.
See it on your own files.

An agentic solution from Botminds. Agents run a mutual fund or ETF launch from idea to first NAV; product leads decide Book a demo, or explore how it works.