> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/other-information/glossary/unclassified-data.md). # Unclassified data Learn what unclassified data means, why it occurs, and how it's represented in Phocas. Unclassified data is data that can't be matched to an entity in a dimension. For example: * In a Sales database, you might have sales that weren't allocated to a sales rep. * In a Finance database, you might have general ledger accounts that weren't mapped to an account group. ### Identify unclassified data How unclassified data is displayed depends on the module you're using. #### Analytics and Flex Modes Unclassified data is represented by **###** in the **Code** column.
#### Financial Statements Unclassified accounts are assigned to the **Suspense** group. See [Map accounts to a group](/financial-statements/managing-statements/customize-a-financial-statement/customize-groups.md#map-accounts-to-a-group). #### Budgets & Forecasts Unclassified data is represented by **###** in the **Code** on the applicable rows in the workbook. You can choose whether to include or exclude unclassified data in a budget workbook. See [Unclassified data in a budget](/budgets-and-forecasts/owner-and-administrator/create-a-budget/unclassified-data.md). ### Resolve unclassified data How you resolve unclassified data depends on why it couldn't be classified. You might need to correct the source data, such as data in your ERP system, or update the mapping or classification in Phocas. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.phocassoftware.com/other-information/glossary/unclassified-data.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.