--- title: "Pay Contractors & Sellers in One Batch, US & UK | Fynex" description: "Pay 50 contractors or 5,000 sellers in one run — by ACH in the US, Faster Payments in the UK — with every payout matched back to your books." url: "/features/payouts" --- Fynex is an AI-native finance operations platform — agentic finance — that automates and orchestrates end-to-end financial workflows for businesses. This page covers payouts: scheduling, approving and settling money out to sellers, contractors, subcontractors and carriers. Fynex works alongside Stripe, Wise, Payoneer and Airwallex rather than replacing them. This page is relevant when money goes out to many payees on a schedule, with approvals, and every payout has to land in the accounting system as it happens. # Pay everyone you owe, *in one run* Pay 50 contractors or 5,000 sellers in one run, by ACH in the US or Faster Payments in the UK. *Payouts.* ## Paying people out shouldn't eat your Fridays Every payout run is manual: work out each share in a spreadsheet, log into a bank, key in each transfer, send, then reconcile what went where. One transfer keyed after the cut-off, and someone waits days longer to get paid. Fynex runs the whole payout chain. It verifies the work, applies your contract terms, splits the revenue and pays by ACH or Faster Payments — every night, with no one on your team touching it. ## From who's owed what to money in their account Three steps from setup to settled — then it runs itself. 1. **Set the rule** — Set a standing share per payee — seller, contractor or partner — just once. Change it any time with no code, and it applies to every run from then on. 2. **Pick the rail and the timing** — US payees go by ACH, or same-day ACH when the money is due today; UK payees go by Faster Payments, in minutes. Fynex times each payout to its deadline, so nobody waits on a missed cut-off. 3. **Pays and reconciles** — Money goes out nightly on schedule, to every payee you owe. Each payout books itself back to your accounting behind the run, so the ledger always matches. ## The payout chain, handled From the share each party is owed to the rail it goes out on — run for you, every night. - **Multi-party payouts, one run** — Pay many parties from one payment in a single run — US payees by ACH, UK payees by Faster Payments. - **Same day when it's due today** — Standard ACH for the scheduled run, same-day ACH when a payment is due today, Faster Payments for UK payees — picked automatically. - **Pay by rule, on schedule** — Set a standing rule per payee. Payouts run every night on schedule, with no work from you. - **Verify before you pay** — Confirm the work and your contract terms before money moves, so nothing leaks on the way out. ## Send it from your own system, exactly once Payment runs are the job nobody wants: an evening of transfers, a bank portal that times out halfway, and a duplicate you find a month later. ### One call, whichever rail fits A US account to ACH, a UK account to Faster Payments — chosen from the account the payee registered. See [Payouts](https://docs.fynex.ai/payments-api/v1/docs/payouts). ```http POST /payments-api/v1/payouts { "walletId": 15, "payoutMethodId": 501, "currencyCode": "GBP", "amount": "420.00" } ``` ### Register where each payee gets paid Bank details are held once against the payee and reused, rather than re-entered on every run. See [Payout methods](https://docs.fynex.ai/payments-api/v1/docs/payout-methods). ```http POST /payments-api/v1/payees/101 /payout-methods { "currency": "GBP", "bankAccountType": "uk_local", "accountNumber": "12345678", "sortCode": "12-34-56" } ``` ### Never pay twice on a retry A key on the send means a timeout is safe to repeat — the second call replays the first result. See [Idempotency](https://docs.fynex.ai/payments-api/v1/docs/idempotency). ```http POST /payments-api/v1/payouts { "idempotencyKey": "a81e6e95-efe2-4e2c-…" } → 200 replay of the original ``` ### Know why one failed, not that some did A failed send reports its own reason on the payout record, so a bad account is one line to fix. See [Errors](https://docs.fynex.ai/payments-api/v1/docs/errors). ```http GET /payments-api/v1/payouts/9001 → { "status": "failed", "failureCode": "…", "failureMessage": "…" } ``` ## Tonight's payout run, before you wake up Fynex works out each share, picks the rail and pays — then reconciles behind it. You see the run, not the work. | | | |---|---| | Pending payouts | $89,500 | | Payees this run | 42 | | Rails | ACH · Faster Payments | | Same-day when due | Auto | ## What it weighs before a payout goes out Before a payout leaves, Fynex weighs the rail, the payee and the run, so the money goes to the right account, on time, and never twice. The checks run on every payout, and your Friday stays yours. - Picks standard or same-day ACH by the payment's deadline - Validates the account number and routing number or sort code before a payout is queued - Screens every payee against sanctions lists - Detects and blocks duplicate payments automatically ## The same job, with the leaks closed Point tools solve part of it. Fynex runs the whole thing on one platform. | The problem | Other platforms (Your bank + a payout tool) | Fynex | |---|---|---| | Pay many parties from one payment | Single transfers, worked out by hand. | Multi-party payouts routed automatically. | | Pay on the payee's deadline | Keyed late, so the payee waits days. | Same-day ACH when it's due today. | | Pay US and UK payees | A different bank portal for each. | ACH for US payees, Faster Payments for UK. | | Tie the payout to the work | Paid first, reconciled later. | Verify work and terms before money moves. | ## The rest of the job, also handled Beyond the headline job, every account gets the whole platform behind it. - **ACH & Faster Payments** — [ACH and same-day ACH in the US, Faster Payments in the UK](https://docs.fynex.ai/payments-api/v1/docs/payout-methods). - **Multi-currency wallets** — Hold and move a [balance per currency](https://docs.fynex.ai/payments-api/v1/docs/wallets) before you pay out. - **Scheduled runs** — Payouts go every night, on your schedule. - **Contract terms captured** — Retention, milestones and discounts applied before payout. - **Reconciliation built in** — Every payout matched and booked as it moves. - **Webhooks & API** — Trigger and track payouts with [webhooks and the API](https://docs.fynex.ai/payments-api/v1/docs/webhooks). ## The rails out, and the books they reconcile to ACH and Faster Payments for the money out, your accounting kept in sync behind it. 100+ integrations. **Accounting stack** — Every payment, fee and payout lands in your ledger, coded and reconciled — nobody re-keys it. QuickBooks, Xero, FreshBooks, Sage, NetSuite, Wave. **Banks & business accounts** — We read your balances and pay out of whichever account is cheapest — no bank portals, no copy-paste. Revolut, Wise, Mercury, Brex, Airwallex, Ramp. **Invoicing & contracts** — The contract sets the terms; we hold you to them — discounts, retention, caps, all applied before money moves. DocuSign, PandaDoc, Dropbox Sign, Adobe Acrobat Sign, BILL, Invoice Ninja. **Payroll & contractors** — Everyone you owe who isn't a supplier — crew, contractors, freelancers, in whatever currency they bank in. Gusto, Deel, Rippling, Remote, ADP, Justworks. **Spend & expenses** — Cards, receipts and subscriptions on the cost side of the same ledger. Expensify, Pleo, Soldo, Payhawk, Spendesk, Navan. **Spreadsheets & docs** — The spreadsheet you rebuild every month — we fill it, or replace it. Your call. Google Sheets, Microsoft Excel, Notion, Airtable, Google Drive, Dropbox. Your customers pay however they already pay — Visa, Mastercard, American Express, Apple Pay, Google Pay, ACH, bank transfer and open banking — through the provider you run today or through us. ## Find what you're leaking, for free Send us your setup. We run a free diagnostic and show you what your payment stack costs you today. > One recent diagnostic found $2M in hidden fees across 10 processors for a proptech client. ## Questions, answered ### Where can Fynex pay people? In the US and the UK. Fynex pays US payees by ACH, in dollars, and UK payees by Faster Payments, in pounds. Your customers can pay you by card from anywhere; the people you pay out to need a US or UK bank account. You don't log into a bank or key in transfers one by one. ### What rails do you support for payouts? ACH and same-day ACH for US payees, and Faster Payments for UK payees — see [payouts in the API reference](https://docs.fynex.ai/payments-api/v1/docs/payouts). Fynex picks standard or same-day ACH automatically, by the payment's deadline. ### Can I pay multiple parties from one payment? Yes. Fynex [splits one incoming payment](https://docs.fynex.ai/payments-api/v1/docs/splits) across several parties — sellers, contractors, partners — and pays each their share in a single run, with the division set by rule. ### Can I schedule payouts or pay by rule? Yes. Set a standing rule per payee and Fynex runs payouts every night on schedule, with no work from you. You can also trigger a run on demand via the API. ### How does Fynex keep payout costs down? Payouts go out in one run instead of a transfer each, and the work, the contract terms and duplicates are checked before money moves — so nothing is paid twice or overpaid. The savings show up on every run, with no new headcount or tools. ### Can I verify the work before a payout goes out? Yes. Fynex can confirm the work was delivered and apply your contract terms — retention, milestone gates, rate cards — before any money moves. Accountability sits inside the payment, not chased after the money's gone. ## Pay everyone you owe. *On time, every night* --- The AI finance layer for platforms and operators. It runs the money chain and keeps more of it in your business. One platform instead of a dozen. [Fynex on LinkedIn](https://www.linkedin.com/company/fynexai/) · [Fynex on X](https://x.com/FynexTeam) · [Fynex on GitHub](https://github.com/fynex-ai) · [Fynex on YouTube](https://www.youtube.com/@Fynex-AI) · [Fynex on Instagram](https://www.instagram.com/fynexteam/) © 2026 Fynex Group LLC