17 May 2026
Tagging conventions that finance teams in Korea can actually use
Tags only help cost attribution when they match how finance already reports. Align labels with cost centres early.
Engineering often invents tag keys that describe services. Finance usually needs cost centre, product line, and environment. When those vocabularies diverge, monthly attribution meetings become translation exercises instead of decisions.
Agree on a short mandatory set: application id, environment, and cost centre. Optional tags for feature team or data classification can follow later. Enforce the mandatory set at account creation and during pull-request checks for infrastructure definitions.
For shared platforms — logging clusters, identity services, CI runners — publish an allocation rule in writing. Percentage splits or per-request charges both work; silence does not. Cloud Solutions Hub documents these rules during spend attribution reviews so quarterly closes do not reopen old debates.
Review tags whenever a product reorganises. Stale cost centres are as damaging as missing tags, because they send accurate charges to the wrong owner.