> 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/workflow/cards-overview/then/action/ai-calculation-for-cost-increase-surcharges.md).
# AI Calculation for Cost Increase Surcharges
## When to use this card
Use this action to request the configured MTZ/ETZ material- and energy-surcharge calculation for the current document. Prepare the document data and calculation-service configuration required by your organization first.
## Actual configuration
The displayed card has no Cost Increase Factor, Base Cost Field or Surcharge Field inputs. It delegates calculation to the configured service. Do not look for these nonexistent card controls or assume a fixed percentage formula from the card name.
## Result and verification
A successful service response marks the card successful. A timeout or unsuccessful response produces a card error. Inspect the card log and the document's resulting surcharge data; success of the call alone does not document a particular amount.
In card-testing mode, the call is skipped and success is simulated. This is useful for testing the workflow structure, but it does not prove that the service ran or any surcharge was calculated.
## Practical example
**When to use:** Request the configured material/energy-surcharge calculation for a prepared invoice.
**Configuration:** Use synthetic invoice `DEMO-001` with the data required by your configured MTZ/ETZ service. Add this action after the document-validation conditions.
**Expected result and counterexample:** A successful service response marks the card successful; a timeout or unsuccessful response produces a card error. Inspect the document fields and calculation result separately. Card-testing mode simulates success and does not call the service, so it cannot prove a real surcharge result.
This is an illustrative configuration and expected outcome. Use fields, users and groups configured in your test organization; it is not a claim that this example was executed.
---
# 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/workflow/cards-overview/then/action/ai-calculation-for-cost-increase-surcharges.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.
