---
title: "Drilling Down to Original Posting Level"
description: "For a posting with a DMS code, you can open the corresponding original document directly from the Show Postings dialog in your Document Management System."
source_url: https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/functions-ledgers-schedules/drilling-down-to-original-posting-level
language: en
last_updated: 2026-07-15
---
# Drilling Down to Original Posting Level

## Overview

If your organization uses a Document Management System (DMS) to store source documents such as invoices or receipts, you can open the original document for a posting directly from its posting data, without leaving Lucanet Consolidation & Financial Planning.

{% info-box %}
Drilling down to the original document is currently supported for cloud- and web-based Document Management Systems, including SharePoint.

Drill-down to on-premise Document Management Systems is not yet supported.
{% /info-box %}

## Prerequisites

Drilling down to the original document is only available for a posting if it was imported through a data source with a DMS script assigned in the **Display scanned documents** field **and** it has a **DMS code** populated during import (see [Defining a Data Source](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source.md)).

{% info-box %}
Configuring the DMS script and connecting it to your Document Management System is done by an administrator in the **Scripts** workspace (see [Creating and Executing Scripts](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/create-scripts.md)). Contact your Lucanet consultant if this has not yet been set up for your organization.
{% /info-box %}

## Opening the Original Document

To open the original document for a posting:

{% stepper %}
{% stepper-step %}
In a ledger or schedule, double-click the desired account value to open the **Show Postings** dialog (see [Show Postings](https://support.lucanet.com/en/documentation/consolidation-financial-planning/report-analyze/elements-ledgers-schedules/postings.md)).
{% /stepper-step %}
{% stepper-step %}
In the value column, click the link of the value for which you want to view the posting data.

Link of a value to open its posting details

{% /stepper-step %}
{% stepper-step %}
In the **Drill down to posting level** dialog, select the value for which you want to display the original document and click the link behind **Posting**.

The Posting link in the 'Details on selected posting' section

**Note:** Posting is only displayed as a link if the prerequisites listed above are fulfilled. Otherwise, the posting is displayed as plain text.
{% /stepper-step %}
{% stepper-step %}
In the **Show Source Document** dialog, select the desired execution location for the script configured in the [data source](https://support.lucanet.com/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source.md) for displaying scanned documents. The drop-down list is pre-filled with the default configured for the data source.

**Note:** For scripts that require execution on the local machine, you need to select your on-premise [Script Execution Application (SEA)](https://support.lucanet.com/en/documentation/consolidation-financial-planning/basic-configuration-cfp/install-and-use-opsea.md) instance.

Show Source Document dialog

{% /stepper-step %}
{% stepper-step %}
Click **Open**.
The original document opens in a new browser tab.
{% /stepper-step %}
{% /stepper %}

## Troubleshooting

If the original document cannot be opened, an error message is displayed, for example:

| Message | Cause |
|---|---|
| System cannot find the file specified | The document could not be located in the document management system, for example because the DMS code does not match a document, or you do not have access to the file. |
| Other error messages | Any other error returned while the DMS script was executed. |

If the error persists, contact your administrator to check the configuration of the DMS script.