> For the complete documentation index, see [llms.txt](https://help.sesami.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sesami.co/ja/akaunto/billing/billing-schedule.md).

# 請求スケジュール

Sesami は、他の Shopify アプリと同様に Shopify 経由で請求されます。

## 請求の仕組み

{% hint style="info" %}

* Shopify は **30日間のサブスクリプション請求期間**.
* Sesami のようなアプリには **別の30日間の請求サイクル**があり、これにより請求が Shopify の請求書に表示される時期が変わります。
  {% endhint %}

Shopify がサードパーティ製アプリにどのように請求するかの詳細が必要な場合は、Shopify ヘルプセンターの Shopify のアプリ請求に関するドキュメントを参照してください。


---

# 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.sesami.co/ja/akaunto/billing/billing-schedule.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.