Subledger Configuration
Use the Subledger Configuration skill to set up and change the accounting rules in Fynapse: how Business Events are identified, which accounts they post to, and how their Journals are built.
The skill reads your current configuration, drafts the change, checks that it balances, validates it with Fynapse, and only then writes it, after you confirm. Where your approval workflow is on, changes go through it.
Example prompts
Once installed, describe the accounting you want in business terms.
Add a posting rul
Add a posting for SubscriptionInvoiced events: debit Trade Debtors with the gross amount, credit Deferred Revenue with the net amount and VAT Payable with the tax.
Set up a new event type
Create a ServicesInvoiced event type for AdamWare that posts straight to Services Revenue.
Check the configuration
Check that our posting components balance for both invoices and credit notes.
Change how Journals are split
Split our Journals by cost centre.
Create test data
Give me a CSV of test events for the new invoice rules and tell me which Journals to expect.
You can name the event types, accounts, amounts and business dimensions you want to work with.
Install
Install the Subledger Configuration skill from the Fynapse skill collection:
The Fynapse MCP Server must also be connected to your AI client. The skill uses the MCP Server to read your current configuration and to write the changes you approve.
What you’ll get
The skill works through the change with you in your conversation and gives you:
- A summary of the existing configuration the change touches
- The proposed change, explained in accounting terms
- A balance check for both positive and negative amounts
- The result of Fynapse’s validation, including what validation does not check
- Confirmation of what was written, or the approval request it is waiting on
- Test events as a CSV file, with the Journals you should expect from them
The skill reuses your existing account lookups and follows the conventions already in your configuration rather than inventing new ones.
Configuration changes affect how future Business Events post. The skill checks balance and validates with Fynapse, but review each proposed change, and each approval request, before it is applied.
Approval workflow
The skill works with your approval workflow and recommends one where it is not in place.
- While the approval workflow is on, changes to Business Event types, account lookups, posting components and identification rules are submitted for approval and take effect only once approved. Related changes are grouped into one change set, so your approver reviews them as a single request.
- If no approval chain is set up for accounting rules, changes are approved automatically. The skill tells you, and can draft an approval chain for your approver groups. Approval workflows are turned on in the Fynapse UI.
- The Business Event Definition, the Journal Line Definition and Journal grouping are not covered by approval and apply immediately. The skill confirms these with you before writing them.
- The skill never suggests turning approval off to get a change through.
Balanced postings
Every posting component must balance: the debits it produces must equal the credits. The skill checks this across the whole component for both a positive and a negative amount, so credit notes and reversals post correctly. By default it uses the AUTO amount sign, which posts a negative amount as the reverse of a positive one.
Things to know
Some configuration cannot be undone through the Fynapse MCP Server. The Business Event Definition, the Journal Line Definition, the Journal mapping and entities can be updated but not deleted. Both definitions take an effective-from date when they are created, which cannot be changed later, and events dated before it may be refused. Enabling foreign exchange settings cannot be reversed. The skill tells you before the first write of any of these.
Fynapse validation checks the structure of a configuration, not its arithmetic. The skill checks balance itself and tells you what validation did not cover.
A Business Event creates at least one Journal, and Business Events are never merged into one Journal. Journal grouping can split an event’s lines into more Journals, but the skill will not group by account, because that separates the debits from the credits and leaves every Journal unbalanced.
The skill recommends a dedicated, unique Event ID on your Business Event Definition, because the ID is how Fynapse removes duplicate events. Accounts are never Business Event attributes: the accounting rules assign them.
When unposted Journals are enabled, Journals dated after the current business date are held as unposted until the business date reaches them. The skill checks the business date before you load test data and tells you if any Journals will be held.