Connected accounting maps
- Ian Fondrk (Unlicensed)
Table of contents
Overview
Like the transactions they represent, accounting records are not independent; they form relationships with other records called links. For example, an invoice record may link to several line-item records, and each line-item record may be associated with a tax record. When the invoice is paid, a payment record is created and linked back to the invoice.
Leapfin provides a visualization of these relationships using connected accounting maps. Accessible from any linked accounting record, these maps offer an aggregated view of your financial data and how different accounting records are connected within your dataset. They make it easier to trace the transactional journey and identify key relationships. Additionally, each map includes aggregated journal entry data for all the records contained within.
Accessing Connected Accounting Maps
You can access a connected accounting map from the main page of any record included in that particular transaction scenario. For example, if a transaction scenario includes an invoice, two line items, and one payment, you can access the same map from any of those records.
For more information on searching and navigating your accounting records, see View, filter, and export your accounting records.
How to use connected accounting maps
The following illustration explains the components of a typical connected accounting map and how these components relate to one another within your Leapfin database:
a. Graph: A snapshot of all related accounting records within a given transactional scenario. Depending on the scenario's complexity, a graph may contain a few records or hundreds. Your Leapfin database may contain millions of graphs, depending on the size of your dataset.
b. Record nodes: Each node represents a type of accounting record, such as a Line Item, Invoice, Payment, or Tax. Each node displays:
The name of the accounting record it represents.
The quantity of those record types within the graph (a single node may represent several accounting records).
The total number of journal entries related to that record type.
You can click and drag nodes to rearrange them within a map.
c. Connections: Lines connecting two nodes indicate that some records of those types are related. The connections illustrate how different financial entities interact and allow you to trace how your transactions flow through Leapfin.
d. Recognition summary/journal entry table: This table shows all aggregated journal entries for the transaction scenario. You can click nodes to add or remove those records from the journal entry table for more granular analysis. If you select a node that contains multiple records, all those records will be included.
Examples
Below are some typical examples of financial graphs to help illustrate the variety of visualizations you might encounter:
|
|
|---|---|
Single node, no connections: This graph shows a single node representing one type of financial object without any connections to other nodes. |  |
Two connected nodes: Displays two nodes linked by a connection, indicating that objects of these types are related. |  |
Three nodes, partially and fully connected: The first image shows three nodes, with two connected and one separate. This visual helps identify isolated financial objects or object types. The second image shows three nodes fully connected. |  
|
Four nodes, fully connected: A network of four nodes where every node has a direct or indirect relation. |  |
Five or more nodes: As the number of nodes increases, the graph becomes more complex. The connections provide a comprehensive view of relationships among multiple object types. We recommend manually rearranging nodes or applying filters to focus on specific areas of interest. |  |