Automating Accruals & Journal Entries with the Numeric MCP

Last updated: May 9, 2026

This is Part 4 of the Numeric MCP series. This is where it all comes together — full close workflows running end to end in a single conversation.

Pick your path:
Need to install the toolkit first? Go back to Part 3: Skills & the Toolkit →
Haven't connected the MCP yet? Start at Part 2: Getting Started →
Brand new to the MCP? Begin at Part 1: What Is the Numeric MCP? ←

What Makes These Workflows Different

The skills in Part 3 are mostly about pulling data and generating outputs — dashboards, reports, workbooks. The two workflows in this article go further: they read data from multiple systems, apply accounting logic, generate supporting documentation, post entries to your ERP, and submit the completed task in Numeric. All in one conversation, all in a few minutes.

These are the workflows that show what "close automation" actually means in practice.

Accruals Automation

The accrual skill processes accruals end to end: identify vendors that need an accrual, calculate estimates based on your methodology, build the supporting work paper, post the journal entry, and document everything in Numeric for the reviewer.

How it works

1. Find the task and set context. You specify the entity and period. Claude locates the accruals task in your Numeric checklist, identifies the relevant GL accounts, and pulls in any prior-period preferences.

2. Carry forward institutional knowledge. Each run saves your decisions — method overrides, exclusions, threshold adjustments — to the task description in Numeric. The next period's run picks those up automatically. You can also edit the saved preferences between periods and the skill will respect those changes.

3. Surface manual accruals. Before analyzing transactions, Claude asks whether there are vendors to accrue for that won't show up in the data — unbilled purchases or invoices known to be incoming. These get carried into the candidate list alongside data-driven candidates.

4. Analyze transactions and flag candidates. Claude pulls transaction history from Numeric across a six-month window, identifies vendors that may need an accrual, and presents a numbered list with the proposed amount, estimation method, and reasoning for each.

5. You decide what to process. Claude presents the candidates and you select which ones to proceed with. You can adjust amounts, swap methods, or exclude vendors. You stay in control of the accounting judgment.

6. Generate outputs. Claude produces three artifacts: a workbook with historical detail, accrual calculations, and a Numeric-formatted tab; a NetSuite-ready JE CSV; and a validation file confirming debits equal credits. The CSV is always generated regardless of whether you have a live ERP connection.

7. Post and submit. If an ERP connector (ex: to NetSuite) is available, Claude posts the journal entry directly. It then submits the task in Numeric, adds structured commentary documenting every accrual, and saves your preferences for next period.

What you get at the end

  • A completed Numeric task with full commentary

  • A supporting workbook with expense history and accrual details

  • A NetSuite-ready journal entry CSV (posted directly if an ERP connector is available)

  • A validation file confirming the entry balances

  • Preferences saved to the task description, carried forward automatically next month

🎥 Watch it in action: End to End Accruals Processing using the Numeric MCP

Journal Entry Creation

The journal entry skill follows a similar structure but starts from a supporting document rather than a transaction scan. Hand it an invoice, a platform export, a GL dump, or an allocation workbook, and it will parse the document, draft a balanced journal entry, generate the work paper, and submit the task.

How it works

1. Find the task. You invoke the skill and Claude surfaces open JE tasks from your Numeric checklist with assignees, statuses, and due dates. Pick the one you're working on — after it completes, Claude loops back to the list so you can process the next one.

2. Upload the supporting document. The skill handles four input types: a vendor invoice or interest statement, a platform export like a cloud usage CSV, a GL dump for reclass or FX entries, or an allocation workbook like a commission split. Claude parses the file structure, detects the JE type, and classifies line items automatically. It also pulls any prior-run instructions saved to the task description — subsidiary, account preferences, External ID patterns — so repeat tasks require less input each month.

3. Clarify and validate. Claude asks targeted questions: how should line items be grouped, which departments apply, whether any classifications need adjustment. It flags potential issues — amount discrepancies, missing fields, anything that could cause the entry to be unbalanced. If lines cross subsidiaries, it automatically structures a four-line intercompany entry with clearing accounts.

4. Generate the journal entry and work paper. Claude produces a balanced journal entry with built-in validation checks and a three-layer Excel workpaper: source data, calculation formulas, and JE lines with every amount traceable back to the source. It also generates a NetSuite-ready import CSV, always available regardless of whether you have a live ERP connection.

5. Post and submit. If an ERP connector is available, Claude posts the entry directly. It then submits the task in Numeric with commentary describing what was processed, and saves instructions to the task description so the next period's run starts with your preferences already loaded.

What you get at the end

  • A balanced journal entry, validated and ready to post

  • A three-layer work paper with source documentation, calculations, and JE lines

  • A NetSuite-ready import CSV (posted directly if an ERP connector is available)

  • A submitted Numeric task with detailed commentary

  • Processing notes saved in the task description, carried forward automatically next month

🎥 Watch it in action: Creating Journal Entries via the Numeric MCP

The Pattern Behind Both Workflows

Notice the common thread across accruals and journal entries:

  1. Claude finds the task in Numeric and inherits any existing instructions.

  2. Claude pulls data from your ERP and/or uploaded documents.

  3. You make the judgment calls — which accruals to book, how to categorize line items.

  4. Claude handles the output — work papers, journal entries, ERP posting.

  5. Claude closes the loop — submitting the task, adding commentary, saving notes for next period.

This pattern extends to other close tasks too. Any workflow where you're pulling data from one system, applying logic, generating documentation, and recording the result in Numeric is a candidate for this kind of automation. Once you've seen it work for accruals and JEs, start thinking about what else on your checklist follows the same shape.

Getting Support

Wherever you are in your MCP journey, the Numeric Solutions team is here to help:

Discovery — demo sessions, use-case workshops, and a growing community and examples library to learn from.

Design — co-build skills and templates tailored to your specific workflows. Get review and feedback on workflows you've created.

Implementation — walkthroughs of MCP fundamentals and hands-on technical support for setting up your environment.

Reach out to your Solutions Manager or email support@numeric.io.

Additional Resources

Start from the beginning: Part 1: What Is the Numeric MCP? ←