Soma · Automation of paid accounting processes · Pilot in progress
When you open RCM and ledger,
Continue through to the workpaper
Soma creates RCM drafts, account reconciliations, and evidence-linked workpapers inside workflows explicitly started by the user. People review the evidence, exceptions, and unresolved items before approving the final judgment.
- ✓ Human confirmation gate
- ✓ Continue after interruption
- ✓ Evidence-record connection
- ✓ Initiated explicitly by the user
- 1RCM draftingIn progress
- 2Reconciliation draftingIn progress
- 3Workpaper draftingIn progress
The actual scope of application and output format are checked in pilot according to business procedures.
Pilot programs
Check out our pilots for the results you want to create
RCM, reconciliation schedule, and report differ in the input data required and the points at which people can make judgments. On each page, the production flow and output scope are explained separately.
RCM drafting
Draft a risk, control, and evidence structure from the job description and existing materials.
Pilot Details →Reconciliation drafting
Connect ledgers, subsidiary books, and statements to organize differences and adjustment items.
Pilot Details →Workpaper drafting
Bundle procedures, samples, evidence, and review memos into a workpaper draft with supporting evidence.
Pilot Details →Workflow
Draft first, then stop where judgment is necessary.
- 01
data connection
Link RCM, ledgers, statements, samples and vouchers to work units.
- 02
Check creation criteria
A person checks the standards for creating company forms, RCM, reconciliation schedules, and records.
- 03
basis connection
Associate source locations and review notes for each amount and phrase.
- 04
Create a draft
Create RCM, reconciliation schedule and workpaper draft based on linked data.
- 05
person is confirmed
Conclusions that require judgment are confirmed and confirmed by the person in charge.
Model & deployment
Review the deployment method appropriate for your operating environment
Soma only uses vLLMs controlled by Propsol or vLLMs in customer environments. It does not fall back to public frontier models such as Anthropic, OpenAI, and Google. For corporate customers, we first suggest deploying to the customer's server or in-house network.
Specific processing locations, network configurations, operational retention periods and update methods are confirmed for each environment before piloting. Using the service and providing data for model improvement are optional, and the default value for learning participation is OFF.
Product boundary
Axon and Soma have different roles
Recalculating numbers and creating carryovers, reconciliation schedules, and rules-based statements is done locally by Axon. Creation that requires risk, control, and procedure descriptions and linking of multiple materials is treated as a Soma task explicitly initiated by the user.
Learn more about our processing locations and scope of connection- Axon
- Local rule-based calculation, verification, and writing, same result for same input
- Soma
- Explicitly initiated procedures, data linking, draft creation and human confirmation
- data
- Separate processing location, operation, preservation, and learning participation to guide and select
Pilot
Start with deliverables you create over and over again
We are discussing the scope of the pilot with accounting and internal accounting teams who repeatedly connect RCM, samples, evidence, and records.
Soma Pilot Consultation