{"id":147,"date":"2026-08-17T20:07:11","date_gmt":"2026-08-17T13:07:11","guid":{"rendered":"https:\/\/bkmos.com\/en\/?p=147"},"modified":"2026-08-17T20:07:11","modified_gmt":"2026-08-17T13:07:11","slug":"cross-border-business-document-checklist","status":"publish","type":"post","link":"https:\/\/bkmos.com\/en\/blog\/cross-border-business-document-checklist\/","title":{"rendered":"Cross-Border Business Document Checklist: A Practical Guide"},"content":{"rendered":"
\n

<\/p>\n

\n
\n<\/p>\n\n\n
<\/p>\n


\n CROSS-BORDER BUSINESS DOCUMENTS
\n <\/span><\/p>\n


\n Cross-border business often requires documents from several parts
\n of an organization: corporate records, contracts, financial statements,
\n tax documents, employment records, licenses, certificates and
\n supporting commercial materials.\n <\/p>\n


\n Before translation begins, the most important question is not simply
\n \u201cWhich files are in another language?\u201d It is \u201cWhich documents does the
\n receiving bank, authority, partner, investor, customer or institution
\n actually require, and in what form?\u201d\n <\/p>\n<\/td>\n

<\/p>\n
<\/p>\n

\"Cross-border<\/p>\n<\/figure>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

\n

\n Translation, certification, notarization-related processing,
\n authentication or legalization may be required for some documents,
\n while other files may only need a clear professional translation.
\n The exact route depends on the destination, document type and receiving authority.\n <\/p>\n

\n This checklist helps businesses organize a multilingual document package
\n before submission and identify where translation or formal document
\n processing may be required.\n <\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n QUICK OVERVIEW<\/span><\/p>\n

Four Questions to Answer Before Preparing the File<\/h2>\n<\/p><\/div>\n
\n
\n 01<\/span><\/p>\n

Who Will Receive It?<\/h3>\n

\n A bank, court, investor, government agency, customer or business partner
\n may have different document requirements.\n <\/p>\n<\/article>\n

\n 02<\/span><\/p>\n

Which Documents Are Required?<\/h3>\n

\n Obtain the receiving party’s checklist whenever possible instead
\n of translating every available company record.\n <\/p>\n<\/article>\n

\n 03<\/span><\/p>\n

What Formality Is Required?<\/h3>\n

\n Confirm whether ordinary translation, certified translation
\n or additional formal processing is required.\n <\/p>\n<\/article>\n

\n 04<\/span><\/p>\n

Which Version Is Final?<\/h3>\n

\n Use current signed or issued documents and prevent obsolete
\n drafts from entering the translation package.\n <\/p>\n<\/article><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n
\n COMPANY & CORPORATE RECORDS<\/span><\/p>\n

Start With the Documents That Establish the Business<\/h2>\n

\n Cross-border transactions often begin with documents that identify
\n the company, its legal status, authorized representatives and ownership
\n or governance structure.\n <\/p>\n

\n The exact corporate package varies by jurisdiction and transaction.
\n Some recipients may request only a business registration record,
\n while others may require resolutions, charters, powers of attorney
\n or evidence of authorized signatories.\n <\/p>\n

\n Company names, registration numbers, addresses and representative names
\n should remain consistent across every translated document in the package.\n <\/p>\n<\/p><\/div>\n

\n
\n

Business Registration<\/h3>\n

Company registration, incorporation or enterprise registration records.<\/p>\n<\/p><\/div>\n

\n

Charter \/ Articles<\/h3>\n

Articles of association, company charter or equivalent constitutional documents.<\/p>\n<\/p><\/div>\n

\n

Board & Shareholder Resolutions<\/h3>\n

Approvals for transactions, appointments, investments or corporate actions.<\/p>\n<\/p><\/div>\n

\n

Power of Attorney<\/h3>\n

Authorization for an individual or entity to act on behalf of the company.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n LEGAL & CONTRACT DOCUMENTS<\/span><\/p>\n

Commercial Relationships Generate Their Own Document Set<\/h2>\n<\/p><\/div>\n
\n
\n Contracts & Agreements<\/strong><\/p>\n

Sales, supply, service, distribution, agency and other commercial agreements.<\/p>\n<\/p><\/div>\n

\n NDAs<\/strong><\/p>\n

Confidentiality agreements and information-protection provisions.<\/p>\n<\/p><\/div>\n

\n Licensing Agreements<\/strong><\/p>\n

Technology, software, brand, trademark and intellectual-property agreements.<\/p>\n<\/p><\/div>\n

\n Terms & Conditions<\/strong><\/p>\n

Formal commercial terms used in transactions, services and online business.<\/p>\n<\/p><\/div>\n

\n Legal Notices<\/strong><\/p>\n

Formal notices, demands, confirmations and transaction-related correspondence.<\/p>\n<\/p><\/div>\n

\n Supporting Legal Records<\/strong><\/p>\n

Amendments, schedules, annexes and related legal documentation.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n
\n FINANCIAL & BANKING RECORDS<\/span><\/p>\n

Financial Documents Often Support Due Diligence and Funding<\/h2>\n

\n Banks, investors, partners and parent companies may request financial
\n information to assess the business, confirm transactions or support
\n financing and reporting.\n <\/p>\n

\n Financial translation requires careful handling of accounting terminology,
\n figures, dates, currencies, reporting periods and notes.\n <\/p>\n

\n The translation should reflect the source document rather than silently
\n recalculate figures or convert the financial statements into another
\n accounting framework.\n <\/p>\n<\/p><\/div>\n

\n
\n

Financial Statements<\/h3>\n

Balance sheets, income statements, cash-flow statements and notes.<\/p>\n<\/p><\/div>\n

\n

Audit Reports<\/h3>\n

Auditor reports, opinions and related financial disclosures.<\/p>\n<\/p><\/div>\n

\n

Bank Statements<\/h3>\n

Account information, transaction records and banking evidence.<\/p>\n<\/p><\/div>\n

\n

Payment Evidence<\/h3>\n

Transfer confirmations, receipts and supporting transaction records.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n TAX & COMPLIANCE DOCUMENTS<\/span><\/p>\n

Regulatory Files Should Be Identified Early<\/h2>\n<\/p><\/div>\n
\n
\n Tax Registration<\/strong><\/p>\n

Tax identification and registration documents relevant to the business.<\/p>\n<\/p><\/div>\n

\n Tax Certificates<\/strong><\/p>\n

Tax-status, payment or compliance certificates where required.<\/p>\n<\/p><\/div>\n

\n Licenses & Permits<\/strong><\/p>\n

Operating licenses, sector permits and other official business authorizations.<\/p>\n<\/p><\/div>\n

\n Compliance Statements<\/strong><\/p>\n

Declarations and records used in regulatory or business onboarding procedures.<\/p>\n<\/p><\/div>\n

\n Quality Certificates<\/strong><\/p>\n

Management, product or process certifications used in commercial qualification.<\/p>\n<\/p><\/div>\n

\n Insurance Documents<\/strong><\/p>\n

Policies, certificates and evidence of required coverage.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n
\n TRADE & COMMERCIAL DOCUMENTS<\/span><\/p>\n

International Trade Creates a Separate Operational Paper Trail<\/h2>\n

\n Import, export and supply transactions may involve product,
\n shipping and commercial records in addition to company documents.\n <\/p>\n

\n These files often contain product codes, quantities, values,
\n weights, specifications and references that should remain aligned
\n across the translated package.\n <\/p>\n

\n The exact documentation depends on the transaction and destination,
\n so businesses should confirm requirements with the relevant commercial,
\n logistics, customs or regulatory parties.\n <\/p>\n<\/p><\/div>\n

\n
\n

Commercial Invoices<\/h3>\n

Seller, buyer, goods, quantities, pricing and transaction details.<\/p>\n<\/p><\/div>\n

\n

Certificates of Origin<\/h3>\n

Origin information and supporting trade documentation.<\/p>\n<\/p><\/div>\n

\n

Packing Lists<\/h3>\n

Packages, quantities, weights and shipment information.<\/p>\n<\/p><\/div>\n

\n

Product Certificates<\/h3>\n

CO\/CQ, conformity, inspection and other product-related records where applicable.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n EMPLOYMENT & PERSONNEL FILES<\/span><\/p>\n

International Operations May Also Require Employee Documents<\/h2>\n<\/p><\/div>\n
\n
\n Employment Contracts<\/strong><\/p>\n

Terms of employment, assignments and personnel agreements.<\/p>\n<\/p><\/div>\n

\n Employment Certificates<\/strong><\/p>\n

Position, employment period, salary or experience confirmation.<\/p>\n<\/p><\/div>\n

\n CVs & Professional Profiles<\/strong><\/p>\n

Qualifications and experience for managers, experts and project personnel.<\/p>\n<\/p><\/div>\n

\n Diplomas & Certificates<\/strong><\/p>\n

Academic and professional credentials supporting personnel qualifications.<\/p>\n<\/p><\/div>\n

\n Passport \/ Identity Records<\/strong><\/p>\n

Personal identification where required for authorized representatives or personnel.<\/p>\n<\/p><\/div>\n

\n Work-Related Records<\/strong><\/p>\n

Assignment letters, reference letters and other supporting employment documents.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n
\n IDENTITY & CONSISTENCY<\/span><\/p>\n

Match Names, Numbers and Addresses Across the Entire Package<\/h2>\n

\n Cross-border files are often reviewed as a set rather than one document
\n at a time. Inconsistent company names, personal names, registration
\n numbers or addresses can therefore create unnecessary questions.\n <\/p>\n

\n Before translation starts, establish the approved English or target-language
\n form of important names and identifiers where one exists.\n <\/p>\n

\n Translators should preserve identifiers exactly and use the same naming
\n convention throughout related files.\n <\/p>\n<\/p><\/div>\n

\n
Company name \u2192 One approved form<\/strong><\/div>\n
Representative name \u2192 Match passport \/ approved form<\/strong><\/div>\n
Registration number \u2192 Reproduce exactly<\/strong><\/div>\n
Address \u2192 Use a consistent target-language rendering<\/strong><\/div>\n
Dates \u2192 Check format and source accuracy<\/strong><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n<\/p>\n\n\n
<\/p>\n

TRANSLATION & FORMAL PROCESSING<\/span><\/p>\n

\n Do Not Assume Every Document Follows the Same Certification Route
\n <\/h2>\n

\n Some business documents may only need a professional translation.
\n Others may require certified translation or additional official
\n processing before they are accepted abroad.\n <\/p>\n

\n Requirements can differ by document type, issuing country,
\n destination and receiving authority. The organization requesting
\n the document should therefore be treated as the primary source
\n for acceptance requirements.\n <\/p>\n

\n Confirm the required route before ordering unnecessary steps,
\n especially when originals, signatures or physical processing are involved.\n <\/p>\n


\n CERTIFIED TRANSLATION SERVICES
\n <\/a><\/p>\n<\/td>\n

<\/p>\n
\n
\n Professional translation \u2192 Confirm whether sufficient<\/strong>\n <\/div>\n
\n Certified translation \u2192 Use when specifically required<\/strong>\n <\/div>\n
\n Notarization-related processing \u2192 Follow applicable local procedure<\/strong>\n <\/div>\n
\n Authentication \/ legalization \u2192 Confirm destination requirements<\/strong>\n <\/div>\n
\n Original documents \u2192 Check whether originals or copies are required<\/strong>\n <\/div>\n<\/p><\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n
\n SOURCE DOCUMENT QUALITY<\/span><\/p>\n

Translation Cannot Fix an Incomplete Source File<\/h2>\n

\n Missing pages, cut-off seals, unreadable signatures and blurred figures
\n can delay translation and create uncertainty during review.\n <\/p>\n

\n Before sending documents, check that every page is present,
\n readable and belongs to the correct version of the file.\n <\/p>\n

\n For documents with stamps, seals, handwritten notes or marginal text,
\n scan the full page rather than cropping only the main printed content.\n <\/p>\n<\/p><\/div>\n

\n
\n

Complete Pages<\/h3>\n

Include every page, even where a page contains only signatures or notes.<\/p>\n<\/p><\/div>\n

\n

Readable Scans<\/h3>\n

Ensure text, numbers, stamps and handwritten information can be reviewed.<\/p>\n<\/p><\/div>\n

\n

Full Page Area<\/h3>\n

Do not crop seals, page numbers, margins or official markings.<\/p>\n<\/p><\/div>\n

\n

Correct Version<\/h3>\n

Confirm that signed and current documents replace earlier drafts.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n
\n VERSION CONTROL<\/span><\/p>\n

Keep Drafts, Signed Copies and Revisions Clearly Separated<\/h2>\n

\n Cross-border projects can evolve quickly. Contracts are revised,
\n financial reports are updated and corporate resolutions may change
\n before the final submission.\n <\/p>\n

\n Clear file names and version information help prevent an obsolete
\n source document from being translated or included in the final package.\n <\/p>\n

\n For larger submissions, maintain a simple document register showing
\n source version, translation status and final delivery status.\n <\/p>\n<\/p><\/div>\n

\n
Draft \u2192 Identify clearly<\/strong><\/div>\n
Signed \/ issued version \u2192 Prioritize for final translation<\/strong><\/div>\n
Revision date \u2192 Keep visible<\/strong><\/div>\n
Translation status \u2192 Track pending \/ reviewed \/ final<\/strong><\/div>\n
Submission package \u2192 Remove superseded files<\/strong><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n
\n CONFIDENTIALITY<\/span><\/p>\n

Cross-Border Business Files Can Contain Sensitive Information<\/h2>\n

\n Contracts, financial statements, bank records, employee documents
\n and transaction materials may contain confidential business or personal data.\n <\/p>\n

\n Before files are shared, identify any NDA, access-control,
\n secure-transfer or file-retention requirements that apply to the project.\n <\/p>\n

\n This is especially important when several external parties are involved
\n in the translation, certification or submission process.\n <\/p>\n<\/p><\/div>\n

\n
\n

NDA<\/h3>\n

Confirm confidentiality terms where required by the organization.<\/p>\n<\/p><\/div>\n

\n

Access Control<\/h3>\n

Limit project access to people who need the documents.<\/p>\n<\/p><\/div>\n

\n

Secure Transfer<\/h3>\n

Use an appropriate method for transmitting sensitive files.<\/p>\n<\/p><\/div>\n

\n

Retention<\/h3>\n

Agree on any project-specific file-retention or deletion requirements.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n MASTER CHECKLIST<\/span><\/p>\n

Cross-Border Business Document Preparation Checklist<\/h2>\n<\/p><\/div>\n
\n
\n 1. Receiving Requirement<\/strong><\/p>\n

Obtain the document list and acceptance instructions from the receiving party.<\/p>\n<\/p><\/div>\n

\n 2. Current Documents<\/strong><\/p>\n

Confirm that registrations, contracts, statements and certificates are current.<\/p>\n<\/p><\/div>\n

\n 3. Name Consistency<\/strong><\/p>\n

Standardize company, representative and address forms across related files.<\/p>\n<\/p><\/div>\n

\n 4. Translation Scope<\/strong><\/p>\n

Identify which documents and which visible elements require translation.<\/p>\n<\/p><\/div>\n

\n 5. Formality<\/strong><\/p>\n

Confirm certification, notarization-related or legalization requirements before processing.<\/p>\n<\/p><\/div>\n

\n 6. Final QA<\/strong><\/p>\n

Check names, numbers, dates, figures, stamps, page count and completeness.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n BKMOS WORKFLOW<\/span><\/p>\n

Cross-Border Business Document Translation Workflow<\/h2>\n<\/p><\/div>\n
\n
\n 1<\/span><\/p>\n

Requirement Review<\/h3>\n

Review destination, receiving party, document types, languages and deadlines.<\/p>\n<\/p><\/div>\n

\n 2<\/span><\/p>\n

Document Preparation<\/h3>\n

Confirm source quality, current versions, names and formal processing needs.<\/p>\n<\/p><\/div>\n

\n 3<\/span><\/p>\n

Translation & QA<\/h3>\n

Translate and review terminology, figures, identifiers, formatting and completeness.<\/p>\n<\/p><\/div>\n

\n 4<\/span><\/p>\n

Processing & Delivery<\/h3>\n

Complete agreed formal processing and deliver the final document package.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n RELATED RESOURCES<\/span><\/p>\n

Related BKMOS Business Translation Resources<\/h2>\n<\/p><\/div>\n
\n
\n Certified & Notarized Translation<\/strong><\/p>\n

\n Understand translation and formal processing options
\n for documents intended for official use.\n <\/p>\n


\n Certified Translation \u2192
\n <\/a>\n <\/div>\n

\n Legal Translation<\/strong><\/p>\n

\n Translation of contracts, corporate documents
\n and other formal legal materials.\n <\/p>\n


\n Legal Translation \u2192
\n <\/a>\n <\/div>\n

\n Financial Statement Translation<\/strong><\/p>\n

\n A practical guide to financial translation
\n for cross-border reporting and business use.\n <\/p>\n


\n Financial Statement Translation \u2192
\n <\/a>\n <\/div>\n

\n Tender & Construction Translation<\/strong><\/p>\n

\n Document control for international bids,
\n technical specifications and commercial submissions.\n <\/p>\n


\n Tender Translation \u2192
\n <\/a>\n <\/div>\n

\n How to Evaluate a Translation Provider<\/strong><\/p>\n

\n A buyer’s framework for assessing expertise,
\n security, quality, workflow and pricing.\n <\/p>\n


\n Provider Evaluation Guide \u2192
\n <\/a>\n <\/div>\n

\n Specialized Translation<\/strong><\/p>\n

\n Financial, technical, medical, legal and other
\n specialist translation for international business.\n <\/p>\n


\n Specialized Translation \u2192
\n <\/a>\n <\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n FREQUENTLY ASKED QUESTIONS<\/span><\/p>\n

Cross-Border Business Document FAQs<\/h2>\n<\/p><\/div>\n
\n
\n

Which business documents usually need translation?<\/h3>\n

\n Common examples include corporate registrations, contracts, financial
\n statements, bank records, licenses, tax documents, employment records
\n and trade documents. The exact list depends on the transaction and receiving party.\n <\/p>\n<\/p><\/div>\n

\n

Do all translated business documents need notarization?<\/h3>\n

\n No. Requirements vary by document, destination and receiving authority.
\n Confirm what form of translation or formal processing is actually required.\n <\/p>\n<\/p><\/div>\n

\n

Should we translate every company document before an international transaction?<\/h3>\n

\n Usually not. Start with the receiving party’s document checklist
\n and prioritize only the records required for the specific purpose.\n <\/p>\n<\/p><\/div>\n

\n

Why is name consistency important?<\/h3>\n

\n Company names, representative names, registration numbers and addresses
\n may appear across many documents. Inconsistent translations can create
\n confusion when the package is reviewed as a whole.\n <\/p>\n<\/p><\/div>\n

\n

Can BKMOS translate financial, legal and technical documents in the same package?<\/h3>\n

\n Depending on the language pair and project scope, related document types
\n can be coordinated under one project so terminology, company information
\n and version control remain consistent.\n <\/p>\n<\/p><\/div>\n

\n

What should we send for a quotation?<\/h3>\n

\n Send representative files, source and target languages, destination
\n or intended use, required processing if known, final format and deadline.\n <\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n

EXPERT REVIEW<\/span><\/p>\n

Reviewed by Nguyen Dinh Phuc<\/h2>\n

\n Founder & CEO of BKMOS. Working in professional translation
\n since 2005 and responsible for BKMOS’s professional direction,
\n translation workflows and expert content.\n <\/p>\n

\n This article provides a translation and document-preparation checklist.
\n It does not replace legal, tax, customs, banking or regulatory advice.
\n Requirements should be confirmed with the relevant receiving authority
\n or qualified professional.\n <\/p>\n


\n About BKMOS \u2192
\n <\/a><\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n
\n CROSS-BORDER BUSINESS TRANSLATION<\/span><\/p>\n

Preparing Business Documents for International Use?<\/h2>\n

\n Send BKMOS representative files together with the target language,
\n destination or intended use, known certification requirements
\n and deadline. We will review the document package and translation
\n scope before quoting.\n <\/p>\n<\/p><\/div>\n

\n
\n GET A DOCUMENT QUOTE
\n <\/a>\n <\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

CROSS-BORDER BUSINESS DOCUMENTS Cross-border business often requires documents from several parts of an organization: corporate records, contracts, financial statements, tax documents, employment records, licenses, certificates and supporting commercial materials. Before translation begins, the most important question is not simply \u201cWhich files are in another language?\u201d It is \u201cWhich documents does the receiving bank, authority, partner, […]\n","protected":false},"author":1,"featured_media":148,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-147","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-technical-business-translation"],"_links":{"self":[{"href":"https:\/\/bkmos.com\/en\/wp-json\/wp\/v2\/posts\/147","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bkmos.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bkmos.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bkmos.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/bkmos.com\/en\/wp-json\/wp\/v2\/comments?post=147"}],"version-history":[{"count":1,"href":"https:\/\/bkmos.com\/en\/wp-json\/wp\/v2\/posts\/147\/revisions"}],"predecessor-version":[{"id":149,"href":"https:\/\/bkmos.com\/en\/wp-json\/wp\/v2\/posts\/147\/revisions\/149"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/bkmos.com\/en\/wp-json\/wp\/v2\/media\/148"}],"wp:attachment":[{"href":"https:\/\/bkmos.com\/en\/wp-json\/wp\/v2\/media?parent=147"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bkmos.com\/en\/wp-json\/wp\/v2\/categories?post=147"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bkmos.com\/en\/wp-json\/wp\/v2\/tags?post=147"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}