> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/settings/document-processing/rule-manager/transactionconfig-pro-template/charge-per-unit-outside-tolerance-rejected.md).

# Case 15: Charge Line - Charge Per Unit Outside Tolerance (Rejected)

The following scenario is an illustrative configured mapping, not a verified deployed default template. Actual output, amounts, signs and document types depend on the active `conflict_resolution` rules and expressions, export mapping and approval decisions. Any debit or credit note described below is conditional on that configuration; the example does not guarantee automatic issuance or legal compliance.

## Scenario

The charge per unit on a charge line is outside tolerance and the variance has not been approved. This case concerns a line charge, not a header charge.

## Illustrative Action

A mapping configured to use the PO charge after rejection would replace the invoice's charge per unit with the PO value. Any separate adjustment or debit/credit note depends on the export mapping and approval decisions.

## Example

* **Purchase Order (PO):**
  * Line charge per unit: $4.00
  * Quantity: 1,500 units
  * Total line charge: $6,000.00
* **Invoice received:**
  * Line charge per unit: $5.00 — 25% above the PO value, outside the configured ±5% tolerance; rejected.
  * Quantity: 1,500 units
  * Total line charge: $7,500.00
* **Configured tolerance:** Charge per unit ±5%.

For this illustrative mapping:

1. Reject the invoiced charge per unit of $5.00 because the 25% variance exceeds the ±5% tolerance and has not been approved.
2. Use the PO charge per unit of $4.00.
3. Recalculate the total line charge: **1,500 units × $4.00 = $6,000.00**.
4. Calculate the excess invoiced charge: **$7,500.00 - $6,000.00 = $1,500.00**.
5. Apply the configured handling of that difference. A credit note for $1,500.00 is one possible mapped outcome, not a guaranteed system action. Its amount, sign, document type and issuance depend on the active rules, export mapping and approvals.

Validate the line charge mapping and resulting accounting documents before using this scenario in production.


---

# 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://docs.docbits.com/administration-and-setup/settings/document-processing/rule-manager/transactionconfig-pro-template/charge-per-unit-outside-tolerance-rejected.md?ask=<question>&goal=<user_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.