Accounts Payable
Supplier invoices in, an approval batch out. Checks suppliers, bank details, duplicates and purchase orders, and flags anything that smells wrong. Never pays.
Ten agents for a business, each doing one job you already know: invoices, reminders, filings, quotes, the month's marketing. Set up in about 15 minutes on prepaid credit. Every send and every rand waits for a person.
Your website and a few lines. We suggest the agents that fit.
As many as you need. They work as a team.
Accounting, mailbox, bank, newsletter. Consent screens, never typed keys.
Your agents are built and wired together, then one tap connects them to your Telegram. Microsoft Teams is in pilot.
Supplier invoices in, an approval batch out. Checks suppliers, bank details, duplicates and purchase orders, and flags anything that smells wrong. Never pays.
Overdue invoices staged, reminders drafted in your voice, sent only when you say so, promises to pay remembered.
Your CIPC, SARS, B-BBEE, CSD, UIF and COIDA dates, with each filing pack prepared in time and a chase until it is done.
A project manager in your team chat. Captures every decision with an owner and a date, and sends one message each morning until it is done.
Contracts, NDAs and resolutions assembled from your attorney's approved templates by parameters, marked for attorney review. Assembly, not advice.
Your website kept current from chat: the change staged, the new wording shown, published only when you approve.
Every new supplier and every bank-detail change checked against CIPC, SARS, B-BBEE and your own master before it touches your books. A one-page verdict; you approve.
The month planned, the posts and newsletter drafted in your voice, published only when you say, leads handed on, one honest report every Monday. Buys nothing without the Buyer.
Purchase requests turned into quotes, from your approved suppliers or from suppliers it finds and checks on the open web when you have none, compared on landed cost and lead time, a purchase order on your approval and handed to Accounts Payable.
A producer for a podcaster, a creator or a founder who posts. The calendar kept, guests invited and booked with every message drafted for your yes, each episode turned into show notes, a blog post, a LinkedIn series, shorts and the newsletter in your own voice, published only when you say so, sponsors chased, one Monday message on what grew. Sponsored pieces carry the disclosure the ARB requires; it never DMs a stranger, pays, signs a deal or clones a voice.
Set up with you in managed onboarding, on a host of your own. A requirement travels between them as one signed work order; each keeps a chained ledger of what was decided and by whom. The agent that writes cannot release; the agent that reviews cannot write. How the bench works →
Reads the system on a schedule, read-only: short dumps, failed updates, IDocs, queues, jobs, and the business backlogs behind them (blocked invoices, unbilled deliveries, parked documents). Groups what it finds into issues, diagnoses each from a playbook, and sends the CoE lead and each process owner a morning note. Never changes SAP. Pilot.
Works your ServiceNow queue: reads each ticket with names, ID numbers and emails masked before it sees them, checks the system read-only, finds how similar tickets were fixed, and drafts the work note or resolution. Nothing reaches ServiceNow until the analyst says yes; a code defect goes to intake as a requirement. Pilot.
Answers SAP questions and drafts SAP actions as the person asking, with their own SAP access and inside what their licence allows. Nothing is done until they approve it; in a shared conversation it has no one's personal access. Pilot.
The front door. A request from the chat or a ticket becomes a numbered requirement with its intent and a first definition of done, routed to refinement or to the functional lane. Never builds, never decides scope.
Reads the system as it really is and writes the specification: every object to create, what already exists, what is out of scope, the transport. One targeted question to your consultant when it matters; a named person clears the write surface before anything is built.
Implements the specification in Dev inside the packages you allow, on the transport you named, with unit tests. Activates only on the approver's own words. Holds no transport authority at all.
The technical gate: ATC, unit tests, coverage on the changed lines, the tests read as evidence. Hands back what is not clean; a finding that repeats escalates to your senior developer instead of looping. Cannot change a line.
Tests the change against the original intent, stages the transport and releases it only when a named person says "release" with the number. Closes the record with a design summary built from the ledger. Never imports, never touches Production.
A junior functional consultant beside the pipeline: draft specifications grounded in the system, incidents classed as knowledge, configuration, data or authorisation with the fix prepared for a person to apply, UAT scripts. A draft stays a draft until your consultant owns it.
Personal agents are not sold here. For your household there is Butlerr, our personal AI butler for estate residents: restaurants delivered, errands handled, the quiet work of a household quietly handled.
Each agent runs on the MshenguX platform in its own isolated space, in Telegram, with human approval on anything that leaves or costs money. You pay with prepaid credit that never expires; no API keys, no subscriptions, no month-end surprise. Every new account starts with free credit, and what each agent typically costs a month is on the pricing page. Built on Claude.
Tell us the process that costs you the most people-hours. We will tell you honestly whether an agent belongs there.
Email MshenguX AI →