Japan Promissory Notes: designing for Tegata and Densai
Tegata is a Japanese promissory note, a paper-based payment instrument with no direct equivalent outside Japan. Densai is its electronic successor. Designing for both inside a global ERP platform meant rethinking the model almost from scratch, for users whose mental model was completely unlike anything in the existing product.
At a glance
What Tegata is, and why it needed its own model
A Tegata is a promissory note: a written promise to pay a specified amount on a future date, typically 90 to 120 days out. Japanese companies use Tegata both to pay vendors (payable Tegata) and to receive payment from customers (receivable Tegata). Before the maturity date, businesses often discount receivable Tegata at their banks to receive cash early, or endorse them to a third party as payment to a vendor.
Densai is the electronic equivalent, managed through the densai.net registry established by the Japanese Bankers Association. Unlike paper Tegata, Densai can be split and partially assigned. A business might receive a 1,000,000 JPY Densai and discount 300,000 JPY of it while endorsing the remaining 700,000 JPY to a supplier. This partial splitting capability is unique to Densai and has no equivalent in traditional accounting software.
A Tegata is a dated payment instrument. Its issuer, receiver, amount, bank, and maturity date shape the user’s mental model.
Learning the workflow from AR and AP teams in Tokyo
I interviewed Japanese finance and accounting professionals in Tokyo who were managing Tegata and Densai outside NetSuite: in spreadsheets, bank portals, or separate accounting tools. Their mental model was different from standard accounts receivable. They thought in instruments with statuses, not transactions with amounts, and the maturity date mattered as much as the amount.
Densai added a problem no NetSuite pattern handled: users needed to see how much of each instrument had already been used for discounting or endorsement, and how much remained.
Bilingual interview guide: structured customer research in Tokyo, Japanese and English
Bilingual interview guide: structured customer research in Tokyo, Japanese and English.
From status tracking in spreadsheets to a native NetSuite workflow
Maturity dates tracked in spreadsheets alongside NetSuite, with a high risk of missed collection or payment.
Tegata and Densai lifecycle managed entirely within NetSuite from receipt to collection or payment.
Tegata status is not visible in a single view and requires navigating multiple transaction screens.
Status-based view of outstanding instruments, with maturity dates and available Densai balance visible.
Partial Densai use is not supported, so users manage split amounts in external tools.
Partial Densai discounting and endorsement supported, with remaining balance calculated automatically.
No alert or notification when a Tegata approaches its maturity date.
Maturity dates are visible in the status-based view, so finance teams can act before collection or payment is missed.
Discounting and endorsing operations require manual journal entries, increasing the risk of error.
GL impact generated automatically at each status transition, removing manual journal entries.
Tegata and Densai lifecycle: full status model from receipt to settlement
Designing for instruments, not transactions
The design followed that mental model, and it became the central decision of the project.
Tegata and Densai lifecycle: the shared instrument model, with Densai partial allocation made visible.
Status flow diagram: all states, transitions, and GL impact
Densai partial use: available balance tracking after split discounting and endorsement
For Densai, the interface also had to show the remaining balance after partial discounting or endorsement, which needed a new data model and UI pattern.
Future opportunities, informed by the research
The product outcomes above were shipped. The following concepts are future opportunities, informed by the research but not presented as delivered functionality.
Research showed finance managers’ biggest risk was missing a collection date, not the mechanics of collecting. An AI-enabled dashboard could rank instruments by urgency, flagging approaching maturities and closing Densai discount windows, so it tells users what to do today.
Choosing which Densai to discount, and by how much, is currently a manual judgement call. With visibility of cash position, payables, and maturities, AI could suggest a partial-use strategy, such as discounting ¥300,000 now and collecting the rest at maturity.
Extension requests, late endorsements, and partial payments can be early signs of a customer in financial stress. AI could surface these signals to finance managers before they become bad debt, turning Tegata management into an early credit-risk check.