Skip to main content
Transaction Data Requirements | Mav Deals

Overview of the transaction data that must be included on your Mav Deals spreadsheet to properly pull information into your Maverick account

Sabrina Garrett avatar
Written by Sabrina Garrett
Updated over 5 months ago

Mav Deals Video Walkthrough

Each transaction uploaded via Mav Deals must contain the following data for the following columns, which will be validated against FUB data:

  • Status (Active, Pending, Closed, Cancelled)

  • Type (Buyer, Seller)

  • Lead Source (FUB Source field on the lead record)

  • FUB Lead Id (FUB ID on the lead record – pulled from FUB URL)

  • Agent 1 (Name of the agent associated with the transaction)

Any transactions with Status or Type values that do not match the specified values will not be imported!

Agent 1's name should match their name exactly as it appears in FUB.

Transactions without Lead Source, FUB Lead Id, or Agent 1 values will still be imported and will appear in data warnings for manual correction.

The following fields are required:

  • Acceptance Date

  • Closing Date

  • Street Number, Name, Unit Number

  • Client 1 Name

  • Client 1 Role (Buyer, Seller)

  • Client 1 Email

Transactions with missing or erroneous data in these fields will still be imported and may need to be fixed via data warnings or the Transactions tab in MaverickRE.

The following fields are suggested to enhance the value of the insights that can be seen in MaverickRE if recorded:

  • Zip

  • Total Commission

  • Brokerage Kept Commissions

  • Agent Paid Commissions

  • Referral Paid Commissions

  • Agent 1 Commission Paid

The remaining fields are not currently utilized in Maverick, but may be in the future:

  • City

  • State

  • List Price

  • Listing Date

  • Agent 2/3

  • Agent 2/3 Commission Paid

  • ISA 1/2 Name

  • Client 2/3/4 Name

  • Client 2/3/4 Role (Buyer, Seller)

  • Client 2/3/4 Email

Important Note: Until we have communicated how many transactions resulted in exceptions (errors) and how those exceptions may be addressed, do not make any changes/corrections to the transactions within the platform as we may need to completely purge the records from the database, in which case any changes would be lost.

This sample spreadsheet contains five transactions that could be successfully imported into Mav Deals without resulting in any exceptions or data warnings: Mav Deals Example Transactions

Did this answer your question?