Melio can bring vendor onboarding, bills, approvals, payment scheduling, and accounting updates into one operating flow. That convenience also concentrates risk. A duplicate vendor can divide payment history, an unverified delivery-method change can redirect funds, and a workflow that omits the Owner or Admin scheduler can leave high-authority payments outside approval. A useful rollout therefore starts with the business process and evidence standard, not with a tour of buttons.
For a CPA firm, responsibility may be shared across the firm and each client. Staff may prepare vendors and bills while a client retains approval and funding authority. Another organization may let department contributors submit bills but reserve vendor changes and payment scheduling for finance. Document who owns each step, who provides backup coverage, and which system is authoritative for vendor and bill fields before connecting accounting software or inviting users.
Melio features vary by subscription and integration. The current Roles & Permissions page says Go permits only the business owner, while Core and above support team roles. Current approval guidance also explains that workflows are premium, do not apply to already scheduled payments, and need explicit scheduler criteria to cover Owner or Admin activity in certain designs. Validate the live plan, tenant, and connected accounting product, then retain dated screenshots or exports as the implementation baseline.
Key decisions at a glance
- Clean and match vendor records before imports, accounting sync, or live payment scheduling can multiply duplicates.
- Separate the organization's funding method from the vendor's delivery method and validate changes independently.
- Configure approval criteria around current Melio plan behavior, including scheduler coverage and the prohibition on self-approval.
- Pilot several low-risk but meaningfully different transactions, then reconcile every state from bill intake through bank evidence.
- Assign owners and response targets for pending vendor details, declined approvals, failed collection, failed delivery, refunds, and sync differences.
Define the payables operating model and clean the vendor master
Map the complete lifecycle before configuration: vendor request, identity verification, duplicate search, bill receipt, coding, review, approval, payment scheduling, funding, delivery, accounting update, bank clearing, and exception closure. For every stage, name the preparer, decision owner, backup, evidence source, and escalation point. If an accounting platform is connected, specify whether vendor and bill changes should originate there or in Melio and which fields actually synchronize for that product.
Build a controlled vendor register rather than importing every contact indiscriminately. Compare full legal or business name, display name, mailing address, email, phone, tax documentation status, accounting identifier, prior payment history, and active state. Melio's current first-connection guidance scans for similar vendors and asks users to confirm links; skipped suggested matches may not be linkable later. Treat that initial matching screen as a master-data decision that deserves review, not a speed bump.
Distinguish a manually created vendor from a verified vendor in Melio's network. Network vendors can have a delivery preference controlled by the vendor, and the payor may be unable to change it. For manual records, require independent confirmation before adding or changing ACH, wire, virtual-card, or paper-check delivery details. The person receiving the change request should not be the only person validating and entering it, especially when the request arrives by email.
- Create a vendor-request form with business purpose, requester, authoritative accounting ID, expected payment type, and approver.
- Search Melio, the accounting file, bank history, and archived vendors for duplicates before creating a new record.
- Record who may create, edit, deactivate, merge, or request delivery details for each client or entity.
- Use a callback or known contact channel to verify sensitive vendor changes before the next payment is released.
Control bill intake, funding choices, and vendor delivery methods
Establish approved intake paths for bills created manually, uploaded from an invoice, received through a controlled inbox, or synchronized from accounting software. Staff should validate vendor, invoice number, dates, amount, currency, attachment, category or coding, duplicate indicators, and payment terms before saving. A scanned or imported invoice is source material, not proof that extracted fields are accurate. Statements, credits, quotes, and supporting documents should not silently become payable bills.
Separate how the organization funds a payment from how the vendor receives it. Current Melio materials describe funding by bank transfer, debit card, or eligible credit card, while delivery can include ACH or paper check and may include other methods based on vendor, plan, country, and eligibility. Record the permitted funding sources, card restrictions, fees, deduction timing, limits, and reconciliation account. Then document who controls the vendor's delivery method and how a change is verified.
Design for the pending-vendor state. Melio can request payment details from a vendor, and when a qualifying payment also needs approval the current help article says approval occurs before the request is sent. Assign an owner to monitor unanswered requests, expiring links, incomplete addresses, delivery changes, and scheduled payments waiting on vendor information. No one should bypass a pending state by copying bank details from an unverified message into a different vendor record.
- Publish a bill-intake checklist and reject documents that lack enough evidence to establish a valid obligation.
- Test manual creation, invoice upload, accounting sync, a credit, and a suspected duplicate before production cutover.
- Maintain an approved funding-source list with owner, limit, accounting mapping, fee policy, and backup method.
- Track vendor-detail requests by age, approver, validation status, expected delivery method, and next action.
Configure approvals and exception ownership around actual Melio behavior
Translate the signed authorization policy into Melio's current payment-approval criteria: amount, scheduler, vendor, and supported combinations. The current workflow guide states that a scheduler cannot approve a payment they scheduled. It also warns that amount- or vendor-only workflows apply to Accountants and Contributors unless Owner or Admin users or roles are explicitly selected under scheduler criteria. Test those boundaries with each relevant role rather than assuming title or seniority supplies a control.
Test conditions at and around thresholds, for named vendors, for every scheduler class, and with unavailable approvers. Include an Owner-scheduled payment, an Admin-scheduled payment, a new vendor, changed delivery details, a card-funded payment, a request for vendor details, and a declined payment. Because payments scheduled before a workflow is created are not captured by that new rule, define how in-flight items are reviewed whenever approval configuration changes.
Give each exception a named queue and response target. Pending approval belongs to an approver or backup; declined items return to the preparer with a reason; failed collection belongs to the funding owner; failed delivery triggers vendor-detail verification; duplicate or overpayment requires accounting and vendor recovery; refund states need bank confirmation; and sync differences belong to a reconciler. Closing the notification without closing the accounting and cash consequences is not resolution.
- Keep the signed authorization matrix, Melio workflow configuration, test cases, results, and effective date together.
- Require independent review when vendor creation, vendor-detail change, scheduling, and approval powers overlap.
- Document a backup approver and expiry for every temporary coverage arrangement or elevated permission.
- Review open exceptions daily during rollout and age them by financial risk rather than notification date alone.
Run a controlled pilot, reconcile it, and expand only after acceptance
Choose a pilot small enough to observe and broad enough to reveal design gaps. Include a recurring vendor, a new vendor, an invoice upload, a bill from accounting sync, two amount bands, a multi-person approval, a vendor-detail request, a changed delivery method, an ACH-funded payment, and another approved funding method if eligible. Use low-risk amounts and avoid making the first transaction time-critical.
For every pilot item, preserve the source bill, vendor match, entered fields, approval match, scheduler, approver decision, funding source, vendor delivery choice, deduction date, payment status, delivery evidence, accounting entry, and bank result. Reconcile by durable identifiers and amounts, not by vendor name alone. Investigate unexpected account mappings, duplicates, fees, date differences, pending states, and failed collection or delivery before adding volume.
Set acceptance gates and a rollback decision before cutover. Users must complete their role tests and account-security setup; vendor records must be deduplicated; approval workflows must cover the intended schedulers; funding methods must map correctly; exceptions must have owners; and pilot cash must reconcile. Expand by client, entity, team, or payment method only after the existing scope meets defined accuracy, timeliness, and control thresholds for an agreed period.
- Record a pre-cutover inventory of open bills, scheduled payments, vendor-detail requests, credits, and unresolved failures.
- Measure duplicate rate, coding corrections, approval aging, failed payments, delivery exceptions, sync errors, and clearing differences.
- Change one controlled configuration element at a time and preserve the before state, authorization, result, and reversal path.
- Schedule a post-pilot review with finance, client owners, approvers, accounting, and support responsibilities represented.
Vendor documentation and ALLMSP resources
- Melio: How to add a vendor
- Melio: Adding a vendor from Melio's network
- Melio: Add or edit a vendor delivery method
- Melio: Paying a vendor for the first time with ACH
- Melio: Vendors and card-funded payments
- Melio: Create a payment approval workflow
- Melio: Approval before requesting vendor details
- Melio Roles & Permissions
- Melio: What can you pay
- Melio: Download Audit Trail reports
- ALLMSP Melio Software Support category
- ALLMSP Software Support services
- ALLMSP Software Support articles
- ALLMSP CPA and Financial Firms IT
- Contact ALLMSP
Frequently Asked Questions
What should a Melio payables rollout configure first?
Start with the operating model: authoritative vendor and bill records, individual responsibilities, approval authority, funding ownership, vendor-delivery verification, accounting mappings, reconciliation, and exception queues. Configure Melio only after those decisions are documented and the current subscription and integration scope are confirmed.
How should a team prevent duplicate vendors in Melio?
Search Melio, the accounting system, payment history, and inactive records using legal name, display name, address, email, tax identity status, and accounting ID. Review suggested matches during initial sync carefully because current Melio guidance warns that skipped suggested vendor links may not be available later.
Is a Melio funding method the same as a vendor delivery method?
No. The funding method is how the payer supplies money, such as an eligible bank account, debit card, or credit card. The delivery method is how the vendor receives funds, such as ACH or check. Eligibility, fees, timing, and control ownership can differ for each side.
Can a verified Melio network vendor control its delivery method?
Yes. Current Melio guidance says verified network vendors may maintain their own delivery preference, which can prevent the payer from changing it. Confirm the vendor identity and current delivery state, preserve change notifications, and contact the vendor through a known channel when a correction is needed.
Should uploaded invoice data be accepted without review?
No. Treat extraction as a draft. Verify the vendor, invoice number, dates, amount, coding, attachment, terms, and duplicate indicators against the source. A statement, credit, quote, or reused invoice can otherwise enter the payables queue as an incorrect obligation.
Can the person scheduling a Melio payment approve it?
The current Melio payment-workflow guide says a user cannot approve a payment they scheduled. Test this behavior for every relevant role and backup path, and avoid shared accounts that would hide whether the scheduler and approver were actually different people.
Do amount-only Melio workflows automatically cover Owner and Admin payments?
Not necessarily. Current Melio guidance says workflows based only on amount or vendor apply to Accountants and Contributors unless Owner or Admin schedulers are explicitly included through scheduler criteria. Build and test a case for each high-authority scheduler you intend to cover.
What belongs in a Melio pilot?
Use low-risk examples that exercise a new and existing vendor, invoice upload, accounting-synced bill, approval thresholds, an Owner or Admin scheduler, vendor-detail request, multiple eligible funding or delivery paths, a decline, and reconciliation. Preserve evidence for each step and its accounting result.
Who should own a failed Melio payment?
Ownership depends on the failure stage. The funding owner handles collection problems, vendor management handles failed delivery and detail verification, accounting handles ledger and clearing consequences, and an operations owner coordinates status and evidence. The issue closes only after cash, vendor, Melio, and accounting states agree.
When is a Melio rollout ready to expand?
Expand only after vendor duplicates are controlled, role and approval tests pass, funding mappings are correct, vendor-delivery changes are verified, pilot transactions reconcile, and every open exception has an owner and deadline. Use measured acceptance thresholds instead of relying on a successful first payment.
