Background & Example
This article follows up on a case in which payment transactions were not being created in M1. Because GrowthZone does not have direct access to M1 beyond seeing the flow of requests, an example from the list was sent to M1 support for review. The example was the agent Nathaniel Christian. M1 support confirmed that, at the time of the transaction, Nathaniel was set as inactive in M1. The payment still went through because the Default NRDS ID was attached to it, but the record is created in M1 only if the agent’s status is active when the payment goes through. This is the same scenario seen with Kristen Swanson: if the payment shows under the Default NRDS ID in M1, the financial record must be manually added by association staff.
Here is the response received from M1 Support:
Nathanial was re-activated briefly on 2/2/2022, and then reactivated 3/9 (and remains active today)
That payment was sent with a different member ID - 176518216, matching staff person Susan Manners. (This is the Default ID for your association)
So if you sent those Financial adds from 2/2 5:25pm - 3/9 6:12pm, then that’s where I’d expect you get the 3305 and 3330 error codes. Nathaniel’s payment was processed on 2/23/22
Below is the original list, annotated with the information received from M1 support. The transactions in this list would need to be manually added to the agent’s record. Use it as a guide to understand when a record is not automatically created in M1 and would therefore need to be created manually.
| First Name | Last Name | NRDS ID | Date Added | NRDS Error | Notes |
| George | Assali | 165102145 | 2/28/2022 | The MemberStatus must be either A, S, or P. | |
| Nathaniel | Christian | 176510465 | 2/1/2022 | 176510465 is not a valid incurring member in the NRDS system | |
| April | Cuneo | 176510358 | 2/7/2022 | The MemberStatus must be either A, S, or P. | |
| Jeanette | Hamming | 175516415 | The MemberStatus must be either A, S, or P. | ||
| Stephanie | Hauge | 175530611 | 3/1/2022 | The MemberStatus must be either A, S, or P. | |
| Laura | Heffington | 176510419 | 2/7/2022 | Default ID was used in the transaction. Financial record will need to be manually added by staff to M1 | |
| Kim | Kanner | 176517917 | 3/15/2022 | The MemberStatus must be either A, S, or P. | |
| Erin | Mann | 176510521 | The MemberStatus must be either A, S, or P. | ||
| Eric | Nissen | 207501410 | 2/23/2022 | The saleable item is not mapped in the NRDS financial mapping in GrowthZone. This is available from the Finance Settings (RE) page under Settings, Real Estate Edition section. | |
| Chloe | Nowell | 175529146 | 1/18/2022 | LFRO fees are not mapped to be sent to NRDS/M1 same as cell F11 | |
| Benjamin | Oren | 176510472 | 2/17/2022 | Paid by Rone Oren. Transaction will need to manually added to Benjamin’s record in M1 | |
| William | Sculley | 176510388 | 176510388 is not a valid incurring member in the NRDS system |
The Fix
Follow these steps to resolve the issue for any transaction that did not create a financial record in M1:
- In M1, confirm whether the payment posted under the agent’s NRDS ID or under the association’s Default NRDS ID. If it posted under the Default NRDS ID, the record was not tied to the agent automatically and must be added manually.
- Verify the agent’s status in M1. A financial record is created automatically only when the agent is active (MemberStatus A, S, or P) at the time the payment goes through.
- Manually add the financial record to the agent’s record in M1 for each transaction flagged in the list above.
- If a fee did not transmit at all (for example, an LFRO fee), confirm the saleable item is mapped in the NRDS financial mapping. This mapping is available from the Finance Settings (RE) page under Settings, Real Estate Edition section. Add the mapping if it is missing.
- To review or manage the M1 connection itself, go to Settings, Real Estate Edition section, click M1 Settings.