Roles and Permissions Required for Credit

Managing credit contracts in the XYB Console requires specific permissions depending on the actions a user needs to perform. This article outlines the key credit-related permissions, what they allow, and when they are typically required.

---

Credit Contract Permissions

These permissions control access to credit contracts and their lifecycle, including creation, updates, payouts, and financial operations.

Permission	Description	Typical Use Cases
credit_contract_r	Can read credit contract	View contracts, query contract data, access contract details
credit_contract_w	Can write credit contract	Create contracts, create or update terms, modify contract status
credit_contract_approve_w	Can approve credit contract	Approve contract applications, authorize contract creation
credit_contract_sign_w	Can sign credit contract	Sign contracts and finalize agreements
credit_contract_payout_w	Can payout credit contract	Execute contract payouts and disburse funds
credit_contract_financial_w	Can write contract financials	Perform write-offs, financial corrections, and adjustments
credit_contract_debt_w	Can write contract debt collection	Manage debt collection processes and update collection status
credit_contract_collateral_w	Can manage contract collaterals	Manage collaterals and update collateral information

---

Customer & Product Permissions

These permissions control access to customer data and credit product configuration linked to contracts.

Permission	Description	Typical Use Cases
credit_contract_customer_r	Can read credit contract customer	View customer information and access customer data
credit_contract_customer_w	Can write credit contract customer	Update customer information and manage customer records
credit_contract_product_r	Can read credit contract product	Browse credit products and view product configurations
credit_contract_product_w	Can write credit contract product	Create products, modify product terms, and update configurations

---

Day Change Permissions

Day change permissions are required to monitor or trigger batch processing, such as invoice generation and schedule recalculations.

Permission	Description	Typical Use Cases
credit_day_change_r	Can read credit day change	View day change status and monitor batch processes
credit_day_change_w	Can execute credit day change	Trigger day change operations and process schedules

---

Recommended Permission Sets

Credit Operations / Testing Role

For users who need to create contracts, manage repayments, run payment holidays, extra payouts, and write-offs, the following permissions are typically required:

• credit_contract_r

• credit_contract_w

• credit_contract_financial_w

• credit_contract_payout_w

• credit_day_change_r

• credit_day_change_w

Read-Only Role

For users who only need to view credit contracts and related data:

• credit_contract_r

• credit_contract_customer_r

• credit_contract_product_r

---

Notes

• Approval and signing permissions are only required if your workflow includes manual approval or signing steps.

• Debt collection permissions should only be assigned to users responsible for collections and arrears management.

• Permissions should be granted following the principle of least privilege, ensuring users only have access to the actions they need.

---