Behind the scenes
What’s actually happening when you send Meredith a job.
The split
Most things don’t need an AI. They need code.
Routine steps may use deterministic rules, while document interpretation and message drafting may use automated tools. Exceptions and matters needing judgement can be escalated for review. The exact workflow depends on the service and controls agreed for the client.
That split is the whole reason it works. AI is great at the messy bits. Code is better at the consequential bits. We use each where it belongs.
The lifecycle of one invoice
From “send it to Meredith” to money in your account.
You provide the invoice details.
Supported intake channels and document formats are confirmed during onboarding. Submitted information is treated as draft data until the checks required by your workflow are complete.
Details are validated.
Automated and manual checks may be used to identify missing, inconsistent, or unusual information. A client remains responsible for the accuracy of the information and instructions it supplies.
An invoice is prepared under your authority.
Where your written agreement authorises it, Meredith prepares or issues the invoice on your behalf. Supplier identity, tax information, and payment instructions follow the approved client setup.
Follow-up follows the agreed workflow.
Reminder timing, tone, escalation, and pause rules are subject to your written agreement and any supplier or customer dispute.
Receipts are reconciled.
Available payment information is matched to invoices. Ambiguous or incomplete records are held for review rather than treated as confirmed automatically.
Records are made available.
Available invoice, payment, and remittance records are provided in the format and cadence included in the client agreement. Tax and accounting decisions remain with the client and its advisers.
Safety architecture
The AI cannot talk its way past the rules.
The boundaries that matter — moving money, changing a bank account, releasing a payment — are enforced in code, not in a prompt. The agent operates inside a fixed set of tools, each with preconditions checked before the tool runs. No clever wording from a customer, supplier, or attacker can get the agent to do something the code won’t let it do.
The public service boundaries, verification dependencies and data handling summary are on Security & trust.
Account verification
Account and instruction changes are subject to the verification steps applicable to the client, territory, and banking arrangement.
Settled-funds checks
A remittance instruction is not released until the corresponding receipt is confirmed as cleared under the applicable banking arrangement.
Compliance checks
Onboarding and ongoing service may require identity, sanctions, fraud, source-of-funds, or other checks under applicable law, contracts, or third-party rules.
Instruction controls
Confirmation rules can be agreed for material or unusual instructions. Meredith may pause an instruction while it seeks clarification or completes required checks.
Exception review
Unusual activity, disputed invoices, unmatched receipts, and changed payment instructions may be routed for additional review.
Human escalation
Automated tools support routine administration. Matters needing judgement or clarification can be escalated under the applicable support process.
Why the price is what it is
A flat 5% on collected only works because the architecture is this.
Automation can reduce repetitive administration while retaining review paths for exceptions. The service scope, pricing, and operational boundaries are set out in the written agreement offered to an eligible client.
Public examples are illustrative and do not override a client’s written terms. The current public pricing explanation is on Pricing.
Common questions
The bits people actually ask about.
What happens if a customer disputes an invoice?
Follow-up is paused when a dispute is identified and the matter is routed according to the support and escalation process in the applicable client agreement.
What triggers a human to step in?
Examples include disputes, unmatched receipts, changed payment instructions, compliance alerts, unusual activity, and a request that needs judgement or clarification.
What if Meredith reads a job ticket wrong?
Contact Meredith promptly. An invoice can be held, corrected, voided, or reissued as appropriate, subject to its status and the client’s instructions.
Can I talk to a person?
Yes. Contact routes and operating hours are provided during onboarding. Response times depend on demand and issue severity unless a written agreement states a specific service level.
What if someone tries to change my payout bank account?
Payment-instruction changes are subject to the verification and review steps applicable to the client and banking arrangement. Meredith may pause the change while checks are completed.
What happens if Meredith is down?
Availability incidents are handled under Meredith’s operational procedures. Payment timing and queued actions remain subject to the relevant banking and platform arrangements. Contact Meredith if a specific invoice is affected.
“Send it to Meredith.”
Apply online. Eligibility, onboarding, service activation, and invoice authority are confirmed before Meredith acts for a client.