Contact
Loan Prime is administered privately for the organization that owns this deployment. Use the established internal support channel for access, correction review, borrower data review, or audit investigation requests.
Access support
If you cannot sign in, ask an administrator to confirm that your email address is active, your Supabase account is approved, and your role has permission to use the requested workspace.
Collection or borrower corrections
For incorrect collection entries, operators should use the latest-entry adjustment workflow when the affected transaction is still the most recent borrower record. The system recalculates the latest amount, interest, principal, commission, remaining balance, and audit tag together.
What to include
Correction requests should include the borrower name, collection date, expected paid amount, reason for the correction, and any internal reference that helps an administrator verify the change. Do not send sensitive borrower details through public channels unless your organization has approved that channel for private operational data.
Operational review
Administrators can compare the borrower timeline, audit log entry, calculated interest, paid principal, and commission impact before and after a correction. If the latest-entry guard blocks the change, create a management review instead of bypassing the guard, because older edits can invalidate later balance calculations.
Privacy or security
For privacy, security, or account removal requests, contact the deployment administrator responsible for this Loan Prime instance.
Deployment support
If a new frontend release references a database RPC that returns not found, apply the matching Supabase migration to the remote project and refresh the PostgREST schema cache before treating the deployment as complete.
Response expectations
Support teams should confirm the request type, requester identity, borrower reference, affected screen, and expected outcome before making operational changes. Access issues normally require account and role review. Data issues require audit review. Release issues require build version, migration status, and deployment target checks.