# Daily Collection Extensive

The **Daily Collection Extensive** report provides a detailed and structured overview of a clinic's daily financial and operational activities. It enables clinic managers and financial teams to monitor revenue, assess doctor-wise performance, and analyze payment collections through different methods. The report also captures collections against previous dues, patient advances, and refunds, thereby offering a holistic view of the clinic’s day-to-day financial health.

***

### Steps to Generate the **Daily Collection Extensive Report**

* Open the **Daily Collection Extensive** report by navigating to **Home > Reports > Daily Reports > Daily Collection Extensive.**
* Optionally, search for a patient using **Patient PIN, Name, Mobile Number,** or **EID Number.**
* Set the **From** and **To** date range.
* Optionally, use the **Users, Clinic** (select single or multiple clinics) and **Doctor** filters to refine results.
* Select the **Include Raw Data** checkbox to generate a detailed report.
* Optionally, include **Show Only Invoice Visits** checkbox to view only the visit associated invoices.
* Optionally, include **Show Raw Data Only** checkbox to view only the Raw Data.
* Click **Search** to generate the report.

***

### Report Structure

The report contains three sheets: **Clinic Summary, Raw Data,** and **Cash Receipt Details** (Advance & Refund Details). Each sheet offers a different level of detail and serves a specific purpose.

* The **Clinic Summary** sheet provides a clear view of the daily billing and collection performance, grouped by doctor. It displays gross billed amounts for each doctor, categorized by services such as dental procedures, drugs, packages, procedures, radiology, services, and tests. Alongside these, it also provides key financial metrics such as the discount applied, VAT collected, net billing after adjustments, and total invoice amount. The collection section further details how payments were received, breaking them down into cash, card, and bank transfer modes, and classifying them into self-pay, insurance claims, advances consumed, collections against overdue amounts, write-offs, and DD amounts.\
  \
  Additional statistics are captured, including the number of visits and invoices generated, the count of visits without corresponding invoices, and invoices issued without patient visits. Patient visit types are also categorized into new visits, revisits, and follow-ups. Invoice types are broken down into self-pay and insurance.\
  \
  This sheet also includes a **Sick Leave Summary** section, which lists any leave entries recorded for doctors, if applicable. A separate section is dedicated to **Previous Due Collections,** showing amounts collected from outstanding dues along with the collection mode and doctor. Similarly, a section on **Advance and Refund** summarizes the advance payments received and refunds issued, categorized by payment method. The sheet concludes with a grand total row that aggregates all the metrics across the clinic for the selected date.<br>
* The **Raw Data** sheet functions as a detailed transaction ledger, providing granular-level data for each patient interaction or invoice. It includes visit and invoice dates, department names, doctor details, and referral information. Patient-related data such as patient ID(Patient PIN), name, and patient status are listed alongside invoice numbers for both self-pay and insurance cases. Manual invoice numbers can be tracked in this report when the setting is enabled. In addition, the report includes an **Associated User** column that displays the user selected during appointment booking.\
  \
  Treatments-wise billing components are recorded for each transaction, covering categories such as dental procedures, drugs, packages, procedures, radiology, services, and tests. The sheet also displays gross amount, applied discount, VAT amount, net billing, and the final invoice amount. Payment collections are shown with a breakdown by cash, card, bank transfer, and other methods.\
  \
  If any amount was collected as advance or applied as advance consumption, those values are recorded separately. Additional fields include credit note consumption, outstanding collections, write-offs, refunds, and credit notes. The audit trail includes invoice status, who created or modified the entry, and any relevant remarks. This sheet is useful for validating summarized figures from the Clinic Summary sheet and for performing audits or custom analyses.<br>
* The **Cash Receipt Details** sheet captures all individual transactions involving patient advances and refunds for the selected day. It lists the transaction date, patient ID(Patient PIN), patient name, and the type of transaction—advance or refund. Remarks associated with each transaction provide clarity, including references to linked invoices.\
  \
  The sheet records the amount collected as advance, the mode of payment such as cash or card, and the specific clinic, department or doctor the advance is allocated to. It also notes whether the advance was consumed, refunded, or transferred to another patient record. If a refund was processed, the refunded amount and collection type used for that transaction are specified. In cases where an advance is transferred, the destination patient ID(Patient PIN) is also shown.\
  \
  This sheet is essential for tracking how much money was taken in advance, how much was refunded, and how funds are reallocated within the clinic system.

The screen also includes functional tools: **Pagination**(To browse multiple pages of results), **Zoom and Refresh** controls, **Search within the report, Print,** and **Export** options.

***


---

# Agent Instructions: 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:

```
GET https://unitecare.gitbook.io/uniteemr/reports/daily-reports/daily-collection-extensive.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.