--- title: "Bolta Integration" description: "Bolta is the Korean electronic tax invoice service that files with the National Tax Service on your behalf. Agents issue tax invoices, generate the correcting invoices Korean law requires, and handle reverse invoices initiated by the buyer." url: https://flowrunner.ai/integrations/bolta date_modified: 2026-09-04T14:53:04-07:00 --- # Bolta [Accounting](https://flowrunner.ai/integrations/category/finance-accounting) Bolta is the Korean electronic tax invoice service that files with the National Tax Service on your behalf. Agents issue tax invoices, generate the correcting invoices Korean law requires, and handle reverse invoices initiated by the buyer. 16 actions · Basic auth · available [Bolta website](https://bolta.io/) · [Platform Documentation](https://docs.bolta.io/) · Capability data verified 2026-08-24 1. A month of Korean sales closes and the tax invoices are due 2. List Issuers confirms the issuing business has a valid registered certificate 3. The agent assembles the item lines for each buyer, between one and sixteen per invoice 4. Every item's tax is checked against the invoice's tax type, because mixing them is rejected outright 5. Issue Tax Invoice files each one with a client reference that makes a retry safe 6. Get Tax Invoice Status is polled against those references until each filing resolves 7. Any filing that resolves to a failure, and every correcting invoice, goes to the tax owner ## What This Integration Enables Bolta is not invoicing software with a tax feature. It is a filing service: the document goes to the Korean National Tax Service, and once it is there it is there. That single fact should shape every workflow built on this connector. There is no delete anywhere in the action list, and there is no edit. A tax invoice you regret is withdrawn by issuing a second, correcting invoice that offsets it, and both stay on the record permanently. FlowRunner agents handle the parts that genuinely reward automation: registering issuing businesses, driving the certificate registration a business has to complete itself, filing tax invoices from wherever your sales data actually lives, running the buyer initiated reverse issuance flow, and issuing and canceling cash receipts. Two operational details are worth knowing before the first flow. Issuance is asynchronous, so the response carries an issuance key rather than an outcome and a flow must read the status to know what happened. And the API key prefix is the environment, with no separate host and no switch, so a live key used in a test flow files real tax documents. That is the sort of irreversibility that makes [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) gating a design requirement rather than a nicety. ### Without FlowRunner **A spreadsheet feeding a portal**: Invoice data is prepared in one system and keyed into a filing portal by a person, monthly **A 2xx read as done**: Issuance is asynchronous, so a successful call means accepted for processing rather than filed **Corrections written from scratch**: The right correcting document depends on why the original was wrong, and choosing it is institutional memory ### With FlowRunner **Filing driven by the source system**: The agent reads the sales data where it already lives and files from it, with the same reference on both sides **Outcome read from the status**: The flow polls the status until it resolves and treats a failure as a failure, not as a delivered document **Corrections proposed with their reason**: The agent shows the original, the proposed reason and the resulting figures, and a person picks ## Use Case Scenarios ### Month end filing driven by the source system Sales close in the billing system or in a storefront like [Shopify](https://flowrunner.ai/integrations/shopify). The agent groups the month by buyer, builds each invoice's item lines, and checks the item tax against the invoice tax type before anything leaves, because a taxable, zero rate and tax free mix inside one request is refused rather than corrected. There is no header total to set, since the invoice amount is the sum of its items. Each filing carries a client reference the agent generated, which makes a retry after a network failure return the original result instead of filing a second invoice. The batch and its outcomes land in [Slack](https://flowrunner.ai/integrations/slack) for the tax owner. ### Onboarding an issuing business without touching its certificate Korea requires the issuing business's own certificate to be registered before anything can be filed, and the certificate never travels through the API. The agent calls Register Issuer to create the business record, then Get Certificate Registration URL to produce a page the business itself completes. It sends that link, waits, and calls Get Certificate Registration Status shortly after the business finishes. This is the shape of the whole connector in miniature: the agent does the coordination and the paperwork, and the act that carries legal weight stays with the person who is allowed to perform it. ### Cash receipts whose outcome is read, not assumed A consumer payment settles. The agent calls Issue Cash Receipt with the recipient as a mobile number for an individual or a business registration number for proof of expenditure, always carrying a client reference because for cash receipts that reference is the only key the status lookup accepts. The call is accepted rather than completed, so the flow polls Get Cash Receipt Status and reads the status in the body. A flow that treated the HTTP response as the answer would report a failed receipt as issued, and the customer would find out at their own tax filing rather than at yours. ## Human-in-Loop Highlight Amend Tax Invoice is where an agent should stop, and the reason is specific rather than general caution. A correction here means filing a second permanent document, and the three reasons behave differently. Cancellation of contract offsets the whole original and is refused outright if any item on it had a negative supply cost. Double issuance by mistake takes nothing at all and reuses the original's write date. Change in supply cost carries the difference, not the corrected figures, so overstating a unit price by one thousand won is corrected by sending negative one thousand. Sending the corrected price instead doubles the error, and it is accepted, because it is a valid amendment. So the agent gathers the original with Get Tax Invoice and proposes: "Invoice for Hanul Trading overstates line 2 by 1,000,000 KRW. Proposed reason: change in supply cost, items carrying minus 1,000,000. Resulting recorded position after both documents: 4,200,000 KRW. Confirm the reason and the delta?" The agent can compute the difference. It should not be the thing that decides which correcting document Korean law expects. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 16 actions ### Issuers 6 - **List Issuers** Lists the issuing businesses registered with Bolta, showing the business registration number and whether a certificate is in place. The first check before any filing run. - **Register Issuer** Creates the business record that filings are made under. - **Get Issuer** Retrieves a single issuing business. - **Get Certificate Registration URL** Produces a Bolta hosted page where the business itself registers its certificate. The certificate never passes through the API. - **Get Certificate Registration Status** Reports whether the certificate registration completed, checked shortly after the business finishes the page. - **Delete Issuer Certificate** Removes a registered certificate, after which that business can no longer file until it registers a new one. ### Tax invoices 4 - **Issue Tax Invoice** Files a tax invoice with the National Tax Service. It returns an issuance key rather than an outcome, because filing is asynchronous. - **Get Tax Invoice** Retrieves a filed tax invoice. It answers only after issuance completes, so an immediate call after issuing returns not found and that is expected. - **Get Tax Invoice Status** Looks a filing up by your own client reference, which is how a flow that lost the response recovers. - **Amend Tax Invoice** Files the correcting invoice Korean law requires. The reason decides the shape, and a supply cost change carries the difference rather than the new figures. This is the operation this page's human gate exists for. ### Reverse issuance 3 - **Request Reverse Issuance** Drafts a buyer initiated invoice for the supplier to approve. - **Get Reverse Issuance Approval URL** Produces the supplier's approval page. It is short lived, so generate it at the moment you are about to show it. - **Cancel Reverse Issuance** Withdraws a reverse issuance request while it is still pending. Once approved the document exists and needs an amendment instead. ### Cash receipts 3 - **Issue Cash Receipt** Issues a cash receipt to a mobile number, a business registration number, or the issuer itself. The request is accepted rather than completed. - **Get Cash Receipt Status** Reads the outcome from the body rather than from the HTTP code, which is the only way to tell an issued receipt from a failed one. - **Cancel Cash Receipt** Cancels a receipt in full. Bolta does not support canceling part of one, and the cancellation needs its own client reference. ## Frequently Asked Questions ### What can FlowRunner do with Bolta? FlowRunner agents can run List Issuers, Register Issuer, and Get Issuer in Bolta, plus 13 more actions. ### Does connecting Bolta to FlowRunner require OAuth? No. Bolta connects to FlowRunner with basic authentication (a username and password), no OAuth flow required. ### Can Bolta trigger a FlowRunner workflow automatically? Bolta doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Bolta?** This integration exposes Bolta to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/bolta. Site index: https://flowrunner.ai/llms.txt