Data
Use Cash & Treasury → Cash → Data to inspect and, when authorized, maintain the underlying cash records. For tracing the whole chain together, use Transaction Explorer; for exceptions, use Cash Recon.
Scope the four tables
Read the four tables as connected layers. Imported feed rows preserve source evidence. Transactions record system movements. Splits divide those movements into portions for attribution or treatment. Cash Split Links connect portions to the activities, income, expenses or transfers they explain. A record at one layer does not automatically establish all the others.
The layers have distinct relationships. Feed-to-transaction support is carried by Account Transaction Links; business settlement is carried by Cash Split Links. Matching IDs or totals cannot substitute for either relationship, so correct the record or link that actually owns the disputed fact.
Choose an Account and optional Date Range. The range uses each feed/transaction's Txn Date, not Value Date. Cash Splits and Cash Split Links inherit their parent transaction's account and date.
A blank account/range broadens the population. Entity and As of Date used on other Cash tabs do not filter these four queries. Each table also has its own search, Filter, Sort and Hide fields controls; those do not automatically filter the other tables.
Fictional Operating USD Account #1, July 1–August 31: three feed rows and three transactions show +100,000 on July 5, −40,000 on July 15 and −1,200 on August 31. These are two layers of the same movements, not six separate cash flows.
Account Activity Feed preserves imported bank activity and context such as bank references, counterparties and balance-after values. Account Transactions records system cash movements, with category, stored status, dates and signed total.
The feed-to-transaction links are separate from the Cash Split Links shown below. To see which feed items support a transaction, open Transaction Explorer. Matching IDs or amounts alone do not establish a relationship.
Follow allocation and settlement links
A split’s owner and its business target are separate facts. Ownership attributes cash to an Entity or Share Class. The target identifies what the cash settles. The link allocation states how much of the split belongs to that relationship, which is essential when a movement or source is shared across several links. A valid owner does not establish the correct target, and a valid target does not fill a missing owner.
Collapse the first two section headers to bring the lower tables into view. This changes the layout only.
Cash Splits and Cash Split Links, with the first two sections collapsed. All three splits belong to Class A. Link #1 connects Split #1 to Subscription Activity #3; Link #2 connects Split #2 to Investment Activity #2; Link #3 connects Split #3 to Expense #1.
Cash Splits divides a transaction into operational portions. Account Transaction Id identifies the parent. Purpose describes the use of the cash; Owner Type + Owner Id identify its attribution. Owning cash and linking it to a settled activity are separate relationships.
Cash Split Links connects a split to a target through Related Type + Related Id. An ID must always be interpreted with its table/type: Subscription Activity #3 is not Expense #3. Allocated Amount records the amount on that particular relationship; Role can distinguish uses such as transfer principal legs.
In this example, the bank receipt is +USD100,000 while its link to Subscription Activity #3 records −USD100,000 under that activity's sign convention. Do not assume every layer uses the bank-cash sign. Inspect the target and the relevant reconciliation rule before changing a sign.
Blank Allocated Amount remains blank in this table; this page does not calculate a substitute. Some categorization/status fields are blank in the example. The screenshot demonstrates stored records and links, not completed classification or approval.
Maintain the owning record carefully
The four tables expose real underlying records. Insert and editing controls depend on permissions, locks and write settings. A permitted save changes operational data; it is not a report-only adjustment. This guide demonstrates inspection, not a completed edit or ingestion workflow.
Prefer the organization's normal ingestion/matching workflow. Do not manually recreate all four layers, duplicate an imported receipt, or change a valid amount merely to make a control pass. Investigate genuine errors at the relevant account, transaction, split or relationship and preserve provenance.
All stored transaction statuses are visible here, including reversed records when they meet the filters. Match Status and Status are stored fields, not fresh reconciliation results. Marking a transaction Posted does not establish a posted journal.
A split or link whose parent transaction is missing may not appear here. Use the integrity checks to investigate missing references; an empty table does not establish that every required record exists.
Refresh after an authorized correction and verify it in Transaction Explorer and the relevant Cash Recon check. Row selection can provide context to an available assistant workflow; selection itself does not execute a change.
In the July 5 example, Transaction #1 leads to Split #1 and then Subscription Activity #3. These records describe the same receipt at different stages, so their amounts should not be added together.