Processed Deal Import

Follow

Zipi allows users to import processed deals (sometimes referred to as 'historical deals'). These deals have been fully completed usually outside of Zipi using a 3rd party system. Deals that are imported using the Processed Deal Import functionality cannot be edited in Zipi unless they are manually converted. Since Processed Deals are imported as Approved, the user conducting the import must have the permission to Approve Deals applied to their profile before import.

IMPORTANT: All deals entered into Zipi, regardless of how the data is entered, count towards the total deal balance (including imported).

Open Example of Deal Import CSV

  1. Any contacts referenced on a deal MUST already have a Contact record in Zipi BEFORE deal import is attempted. If it is an agent, the agent MUST already be in the Directory.
  2. On the CSV file, deals are separated by Deal ID, a string of characters that is unique to that specific deal. This means that any row that has the same Deal ID will be combined to the same deal in Zipi.  
  3. Each deal must have 1 row where the 'Entity Type' is Primary. If a deal has multiple rows of information the Primary row should be the first row in the series of many.
  4. Any information to be imported for a deal in columns E - AD must be on the Primary row. Any information entered in these columns on rows that are not the Primary will be ignored.
  5. Deals that are imported through the Processed Deal Import functionality will skip any compensation validation or checks and use the exact figures that were entered for import.
  6. All Columns listed below that have an Asterisk (styled in red bold font) are required fields. 
  7. At a minimum the User conducting the import must have the permission for Application Access, Import, Create Any Deal, and Approve Disbursement.
  1. Deal ID (any unique #)*
    • Description: This column is used to join multiple CSV rows for a single deal.

    • Requirements:
      - Cannot be empty.
      - Each deal must have unique value in this column.
      - Each row of the deal must have exactly the same values for this column.

      Example

  2. Entities Getting Paid from Commission (excluding Broker)*
    • Description: Name of the entity.
    • Requirements:
      - Must have a value on the Primary Entity row.
      - The entity MUST already exist in Zipi and match the Contact records 'Display Name'.
  3. Person or Entity's Email
    • Description: The import feature uses this email field when more than 1 contact is recognized with the same 'Display Name'. The email field will be used to determine which contact record to use in Zipi.
  4. Entity Type*
    • Description: Defines what type of participant this entity is serving as on this deal.
    • Requirements:
      - Cannot be empty
      - MUST have one of these values:
      -- Primary (agent that has primary responsibility for deal)
      -- Agent (additional agent that is participating on deal)
      -- Transfer - (others that are receiving some money on that deal)
  5. Type of Deal*
    • Description: The type of transaction this deal may be classified into.
    • Requirements:
      - Cannot be empty.
      - Must match one of these values EXACTLY:
      -- Seller
      -- Buyer
      -- Rental Tenant
      -- Rental Owner
      -- Referral
      -- Broker Price Opinion
  6. Buyer Name
    • Description: References the Buyer or Renter's Contact record in Zipi.

    • Requirements:
      - Contact MUST already be existing in Zipi.
      - Names in these columns must match EXACTLY to the 'Display Name' on the Contact record in Zipi.
      - Can have more than 1 name (separated by commas and enclosed in double quotes) Screenshot of Example.

  7. Listing (Seller) Name
    • Description: References the Listing or Landlord's Contact record in Zipi.

    • Requirements:
      - Contact MUST already be existing in Zipi.
      - Names in these columns must match EXACTLY to the 'Display Name' on the Contact record in Zipi.
      - Can have more than 1 name (separated by commas and enclosed in double quotes) Screenshot of Example.

  8. Deal Status*
    • Description: The current status in the deal's life-cycle.
    • Requirements:
      - Cannot be empty.
      - The ONLY accepted value for processed deal imports is 'processed'.
  9. Escrow Company Name
    • Description: This column contains information about Escrow Company
    • Requirements:
      - Contact MUST already be existing in Zipi.
      - Names in these columns must match EXACTLY to the 'Display Name' on the Contact record in Zipi.
  10. Zip
  11. State
  12. City
  13. Deal Address
  14. Closing Date*
    • Description: Enter the date that this deal was executed.
    • Requirements:
      - Cannot be empty
      - Date Format MUST be: MM-DD-YYYY
  15. Sales Price*
  16. Gross Commission
  17. Deal Royalty
  18. Deal Referral Sum
  19. Net Commission (Deal)
  20. Additional Deal Income
  21. Additional Deal Expense
  22. Deal Net
  23. Sales Total
  24. Additional Sales Income
  25. Additional Sales Expense
  26. Sales Net
  27. Company Split
  28. Additional Company Income
  29. Additional Company Expense
  30. Company Net
  31. Entity Company Split
  32. Entity Split
  33. Entity Referral (Income)
  34. Entity Referral (Expense)
  35. Entity Royalty
  36. Additional Entity Income
  37. Additional Entity Expense
  38. Entity Net

Comments

0 comments
Please sign in to leave a comment.