quaestor-agent

Inspiration

As accountant, I need to manage company’s accounting, but knowing all the accounts and journal entries to be recorded can be challenging and annoying.

The ERP generates journal entries automatically from transactions - e.g. invoices, payments etc. - but when I need to record transactions manually I have to consult the user guide of the ERP and ask to the senior accountant.

I need a tool to easily record journal entries when no automation is available from ERP.

What it does

From accounting instructions the agent records a journal entry in the ERP. The agent looks up accounts from the ERP and records the transaction in the ERP.

How we built it

It's been defined a Multi-Agent applying the strategy Orchestrator control.

By transaction type it is implemented a Sub-agent provided with tools to get ledger accounts from ERP and to record journal entries in the ERP

👉🏻 sub-agents just have the necessary tools for the specific transaction.

Agents and Tools have been implemented with Strands Agents SDK for python

Challenges we ran into

Defining a single Agent to manage all transaction types requires a lot of context because it is provided with all the tools to get accounts from the ERP and to record transactions in the ERP.

To solve the above problem with defined sub-agents by transaction type which are provided with just the necessary tools to get the accounts of the journal entry.

Accomplishments that we're proud of

What we learned

An agent can be more than a tool that translates natural-language to actions. In our case we will use the agents as a repository of knowledge to avoid silos of knowledge in the company.

What's next for quaestor-agent

• Register sub-agents dynamically from accountant specification.
• Integrate the agent with commercial ERP's like SAP or Oracle Fusion.

Built With

• python
• strands-agents