The Ringi System: How Japanese Companies Approve Your Deal

Written by

Rie Sakurai

Reviewed by

KAIZEN Digital OÜ

When a Japanese deal goes quiet, the thing that is often moving is a document you never see. It is called the ringi, and the paper, or increasingly the electronic form, that carries it is the ringisho. It is the internal proposal a Japanese company circulates to gather approval from everyone whose sign-off the purchase needs. If your inquiry has slowed after a promising few exchanges, one possible explanation is that an internal approval process is under way that you cannot see from the outside. This article explains what that document is, who writes it, how it moves, why it can take time, and what you can hand your counterpart to make it easier to approve.

A companion piece, what happens after your Japanese inquiry goes quiet, covers the silence itself. This one is about the mechanics behind it.

A note on sources: the ringi is a matter of corporate procedure and business convention, not statute, so there is no single government page that defines it. The description below is drawn from authoritative Japanese business and academic references, including a major Japanese bank, established accounting-practice publishers, and university research held by the National Diet Library. Because approver counts and timelines vary widely by company, amount, and internal rules, this article deliberately describes what shapes the time rather than asserting fixed numbers. Where a point is our own practitioner observation, it is marked as such.

What a ringisho actually is

The word ringi (稟議) translates roughly as “request for a decision,” and the ringisho is the written form of that request. It is not a memo asking a manager what they think. As one major Japanese bank’s guidance on writing a ringisho puts it, the document is circulated to the relevant people so that approval can be obtained from all of them, in place of convening a meeting. It is a specific proposal about a specific matter: the recommendation, the cost, the supplier being proposed, the evaluation behind that choice, the timeline, and the risks. It reaches senior people already argued, and asks them to approve rather than to decide from scratch. Approvers can and sometimes do add comments or request changes, so it is a document to be approved, not merely rubber-stamped.

Japanese management research describes the ringi as a bottom-up process: a matter is raised and drafted at the front-line or middle-management level, written up as a ringisho, circulated to the relevant people, and approved stage by stage up to the authorized decision-maker. University research on Japanese corporate decision-making, catalogued by Japan’s National Diet Library, sets out this same drafting-then-circulation structure and notes that informal coordination, nemawashi, often precedes the formal document. So the pattern is not that the top of the company decides in isolation; it is that proposals rise from below and are approved in sequence above.

Ringi, ringisho and kessai: three words worth separating

English readers tend to compress all of this into one word, “approval,” which hides a distinction that Japanese practice keeps clear, and the three terms repay being held apart. Ringi is the internal approval process, the circulation and accumulation of sign-offs. The ringisho is the document that carries that process. Kessai (決裁) is the final decision made by the person with the authority to make it. Established Japanese accounting-practice guidance draws exactly this line, describing the ringisho as a document for circulating a matter beyond one’s own authority and obtaining approval from multiple parties, and treating the final decision as a separate step. Keeping ringi (the process) apart from kessai (the decision) helps you read where a stalled deal actually sits: still gathering approvals, or waiting on the one person who signs it off.

Not an inquiry, a recommendation

This distinction matters because it changes what your counterpart needs from you. They are not gathering opinions. They are building a case that has to survive being read by people who were never in your meetings and who may never speak to you. Every gap in that case, a price that needs a caveat, a delivery date you hedged, a certificate that is not ready, becomes something the drafter has to explain on your behalf, in writing, to a reader who may look for reasons to send the document back.

In practice a ringisho for a supplier purchase pulls together a predictable set of elements: a statement of the need or problem, the recommended supplier and product, the reasoning for choosing that option over the alternatives considered, the total cost and how it fits the budget, the delivery and implementation schedule, and an honest accounting of the risks and how they are mitigated. Read that list from your side and a useful question follows: for each element, has the buyer got what they need from you, or will the drafter have to fill the gap with a guess? The elements where they are guessing are the elements most likely to draw an approver’s objection, and the objection can land weeks later, out of your sight.

Who drafts it, and why it is usually not the person you email

The ringisho is typically written by the employee responsible for the matter day to day, not by the senior manager you have been corresponding with. That person is not necessarily junior; the point is that they own the case, and they may be the contact you know or a colleague behind them. The person whose English is best, and who sat across from you, is often not the person writing the argument that decides your deal. That writer is working from what you gave them. If you handed over a polished slide deck in English and a verbal reassurance, you have given them very little to lift into a Japanese-language internal document.

How the document moves: circulation and approval

The ringisho does not go to one approver. It circulates, and at each stop the reviewer records their approval, accumulating sign-offs as it climbs toward the person authorized to make the final decision. Historically this was done on paper, with each approver affixing a personal seal, the hanko. Today many Japanese companies run the same process through electronic workflow systems, where drafting, review and final sign-off happen digitally and the “seal” is a recorded approval rather than a physical stamp. The image of a document travelling desk to desk with red seals is a fair picture of the tradition, but for a 2026 buyer it is just as likely to be an approval trail inside a workflow tool. What has not changed is the logic: several people, in sequence, each have to be comfortable enough to approve.

What a returned ringisho means

Because approval is sequential, one reviewer can hold up the whole thing. If an approver has a question or an objection, the document does not usually come back to you. It goes back to the drafter, who has to resolve the point and re-circulate. This is one common reason a foreign supplier suddenly gets a specific, seemingly out-of-nowhere question after a stretch of silence: an internal approver flagged something, and your counterpart is now assembling the answer. Reading a delayed technical question as a loss of interest is often a mistake. In our experience it can be the opposite, a sign the matter is far enough along to be inside the approval process, though that is our practitioner observation rather than something you can assume in any given case.

How many approvers, and how long

Resist the urge to attach a number to this. The number of approvers and the elapsed time vary widely, and no single “typical” figure holds across companies. What a ringisho’s route depends on is concrete: the amount of money, the importance of the matter, the departments it touches, the size of the company, and its internal delegation-of-authority rules. A small, routine purchase may need a short chain of approvals; a large or cross-departmental commitment may involve the responsible employee’s manager, a department head, related departments, and executives, in a sequence set by those internal rules. The bank guidance cited above makes the same point in its own way: how far a matter has to travel for approval depends on what the matter is.

Time behaves the same way. Rather than counting weeks, it is more useful to understand what creates the time: sequential review in which each approver has to be satisfied before the next sees it, the checks and send-backs that happen when someone has a question, coordination across multiple departments, and the informal alignment that often precedes the formal document. Multi-department matters, in particular, can stretch when a single query sends the ringisho back a step. A company on an electronic workflow can compress the calendar without changing that underlying logic.

Why it can take time, and what the delay usually is

Foreign suppliers tend to read the elapsed time as indecision. It is often more accurate to read it as a process that front-loads agreement so that execution, once approved, is fast and rarely reversed.

Nemawashi comes first; the ringi formalizes it

Before the ringisho is circulated, groundwork is often laid informally, one conversation at a time. That is nemawashi. By the time a proposal enters formal circulation, substantial internal alignment may already have taken place through it, so the ringi can serve less as a place where a decision is made from zero and more as the step that carries a pre-formed consensus onto the official record. University research on Japanese decision-making supports this reading of nemawashi as a genuine precursor to the formal document. The practical consequence is that pushing on the formal timeline rarely helps, because the substantive work is happening in conversations you are not in. We cover that dynamic in depth in the nemawashi article.

The separate question of budget

Budget is a different mechanism from the ringi, and the two are better kept apart rather than treating the budget cycle as the reason the ringi is slow. Even after internal support has been built, a purchase may still depend on whether the required budget is available. Many Japanese companies operate on an April-to-March fiscal year, though not all do, and a commitment that needs funding can wait for the budget to exist regardless of how convinced your counterpart is. If a deal seems to have stopped, the explanation may have nothing to do with the merits and everything to do with the current year’s budget being committed. Asking your counterpart, plainly, whether the purchase is a matter of internal approval or of budget availability is a fair question, and the answer tells you a great deal about the timeline.

A realistic sequence, from first meeting to signed order

It helps to see the whole arc laid out, because the part you can observe is a thin slice of it. The sequence below is a composite drawn from how a mid-sized capital purchase tends to move. Treat it as a shape, not a schedule: your deal may be faster or slower, and details differ by company.

The part you see

You meet, you present, you exchange a few rounds of email, and the questions are engaged and specific. Then the responses slow and the tone turns non-committal. From the outside this looks like the deal cooling. From the inside, it can be the moment your counterpart stops selling you and starts doing the quiet work of lining up internal support. The visible conversation can go quiet precisely because the substantive conversation has moved somewhere you cannot follow.

The part you do not see

Your counterpart may begin the informal groundwork, testing the idea with the people whose approval the ringisho will eventually need. If one of them is unconvinced, that objection is often resolved before anything is written down, because a ringisho that gets rejected in circulation is a poor outcome the drafter will work to avoid. Once the informal support is in place, the ringisho is written and begins its formal circulation, gathering approvals in sequence. A single reviewer with a question can pause the whole document while the drafter comes back to you for one more data point. That is a common origin of the oddly specific email that arrives after a stretch of silence. When the last approval lands, the decision is often more a ratification of settled agreement than a fresh choice, which is why execution afterward tends to be quick.

Where the time actually goes

Notice that much of the elapsed time is not decision-making in the sense a Western supplier means it. It is consensus-gathering, sequential review, and sometimes budget timing. This is why a chaser email asking whether they have “made a decision yet” can land awkwardly: it assumes a single moment of choice that the process is designed to spread across many people. A better question asks where the proposal sits in its path, not whether a verdict has been reached.

What you can put in the drafter’s hands

Here is the part most guidance skips. If someone inside the buyer is writing the ringisho that decides your deal, the most useful thing you can do is make that document easy to write and easy to approve. You cannot enter the room, but you can equip the person who is in it.

The one-page Japanese summary

Give your counterpart a short, self-contained summary in Japanese that they can lift straight into the ringisho: what the product is, what problem it solves for this buyer, the price and what is included, the delivery commitment, and the two or three facts an approver will want. A one-page document in the reader’s language, written to be quoted without you present, does more work than a fifty-slide English deck that no one will translate. This connects directly to the evidence a Japanese buyer expects on paper, which we cover in what Japanese buyers want in your technical documentation.

Pricing and answers that survive the room without you

Because the decision is argued when you are absent, anything ambiguous will be resolved without your input, and not always in your favour. Quote a price that does not need a verbal caveat to make sense. State a delivery commitment you can keep rather than one you will have to walk back. Anticipate the objection you can already predict, on lead time, on minimum order, on after-sales support in Japan, and answer it in writing before it is asked. Provide named references the approver can recognise. Every one of these removes a reason for the ringisho to be sent back a step, and each avoided round can save real time.

None of this lets you control the ringi. It is an internal process and it belongs to the buyer. What it lets you do is stop being the weakest paragraph in a document you will never read.

What not to do while the ringi is moving

Three instincts that serve a supplier well in other markets tend to backfire against a ringi in progress. Each one can add friction to the document rather than speeding it up.

Do not try to compress the timeline by pushing

Repeated chasers framed as urgency read very differently on the receiving end. The drafter cannot make an approver sign off faster, and pressure aimed at your contact often has to be absorbed and explained internally, which can cost them standing. If you have a genuine deadline, state it once, early, with the reason attached, and ask what is realistic given their approval cycle. A deadline presented as information is useful. A deadline presented as leverage is a problem your counterpart now has to manage.

Do not go over your contact’s head

As a general rule, escalating to a senior executive you met once, in the hope of forcing momentum, can undercut the very person building your case. In a bottom-up process the drafter and their immediate managers are usually your allies, not obstacles, and a senior who receives an out-of-sequence approach may route it back down to the same people while noting that the supplier did not understand the process. The person who can most help you is often the one closest to the document, not the most senior name on your contact list.

Do not go silent yourself

Because your side often hears nothing for stretches, it is tempting to match the silence and wait. But the drafter may need exactly one thing from you to move the document, and a slow response on your end can cost a full circulation cycle. Stay reachable, answer quickly and completely, and make it easy to get a fast, quotable answer from you. Responsiveness is itself read as a signal, a point we return to in the discussion of how Japanese buyers score suppliers beyond price.

Key takeaways

Three words, kept apart. Ringi is the internal approval process, the ringisho is the document that carries it, and kessai is the final decision by the authorized decision-maker.
It is a recommendation, not an inquiry. The ringisho is a completed proposal with cost, evaluation, timeline and risk, built to be approved by people you will never meet.
The drafter is the person responsible for the matter, not necessarily your main contact, and they build your case in Japanese from whatever you provided.
Approver counts and timelines vary widely. They depend on the amount, the importance, the departments involved, the company’s size, and its delegation-of-authority rules, so treat any single number with caution. Traditionally done on paper with hanko, the process today often runs through electronic workflow systems.
Silence is not proof of anything by itself. An internal approval process may be progressing out of your sight, but a stall can also be budget, priorities, personnel changes, or a competitor. Ask which it is rather than assume.
Budget is a separate question from approval. Even with internal support in place, a purchase can wait on whether the funding exists, often tied to the fiscal year.
You cannot join the process, but you can equip it. A one-page Japanese summary, quotable pricing, pre-answered objections and named references make the ringisho easier to write and to approve.