> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/general-ledger/general-ledger-module/gl-party-outstanding/debit-bill-matching.md).
# Debit Bill Matching
**Debit Bill Matching** is the process of verifying and reconciling debit bills or debit memos issued to vendors or received from them against the corresponding invoices, purchase orders, vouchers, or payment records. This process helps ensure the accuracy of financial transactions and proper accounting before posting adjustments to accounts.
## Steps to Perform Debit Bill Matching
Step 1: Navigate to the **General Ledger** module.
1. Click **Party Outstanding** from the menu.
2. Select **Debit Bill Matching** option.
* The debit bill matching screen will be displayed.
Step 2: Click the **Party Group** drop-down.
1. Select the required group from the available list.
Step 3: After selecting the Party Group, choose the **Party** for whom the debit bill matching needs to be performed.
* The screen displays the available debit bills and related voucher details that can be matched.
Step 4: Select the appropriate **Voucher Number** from the available records.
1. Verify the corresponding **Bill Amount**.
* Ensure that the selected voucher number corresponds to the correct debit bill.
Step 5: Once the required voucher and bill amount have been selected and verified:
1. Click the **Save** button..png?alt=media)
2. The system will save the matching details.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.rbsgo.com/general-ledger/general-ledger-module/gl-party-outstanding/debit-bill-matching.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
