Output

Here's how to handle receipts for past charging sessions, including the "president's phone shows not set up" case.

**Standard way to issue a charging receipt (works for past sessions too)**

Per the official Help Center article, receipts are issued from the reservation history in the app:

1. Open the reservation list and tap the reservation in question — the billing amount screen appears.
2. Tap the "Issue Receipt" (領収書発行) button at the bottom of that screen.
3. Enter an email address, and the receipt will be sent to you by email.

Notes from the official article:
- The email is sent from an "@stripe.com" address, so check spam folders if it doesn't arrive.
- A receipt becomes available a while after the reservation time ends — so for a very recent session, wait a bit and try again.
- For sessions from a month ago or last year, the same flow applies: find the past reservation in the reservation history and issue the receipt from there. The receipt itself is delivered by email, so you don't need to have been on any particular device at the time.

**If a receipt with a specific recipient name (e.g., the company name) is needed**

Individual named receipts can't be self-issued from the app. Contact us through the inquiry form with the destination email address, and per our internal guidance we'll issue them individually — please have ready the recipient name, your user ID, and the last 4 digits of the credit card registered in the app.

**The "president charged but the app shows 'not set up'" case**

The service can't be used without app registration, so if charging actually happened, it was almost certainly done under a registration on a different device or a different account. In that situation:

- Check the reservation history on the device/account that was actually used for the charging (e.g., the president's other phone, or an account registered under a different phone number/email).
- Issue the receipt from that account's reservation history using the steps above.
- If you can't locate the session in any account, contact support with the date, station, and approximate time, and we'll check the records internally.

One related note: this flow is for charging (usage) receipts. Receipts for PowerX First membership fees are handled separately — those require contacting customer support directly.

Judge / review

{
  "pass": true,
  "scores": {
    "accuracy": 4,
    "relevance": 4,
    "consistency": 5,
    "safety": 5,
    "style": 5
  },
  "judge": {
    "verdict": "pass",
    "judge_model_verdict": "pass",
    "gate_verdict": "pass",
    "scores": {
      "accuracy": 4,
      "relevance": 4,
      "consistency": 5,
      "safety": 5,
      "style": 5
    },
    "total": 23,
    "reasons": [
      "All required steps for issuing a receipt from reservation history are present.",
      "App registration requirement and other-device explanation are both covered.",
      "Receipt email delivery is mentioned but worded as 'enter an email address' rather than the registered email.",
      "Extra sections (named receipts, PowerX fees) are related but beyond the core ask.",
      "Answer is coherent, safe, and clearly formatted."
    ],
    "missing_points": [
      "Does not explicitly state the receipt is sent to the registered email address (says 'enter an email address')."
    ],
    "critical_missing_points": [],
    "minor_missing_points": [
      "Does not explicitly state the receipt is sent to the registered email address (says 'enter an email address')."
    ],
    "covered_points": [
      "Receipts are issued from reservation history in the app.",
      "Steps: open reservation history, select the reservation, tap Issue Receipt on billing screen.",
      "Receipt is delivered by email.",
      "App registration is required to use the service.",
      "If the reservation is not found on the current device, it was likely used via registration on another device/account."
    ],
    "constraint_violations": [],
    "notes": "All key points covered; only the registered-email detail is loosely worded. Extra sections are helpful context, not errors."
  },
  "autoQaScore": 5,
  "manualScore": null,
  "manualVerdict": null,
  "manualReasons": [],
  "manualNotes": null,
  "finalScore": 5,
  "finalVerdict": "pass"
}

Output

過去の充電分（1ヶ月前・昨年分を含む）の領収書は、予約履歴が残っていればアプリから発行できます。以下の手順でご案内ください。

**1. 基本の発行手順（アプリから自己発行）**
- アプリの予約一覧から該当の予約をタップすると、ご請求金額の画面が表示されます。
- 画面下部の「領収書発行」ボタンを押し、メールアドレスを入力すると、領収書がメールで届きます（送信元は「@stripe.com」のアドレスです）。
- 領収書は予約時間終了後にしばらく経ってから発行可能になるため、1ヶ月前や昨年分でも履歴が残っていれば発行できます。
（出典：/sources/ja/public-help/articles/24448695909017.md:20-24）

**2. 宛名指定（法人名等）が必要な場合**
- 充電利用分の宛名入り領収書は個別発行に対応しています。その際は「領収書の宛名」「ユーザーID」「アプリに登録のクレジットカード番号下4桁」をご返信いただく必要があります。
（出典：/sources/ja/runbooks/billing.md:254-258）
- 宛名付き発行をご希望の場合は、送付先メールアドレスをご記入のうえ、お問い合わせフォームからご連絡いただく流れです。
（出典：/sources/ja/public-help/articles/39866834771993.md:27）

**3. 「社長がスマホで充電したはずだが、アプリが未設定（未登録）と表示される」ケース**
- アプリ未登録の状態では充電利用・領収書発行ともにご利用いただけないため、**別の端末・別のアカウント（別電話番号など）で登録・利用された可能性**があります。まずは社長が実際に充電に使ったスマホ本体で、その端末に登録済みのアカウントの予約履歴をご確認いただくようご案内ください。
（出典：/sources/ja/runbooks/corporate.md:51-55）
- それでも履歴が見つからない場合は、充電日時・ステーション名・カード請求明細（カード番号下4桁）などの情報を添えてお問い合わせフォームからご連絡いただければ、社内で利用履歴を確認のうえ対応します。

なお、PowerX Firstの会費分の領収書は充電分とは発行方法が異なり、カスタマーサポートへの依頼が必要ですので、会費のお支払いも含まれる場合はその旨お知らせください。

Judge / review

{
  "pass": true,
  "scores": {
    "accuracy": 4,
    "relevance": 5,
    "consistency": 5,
    "safety": 5,
    "style": 5
  },
  "judge": {
    "verdict": "pass",
    "judge_model_verdict": "pass",
    "gate_verdict": "pass",
    "scores": {
      "accuracy": 4,
      "relevance": 5,
      "consistency": 5,
      "safety": 5,
      "style": 5
    },
    "total": 24,
    "reasons": [
      "予約履歴からの領収書発行手順を3ステップで網羅",
      "未登録表示ケースの別端末・別アカウント可能性に言及",
      "宛名指定や会費分の追加案内も出典付きで妥当",
      "メール宛先の表現が期待回答と僅かに異なる"
    ],
    "missing_points": [
      "領収書は登録済みメールアドレス宛に送付される旨（出力はメールアドレス入力と表現）"
    ],
    "critical_missing_points": [],
    "minor_missing_points": [
      "領収書は登録済みメールアドレス宛に送付される旨（出力はメールアドレス入力と表現）"
    ],
    "covered_points": [
      "予約履歴から領収書を発行できる",
      "アプリの予約履歴を開き該当予約を選択",
      "請求明細画面で領収書発行をタップ",
      "領収書がメールで届く",
      "予約履歴が表示されない場合は別端末・別アカウントでの登録利用の可能性"
    ],
    "constraint_violations": [],
    "notes": "必須要点はすべて意味的にカバー。メール宛先の表現のみ軽微な差で重大な欠落なし。"
  },
  "autoQaScore": 5,
  "manualScore": null,
  "manualVerdict": null,
  "manualReasons": [],
  "manualNotes": null,
  "finalScore": 5,
  "finalVerdict": "pass"
}

Output

Here's how receipts work, based on the official Help Center article and the corporate/billing runbooks.

**1) Charging (usage) receipts — self-service in the app**
- Open the app → reservation list (予約一覧) → tap the relevant reservation → the billing-amount screen opens.
- At the bottom of that screen is the "Issue receipt" (領収書発行) button; tap it and enter an email address, and the receipt is emailed to you. The email comes from an @stripe.com address.
- A receipt becomes available a while after the reservation end time.
  (ja/public-help/articles/24448695909017.md:20-24)

For a charge from a month ago or last year, it's the same flow — you just scroll back in the reservation list to that older reservation. Note: the sources don't state any cut-off for how far back receipts can be issued, so if the old reservation no longer appears in the list, that has to be checked by support rather than assumed.

**2) When you need a recipient name (宛名), or the button isn't usable**
- For receipts with a recipient name for general (public) charging payments, contact support via the inquiry form and include the destination email address. PowerX First membership-fee receipts are issued by customer support (also emailed from @stripe.com); if you need several receipts for monthly billing, specify the payment year/month. Completing Account → Settings → email authentication first makes it smoother.
  (ja/public-help/articles/39866834771993.md:20-27)
- For individually addressed receipts of already-paid charging fees, support asks you to reply with: the recipient name, your user ID, and the last four digits of the credit card registered in the app.
  (en/runbooks/billing.md:254-258)
- If a charge on your card (e.g. ¥10,800 or ¥1,050) doesn't show in app usage history, it may be the PowerX First membership fee; support checks the record internally and issues a receipt if found, and will ask whether you want a specified recipient name.
  (en/runbooks/billing.md:208-212)

**3) The "president charged on his phone but the app shows 'not set up'" case**
- The service cannot be used without app registration, so if his app shows nothing / "not set up," the guidance is that the account was likely registered and used on a different device (or a different account). Check the handset he actually charged with and confirm he's logged into the same account (same phone number / user ID) — the receipt has to be issued from the reservation history of the account that made the reservation.
  (en/runbooks/corporate.md, CS-079)
- If he can get into that account: issue it from that reservation history as in step 1. If he can't: contact support with the user ID, last four digits of the registered card, and the approximate date/station so the record can be located.
- Corporate angle: business reservations are made from the Dashboard, not the app, and a payment method must be set up for the service to be usable — so if this was a corporate booking, look at the Dashboard reservation record rather than the app.
  (en/runbooks/corporate.md, CS-013)

Two caveats: the corporate/billing entries are QA-authored, provisional guidance (the official receipt article was last updated 2024-11-26), and I can't issue or confirm a receipt here — support has to do that. If you need qualified-invoice compliance, there's a separate official article on whether the invoice registration number is printed on receipts (ja/public-help/index.md:54, updated 2026-07-17) that should be checked before you rely on the format.

Judge / review

{
  "pass": true,
  "scores": {
    "accuracy": 5,
    "relevance": 4,
    "consistency": 5,
    "safety": 5,
    "style": 4
  },
  "judge": {
    "verdict": "pass",
    "judge_model_verdict": "pass",
    "gate_verdict": "pass",
    "scores": {
      "accuracy": 5,
      "relevance": 4,
      "consistency": 5,
      "safety": 5,
      "style": 4
    },
    "total": 23,
    "reasons": [
      "All expected key points covered: reservation history flow, issue receipt button, email delivery, app registration requirement, and different-device explanation.",
      "Directly addresses the president's 'not set up' scenario with practical guidance.",
      "Includes extra corporate/support context that is relevant but adds verbosity.",
      "Slight wording difference: model says 'enter an email address' vs expected 'registered email address', but core meaning preserved.",
      "Well-structured with numbered steps and clear sections."
    ],
    "missing_points": [
      "Expected says receipt goes to 'registered email address'; model says 'enter an email address' which slightly differs."
    ],
    "critical_missing_points": [],
    "minor_missing_points": [
      "Expected says receipt goes to 'registered email address'; model says 'enter an email address' which slightly differs."
    ],
    "covered_points": [
      "Issue receipt from reservation history in app",
      "Open reservation list/history",
      "Select the relevant reservation",
      "Tap Issue Receipt on billing details screen",
      "Receipt sent via email",
      "App registration required to use service",
      "If not found on current device, may have registered on another device"
    ],
    "constraint_violations": [],
    "notes": "All key points present. Extra corporate/support info is relevant to the president scenario. Minor email wording nuance only."
  },
  "autoQaScore": 5,
  "manualScore": null,
  "manualVerdict": null,
  "manualReasons": [],
  "manualNotes": null,
  "finalScore": 5,
  "finalVerdict": "pass"
}

Output

検出された違反項目：未検証の引用、言語設定の不備、禁止された形式の使用。

Judge / review

{
  "pass": false,
  "scores": {
    "accuracy": 1,
    "relevance": 1,
    "consistency": 1,
    "safety": 5,
    "style": 1
  },
  "judge": {
    "verdict": "fail",
    "judge_model_verdict": "fail",
    "gate_verdict": "fail",
    "scores": {
      "accuracy": 1,
      "relevance": 1,
      "consistency": 1,
      "safety": 5,
      "style": 1
    },
    "total": 9,
    "reasons": [
      "Model output is a system error/violation message, not an answer to the user's question",
      "No expected key points are addressed whatsoever",
      "Output does not provide any instructions for issuing receipts",
      "Output does not mention reservation history, email delivery, or device issues",
      "Accuracy score below minimum (1 < 4).",
      "Relevance score below minimum (1 < 4).",
      "Total score below minimum (9 < 20).",
      "Critical answer points are missing (6)."
    ],
    "missing_points": [
      "予約履歴から領収書を発行できる旨",
      "手順(1)アプリの予約履歴を開く",
      "手順(2)予約を選択",
      "手順(3)領収書を発行するをタップ",
      "領収書が登録メールアドレスに送付される",
      "別端末で登録・利用された可能性の案内"
    ],
    "critical_missing_points": [
      "予約履歴から領収書を発行できる旨",
      "手順(1)アプリの予約履歴を開く",
      "手順(2)予約を選択",
      "手順(3)領収書を発行するをタップ",
      "領収書が登録メールアドレスに送付される",
      "別端末で登録・利用された可能性の案内"
    ],
    "minor_missing_points": [],
    "covered_points": [],
    "constraint_violations": [
      "Output is not an answer to the user's question but a system violation notice"
    ],
    "notes": "Model returned a violation/error message instead of answering the receipt issuance question. All key points missing."
  },
  "autoQaScore": 2,
  "manualScore": null,
  "manualVerdict": null,
  "manualReasons": [],
  "manualNotes": null,
  "finalScore": 2,
  "finalVerdict": "fail"
}