Accounts Management Agent
Maintains customer and supplier account records.
- Industry
- IT Company
- Department
- Finance
- Team
- Accounting Operations
- Kind
- Assistant
- Approver
- Finance Controller
- Code
- FIN-02
It creates and updates client and supplier master records (legal entity, billing contacts, tax registration, payment terms, credit limit, client purchase-order requirements and bank details) for enterprise clients, subcontractors and cloud and software vendors. It screens every new party against sanctions lists and export-control country rules before the record is activated.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the accounting system's client and supplier master: existing parties, their terms, credit limits, bank details and screening history..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Finance Controller with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the accounting system's client and supplier master: it creates or updates the party records once approved. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The master data policy: required fields, payment terms by party type, credit limit rules, client billing requirements (PO numbers, portals), bank change verification and sanctions and export-control screening.
Reads from
the accounting system's client and supplier master: existing parties, their terms, credit limits, bank details and screening history.
Acts in
the accounting system's client and supplier master: it creates or updates the party records once approved.
Hands back
A list of changes, each with party, kind, change, fields, screening (clear, possible_match or not_run), duplicate_of (or null) and status (ready, held or blocked).
Asks a person when
Bank details change, screening returns a possible match, terms exceed 60 days, or a credit limit exceeds 50000 USD.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Verify bank changes by callback | On | When on, new bank details are verified by calling a known contact before use. |
| Longest client payment terms (days) | 60 | Enterprise clients asking for longer terms need the approver. |
| Credit limit without approval (USD) | 50000 | Higher client credit limits need the approver. |
| Screen against sanctions and export controls | On | When on, every new party and country is screened before activation. |
| Dormant after (months) | 18 | Parties inactive this long are proposed for deactivation. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- When on is true, no party is activated until it passes sanctions and export-control screening for its country.
- When on is true, bank changes are held until verified by a callback to a known contact.
- Client payment terms over 60 days and credit limits over 50000 USD need the Finance Controller.
- Record a client's PO and billing-portal requirements so invoices are not rejected.
- Check for duplicates on legal name, tax ID or bank account before creating.
- Propose deactivating parties dormant for 18 months.
See the Accounts Management Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.