The Scenario
You are a compliance analyst at a lending company. Underwriting just sent over a batch of 30 loan applications that require KYC review. Each applicant connected at least one bank account through MX during the application process. Your Excel workbook has user GUIDs in column A, member GUIDs in column B, and applicant names from the application form in column G. Columns C through F are empty.
The underwriting team needs the owner verification results by end of business.
The bad version:
- For each of the 30 rows, call the MX list-account-owners endpoint using the two GUIDs from that row.
- Parse the JSON response and paste owner name, email, and address into columns C, D, and E.
- Manually compare the name in column C to the application name in column G for each row and write the verdict in column F.
Thirty rows, thirty API calls, thirty manual comparisons. You will spend as much time formatting as you spend pulling data.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent that runs inside your Excel workbook. It reads the GUIDs already in your workbook, fetches MX account owner data for each row, and performs the name comparison inline — writing results back to the right columns automatically.
For each row in this workbook with a user GUID in column A and member GUID in column B, fetch account owner details from MX and write the legal name, email, and mailing address to columns C, D, and E — then in column F compare the owner name to the applicant name in column G and write "Verified", "Mismatch", or "No data".
What You Get
- Column C: legal owner name from the MX account record.
- Column D: email address on file.
- Column E: mailing address.
- Column F: "Verified", "Mismatch", or "No data" based on name comparison to column G.
What If the Data Is Not Quite Ready
Owner names include middle names that the application form doesn't capture
For each row with user GUID in column A and member GUID in column B, fetch the MX owner name — in column F compare first and last name tokens only to the applicant name in column G and write "Verified", "Partial match", or "Mismatch".
Some applicants have joint accounts with two account owners
For each row with user GUID in column A and member GUID in column B, fetch account owners from MX — if multiple owners are returned, write each to a separate row repeating the GUIDs, number the owners in column H, and compare each owner name to the applicant name in column G in column F.
You also need to verify the address against what the applicant submitted
For each row, fetch MX owner name and address — write to columns C and E — in column F compare owner name to applicant name in column G — in column H compare the MX address to the application address in column I, writing "Address match" or "Address mismatch".
You want the full underwriting package: all 30 rows verified, name and address comparison, joint-account handling, and a compliance summary
For each row with user GUID in column A and member GUID in column B, fetch owner name, email, and address from MX and write to columns C, D, E — compare name to applicant name in column G in column F — compare address to application address in column I in column H — in a Compliance Summary worksheet show total verified, total name mismatches, total address mismatches, and total no-data rows.
Try It
Get the 7-day free trial of SheetXAI and open any Excel workbook with applicant GUIDs, then ask it to pull MX account ownership data for the full batch and flag any discrepancies against the application form. For building a statement index for those same accounts, see the statement index article.