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
- Counterparties and accounts
Counterparties and accounts
Connect eligible banking counterparties to the provider accounts used in instructions.
OverviewEligible counterparties×
Loan Origination System · Counterparties and accounts
New
Eligible counterparties
Borrowers
| Name | Code | Contact name | Eligibility note | Organization | Active | |
|---|---|---|---|---|---|---|
| Borrower 759 | CDE-200 | Contact 758 | EN-625 | ORG-9152 | Yes | |
| Borrower 130 | CDE-583 | Contact 444 | EN-587 | ORG-2304 | Yes | |
| Borrower 161 | CDE-103 | Contact 848 | EN-214 | ORG-3160 | Yes | |
| Borrower 799 | CDE-604 | Contact 665 | EN-556 | ORG-6573 | Yes | |
| Borrower 284 | CDE-994 | Contact 936 | EN-152 | ORG-5867 | Yes |
6 of 6 records
Borrower 759Borrowers · BRR-33769
YesCodeCDE-200
Contact nameContact 758
Eligibility noteEN-625
OrganizationORG-9152
What you can do
Choose the financial parties deliberately
Before a banking instruction is prepared, the team needs to know which counterparty and provider-held account it concerns. The counterparty directory records banks, custodians and settlement parties, together with their organization, active state and eligibility note. The account directory records the provider, external account identifier, currency, active state and counterparty owner. Keeping those links clear gives the reviewer a concrete destination to check.
A counterparty’s active flag is an operating control, not proof of a specific provider transaction. The Credit Officer selects an eligible counterparty for an instruction. The Independent Credit Approver checks that choice against the instruction and its supporting documents. The App Administrator maintains the counterparty directory and resolves ownership or membership errors before they affect a review.
How the work is organized
- Counterparty directory. Keep the party’s name, code, contact and eligibility note with its organization.
- Provider account identity. Preserve the provider’s account identifier and currency alongside the account code and owner.
- Instruction connection. Link the selected counterparty to the instruction, then use the account in its debit and credit scope.
What to agree during setup
Name the person who verifies a new counterparty and the source used to confirm its eligibility. Agree how existing provider account identifiers are imported and how duplicate codes are resolved. An account owner is a counterparty record; it is not the team member who prepares an instruction. Decide who can retire an inactive account and how the team will keep old instruction references readable after retirement.
For a lending business that sends a settlement instruction through a custodian, the custodian can be the counterparty while the provider account is the account used in the movement. Before go-live, walk through that mapping with real records. Check that the account currency is appropriate for the instruction, and confirm which exchange-rate source is used when a cross-currency amount is involved. The read-only effective rate record should be treated as an input to a reviewed decision, not as a provider confirmation.
Check the handoff on an actual case
Create an eligible counterparty for the appropriate organization and connect an active provider account with its external identifier. Prepare a draft instruction owned by a Credit Officer and select that counterparty. Add debit and credit scope that points to the provider account. The reviewer should see the party, account identity, currency and amounts together before approving the instruction.
Now mark the counterparty inactive and test the same case again. The team should resolve the eligibility issue before submitting a new instruction. Existing instruction and provider-event history should remain attributable to the original counterparty and account. If a provider movement arrives later, the settlement team should use the provider event identifier and account reference to locate the right instruction instead of guessing from a matching amount alone.
What your team sees
- Eligible counterparties — The active party directory with eligibility notes and organization context.
- Active provider accounts — Provider-held accounts with owner, currency and external identifier for checking scope.
Follow the work through
See instruction preparation for the account selection, then provider outcome for how the same identity follows the external operation.
What it keeps track of
Data model- Borrowers
- Banks, custodians and settlement counterparties eligible for banking instructions.
- Loan accounts
- Provider-held financial accounts owned by a counterparty.
- Organizations
- Banking organizations whose treasury operations are run in this app.
- Disbursements
- Debit and credit account scopes that make an instruction balanced.
- Loan applications
- Typed banking instructions moving through authorization, submission and confirmation.
- Exchange rates
- Read-only effective exchange rates for this app.
Who uses it
Permissions- App Administrator
- Maintains counterparties and organizational scope.
- Credit Officer
- Selects the counterparty and account for an instruction.
- Independent Credit Approver
- Verifies the selection before approval.
- Auditor
- Can trace the identity used in a completed case.
Set up Loan Origination System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.