implement-account-operations

Automate account operations across Firefly Banking Platform microservices.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/firefly-oss/firefly-oss-claude-skills --skill implement-account-operations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-account-operations
Source: https://github.com/firefly-oss/firefly-oss-claude-skills/tree/main/skills/implement-account-operations
Command: npx skills add https://github.com/firefly-oss/firefly-oss-claude-skills --skill implement-account-operations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating end-to-end account operations across multiple microservices to ensure data consistency, auditability, and reliable accounting within Firefly's banking platform.

Core Features & Use Cases

  • Cross-service account lifecycle: opening, updating, and closing accounts across core-banking-accounts, core-banking-ledger, and core-common-accounting-gl.
  • Double-entry accounting: ensuring debits equal credits with dedicated TransactionLegs and Journal postings.
  • Standing orders & multi-currency: supporting recurring payments and multi-currency flows with GL integration.

Use Case: Implement a customer onboarding flow that creates an account, initializes balances, and posts the opening GL entry across services.

Quick Start

Walk me through a minimal end-to-end example that opens a new account, initializes balances, and posts the opening GL entry across services.

Frequently Asked Questions about implement-account-operations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate cross-service account opening and GL postings in a microservices banking platform?

Cross-service account opening and GL postings are automated by coordinating workflows across core-banking-accounts, core-banking-ledger, and core-common-accounting-gl. This ensures consistent data propagation, validation, and auditing while posting the opening GL entry across services.

How does double-entry accounting work for multi-currency transactions and standing orders?

Double-entry accounting for multi-currency transactions and standing orders works by modeling TransactionDTOs and TransactionLegDTOs with matching debits and credits. This enforces balanced transactions and maintains accurate histories across banking services.

What's the best way to ensure balanced transactions across core-banking-ledger and core-common-accounting-gl?

The best way to ensure balanced transactions across core-banking-ledger and core-common-accounting-gl is by enforcing balanced TransactionDTOs and TransactionLegDTOs with equal debits and credits. This approach publishes domain events to maintain accurate balances across all services.

Can I use this approach for customer onboarding flows that initialize account balances across microservices?

Yes, you can use this approach for customer onboarding flows that initialize account balances across microservices. It opens a new account, initializes balances, and posts the opening GL entry across services with consistent validation and auditing.

Do I need separate services for account lifecycle management and ledger postings in a banking platform?

You need separate services for account lifecycle management and ledger postings to ensure data consistency and auditability. This approach coordinates operations across core-banking-accounts and core-banking-ledger to maintain reliable accounting within the banking platform.