Kintone is unusually good at letting ordinary teams build the app they actually need. A quote tracker, an inspection log, an order pipeline, built by the people who use it, without a developer in the loop. Users have built over three million apps that way.
Then somebody has to send a customer an invoice, and the platform runs out of road.
Kintone can show you a record and it can hand that screen to your browser’s print dialog. What it cannot do is produce a designed document: your letterhead, a proper line-item table, a totals block, a barcode, the layout your customer expects. There is no template system. For multiple records at once, Kintone’s own documentation suggests exporting to CSV and printing from Excel. The free first-party PDF plugin previews files that are already attached and generates nothing.
So this is a solved problem, but it is solved by add-ons rather than by Kintone. And here the market has a shape most people do not expect.
In Japan, where Kintone has 38,000 companies and roughly half of TSE Prime-listed firms running it in at least one department, document output is a crowded, mature plugin category with several established vendors. Outside Japan, the same category is nearly empty, and what exists is mostly generic glue through automation platforms. That means the shortlist you find depends heavily on where you search from, and the tools that top the Japanese comparison charts are not the ones that surface in English.
Seven options worth knowing in 2026, and what each one is actually built for.
First, work out what you actually need
Four questions decide this faster than any feature table.
Does it have to be a designed document, or just readable? If a plain record printout is genuinely fine, native Kintone is free and you can stop reading. Most people asking this question have already discovered it is not fine.
One record at a time, or hundreds? Batch output and scheduled runs are the line where free options drop out entirely.
Who will design the template? If the answer is “the person who owns the invoice, not a developer,” you need a visual editor. If the answer is “our dev team, and they want an API,” you want something different and cheaper to automate.
What does the finished document have to comply with? Japanese business documents have their own conventions, seals and the qualified-invoice system. European invoicing increasingly means structured e-invoicing under EN16931, not just a PDF. Barcode-driven logistics and retail add their own symbologies on top. Check each tool against the specific standard you need rather than the general category, because coverage varies more than the feature lists suggest.
The seven options at a glance
| Option | Type | Language | No code | Output | Batch | Rough cost |
|---|---|---|---|---|---|---|
| Native Kintone printing | Built in | Full | Yes | Browser print, PDF via Save as PDF | No | Free |
| PDF Generator API | In-app plugin plus API and visual editor | English | Yes | PDF, HTML, structured e-invoices | Yes, up to 200 per run | From $93 per year |
| PrintCreator (Toyokumo) | External cloud, record button | Japanese | Yes | PDF only | Yes, higher tiers | ~$45 to $220 per month, per domain |
| RepotoneU (Soulware) | In-app plugin | Japanese | Yes | PDF, Excel | Yes | One-time ~$675 to ~$1,175, Pro ~$247 per subdomain per month |
| Docutone (Opro) | External cloud | Japanese | Yes | Word, Excel, PowerPoint | Yes | ~$6 per user per month |
| k-Report (Awesome Job) | External | Japanese | Yes | Yes | Around $65 per month | |
| Automation platform glue | Zapier, Make or n8n plus a doc tool | English | Mostly | Depends on the tool | Yes | Platform fee plus tool fee |
All dollar figures are converted at August 2026 rates. The Japanese products bill in yen and PDF Generator API bills in euro, so the exact dollar amount moves with the exchange rate.
1. Native Kintone printing (the free baseline)
Every Kintone plan can print a record. You open it, you print it, and if you pick “Save as PDF” in the browser you get a PDF of the on-screen field layout.
Strengths: free, instant, no admin approval, no vendor. For internal records that only need to exist on paper, this is the correct answer and buying anything else is waste.
Limitations: no templates and therefore no branding. No logo placement, no invoice grid, no totals block, no letterhead. Comments, revision history and status buttons are stripped from the output, which is helpful, but the result still looks like a form screen because that is what it is. No batch: the documentation points you at CSV export and Excel. Layout is whatever the browser decides.
Best fit: internal-only paperwork, and proving to yourself that you need something else.
Worth naming the real cost of stopping here. Teams that cannot get a presentable document out of Kintone tend to copy the data into a Word or Excel file and fix it by hand. The record stops being the single source of truth, and every manual retype is a chance to send the wrong number to a customer.
2. PDF Generator API
Our own tool, and we have placed it second on this list, so read this section with that in mind. Here is where it genuinely fits and where it does not.
PDF Generator API is a document generation service with a drag-and-drop template editor and a REST API. It is not Kintone-specific: the same templates and the same API run across Kintone, Make, n8n, Odoo, Zapier, Bubble, Airtable and ten more platforms, or against any app that can make an HTTP request.

For Kintone there is an in-app plugin, and it covers all three of the ways people actually need documents made. A button on the record generates one document and attaches it back. A list view generates in batch, up to 200 records in a run, either one document per record or a single document listing them all. And automation rules generate on record events, so a document can be produced the moment a record is created, edited, or moved into a status in your process flow, with conditions on any field deciding whether it fires. Rules can attach the result to the record, POST it to an external system, or both.
The part that separates it from most of this list is where the design happens. Open the editor from a Kintone record and it arrives already populated with that record’s real values, so you place your actual customer name and your actual order total rather than mapping a schema. Twenty drag-and-drop components, including tables that repeat one row per line item, barcodes, QR codes and charts. No code, no XML, no mapping file to maintain.

Strengths: templates lay out dynamically rather than pinning fields onto a background image, so a two-line address and a forty-line order table both come out correctly without a second template. 38 barcode and QR formats, which is real coverage for logistics, retail, pharma and asset tracking rather than one generic barcode field. Structured e-invoicing under EN16931, meaning Factur-X, XRechnung and UBL, which none of the Japanese tools further down this list offer and which matters the moment you invoice a European customer. Every generated document writes a line to an audit field on the record, with the time, the template and what caused it. The editor is embeddable, so software vendors delivering Kintone projects can hand template design to their own clients inside their own product. ISO 27001 certified, GDPR compliant and HIPAA ready on every plan. Pricing starts at $93 per year, so testing the whole flow is cheap.
Limitations, stated plainly: there is no electronic signature feature, so if signing inside Kintone is the core requirement, PrintCreator further down this list does something we do not. Documents are processed in our EU or US regions, so check that against your own data residency policy. The automation rules run when a user acts on a record rather than as a scheduled server-side job, so they suit event-driven generation and not an overnight batch. And we are not on the Cybozu marketplace, so today the Kintone plugin is set up with you directly rather than self-installed.
Best fit: Kintone teams whose documents need barcodes or structured e-invoicing, teams running Kintone alongside other platforms, and software vendors who want document generation they can embed and reuse across more platforms than Kintone alone.
3. PrintCreator (Toyokumo)
The category leader inside Japan, and the one you should study if you are choosing seriously. Toyokumo was originally Cybozu Startups, spun out of Kintone’s own maker, and that lineage carries real trust in the ecosystem. PrintCreator holds a top three-star rating in Cybozu’s own 2025 partner evaluation and reports over 3,000 active contracts, inside a six-product suite that has passed 15,000 combined contracts.
Mechanically it is an external cloud service that pulls Kintone data: you register your Kintone app URL and an API token in PrintCreator, then trigger output from inside a record. The result can be saved back onto the record.
Strengths: genuinely no code, mouse only. You upload an existing document as a PDF background and place Kintone fields on top of it, which is the fastest route in the world to replicating a form you already use. Line-item table import, images including seals and stamps, automatic QR codes and barcodes, multi-page adjustment. Bulk output from list views, scheduled and real-time output on higher tiers, automatic email delivery. It bundles electronic signatures and timestamps compliant with Japan’s Electronic Signatures Act, so create, send, sign and archive happens in one place. Per-domain pricing means unlimited users, apps and templates.
Limitations: the background-overlay approach that makes it fast is also its ceiling. Fields sit at fixed positions on a fixed image, so layouts that need to reflow, a table that might be four rows or forty, are harder than in a template engine that lays out dynamically. Output is PDF only, with no Word, Excel or HTML. There is no support for European e-invoicing standards, so no Factur-X, XRechnung or UBL. It is Kintone-bound rather than a general document service, so nothing you build carries over to the rest of your stack. And it is Japanese: product, docs, support and billing.
Pricing: roughly $45 per month for Light up to $220 for Enterprise, per domain, with batch appearing at the $115 tier and full e-contract features at $190. All tiers include a large free page allowance and a 30-day trial.
Best fit: a Japanese company, on Kintone, that wants Japanese-format documents and signing in one product. It is the only option here that handles create, send, sign and archive in a single place.
4. RepotoneU and RepotoneU Pro (Soulware)
An in-app Kintone plugin rather than an external service, which some IT teams prefer because the data path stays shorter.
Strengths: runs inside Kintone. Outputs both PDF and Excel, which matters more than it sounds: plenty of back-office processes need the spreadsheet, not the print-ready file. The standard product is sold as a one-time license, so there is no monthly line item.
Limitations: Japanese product and support. The one-time price is a real up-front number rather than a small monthly test. The Pro tier moves to per-subdomain monthly pricing at a level where it stops being the cheap option.
Best fit: Japanese teams that want the plugin to live inside Kintone, and anyone whose real requirement is Excel output.
5. Docutone (Opro)
Opro comes from the enterprise reporting world rather than the Kintone plugin world, and Docutone reflects that.
Strengths: outputs Office formats, so Word, Excel and PowerPoint. If your document has to be editable after generation, or a colleague has to add a paragraph before it goes out, that is a genuine differentiator over every PDF-only tool here. Per-user pricing is low.
Limitations: Japanese product. Per-user pricing inverts the per-domain model, so it gets more expensive as more people need it rather than less. An external cloud service, so the same data-path considerations as PrintCreator.
Best fit: document workflows where a human edits the file after generation.
6. k-Report (Awesome Job)
A smaller external PDF output service in the same Japanese cluster, at around $65 per month.
Strengths: straightforward PDF output at a mid-range flat price, from a vendor focused on this one job.
Limitations: smallest vendor on the list, thinnest public information, Japanese only. Less independent evidence to judge it on than PrintCreator, RepotoneU or Docutone.
Best fit: worth a quote if you are already shopping the Japanese market and want a third comparison alongside PrintCreator and RepotoneU.
7. Automation platform glue (Zapier, Make or n8n plus a document tool)
This is what most non-Japanese Kintone users actually end up doing, and it deserves a fair hearing rather than being written off as a workaround.
Kintone has webhooks and a full REST API. So you connect Kintone to an automation platform, pass the record data to a document service, and send the finished file back to the record, to an email or to storage. Formstack Documents is promoted on kintone.com itself for exactly this. Documentero and PDF.co are the other names you will meet. Kintone’s own integration page is where most people find this route.
Strengths: works today, no plugin approval, no vendor conversation. English throughout. Because the trigger lives in the automation platform, you get things the plugins struggle with for free: send the PDF to Slack, file it in Google Drive, write a row to a spreadsheet, chain three documents in one run. If your team already pays for one of these platforms, the marginal cost is small.
Limitations: two or three vendors to configure instead of one, and two or three places to debug when it breaks. Your users do not get a button on the Kintone record unless you build one, so someone has to remember the automation exists. Per-task pricing on the automation platform can bite at volume. And the document tools reached this way are often template-fill utilities rather than real design tools.
Best fit: teams already running an automation platform, and anyone who wants the document to be one step in a longer process rather than the end of it.
How to choose in one pass
- Internal paperwork only: native printing. Spend nothing.
- Barcodes, structured e-invoicing, more than one platform, or you are building this into your own product: PDF Generator API.
- Japanese-format documents with signing in the same product: PrintCreator.
- Excel output matters more than PDF: RepotoneU.
- Somebody edits the file after it is generated: Docutone.
- You already run Make, n8n or Zapier: the glue route, with a real document engine on the end of it.
Wrapping up
Kintone’s document gap is not a flaw in Kintone, it is a boundary. Kintone’s job is to hold your records and route them through your process, and it does that better than the spreadsheets it replaces. Producing a designed, sendable document is a different job with different requirements, which is why an entire plugin category exists to do it.
The choice comes down to what the finished document has to comply with, whether anyone needs to sign it, and whether the document is the end of the process or one step inside it.
If you want to see the PDF Generator API route in detail before deciding, our step-by-step Kintone tutorial walks through the whole thing, from connecting the plugin to designing the document to generating it automatically on a status change.
And if you want to see your own Kintone records come out as a designed document, book fifteen minutes and we will set it up with you: grab a slot here.

