Payments

Pay any PO at interbank. Same business day.

Tap Pay on a purchase order. The FX rate locks at issuance so the margin you quoted on survives the 30-to-60-day gap. The supplier receives funds same business day on major corridors. The PO reconciles back to the workspace and to your accounting tool. No wire portals, no $30 fees, no 5-day settlement.

TuringDock
PO SI-2026-00031
Acme Plastics (Frankfurt)EUR
1000 × CAP-100 @ €0.18€180.00
5000 × RES-100 @ €0.04€200.00
Total€380.00
FX rate locked at PO issue
1 CAD = 0.6792 EURinterbank
PAYMENT STATUSlive
  1. 14:02Issued from PO
  2. 14:02FX locked at 0.6792
  3. 14:03Beneficiary verified
  4. Settled with Acme
Source debitCAD 559.48
Destination creditEUR 380.00
Bank-equivalent costCAD 575.83

How it works

FX rate locks the moment you issue the PO

Legacy wires expose you to FX drift between quote, PO issuance, and supplier payment. A 2.5% move over 60 days, on a $50k USD supplier order, eats $1,250 of the margin you already booked. With the rail, the rate snaps at the moment you tap Issue on the PO. The cost in CAD is frozen. The supplier still gets paid in their currency at the rate you locked.

The locked rate is shown on the PO record + on the supplier's node in your canvas. If the spot rate drifts in your favor between lock and pay, that's your win to keep. If it drifts against you, you're protected.

Same-business-day settlement on the corridors you actually use

CAD source, plus USD, EUR, GBP, JPY, AUD, MXN, CHF, HKD, SGD as destination. Funds land in the supplier's bank account on the same business day for orders submitted before the corridor's cut-off (typically 11am ET for European corridors, 1pm ET for USD, 9pm ET for APAC same-day; UI shows the live cut-off when you press Pay).

The supplier doesn't onboard, doesn't install an app, and doesn't need to know anything about TuringDock. Funds arrive via their normal banking infrastructure with our payment reference (typically the PO number) in the memo line. From their side it's just an inbound wire that landed on time.

KYB onboarding in one sitting; supplier beneficiary added once

The first time you turn on Payments, the workspace admin completes a one-time KYB flow: legal name, business address, jurisdiction, directors, source-of-funds, and a CAD-denominated funding account we'll debit. Standard Canadian SMB profile, typically approved within a business day.

Each supplier you want to pay gets a beneficiary record once: bank name, IBAN or local account number, SWIFT/BIC, address. Capture it from the supplier's last invoice or the supplier modal, save once, reuse for every future PO. Bulk-import is available for the dozens-of-suppliers move.

Reconciliation back to the PO and to your books

Payment status streams back live: Pending → Settled → Reconciled. The PO record flips to paid the moment funds confirm. The Money page's AP aging recalculates. Alan posts a one-liner in your Slack with the actual settlement timestamp and the bank-equivalent cost you saved.

If accounting is connected, the supplier payment pushes to QuickBooks or Xero against the matching bill, including the exact FX rate used. Your bookkeeper opens QuickBooks Friday and everything is already where it should be. No reconciliation queue to clear.

Why this is the new age of MRP

Legacy flow: open the MRP, copy the supplier's bank details, switch to your bank's wire portal, paste them in, type the amount, accept whatever rate the bank quotes you, pay the $30 fee, wait 3-5 days, hope it arrives, paste the confirmation back into the MRP, and re-key everything into QuickBooks on Friday. The MRP never sees the money.

Payment rail: open the PO, tap Pay, confirm. The supplier is paid same day at the rate locked when you issued the order, the PO marks paid, the bill posts to QuickBooks, and Alan tells you in Slack. The MRP and the rail are one motion.

Build what's next. Leave the MRPing, and the wire-portal grind, to our AI.

Build what's next.

Leave the MRPing to our AI. Sign up free, set your shop up in an afternoon.

Get started for free

Common questions

What currencies are supported at launch?
CAD as the source. USD, EUR, GBP, JPY, AUD, MXN, CHF, HKD, SGD as destinations at launch. If a supplier you pay is in a corridor outside this list, talk to us at hello@turingdock.com so we can prioritize. New corridors typically take two weeks once we open the conversation with our infrastructure partner.
When exactly does the FX rate lock, and what rate do I get?
The rate locks the moment you tap Issue on the PO (not at payment time). The rate is the interbank mid-market rate at the moment of lock, with no markup added by TuringDock. Between lock and payment we hold the FX exposure; you pay the CAD amount frozen at lock. If FX moves in your favor between lock and pay, the gain is yours; if it moves against you, you're protected.
Does the supplier need to install or sign up for anything?
No. Funds arrive at the supplier via their normal banking infrastructure as an inbound wire. From the supplier's perspective, nothing changes about how they receive payment: they see a deposit hit their account with our payment reference (typically the PO number) in the memo line. The supplier doesn't know or need to know about TuringDock or the rail.
What are the cut-off times for same-day settlement?
Typical cut-offs: 11am ET for European corridors (EUR, GBP, CHF), 1pm ET for USD, 9pm ET for APAC same-day (JPY, HKD, SGD, AUD). Orders submitted after the cut-off settle next business day. The Pay button in the UI surfaces the live cut-off for the destination corridor so you know before confirming.
What does KYB onboarding look like for my company?
One-time flow at the start. Workspace admin provides: legal name, business address, jurisdiction of incorporation, directors + their basic identity info, beneficial owners over 25%, source of funds, and the CAD bank account we'll debit from. Standard Canadian SMB profile. Most workspaces are approved within one business day. After approval the funding account stays attached; you don't re-do KYB for each payment.
How do I add a supplier so I can pay them?
Open the supplier's node in the canvas, tap “Add bank details for payment.” Capture bank name, account number (or IBAN), SWIFT/BIC, beneficiary address. Verified on first payment; reused for every PO to that supplier from then on. Bulk import from CSV or from your existing supplier directory is available for getting started.
How does reconciliation work back to my books?
Three layers, all automatic. (1) The PO record flips from issued to paid the moment funds confirm. (2) The Money page's AP aging recalculates. (3) If accounting is connected, the supplier payment pushes to QuickBooks or Xero against the matching bill with the exact FX rate. Alan also posts a one-liner in your Slack with settlement timestamp and bank-equivalent savings. No queue to clear on Friday.
What happens if a payment fails or is delayed?
Failures (typically beneficiary detail mismatches or KYB-side flags) are surfaced inline on the PO with the upstream error verbatim and a one-tap retry once the issue is fixed. Funds never leave your account on a failed payment. Delays past expected settlement (rare on supported corridors) trigger an Alan DM and a Money-page banner so you and the supplier aren't in the dark.
Is the rail live?
Currently in private preview with the first cohort of Canadian manufacturers. The savings-panel + Enroll-in-beta CTA on every supplier inside the workspace records your interest; when your workspace is enrolled, the “Enroll in beta” button on supplier nodes morphs to “Pay this PO” in the exact same spot. To join the first cohort, reach out at hello@turingdock.com.
Is TuringDock a bank?
No. The payment rail runs on a licensed infrastructure partner with the necessary banking relationships and regulatory licenses in Canada, the US, and supplier-side jurisdictions. TuringDock owns the MRP layer, the rate-lock UX, the per-PO integration, and the reconciliation back into your workspace and books; the actual money movement is provided by partners. Structurally similar to how Wise or Stripe operate.

Last updated 2026-05-26 (private preview with the first cohort; reach out to join)