SEPA Payments Directly from QuickBooks Online
European businesses rely on SEPA for supplier payments and customer collections, but QuickBooks Online has no native SEPA file generation. FOR:LEDGER fills the gap — generating ISO 20022 compliant SEPA Credit Transfer (SCT) files for outgoing payments and SEPA Direct Debit (SDD) files for incoming collections, directly from your QuickBooks bills and invoices. Upload the XML to your bank, and let FOR:LEDGER reconcile the results.
SEPA Payment Features
SEPA Credit Transfer (SCT)
Select open bills in QuickBooks and generate a SEPA Credit Transfer XML file ready to upload to your bank. FOR:LEDGER includes the vendor IBAN, BIC, payment reference, and amount — all pulled automatically from your QuickBooks vendor records and open bills.
SEPA Direct Debit (SDD)
Collect payments from customers by generating SEPA Direct Debit files from open QuickBooks invoices. FOR:LEDGER manages mandate references, sequence types (FRST, RCUR, FNAL), and creditor identifiers required by the SDD scheme.
ISO 20022 XML Compliance
All generated files conform to the ISO 20022 pain.001 (SCT) and pain.008 (SDD) XML schemas. These are the standard formats accepted by every SEPA-participating bank across 36 European countries.
Batch Processing
Process dozens or hundreds of payments in a single batch. Select multiple bills by due date, vendor, or amount — FOR:LEDGER generates one consolidated XML file containing all payment instructions, reducing bank upload overhead and transaction fees.
Bank Integration
Download the generated XML and upload it to your bank's payment portal. FOR:LEDGER records the bill payments in QuickBooks automatically once the batch is created, keeping your books in sync with your bank activity.
How SEPA Credit Transfers work with FOR:LEDGER
The SEPA Credit Transfer workflow starts in your QuickBooks bill list. You select the bills you want to pay — filtering by due date, vendor, currency, or amount. FOR:LEDGER validates that each vendor has an IBAN on file (pulling it from the vendor record in QuickBooks or from your FOR:LEDGER vendor settings) and flags any missing banking details before generating the file.
Once validated, FOR:LEDGER generates a pain.001.001.03 XML file containing all payment instructions. Each payment includes the debtor IBAN (your company bank account), the creditor IBAN (the vendor), the amount, the payment reference, and the requested execution date. You download the file, upload it to your bank, and the payments are processed. FOR:LEDGER then creates the corresponding Bill Payment transactions in QuickBooks, closing the open bills and keeping your accounts payable accurate.
SEPA Direct Debit for customer collections
For businesses that collect payments from customers — subscription services, utilities, membership organizations — SEPA Direct Debit automates the collection process. FOR:LEDGER generates pain.008.001.02 XML files from your open QuickBooks invoices, including all the fields required by the SDD scheme: your SEPA Creditor Identifier, the customer's mandate reference, the mandate signature date, the sequence type, and the collection amount.
The system handles both Core (B2C) and B2B SDD schemes, and correctly manages sequence types: FRST for first collections under a new mandate, RCUR for recurring collections, and FNAL for final collections. Once the direct debit batch is submitted to your bank and collections are confirmed, FOR:LEDGER records the payments in QuickBooks against the corresponding invoices.
FAQ
Does QuickBooks Online support SEPA payments natively?
No. QuickBooks Online does not have built-in SEPA file generation. FOR:LEDGER adds this capability by reading your open bills and invoices, generating ISO 20022 compliant XML files, and recording the payments back in QuickBooks after bank processing.
Which banks accept the files generated by FOR:LEDGER?
The pain.001 (SCT) and pain.008 (SDD) XML formats are standardized across all 36 SEPA-participating countries. Any bank that supports SEPA file uploads will accept the files generated by FOR:LEDGER. This includes major banks like Deutsche Bank, BNP Paribas, UniCredit, ING, Santander, and thousands more.
How does FOR:LEDGER handle vendors without IBAN information?
Before generating the XML file, FOR:LEDGER validates all selected payments. If a vendor is missing an IBAN or BIC, the system flags it and excludes that payment from the batch. You can add the missing information in QuickBooks or FOR:LEDGER and regenerate the file.
Can I schedule recurring SEPA payments?
FOR:LEDGER generates SEPA files on demand based on your open bills and invoices. For recurring collections via SDD, the system manages mandate sequence types (FRST, RCUR, FNAL) automatically, so you simply select the invoices to collect and the system handles the rest.