Guides

How to automate accounts payable in QuickBooks with Fynex

Automate accounts payable in QuickBooks: connect QuickBooks Online to Fynex, add suppliers as payees, approve one run, match each payment to its bill.

To automate accounts payable in QuickBooks with Fynex, connect QuickBooks Online, add your suppliers as payees, and let Fynex build a payment run from the open bills that are due. You approve the run once. Each supplier is paid over their bank rail, and each settled payment is matched back to the bill it paid.

This guide is for professional services firms (consultancies, accounting and legal practices, studios) that run their books in QuickBooks Online and still pay bills by hand. If you are still choosing an AP tool, start with the best AP automation software for QuickBooks. For the full sequence of what to automate first, see how to automate accounts payable.

How to automate AP in QuickBooks on Fynex: the steps

Seven steps take you from a QuickBooks bill list to a paid, matched run. Steps 1 to 3 happen once. Steps 4 to 7 repeat on every payment cycle.

  1. Create a Fynex account. The setup dock walks you through a first payee, a commission rule, an invoice and a test payment; you can explore in sandbox before verification. How to get started with Fynex covers every screen.
  2. Connect QuickBooks Online. Pick QuickBooks at sign-up, or open Settings → Integrations, choose QuickBooks and approve Fynex in Intuit’s OAuth screen. Fynex reads your bills, vendors, payments and customers from that point on.
  3. Add your suppliers as payees. Each vendor you pay becomes a payee: business name, email, tax ID, address, bank country, account number and routing or BIC. A wallet for the payee is set up automatically.
  4. Let Fynex build the payment run. Open bills that are due are grouped into one proposed run, each line showing the bill, the supplier, the amount and the account it pays from.
  5. Review and approve once. Remove a bill, hold a supplier or change a date. Then approve the run. Nothing moves before that.
  6. Fynex pays each bill over its rail. ACH or same-day ACH for US suppliers, wire where a supplier needs it, and the local scheme for suppliers abroad. The bill number travels as the payment reference.
  7. Each payment is matched to its bill. A settled payment is tied to the bill it paid and to the bank line it left on. Anything that fails or does not match surfaces as an exception.

What do you need before automating AP in QuickBooks?

You need three things in place: a QuickBooks Online company file with bills entered against vendors, bank details for each supplier you pay, and a funded Fynex balance to pay from. QuickBooks Desktop is not covered by this connection; if you are still on it, read QuickBooks Desktop is going away first.

What Fynex needsWhere it comes fromDocs reference
Bills, due dates, amountsQuickBooks Online, read by webhookQuickBooks integration
Supplier identity, tax ID, addressThe QuickBooks vendor, completed on the payeePayees
Supplier bank accountEntered once on the payee as a payout methodPayout methods
Money to pay fromYour Fynex USD, GBP or EUR balancePayouts
Proof of paymentPayout status and the matched bank lineReconciliation

Clean vendor records pay off here. The recurring suppliers (the thirty names behind most of your bills) are worth completing first.

How does Fynex decide which bills go into a run?

Fynex proposes; you decide. A run is built from open QuickBooks bills whose due date falls inside the cycle you pay on, weekly or twice a month for most firms. Each line carries its reasoning: why it is due now, which supplier it pays, and which balance it draws from.

Three checks run before a bill reaches the run:

  • Duplicate check. The same supplier, amount and reference close together is flagged, not paid twice.
  • Payee check. A supplier without an active bank account is held back with the reason shown.
  • Balance check. If the balance does not cover the run, Fynex shows the shortfall before you approve.

You can also ask in plain language in the Message Fynex box, for example “which bills are due before the 15th?”, and get the list with its reasoning. This is the agentic finance part: the configured workflow does the sorting, so you run the business, not the books.

What happens when a supplier payment fails?

A failed payment comes back to your balance and shows as an exception with a plain-language reason. Every supplier payment moves through the same statuses: pending, processing, then completed, failed or cancelled. A failure never disappears into the run total.

The usual causes are a closed account, a wrong routing number or a name mismatch at the receiving bank. Fix the payout method on the payee, then pay the bill again. Reusing the same idempotency key on a retry means a payment that did go through is never sent twice. Payout failure reasons lists the codes and what each one means.

If a supplier says the money never arrived but the status is completed, the payment reference and the settled date are on the payment. The supplier says the payment never arrived covers that conversation.

How do supplier payments land back in QuickBooks?

QuickBooks stays your book of record. Fynex reads the bill, pays it and ties the settled payment to that bill and to the bank line, so the link your accountant needs already exists at reconciliation.

This matters most for batch runs. A run paying forty bills leaves your bank as forty payments with forty references, not one debit someone has to split by hand. Fees post as fees, and a payment made outside the run is still picked up, so the bill does not sit open.

The result is a month-end where reconciliation is a confirmation, not an investigation. If your AP also runs on Xero, the same logic is covered in AP automation for Xero.

Can you run QuickBooks AP payments through the Fynex API?

Yes. The dashboard run and the API use the same payout engine, so a firm with its own AP tooling can push approved bills to Fynex and pay them programmatically.

The sequence has four calls:

  1. Create the supplier with POST /payments-api/v1/payees, carrying the display name, email and tax ID from the QuickBooks vendor.
  2. Register the bank account with POST /payments-api/v1/payees/{payee_id}/payout-methods.
  3. Pay the bill with POST /payees/{payee_id}/payouts, passing payoutMethodId, amount, a description holding the bill number, and an idempotencyKey.
  4. Confirm the result by polling GET /payouts/{id} until the status is completed, failed or cancelled. Payouts do not emit webhooks yet.

The description reaches the supplier’s bank statement as remittance information, up to 140 characters. Put the bill number there and the supplier can apply the payment without asking. Invoice fields that make matching work explains why the reference matters on both sides.

Where to go next

  • Payouts: how Fynex pays suppliers, contractors and partners from one approval.
  • Fynex for professional services: the full picture for consultancies and practices.
  • Payees and Payouts in the docs, if you run AP through the API.
  • How to start reconciliation for a small business: the next step once bills are paid through Fynex.
  • Pricing: 0.5% per payout ($1 minimum) plus $100 a month; card payments from 1.4%.
FAQ

Frequently asked questions

Keep QuickBooks as the book of record and automate the two stages it leaves manual: paying the bills and matching the payments back. Connect QuickBooks Online to Fynex with OAuth, add your suppliers as payees with their bank details, and let Fynex build a payment run from the open bills that are due. You approve the run once, each bill is paid over its rail, and each settled payment is matched to the bill it paid.
Not the capture or approval-routing part. Bills keep reaching QuickBooks the way they do today, through a capture tool or entered by hand. Fynex starts from the bill already in QuickBooks: it reads the bill and its vendor, pays it as part of an approved run, and matches the settled payment back to the bill and the bank line. That is the stage after payment, where most AP month-end work actually sits.
Through the QuickBooks Online connection, Fynex reads bills with their vendors, payments, invoices and customers. QuickBooks notifies Fynex by webhook when a record changes, and a scheduled resync catches anything a webhook missed. There is no CSV export and no nightly import job. The access token is stored encrypted, and you can revoke it from Fynex or from your Intuit account at any time.
No. Anything that moves money waits for an explicit approval. Fynex proposes the payment run, shows why each bill is in it (due date, supplier, amount, the account it pays from) and queues it for you or whoever holds approval rights. Nothing leaves until the run is approved, and every approval, change and payment is kept in the audit log with the reasoning behind it.
Fynex's public price for paying suppliers is 0.5% per payout, with a $1 minimum, plus $100 a month for the payouts plan, billed in USD. On a $50,000 supplier payment run, the payout fee is $250. Card payments you collect are 1.4% on US-issued cards plus $0.20 per authorization. You can explore the whole flow in the sandbox before your business is verified. Current details are on the pricing page.
Book a demo