Appearance
Color theme
Appearance
→Supporting documents and evidence.
Deal documents and asset evidence.
Saved results for investment discussions.
Research requests and saved results.
Source-backed research and comparisons.
Document folders and source access.
→Documents for asset and buyer review.
Portfolio reports and source dates.
Servicing records and supporting evidence.
Receivables from accounting files.
Financial records and source identity.
Receivables and accounting records.
Receivables for local review.
Accounting sources for obligations.
Enterprise receivables and supporting events.
Vendor names and marks belong to their respective owners. Google Drive is a trademark of Google LLC. Microsoft, Microsoft Excel, SharePoint, and Microsoft Teams are trademarks of the Microsoft group of companies. SAP is a trademark or registered trademark of SAP SE or its affiliates in Germany and other countries. Slack is a trademark and service mark of Slack Technologies, LLC, registered in the U.S. and other countries.
Intuit and QuickBooks are trademarks of Intuit Inc., registered in the U.S. and other countries. This material has not been approved by Intuit.
OpenAPI Spec — download the machine-readable contract for MINT cohort-definition HTTP access, including the complete response schema.
Use the MINT Asset Passport to inspect a receivable and the evidence behind it. The record carries its identity, amount, evidence references, and current state so the team can return from the investment record to the exact source supporting each field.
Use the MINT Collateral Integrity Report to review a selected pool. Keep concentrations, reserves, conditions, and the source date together so the team can assess the same package without losing its scope.
Use the MINT Exception Report to focus on checks that need attention. Each exception identifies the affected records, the reason, and its supporting source so the team can review the issue and retain the outcome.
Use the MINT Forward Flow Term Sheet to bring a saved package into the deal discussion. The record carries the economics, conditions, discussion terms, and exact saved-result reference so the team can compare terms against the same assets.
Explore Allvue · Explore S&P iLEVEL
Use the MINT System update to see what changed since a specified prior state. Keep the affected assets or program conditions beside the old and new source references so the team can trace the change and decide what to review next.
Identify the system, account, and records needed for the task. Retain source IDs and dates. Keep reading data, preparing a result, and changing an external system as separate actions.
A copied file retains its original source date. Another source must not silently replace the active batch or the original buyer terms. Open a guide for the data requirements and related MINT workflow.