Notes from a PM's desk.
- 翻訳PMのデスクからのメモ。
- 翻译项目经理的工作笔记。
- 번역 PM의 업무 노트.
- Notizen vom Schreibtisch eines Projektmanagers.
- Заметки менеджера переводческих проектов.
- Tarjima loyihasi menejerining qaydlari.
- ملاحظات من مكتب مدير مشاريع الترجمة.
Purchase orders in translation: client and vendor POs
A translation job can have two purchase orders. The client sends one to the agency. The agency issues a separate PO to an outside linguist. They cover different agreements, so keep both references clear.
A missing reference can hold up an invoice. A reference with the wrong language pair or word count can cause a dispute. Check the terms as well as the number.
Client PO and vendor PO: who issues each one?
The client PO. This records the work the client has approved. Check the scope, price and billing details against your quote. Ask which PO reference must appear on your client invoice.
The vendor PO. This records the work you assign to a linguist. It should identify the task, service, language pair, agreed fee and deadline. Keep it with the assignment so both sides can check the terms.
The Translator's Guide to the Industry advises translators to check a PO and raise any mismatch at once. That is useful advice for the PM issuing it too.
What a PO gate checks
A PO gate is a rule that blocks a workflow step until a PO reference is present. Choose the step based on the agreement you need to protect. A client approval check before work starts serves a different purpose from a vendor PO check before closing a job.
A number alone does not prove that the client approved the work. Keep the approval email or PO document too. Someone must check that it covers the right scope and price.
Check scope before work starts
Source changes. A client approves 50,000 words, then sends 30,000 more. This is an invented example, but the check is simple: agree the added fee before translating the extra text. Update the quote and PO where needed.
Rush work. A PM receives a request for an urgent add-on. Confirm who at the client can approve the extra cost. Keep that approval with the job.
Many language pairs. Check that the client PO covers every language ordered. On the vendor side, check each linguist's service and fee separately.
Long projects. Record the billing contact as well as the PM. A job can outlast the person who first approved it.
Set up a PO workflow for your agency
Choose the checkpoint. Decide whether you need client approval before assignment, vendor PO references before closure, or both. Write down which check belongs at each stage.
Name the fields clearly. Use "Client PO" and "Vendor PO". A single field called "PO" leaves room for the wrong number.
Define who checks the terms. The PM should compare the PO with the quote or assignment. Give the billing team a way to find that record.
Agree changes in writing. When the source, deadline or service changes, check whether the price changes too. Keep the approval and the revised terms together.
Match the invoice to the right PO. A client invoice uses the client's reference. A vendor invoice relates to the linguist's work. Use our translation invoice checklist to check the rest of the bill.
How KanCAT checks vendor PO numbers
In KanCAT, the PM adds a vendor PO number to each external assignment. A job cannot move to Done while an external assignment is missing one. In-house linguists are exempt. This rule is not limited to Team Pro.
The number also appears on vendor invoice lines. This is a vendor PO check. It does not validate a client's purchase order or add the client's PO number to a client invoice.
Teams can use custom Kanban columns and PM approval checkpoints to organise the wider job flow. See the translation project board features. Check client approval through your agency's own process before work starts.
Ask for the reference before you need it
Use a direct request: "Please confirm the approved scope and the PO reference your accounts team needs on our invoice."
If the client has no PO process, ask what written approval their billing team accepts. Keep that reply. A company with no formal PO system can still agree a job in writing.
Keep a record you can find later
Keep the quote, client approval, vendor assignment and invoices under the job reference. When scope changes, retain the earlier version as well as the approved change.
Store records for the period your local rules require. KanCAT records account activity, but customers cannot view or export that log. Keep your own PO register and approval files.
Start by checking one completed job. Can another PM find who approved the work, what each linguist was owed and which invoice covers it? Any missing link gives you a concrete place to improve the process.