Contracting and won-denominated billing for overseas IT services

The tool is chosen and then the process stops at the checkout screen. Most overseas services accept only foreign card payments and issue an English invoice. A Korean purchasing process runs on the opposite set of documents: a quotation, a contract, and a tax invoice have to exist before the request moves and the spend is approved. Paying by corporate card runs into limits and approval authority, and the amount moves with the exchange rate every month, so budget and actuals drift apart. It is also common for one person to pay on a personal card and claim it back later, which makes an individual, not the company, the contracting party. When that person moves on, the account and the payment method leave with them, and nobody is left who knows the renewal date. What blocks the purchase is the shape of the contract and the evidence, not the choice of tool. So the first question in a review is not what to use but who to contract with and what document will remain as evidence.

There are broadly three ways to run an overseas service from Korea. The first is a direct contract with the overseas head office, with only implementation and operations handed to a Korean company: your company is named on the contract and receives the bill. The second is resale by a Korean company, where the counterparty is a Korean entity that also sets the price and the contract terms. The third leaves the vendor relationship in place and has a Korean partner take over billing and payment. The three differ in three places: who the parties to the contract are, who issues the tax invoice, and who you talk to when the price or the terms change. IXC is the official OneSignal partner in Korea and handles domestic contracting, won-denominated payment, and tax invoice issuance; receives public cloud billing through the Megazone partner network; and holds a direct partnership with Akamai. One company has been through all three routes, so what each one asks of a buyer sits side by side.

Contract with a Korean entity and the billing arrives in won with a tax invoice attached. The paperwork behind the spend looks like any domestic transaction, so accounting and audit have nothing to ask back. Contract directly with the head office and what remains is an English invoice, a card slip, and remittance records. Those two bundles travel different routes through tax treatment. Input VAT deductibility differs, and the exchange rate at which a foreign-currency amount enters the books has to be decided separately. With a monthly subscription, that decision repeats every month. Three things are worth confirming during review: whether the invoice carries your legal entity name and business registration number, whether the contract can be issued in Korean, and whether the documents satisfy what an audit asks for. If any of the three does not line up, the cost is not only a slower rollout — it comes back at the next year-end close. The form of the paperwork follows the contracting route, so finance should read the contract before it is signed. After signature, changing the evidence means reopening the contract.

A direct contract with an overseas supplier brings two tax judgements with it. The first is VAT. When a foreign supplier provides electronic services into Korea, who files and pays depends on the nature of the customer and on whether the supplier is registered locally. In business-to-business transactions there is a position where the recipient accounts for the tax. The second is withholding. Whether the payment is a royalty or a fee for services changes the withholding obligation, and the tax treaty with the supplier's country then adjusts the rate. The starting point for both is the wording of the contract: it has to be readable there whether a licence to use software was granted or a service was performed. Applying a treaty also brings the step of obtaining a certificate of residence from the counterparty. Contract with a Korean entity and both judgements become a domestic transaction and disappear. An organisation with a tax function absorbs them; an organisation without one finds this single item deciding the route.

Overseas price lists are usually written in dollars. Left as they are, they move the budget every month. Where billing is in won, the party issuing the bill absorbs the currency movement; where billing is in foreign currency, you absorb it. Either way, check the conversion point. Contract-date rate, invoice-date rate, and card-settlement-date rate produce different amounts for the same usage in the same month. Card payments add a foreign transaction fee, so the price list and the statement diverge from the start. Annual commitments and usage-based billing separate here. An annual commitment fixes the amount once and makes budgeting easy, at the cost of buying the unused portion in advance. Usage-based billing tracks actual use but overruns the budget in peak season. Write down the lowest and the highest month of the last twelve and let that spread decide.

Most overseas contracts renew automatically. Miss the notice deadline and the next term simply begins, and from then on you pay for what you are not using. Four items are worth finding in the contract first: the start and end of the term; how many days before termination notice is due and in what form; whether exceeding a usage limit promotes you automatically to a higher tier; and whether there is any point at which the volume can be reduced mid-term. Put those four on a calendar a month ahead of the notice deadline, with an owner's name attached. When the person who created the account is not the person who manages the contract, that calendar is the only thing connecting them. Contracts routed through a Korean partner bring renewal notices in Korean ahead of time, and reduction talks run through the same desk. On a direct contract the notice email goes only to the account owner's address, so if that address is personal the notice never reaches the organisation.

Where you turn first during an incident differs by route. On a direct contract, the vendor's global support channel is the desk: the language and the time difference become part of the response time, and reproduction steps and logs have to be assembled on your side. Where a partner is in the middle, intake, reproduction, and cause isolation happen in Korea, and only what needs to go to the vendor goes. What matters is where the scope of support is written. Support attached to the licence agreement and support supplied by a Korean company under a separate agreement live in different documents and promise different response times. The cheaper route is not automatically the better one. Once the person who owns billing and the person who owns the technical relationship deal with different companies, there are two places to wait for a reply when something breaks. Separate onboarding support from ongoing support as well: the first ends once, the second runs the whole term, and most of the price difference sits in the second.

Whatever the route, the servers that actually process the data are overseas. If the service touches personal data, settle the cross-border transfer notice and consent before rollout. The privacy policy has to name the recipient, the items transferred, the destination country, and the retention period, and the list of sub-processors the vendor in turn relies on has to be read alongside it. Even when the contract runs through a Korean company, the vendor's data processing terms define the responsibility structure. Put that document on the review table together with the scope of the security certifications, the data residency, and the deletion procedure at the end of the contract. It is the item most often postponed when a rollout is urgent, and postponing it brings it back during a privacy review. Routed through a Korean partner, these documents are reviewed in Korean and the open questions are put to the vendor from the same desk, which removes the meeting where legal and the privacy owner arrive with two different readings of an English agreement.

Once the items above are settled, the request document gets short. One line each for the counterparty's legal name, the billing currency and payment method, the form of evidence, the term and the notice deadline, the support desk, and whether a cross-border transfer notice is required. Keep the licence cost and the implementation and operations cost on two separate lines. Merged into one, next year's increase cannot be read. When comparing quotes, do not look at the monthly unit price alone. For the same service, the route changes the tax handling, the hours your own people spend, and how hard the renewal conversation is — and that is part of the real cost. Settle the tool, then choose the route in that order, and the same service produces a different number.