> For the complete documentation index, see [llms.txt](https://guide.wiseapp.co.kr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.wiseapp.co.kr/lang/eng/wiseretail/data-methodology/data-correction-timing.md).

# Data Correction Timing

### Irregular Data Correction

* When the payer population changes due to shifts in the credit and debit card user population.
* When data is changed due to statistical algorithm improvement

{% hint style="info" %}
Published statistics will be kept as stable as possible, but may be adjusted without notice to maintain data quality.

In the event of changes to the overall statistical criteria, including changes to the reference population, the Company will provide prior notice through a separate announcement.
{% endhint %}

### Regular Data Correction

* Adjustment of daily data for the current month upon monthly data release

{% hint style="info" %}
Since daily data for an ongoing month is preliminary, it may be adjusted and provided without prior notice when monthly data is released.
{% endhint %}

* Adjustment of daily/monthly data from two months prior upon monthly data release

{% hint style="info" %}
Based on actual Korean card spending data published by Statistics Korea with a delay of up to 45 days, previously estimated daily and monthly data for the relevant month may be adjusted without prior notice to better reflect actual spending levels.
{% endhint %}


---

# 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://guide.wiseapp.co.kr/lang/eng/wiseretail/data-methodology/data-correction-timing.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.