MBS Ops Network — operational [email protected] (888) 663-9319 LinkedIn
Alpha Financial Software
Home/Vendor checklist
Evaluation guide

What to ask an MBS operations vendor.

Most systems that claim to handle Agency MBS handle part of it. These are the questions that show you which part. Ask them of us, and ask them of anyone else you are looking at.

Trade capture and matching

Does it start where the trade starts?

01

Does it match through CTM and RTTM directly?

Matching that depends on a file drop or a manual upload is not matching. Ask whether the system connects to DTCC directly and what happens to an unmatched trade.

02

Does it process both sides of the market, or only yours?

A buy-side tool that cannot model the dealer side leaves half the workflow outside the system. Ask whether the same platform runs dealer operations.

03

Does it handle Megas and non-TBA-eligible securities on the same workflow?

Most of the month is standard TBA. The exceptions are where the manual work concentrates, and where systems quietly hand the problem back.

04

How does it surface exceptions?

Every vendor says straight-through processing. Ask what happens on the trades that are not straight-through, and whether the team works a queue or works the breaks.

Offsetting

Can it actually close the position?

05

Does it generate and deliver the assignment, or produce a document someone emails?

This is the question that separates automation from a template. Ask how long from offset to the assignment reaching the third dealer, and whether anyone touches it. Why this matters →

06

Does the system execute the round robin, or prepare it for a trader?

There is a large difference between assembling a round robin and placing the trades. Ask whether the platform connects to the venue and executes, or whether it hands the work back to the front office. How ours works →

07

Are pair-offs performed automatically, every day, with no cut-off?

Pair-offs are the easy case. If they are not fully automatic and unconditional, ask what else is not.

08

Is every digital assignment stored and retrievable?

Assignments are legal documents. Ask where they live afterward and how you produce one two years later for an audit.

Allocations and pool data

Is the pool data real, and is it current?

09

Is the vendor a FICC-approved EPN vendor?

This is a yes or a no, and it is checkable. Ask for it early.

10

Are allocations validated against the full agency pool universe?

A sample or a cached subset is not the universe. Ask what the validation runs against and how often it refreshes.

11

Is validation re-run on every notification and every substitution?

Pools get substituted. A system that validates once at allocation and never again will pass a bad pool through.

12

Are SIFMA good delivery guidelines and TBA stipulations checked automatically?

Ask whether the system enforces the rules or expects the operator to know them.

Reporting and messaging

Does the output reach everyone who needs it?

13

Is settlement reporting SWIFT-compliant and scheduled?

Ask whether reporting goes out on a schedule without anyone starting it, and what message types are supported.

14

Can it reach counterparties who are not on SWIFT?

Not every counterparty is. Ask what happens to those, and whether the answer involves somebody sending something by hand.

15

Is there a delivery log?

Ask how you prove a report was sent, when, and to whom. If the answer is a sent folder, that is the answer.

16

Is reconciliation daily, and is it across counterparties?

Reconciling your own book is table stakes. Ask whether the system reconciles what you think you have against what your counterparty thinks they have.

Integration and the counterparty side

Does it fit what you already run?

17

What does it connect to, and how?

Ask for the list. OMS and EMS platforms, clearing utilities, trading venues, pool data providers, and whether the connection is API, SFTP or a file someone drops.

18

Can transactions flow into dealer books directly?

A lot of this market still runs on mainframes that were never designed to take a modern feed. Ask what the integration options actually are.

19

Does your counterparty see the same data you see?

Most systems automate one desk. Ask whether the counterparty can see the trade and its clearance impact, or whether they find out by email. How the network handles this →

20

Who carries the development cost when the rules change?

Central clearing is coming to this market. Ask whether adapting to it is your project or theirs.

And the vendor itself

Four more that have nothing to do with the software.

21

How long has it been in production?

Not how long the company has existed. How long this software has been running real settlement for real firms.

22

What are the security certifications?

Ask for ISO 27001 and ISO 22301, and ask when they were last renewed rather than whether they exist. Ours are here →

23

Is there an independent financial health rating?

You are taking a dependency on this firm for years. Ask whether anyone outside it has assessed whether it will still be there.

24

Who trains your team, and what happens at go-live?

Ask what implementation looks like, how long it takes, and who is on the other end of the phone in month eighteen.

We wrote these because they are the questions we get asked by the firms that evaluate us most carefully, and because a buyer armed with them makes a better decision than one working from a feature grid.

Ask us all twenty-four.

Bring the list to a demo. We will go through it in order.