These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Loan Origination System
- Features
- Organization and access
Organization and access
Keep organization membership and operating authority clear before instructions enter review.
OverviewMy instructions×
Loan Origination System · Organization and access
New
My instructions
Loan applications
| Record number | Subject | Status | Submitted at | Value date | Counterparty | |
|---|---|---|---|---|---|---|
| LA-77545 | Draft la-597 | Draft | 05 Oct | 14 Oct | BRR-1405 | |
| LA-62680 | Under Review la-193 | Under Review | 17 Oct | 21 Oct | BRR-5784 | |
| LA-69302 | Approved la-473 | Approved | 20 Oct | 29 Oct | BRR-2299 | |
| LA-79508 | Submitted la-796 | Submitted | 09 Oct | 18 Oct | BRR-9665 | |
| LA-17151 | Pending la-491 | Pending | 14 Oct | 18 Oct | BRR-6427 |
6 of 6 records
Draft la-597Loan applications · LA-77545
DraftSubmitted at05 Oct
Value date14 Oct
CounterpartyBRR-1405
What you can do
Establish the operating boundary
A lending operations team may coordinate instructions for more than one banking organization. Start each instruction in the right organization and give its preparer a named owner. The organization record carries its active state, time zone and currency. Team membership ties a person to that organization, so a reviewer can see which records are in scope before making a decision. A shared login or an ambiguous membership makes the later decision trail hard to explain.
The App Administrator maintains organization and membership records. That role can correct a member’s identity or organization, but it does not replace the Independent Credit Approver. The Credit Officer prepares instructions within the assigned organization; the Auditor reads the evidence without changing it. Set this boundary before a provider account or counterparty is selected for a live instruction.
How the work is organized
- Organization identity. Use the organization code, active state, time zone and currency to anchor the operating context.
- Named membership. Connect each team member to a user and organization, and keep inactive members out of current work.
- Separate authority. Give preparation, independent review and audit their own roles; retain the acting person’s identity on each decision.
What to agree during setup
Decide who maintains the organization directory and who can activate a team member. Review existing user identities before linking them to membership records, especially when an operator works across more than one organization. Agree which organization owns each counterparty and which team members may prepare instructions for it. The membership scope must be checked again when a person changes teams or leaves the operation.
The team should also decide how provider accounts are verified before use. Account ownership links to a counterparty, while instruction ownership links to a team member. Those are different responsibilities. For a case involving a provider-held account in euros and an instruction in an organization’s base currency, confirm the intended account and effective exchange-rate reference before a preparer sends work to review.
Check the handoff on an actual case
Take an instruction owned by a Credit Officer in one organization and linked to a counterparty in that organization’s directory. Ask the officer to open the draft, attach support and submit it for review. Then ask an Independent Credit Approver with the relevant scope to inspect the revision and evidence. The approver should make a decision under their own identity; the officer should not be able to record that independent approval. An Auditor should be able to follow the instruction, review decision and operation receipt without changing any of them.
Repeat the exercise after deactivating a team member. Historical decisions must retain their recorded reviewer and time, while current access follows the new membership state. If a member belongs to the wrong organization, correct the membership and recheck the instruction’s owner and counterparty before any provider submission.
What your team sees
- My instructions — Assigned work with status, submission date, value date and counterparty in one place.
- Eligible counterparties — Active counterparties with their organization and eligibility note for selection.
Follow the work through
Start with instruction preparation, then see how independent review uses the same organization and actor scope.
What it keeps track of
Data model- Organizations
- Banking organizations whose treasury operations are run in this app.
- Team members
- Preparers, approvers, auditors and administrators working in the organization.
- Users
- Users
- Borrowers
- Banks, custodians and settlement counterparties eligible for banking instructions.
- Loan applications
- Typed banking instructions moving through authorization, submission and confirmation.
Who uses it
Permissions- App Administrator
- Maintains the organization and membership directory.
- Credit Officer
- Owns preparation within that scope.
- Independent Credit Approver
- Makes the separate decision.
- Auditor
- Reviews the resulting trail.
Set up Loan Origination System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.