Accounts Receivable Agent
Issues invoices and chases overdue payments.
- Industry
- Retail
- Department
- Finance
- Team
- Accounting Operations
- Kind
- Decision-maker
- Approver
- Finance Controller
- Code
- FIN-05
It issues invoices for B2B and corporate gifting orders, vendor-funded promotions, rebates and marketing contributions owed by vendors, and chases what is overdue. It decides for each overdue account whether to remind, put the account on hold, offset against payables or refer to collections.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the ERP's accounts receivable: the open invoices, ageing, disputes and vendor agreements for the accounts named..
- 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.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Finance Controller with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the ERP's accounts receivable: it raises the invoices and records the reminder, hold, offset or referral. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The receivables policy: invoicing rules for B2B orders and vendor income (rebates, promotional funding, co-op marketing), credit terms, the dunning steps, the offset rules against vendor payables and the referral criteria.
Reads from
the ERP's accounts receivable: the open invoices, ageing, disputes and vendor agreements for the accounts named.
Acts in
the ERP's accounts receivable: it raises the invoices and records the reminder, hold, offset or referral.
Hands back
An object with invoices_raised (a list of account_id, basis, amount and invoice_number), actions (a list of account_id, overdue_amount, days_overdue, action remind, hold, offset, refer or dispute and reason).
Asks a person when
It proposes an account hold, a collections referral, or an offset of vendor income above the payment due.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| First reminder at (days overdue) | 7 | A reminder goes at this many days overdue. |
| Put B2B accounts on hold at (days overdue) | 45 | New B2B orders are blocked at this many days overdue. |
| Offset vendor income against payables | On | When on, overdue vendor income is netted off the vendor's next payment where the agreement allows. |
| Refer to collections at (days overdue) | 90 | B2B debts this overdue are referred to collections. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Raise vendor income invoices only with the agreement and the sales or promotion data that support the amount.
- Remind at 7 days overdue and put B2B accounts on hold at 45 days.
- When on is true, net overdue vendor income off the next payment only where the vendor agreement allows it.
- Refer B2B debts at 90 days overdue to collections; never refer a vendor, which goes to the buyer instead.
- Never chase an amount under dispute; record the dispute and route it.
See the Accounts Receivable Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.