A company's DART report: how to read Korean corporate disclosures before a B2B conversation
Read a company report in DART before B2B contact: confirm the entity, period and scope, keep the source, separate interpretation and prepare questions.
Article language: English

In this article
You are looking for one process, but the report describes an entire group. To stay focused, read the DART material with a specific question in mind: what can it tell you about the company you are considering approaching? First confirm the company, the type of material, the period and the scope of the description. Then find the passage relevant to the application and record its limits. A company's appearance in a disclosure system does not establish product fit, willingness to cooperate or ability to fulfil a future order.
This guide is about understanding a source before B2B contact. It does not assess an investment or a company's solvency. DART can help you prepare better questions if you separate the document's contents from your own assumptions. All examples are exercises in how to work. They do not describe an analysis of a particular company or relationships with Aeneia clients.
Start with a question the report might address
One possible task is to find out how a company describes activity connected with a particular process. Another is to determine whether the material concerns the relevant group entity. Both can be tied to a document. "Is this a good partner?" is too broad to settle from one report. Break it down into identity, scope of activity and issues requiring separate assessment.
In partner verification in Korea, Japan or China (in Polish), disclosure data is one possible source. It does not replace checking the product page, clarifying the company's role or discussing the task. Decide what would make the review useful: identifying the right entity and preparing three questions for a conversation may be more valuable than summarising everything the company has published.
Understand the system and where information comes from
The official OpenDART service says that information in its data search comes from disclosures prepared under the responsibility of the filer. It also advises comparison with the original reports. This view of periodic information covers companies that have filed the relevant reports. An entity's absence from such a result is not an assessment of its business. This boundary matters: the institution provides the system, but the material still has to be read in context. An official address does not make every interpretation of what is found a verified fact.
Keep the full document, a data extract and your own notes distinct. Record the address and date accessed for each. If you use an export or a supporting tool, record where the result came from and how to return to the document. In East Asian market monitoring (in Polish), the same trail helps you later tell whether the report, the method of obtaining data or only the analyst's commentary has changed.
Confirm the entity before reading the story of the whole group
Compare the original name, any available identifier and contact details with the material that started the conversation. Check whether you are dealing with a parent company, a subsidiary or another business using a similar brand. If a model helps extract these connections, check the type, direction and source basis of each relationship in a knowledge graph (in Polish), rather than simply accepting a line between names. A name on a product page may not be enough to assign an entire report to that entity. If the relationship cannot be established, leave the question open and name the gap.
The FSS guide describes company information, the original disclosure file and corporation codes separately. Structure your source record so these elements can be connected. When combining results, use rules for organising an Asian company database (in Polish). Similar-sounding names are a lead to investigate, not sufficient reason to merge entities.
Record the document type, period and scope
Before drawing a conclusion, check when the material was published and what period it covers. The download date is not the date of the event described. Also establish whether you are reading an original document, a correction or a later supplement. If you cannot determine how the versions relate, do not combine passages into one account without stating that uncertainty. The newest file you find will not necessarily answer your precise question.
Check whether the information concerns one company, the group or a particular line of business. Do not automatically apply a group description to the entity corresponding with you. When reading a market report about Korea (in Polish), the scope of the data matters as much as the value. Apply the same discipline to a company report: first establish what the material describes, then assess what it means for the planned conversation.
Find the passage related to the application
Do not begin by summarising the entire document. Look for a product, process or business area relevant to the task. Read the surrounding paragraphs and footnotes too. A technology may appear in a description of current activity, a former project or a plan. A search hit alone does not tell you which. Preserve that distinction and the exact location in your notes. For Korean smart factory solutions (in Polish), for example, clarify whether the description concerns equipment, software, a service or integration. A broad industry label does not yet explain the company's role in the application.
For an important term, keep a working explanation in your own language and the original wording. If a conclusion depends on its meaning, have it checked by someone who knows both the language and the subject. A technical glossary for Korean and Japanese (in Polish) can preserve terminology decisions. You do not need to translate an entire report to define the scope of one question. You do need to understand reliably the passage on which an important claim rests.
Distinguish activity, an announced plan and your own hypothesis
Record three levels in an analysis note. The first is information stated in the document. The second is your interpretation of its connection to the project. The third is a question that remains to be checked. For example, a report describes a business area; the team suspects it may relate to the product's application; the role of the particular entity and the need to change the current solution remain open. These are not three equivalent pieces of evidence of demand.
Do not turn a planned project into confirmed delivery capability. Nor should you assume that the technology described is currently offered to external customers. Competitor analysis in Korea (in Polish) requires a similar distinction: the existence of a solution, a public offer and use by a customer answer different questions. A report can point towards further checks while leaving important conditions entirely open.
Practise the source record with a hypothetical business description
Suppose a Polish company is looking for a buyer for a component used in measuring equipment. It finds the name of a related process in a report. This is a workshop example. The analyst records what the passage concerns and which entity it describes, without immediately marking the record as a potential buyer. First they check whether that entity carries out the process, whether the report describes work with another entity and whether the passage concerns current activity.

Next they compare the information with a public product sheet. If the materials concern different variants, they record the discrepancy. If the connection cannot be established, they prepare a question for the contact rather than filling the gap with an assumption. When resolving conflicting sources about Asian markets (in Polish), the scope and provenance of information matter. Two sources can both be correct while being unsuitable for combination into one claim.
The result is a short note: the description found warrants further investigation of the application, but it does not establish demand for the component. The document, passage and unknown are identified. This is less dramatic than calling someone an ideal partner, but it gives the team concrete work. A report does not need a crystal ball. It only needs to help the team ask the right question.
Establish what the report alone cannot tell you
Open questions might include the current purchasing process, the person assessing the application, test conditions and willingness to talk. A lack of this information in the material reviewed does not prove the company does not carry out the activity. It is a limit of the check. Record what you read, the words you searched for and what remained outside that scope. The next person will then be less likely to confuse an absence of data with a negative answer.
Do not assess future order fulfilment from a single business description either. If a decision needs a different kind of analysis, separate it from this review. In a brief for Asian market research (in Polish), name the scope and expected result. A commission may cover finding documents and preparing B2B questions. It should not quietly become a broader assessment for which neither the material nor the appropriate expertise has been assembled.
Prepare a note that can be checked
For every important finding, give the entity, document, period, passage and date accessed. Place your interpretation, reasoning and next action alongside it. Identify passages that received a language check. If a working translation was used, retain that information. The person approving the note should know where the source reading ends and the team's own choice begins. Pasting a document address beneath an emphatic conclusion is not enough.
Review several findings, including one that remains unresolved. Ask to trace a sentence in the note back to the source passage. Then check that the interpretation does not go beyond the text. If the author cannot show that connection, refine the conclusion. The value is in reasoning that someone else can check. A downloaded folder does not become an analyst just because it gets heavier. Even a very long document may provide only one answer useful to a particular task.
Turn the finding into a question for the contact
Prepare a short question about the application that refers to the passage you read. A working draft might say: we found the specified process in a public business description and would like to establish whether it relates to the task for which our component is intended. Give the document and section so the recipient knows what you mean. Do not present your assumption as information confirmed by their company.
Choose one unknown next: perhaps the entity responsible for the process, the scope of application or the right person to discuss its assessment. Do not immediately ask about every area of the company's business. The recipient can understand the task more easily when the connection between source, application and proposed next step is clear. Reading a report is not in itself a reason for the other party to spend time on an entire presentation.
Also check whether the question contains an unverified claim. A sentence that assumes the company is developing a particular product now may be wrong if the document describes only a possibility or a historical project. Return to a neutral question about the scope of activity. This small editorial choice changes the conversation: the other party does not have to begin by correcting a story it never told.
Record the result when an important passage is not found
Record the documents, period and terms checked. If you examined only selected sections, do not describe the result as a full review of all disclosures. A passage not found may justify a question to the contact, reading another document or closing that line of enquiry within the agreed scope. The choice depends on the importance of the unknown to the project. Not every gap requires more searching, but every important gap needs the right label.
Add what could change the assessment: a new document, clarification of the relationship between entities or confirmation of the application. The review then has a clear stopping point and a condition for updating it. Someone returning to the matter months later need not start from zero or treat an earlier lack of data as a permanent characteristic of the business. This is especially useful when responsibility for the contact changes hands.
Close the review with a decision about further checks
The result may identify the right entity to approach, a term that needs checking or insufficient grounds to attribute an application. Each outcome is useful if its basis is clear. In the final market research recommendation (in Polish), connect the finding to a project decision. Do not simply add the report to a source folder without explaining which passage actually affected the plan.
For work with Aeneia Oriens, a useful starting point is the entity's name, a known document and a question connected to the intended cooperation. A clearly scoped review can support a B2B conversation with an identified basis and limits to what is known. The result can be updated when new material appears.
Aeneia Oriens
Bring the document and the passage about the company's activity that you want to understand. We can discuss the scope of source research and the checks on meaning needed to prepare for a specific conversation.









