Transaction terms

Transaction information

This page summarizes only the transaction information that can be shown before contract. You can check pricing references, where to proceed next, and when disclosures happen.

  • This page lists only the public scope of transaction information (final terms are fixed by individual contract).
  • Contracting entity, billing entity, address, contact, and other legally required disclosures are provided in writing after eligibility review or at the time of contract draft presentation. For international cases, confirmation documents are provided after NDA execution as needed.
  • Items requiring confidentiality or entity verification are shared only to the necessary extent. The default governing law and jurisdiction are as set out in the Terms of Use, but these may be separately adjusted by individual contract where required for cross-border transactions, regulatory compliance, or internal approval.
  • Non-Japanese pages are reference translations. If there is a conflict or interpretation gap between language versions, the Japanese version prevails.
What is here

This page covers the pre-contract public scope: pricing references, payment, delivery, and the public refund scope.

What is not here

Final terms, confidential information, entity-verification materials, and technical details are not listed here; they are handled separately when needed.

What to see next

Go to Paths if you are choosing how to proceed, to the Standard-Track estimate if you need a public price model, or to Consult if you need a case-specific discussion.

For introducers (invite‑only)

A one‑page pre‑contract brief to help introducers make safe referrals without misreading.

Do not send confidential information before NDA (public‑level info is enough).

Introducer brief

1. Disclosure policy for business/transaction information (public scope)

Business name
disclosed before contract (not public on this page)
Responsible person
disclosed before contract (not public on this page)
Address
disclosed before contract (not public on this page)
Contact
consultation form
Disclosure timing
after eligibility check, at contract draft presentation, or upon the requester’s written request; provided in writing before contract
Standard lead time (guide)
within 2 business days after eligibility completion
Disclosure items
business name / address / billing entity / contact (as needed)
Qualified invoice issuer registration number
When the billing entity is fixed, the number is listed on invoices and pre-contract written materials if obtained. It is treated as public information confirmable on Japan’s National Tax Agency publication site.
Process
eligibility check → (NDA if needed) → provide in writing (PDF, etc.) at contract draft stage
Emergency contact (phone/email)
provided in writing before contract

This service is limited to B2B transactions for business operators, including corporations, sole proprietors, research institutions, and public institutions. Applications, purchases, and service contracts from individual consumers are not accepted. If an application is confirmed to be from an individual consumer, it will not proceed to contracting, billing, delivery, or acceptance. Items required by applicable laws are disclosed in writing before contract. This page describes public scope only.
If entity verification is required at the eligibility stage, we provide verification materials (contract/billing entity, etc.) under NDA as needed.

2. Service scope

This page explains the public pre-contract scope and terms. The deliverable is still the Evidence Pack (canonical JSON), but the acceptance flow and the reading order for the Submission Bundle are handled by the audit guide.

The Submission Bundle is an auxiliary submission set for third-party submission or post-deadline review of the Evidence Pack (canonical JSON). It does not replace standard acceptance. The audit guide is authoritative for the acceptance procedure details.

How external scope is divided

  • What is public (Public): public text + fixed demos only. We do not provide arbitrary-input computation or gated features.
  • What is delivered after contract (Client Delivery): Evidence Pack (canonical JSON) + verification digest.
  • What is fixed before third-party submission (Third-party Submission): whether/what to submit (including redaction) is fixed in advance by contract. Use the audit guide for how the submission materials should be read.

We do not disclose internal methods (formulas/implementation/operational procedures) or provide reproducible source materials in any lane.

Deliverables are provided as verifiable records of computation results (Evidence Pack) and do not guarantee business adoption or specific outcomes.

When explaining SCU to auditors or third-party recipients, use this page as the contract-scope entry point and hand off the reading of deliverables, verification, and the Submission Bundle to the audit guide.

Open audit guide

3. Pricing

Plan 1/2/3 pricing is determined by plan operations (sealed bid / buyout) and may be revised annually. Tier A/B/C are fixed-price lanes. Annual revision is used to move decisions on current-year conditions, not to promise the same conditions next year. Latest pricing/terms are listed on Monthly path, Annual path (eventization), Annual path (consistency checks) , and Tiers .

Price revision is not just an update. It is an operating rule that makes decisions easier on current-year pricing, capacity, and intake conditions. It does not pre-commit next-year conditions in advance.

Displayed prices are indicative/operational; final billing terms are fixed by individual contract/invoice.

4. How to apply

Monthly path Bid form

Annual path (eventization) Form

Annual path (consistency checks) Form

Consult consultation form

5. Payment method & timing

Payment method: invoice (bank transfer)

Due date: within 10 business days from invoice issuance (default; adjustable by agreement)

Bank details: shown on invoice

Two‑step (standard): 30% deposit (start condition) + remaining 70% after acceptance

Definitions of deposit, acceptance, and billing are fixed by individual contract.

Billing currency is JPY by default. Overseas transfer/intermediary fees and FX differences are borne by the client; shortages may be billed additionally and work/delivery may be held until paid in full.

Amounts are agreed net of tax by default; tax applicability/handling is explicitly stated on the invoice (we do not issue invoices with unclear tax treatment).

For cross-border B2B transactions, where reverse charge or equivalent destination-country tax handling applies to VAT, consumption tax, or similar taxes, the required annotation is included in the individual contract and invoice. We do not issue invoices with unclear tax handling.

6. Delivery timing & method

As a guideline, within ~30 days after input freeze, we provide the Evidence Pack set via access‑controlled / expiring URL (delivery at the time of presentation; varies by case). Post‑delivery retention follows the retention policy (strict/standard/audit).

7. Cancellation / refund (cooling‑off)

Due to the B2B nature, cancellation/refund after start is defined by individual contract.

Input Freeze means the point at which the accepted inputs, conditions, return scope, and acceptance conditions are fixed in the SOW or equivalent contract record; later changes are treated as a separate request or separate Evidence Pack (canonical JSON).

Default (overridable): client‑initiated cancellation is allowed only before Input Freeze (generally not after).

Refund before Freeze defaults to net of actual costs (including transfer/intermediary/receiving/FX/refund transfer/external service fees, etc.); we do not bear such costs.

Default (overridable): if an audit mismatch reproducibly occurs due to our side, we will redeliver once at no charge.

For the disclaimer and purpose of deliverables, see the note in “2. Scope”.

8. Jurisdiction availability and intake conditions

This service is not offered uniformly worldwide.

Whether an application, contract, invoice, delivery, or acceptance process can proceed is decided case by case after checking the requester location, entity jurisdiction, applicable laws, sanctions/export controls, tax handling, disclosure duties, and data-protection requirements.

If we cannot confirm the service conditions for the relevant jurisdiction, the process does not proceed to contracting, billing, delivery, or acceptance.

This page describes public information scope. Final transaction terms are set by individual contract documents. If there is a conflict or interpretation gap between language versions, the Japanese version prevails.