Partner registration that starts on approval

A kintone approval starts the workflow by webhook. It looks up the tax registration number, AI matches it to the request, and a match enters the sales system.

  • All industries
  • Accounting & finance

The problem today

After a new partner is approved in kintone, accounting looks up its invoice registration number on the National Tax Agency's site and types the partner into the sales system. The part automated with RPA runs twice a day, so a partner can wait half a day after approval, too late for an urgent order.

The workflow in Kitewell

  1. When a request is approved in kintone, a webhook starts the workflowAutomatic
  2. Look up the registration number's status and name on the National Tax Agency's siteWeb
  3. AI judges whether the result matches the request's name and addressAI judgment
  4. Accounting checks any request that does not match, and decidesApproval
  5. Register the partner in the sales system's screens and get its partner codeWeb
  6. Write the partner code and the lookup result back to the kintone record through its APIAutomatic

What AI does

Compares the lookup result with the request's name and address, allowing for differences in how a company name or address is written, and records its confidence and the evidence.

Where people decide

Checks only requests whose name does not match or whose number is not found, and decides whether to register the partner or ask the requester. Matching requests are registered without a check.

Features used

What a PoC checks

  • Whether the network lets the machine running Kitewell reach the relay (hooks.kitewell.app)
  • Whether AI treats different spellings of a name or address as the same company
  • Whether requests approved while the machine was off run in order once it is back on

Discuss a PoC for this work

We check whether this workflow runs on your own work and screens.