Translation offices and software localisation teams often incorporate a UK Ltd for corporate contracts and cross-border invoices. We file with Companies House via ACSP.
A translation business needs clear project records as well as a company. Define what each client is buying before you quote in the company's name.
A project brief that survives revisions
Record the languages, the version of the source file and the agreed deliverable. Separate translation from editing, terminology work, layout and software localisation. If a client needs the translation in a particular format for an official body, find out the requirement from the client before you start. A UK company registration does not make a translation acceptable to any particular recipient.
Keep the accepted brief, revisions, delivery record and invoice together. GOV.UK requires company records of money received and spent, backed by documents such as contracts and invoices. Linking them to each project makes a change of scope easy to explain.
In the order form, describe the work the company will actually do. We choose the matching SIC codes with you from that description.
Certified translations and the code we file
Some clients need a translation they can hand to an official body. GOV.UK's guidance on certifying documents, which covers documents used in the UK, says that for a document not in English or Welsh, the translator confirms in writing on the translation that it is a "true and accurate translation of the original document", adding the date of the translation and their full name and contact details. The organisation receiving it may have its own rules, so ask the client which apply.
On the formation side, the Companies House list gives SIC code 74300 for translation and interpretation activities. If the company will also do software localisation, subtitling or layout work, say so in the order form, and we agree the final codes with you.
Eteform is a registered ACSP, supervised by HMRC for anti-money laundering (XTML00000224050).