Loading…
Loading…
Every supplier invoice extracted, checked against the PO and for duplicates and changed bank details, routed to the approver your policy names and posted to the ledger as a draft; purchase requests turned into complete, approved POs; bank and processor lines matched every morning with the breaks explained. Three blueprints, in the ERP and inbox the team already runs.
Repeating work, per week24 h
Three blueprints cover most of it. The rest stays yours.
Three rungs
One-time prices, no subscription. Every rung is credited in full against the next one for 30 days, so starting small costs nothing extra. Card checkout on Stripe; the confirmation and the next step arrive within a minute.
$49one-time
You have imported a workflow before, or want to try before anyone touches your accounts.
$249one-time
You want the first blueprint running in your accounts this week, without learning a tool.
$490one-time
You want the whole job automated — all three blueprints, in your voice, with someone to call.
Every rung is credited in full against the next one for 30 days: kit → install → package. Model usage and any paid n8n, Make or Zapier plan are billed by the providers to your own accounts, usually a few dollars a month. Need more than the package? When a AP team needs a custom build. Package terms: fixes, credits, refunds, your data.
What gets installed
Each is a documented blueprint from the library — trigger, steps, guardrails, free template — adapted here to how accounts payable teams work. The kit and the install cover the first; the package covers all three.
Every supplier invoice extracted from the AP inbox, checked for duplicates, changed bank details and a matching PO, coded from your rules, routed to the approver the policy names for the amount, and posted to the ledger as a draft after one tap.
A request from a form or Slack becomes a complete, policy-checked PO: budget line confirmed, approvals routed by amount and category, the PO created in the ERP and sent to the supplier, receipt tracked against it.
Bank, processor and ledger lines matched every morning; each break explained in a sentence and a proposed journal entry queued for an accountant's approval — never posted on its own.
What it actually does
Not a feature list — the messages and actions as they happen once the first blueprint is installed. Every outgoing message starts as a draft you approved once; after that it runs on the rules you set.
Worked example · illustrative
Not a client report
About 420 supplier invoices a month, keyed by two people; approvals chased by email on Fridays; a month-end close that landed on day eight. One duplicate payment found last quarter at reconciliation.
The first month| Metric | Before | After a month |
|---|---|---|
| Hours a week keying invoices | 10 | 2 |
| Invoice received → approved | 4 days | same day |
| Duplicate payments | 1 a quarter | 0 (2 caught) |
| Month-end close | day 8 | day 5 |
This is a worked example, not a client's results: the figures are what the blueprint's own metrics and the role's published benchmarks make typical for an install of this size. Real numbers will replace it, with permission, once the first installs have run a month.
Which rung
Your tools, your volume, how much you want to touch. The answer is a rung and a price — no call at any rung. If you would rather write three sentences, the form is below.
Not on the list? Most tools with an API work; say which on the form.
Answer all three and the rung appears here — with what happens next and the price.
What happens after you pay
Card checkout on Stripe, then the confirmation lands within a minute. This is what it says — the same for every role, with the tools and blueprints swapped for yours.
Before you order
From your approval matrix — a small table of amount bands, categories and approvers that we fill in during the install. The automation routes; it never approves. Anything the matrix does not cover goes to the AP lead.
Supplier, quantity and price within the tolerances you set (typically 2% on price, 5% on quantity). Outside tolerance, or no PO where the policy requires one, the invoice waits in the exceptions queue with the difference spelled out.
No. Bills post as drafts after approval; payment runs stay in the ledger and stay yours. Reconciliation proposes journal entries; an accountant posts them.
If it has an API — most do — the install covers it; the field map is the same. Dynamics, Sage Intacct and Business Central are common. A system with no API is a custom build with a different capture step.
Every automated action is logged in the ledger where it happened, tagged as automated, with the source PDF attached and the approver named. Auditors filter on the tag; the approval matrix is the control they ask for.
When a package isn’t enough
A custom build starts at $2,000: your own rules, delivered into your accounts to keep, with documentation and 30 days of fixes. The package is credited against it for 30 days.
How custom builds workSeveral entities or currencies with intercompany reconciliation and consolidated approvals.
Three-way matching against goods receipts in a WMS, or supplier onboarding with bank-account verification workflows.
A supplier portal where suppliers submit and track invoices themselves.
Order, or ask
One reply within 24 hours: the rung that fits, the payment link, and the next step. Everything happens by email and in your accounts — there is no call at any rung.
Prefer email? ask@agentmelt.com
Other packages
Speed-to-lead · Long-term nurture · Listing descriptions and posts
From $49 →RecruitersResume screening · Candidate outreach · Interview scheduling and reminders
From $49 →Executive assistantsInbox triage · Meeting briefs · Weekly report
From $49 →Legal professionalsContract review · Document drafting · Client intake and inbox
From $49 →AccountantsInvoice processing · Daily reconciliation · Client reporting
From $49 →Support teamsTicket deflection · Proactive outreach · Feedback analysis
From $49 →HR teamsNew-hire onboarding · Offboarding · Interview scheduling
From $49 →