Localization Vendor QA: Translation Payments Priced Right and Paid Within Each Run's Cap

Per-word rates, rush fees and late penalties, rounded the way the agreement says

Every translation job carries its own small invoice: the word count in each match band from the translation memory, the vendor's rate for each band, a rush uplift when the deadline was short, and a penalty when delivery was late. The vendor agreement says each of those amounts is rounded down on its own, and that a job on QA hold is not paid until the hold clears. A cycle of fifty jobs across a dozen language pairs is detailed work.

The jobs are tracked in ClickUp, vendor invoices and quality reports land in Box, and the rate card and payment policy sit in Google Drive. Vendors answer QA holds and raise disputes in the localization mailbox in Outlook. Finance sets a cash cap on each payment run, so jobs that do not fit roll to the next one. The draft spend summary someone builds by hand is where a job from last cycle or a duplicate line usually hides.

Who works in the room

Pricing questions go to Ada without a mention, since it is the room's default agent and owns the pricing and the run allocation. Fin takes the spend summary audit, because checking another person's figures against the jobs is its specialty. Ryan reads vendor replies in the Outlook mailbox through a lasting grant the vendor manager approved for the room. When a vendor's note clears a hold or opens a dispute, Ryan mentions Ada in the thread with the job and the note, and Ada re-prices it before anything else moves.

Pricing a cycle and paying it

The rate card, the rounding rule and the run caps are written into the room guidelines, so every agent prices the same way and every amount waits for a person.

Rate amendments and unprompted vendor notes

A rate amendment for low-leverage work looks like a small edit, but the amount stored on each ClickUp job is the result of three rounded steps. Adjusting that stored amount would carry the old rounding forward. Ada recomputes each affected job from its word counts and the amended rate, step by step, and shows the old and new amounts in the thread before anything is written.

Vendor notes do not always arrive as replies to a request. A vendor may write unprompted to say a corrected file is in Box, and that still clears the hold once the language lead confirms the file. When a cleared job joins a run, Ada adds up the run again against its cap. If the job no longer fits, it moves to the next run rather than pushing the run over.

What the checks catch

• A job priced with the rush uplift and late penalty combined into one step, which rounds differently from three separate steps
• A recompute that started from the stored ClickUp amount instead of the word counts and rate
• A spend summary line for a job paid in last cycle's run, a job listed twice, or a job missing entirely
• A run total that goes over the cash cap once a cleared job is added
• A close-out written as a new list when the cycle's close-out list already exists in ClickUp

What stays with people

• Approving each job's payment and the run it goes into
• Confirming that a vendor's corrected delivery clears the QA hold
• Deciding disputes and sending notices to vendors, which Ryan prepares as drafts in Gmail
• Signing the cycle close-out

Integrations in this workflow

Kylon is not a translation management system or an accounts payable tool, and it does not replace either. It sits across the job tracker, file store and mailboxes the team already uses, and gives the work that passes between them a single place to live.

• Box
• ClickUp
• Gmail
• Google Drive
• Outlook
• Slack

• ClickUp tracks each translation job with its approved amount and payment run, and holds the close-out list for each language pair
• Box holds vendor invoices, delivered files and quality reports
• Google Drive keeps the rate card, the payment policy, the rate amendment and the draft spend summary
• Outlook is the localization mailbox where vendors answer holds and raise disputes
• Gmail carries payment and dispute notices to vendors, each a draft the vendor manager sends
• Slack is where language leads post quality calls and finance confirms the run caps

Where to start

Try one payment cycle with two or three language pairs. Connect the ClickUp list where jobs are tracked and the Box folder where invoices land, and write the rule the room cannot get wrong into its guidelines: each pricing step is rounded down separately, and nothing is written to ClickUp until the vendor manager approves.

“Three small roundings, in the order the agreement sets, are what make a payment match the vendor's own invoice.”

Set it up with your agent

Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.