> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.tabs.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.tabs.com/_mcp/server. # View Contract Journal Entries ## What it is The **Journal Entries** tab on the Contract Details page shows every journal entry a contract has generated across all prior periods it spans, in a single chronological list. Previously, confirming a contract’s accounting treatment meant checking the invoice, credit memo, and then each month’s journal entry period by period. The Journal Entries tab puts the entire lifecycle in one place—right where you already manage the contract. It is a **read-only review tool**. It shows you what your entries are so you can confirm they are complete and accurate. It does not push them to your connected ERP. ## Where to find it Open a contract → **Contract Details** → **Journal Entries** tab. ![Journal Entries tab on the Contract Details page](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/tabs.docs.buildwithfern.com/b67220136612ca681be30c14d53c27ec2b8cdb20604a3041ad6d33ca983c26c8/docs/assets/getting-started/revenue/contract-journal-entries.gif?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260921%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260921T233818Z&X-Amz-Expires=604800&X-Amz-Signature=8f6cc31c5e864819f80f2a7d751b7501f3bdbca3645c058eeafc50e0d5f52d34&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject) ## What appears in the table Every journal entry tied to the contract, including: * Economic events as they occur * Invoice sent, voided, one-off items, or marked as done * Credit memo sent or voided * Invoice and credit memo offsets * Scheduled revenue recognition events on last day of each period * Revenue recognition entries **However, it does not include:** * Invoice payment entries * Credit memo application as the entry was already created when issued. ## How to read the table ### Default order Entries are grouped rather than sorted flat. Each event keeps its original entry, its offsets, and its reversals together, and revenue recognition entries appear last, because recognition is always the final event in the period. Applying an explicit column sort replaces this grouping with a flat sort. Clear the sort to return to the grouped view. ### Status * **Info Only** Shows the journal entries expected in your ERP when Tabs syncs an invoice or credit memo. * **Draft** Generated by Tabs for this period, not pushed to the ERP yet. * **Posted** Generated by Tabs and already pushed to the ERP. ### Default columns * **Status** Info Only, Posted, or Draft * **Date** The journal date of the entry * **Type** The source event: invoice or credit memo sent, void, offset, or revenue * **Product** The Tabs product the entry relates to * **Integration item** — the ERP item used to map the GL account * **Account** The GL account * **Description** Hyperlinked to the source invoice or credit memo * **Reversal** — flags whether the entry is a reversing entry * **Amount** Split into debit and credit ### Optional columns Add these from **Columns button:** * **Integration class** — the ERP class used when applicable * POB ID — Tabs performance obligation ID ## Finding a specific entry * **Search** — matches any content currently loaded on the page * **Filter** — filter by journal entry source type, status, or currency * **Sort** — sort by any column header * **Export** — download the contract-scoped list as a CSV * **Update entries** — refresh journal entries if anything has changed since the last updated timestamp * **Pagination** — choose how many items to display per page to navigate through results ## Updating entries Only use it if something has changed since the last updated timestamp. The **Update entries** button regenerates journal entries for **every month the contract spans**, not just the current month. This ensures balance sheet accounts (deferred and unbilled) reflect any upstream changes by rolling balances forward into all subsequent periods. Expect this to take longer than a single-month refresh. ## If you see a warning banner A banner reading **Accounts set up incomplete** means one or more GL account mappings are missing. You will notice missing GL Accounts in some JE lines in this case. You can sort by Account column to quickly identify any JE with missing accounts. Follow the link in the banner to complete the mapping. Incomplete or incorrect mapping is the most common cause of entries that look wrong — for example, an entry posting to revenue instead of deferred revenue because an integration item “Deferred Account” is mapped to the revenue GL account. ## Frequently asked questions **What is the difference between this and the journal entries table in close management?** The underlying journal entry info comes from the same source, but this table is filtered to a single contract across periods, whereas the table in close management is filtered to a single period across all contracts. **Can I push entries to my ERP from this tab?** No. Pushing remains the final step of close management. This tab is where you check entries before you push them. **Can I correct an entry here?** No. If an entry is wrong, the correction happens upstream — in your GL account mapping or in the contract itself. This tab shows you where to look. **Will Tabs tell me what the entry should have been?** No. Tabs shows what was generated and the source events. It does not infer a corrected entry when there is an upstream mapping issue. **Will I see entries for periods that haven't happened yet?** No. The list shows entries for events that have occurred. Projected future entries are not part of this release.