Sign in to Fortress OSIntegration Partner · Screening
TransUnion + Fortress OS
Screen applicants for credit and criminal history inside Fortress OS. Submit, read the result, and make the call on one screen.
Updated · 3 min read
What is the TransUnion + Fortress OS integration?
TransUnion is a credit bureau. Fortress OS uses it to screen rental applicants for credit and criminal history. Your leasing team submits the application from inside Fortress, the result comes back on the applicant's record, and you approve or decline in the same place.
Key takeaways
Your team submits screening from the lease application, using details Fortress already holds.
Results land on the applicant record with a recommendation scored against the rent you entered.
Decline an applicant and Fortress builds the adverse action letter.
How does TransUnion work with Fortress OS?
Each property carries its own TransUnion code in Integrations Setup, so screening is billed and tracked at the site that ran it. When an application is complete, your leasing team submits it to TransUnion from the application itself. Fortress sends the applicant details it already holds, so nobody keys a name and a date of birth into a second system.
What data flows between the two?
Fortress sends the applicant's details along with the estimated monthly rent for the unit. TransUnion returns the credit and criminal result with a recommendation, and Fortress attaches both to the Credit and Criminal Status tab on that applicant. The rent travels with the application, so the recommendation reflects what the applicant would pay.
Who handles the setup?
Our integrations team handles documentation exchange, API keys, and end-to-end testing. Most TransUnion connections go live in a few weeks. You can request a setup any time.
Why should you connect TransUnion to Fortress OS?
A team running screening in a bureau portal keys the same applicant twice, then saves the result as a PDF someone has to hunt for six months later when an auditor asks. Running screening inside Fortress keeps the decision and the letter on the application they belong to.
What changes once you connect TransUnion?
Same screening tool. Different day-to-day for your team.
| Daily task | Without the integration | With Fortress OS + TransUnion |
|---|---|---|
| Submitting a screening | Your team opens the bureau portal and keys the applicant in again. | Your team submits from the application Fortress already holds. |
| Reading the result | You download a PDF and file it somewhere. | The result sits on the applicant record with the recommendation. |
| Approving with conditions | You track the condition in a note or an email. | You set approved with conditions as a status on the application. |
| Declining an applicant | Someone writes the adverse action letter by hand. | Fortress generates the letter from the screening result. |
Tags
- TransUnion
- TransUnion integration
- Screening
- Fortress OS
- integration
- property management software
- affordable housing
Frequently asked questions
Quick answers about how TransUnion and Fortress OS work together. Don't see your question? Ask us →
Where does TransUnion screening happen in Fortress OS?
On the lease application. Your team submits the completed application to TransUnion from the applicant's record, and the result returns to the Credit and Criminal Status tab on that same record.
Do we need a TransUnion account of our own?
Yes. You bring your own TransUnion relationship, and each property is set up with its own code in Integrations Setup so screening is attributed to the site that ran it.
Does Fortress decide who gets approved?
No. TransUnion returns a recommendation and your team makes the call. Fortress records the outcome as approved, approved with conditions, or declined, so the decision sits on the record where an auditor will look for it.
What happens when we decline an applicant?
Fortress creates the adverse action letter from the screening result, so the notice the applicant is owed comes out of the same system that made the decision.