> For the complete documentation index, see [llms.txt](https://docs.xyb.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyb.co/credit/create-and-manage-contracts/viewing-and-managing-day-changes-in-the-console.md). # Viewing and Managing Day Changes in the Console The **Day Change** process is a core part of the system’s daily operations that provides a clear, transparent view of how your system transitions from one business day to the next. Each **Day Change** execution performs a series of scheduled operations that include: * **Invoice processing:** Generating, processing, and settling scheduled invoices that are due on the new business day. * **Ledger transactions:** Posting accounting entries related to fees, payments, interest, and penalties. * **Overdue payment handling:** Updating overdue invoices, calculating penalty interest, and adjusting balances for contracts that have entered debt status. * **Amortisation schedule processing:** Recording principal and interest amortisations to update contract balances and ledgers.
This automated process ensures that all contracts, invoices, and ledgers remain current and accurate each day, reflecting real-time financial activity across the system. You can access Day Change information directly from the console:\ **Platform** > **Contracts** > **Lending** > **Day Changes** This opens the **Day Change list view**, which displays all past and recent executions, including the execution date and time, the duration of each run, the execution status, the created and updated timestamps, and the system user that triggered the process *** ### **Day Change Execution Overview** Clicking any record in the list opens the **Day Change Execution Information** page, where you can review detailed information about that specific run.
The page includes: * **Execution status:** Whether the run completed successfully, failed, or is still in progress. * **Timestamps:** When the execution was created, updated, and how long it took. * **System details:** Information about the system user and automated execution environment. At the bottom of this view, you’ll find two key tabs: **Invoices** and **Amortisations** which display the results of the daily processing. *** ### **Invoices Tab** The **Invoices** tab lists all invoice-related actions processed during that day change. This includes both successful and failed executions. Each row provides detailed information such as: * **Contract ID:** The contract linked to the invoice. * **Amount and amount type:** Whether it’s a Principal, Interest, Fee, or Penalty. * **Payment date and balance:** The due date and remaining balance after processing. * **Accrued interest and paid amount:** Financial activity applied during the process. * **Status:** Indicates if the invoice was Completed or moved In Debt. If invoices are shown as In Debt, it means payments were missed, triggering penalty calculations and debt updates for those contracts. *** ### **Amortisations Tab** The **Amortisations** tab shows how the system updated contract amortisation schedules and ledger postings during the day change. For each contract, it displays: * **Amount and cumulative amount** applied for principal and interest. * **Balance** after amortisation. * **Payment and processed dates.** * **Execution status** (Processed or Completed). This ensures that daily interest accruals, repayments, and principal reductions are reflected correctly in the system’s financial records. *** ### **Role-Based Actions** Depending on your permissions, you can: * **Run Day Change manually** (if enabled for your environment). * **Monitor execution history** to ensure each day was processed without errors. * **Verify contract, invoice, and ledger updates** for financial accuracy. * **Investigate failed executions** and re-run them after correcting issues. *** *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.xyb.co/credit/create-and-manage-contracts/viewing-and-managing-day-changes-in-the-console.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.