Vendor and Customer Accounts Agent
Maintains merchandise vendor and B2B customer account records.
- Industry
- Retail
- Department
- Finance
- Team
- Accounting Operations
- Kind
- Assistant
- Approver
- Finance Controller
- Code
- FIN-02
It maintains the merchandise vendor, non-merchandise supplier and B2B customer accounts, such as corporate gifting and franchise partners, setting up and changing names, tax details, payment terms, rebate agreements and credit limits. It checks each change against the source documents and holds bank detail changes until they are verified.
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 ERP's vendor and customer master: the account, its history, open items and any accounts sharing its tax id or bank account..
- 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 ERP's vendor and customer master: it creates or updates the account, holding bank changes until verified. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The account master rules: required fields for vendors and customers, the payment terms and rebate agreement types, the tax registration checks, the bank detail verification process and the duplicate checks.
Reads from
the ERP's vendor and customer master: the account, its history, open items and any accounts sharing its tax id or bank account.
Acts in
the ERP's vendor and customer master: it creates or updates the account, holding bank changes until verified.
Hands back
An object with account_id, account_type, changes (a list of field, old_value and new_value), checks (a list of check and status passed, failed or pending) and effective (true or false) with reason.
Asks a person when
The change alters bank details, sets a credit limit above 25000, or creates an account that matches an existing one.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Verify bank changes by callback | On | When on, a bank detail change is confirmed by calling a known contact before it takes effect. |
| Default vendor payment terms (days) | 60 | Terms set when the agreement does not say. |
| Largest B2B credit limit it may set (USD) | 25000 | Higher limits need the approver. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Every new account needs the required fields and a valid tax registration; check for duplicates by tax id and bank account.
- When on is true, bank detail changes take effect only after a callback to a known contact, never one given in the change request.
- Set vendor terms from the vendor agreement, or 60 days when it is silent, and record rebate and chargeback terms.
- B2B credit limits above 25000 need the Finance Controller.
- Close accounts only with no open invoices, credits or rebates due.
See the Vendor and Customer Accounts Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.