QuickBooks ® FedNow RfP Message Format Invoicing
The Best Solution for Payment Processing in QuickBooks®
Today Payments is an Authorized Reseller of Intuit offering a highly robust app that supports both QuickBooks’ desktop and online customers, provide merchants with the tools they need so they can focus more time on their customers and businesses, and less time on data entry."Our Integrated payment solutions can save a typical small business owner more than 180 hours each year"
See
the features
QuickBooks® ACH, Cards, FedNow and Real-Time Payments
- Payment processing for all QuickBooks desktop, Pro, Premier, Enterprise and also QBO QuickBooks Online Our software is designed for simplicity and ease-of-use.
- ~ Automate Account Receivable Collection
- ~ Automate Account Payable Payments
- ~ One-time and Recurring Debits / Credits
Secure QB Plugin payment processing through QuickBooks ® specializes in the origination of moving money electronically.
Ask about our special:
Request for Payments
To integrate a FedNow Request for Payment (RfP) message with QuickBooks Online (QBO) using SecureQBPlugin.com and maintain compliance with ISO 20022 XML, we’ll create an end-to-end message structure that spans from customer notification (via text, smartphone, and email) to backend processing through QBO, utilizing the SecureQBPlugin for API integration. Below is the structure, considering the different formats involved.
1. Overview
The FedNow RfP message will notify a payer (customer) of a payment request via texting, smartphone notification, and email, while simultaneously pushing the transaction data to QuickBooks Online (QBO) using the SecureQBPlugin for automated invoicing and bookkeeping. The final payment request is sent via the ISO 20022 XML standard for payment processing through the FedNow system.
2. General Structure of an RfP Message
- Payee Details
- Name
- Contact information (email, phone)
- Bank details (optional)
- Payment Request Details
- Amount to be paid
- Purpose or reason for payment
- Invoice number or reference number
- Due date
- Payer Details
- Name
- Payment method link (integrated with SecureQBPlugin to QuickBooks)
- SecureQBPlugin Integration
- Trigger event in QBO (generate or update invoice, record payment)
3. Communication Components
a. Texting (SMS)
A brief SMS message will inform the payer of the payment request:
[Payee Name] requests a payment of [$Amount] for [Purpose/Invoice #12345].
Please respond via: [Payment URL linked to SecureQBPlugin]
Due by: [MM/DD/YYYY]
Example:
John Doe requests a payment of $250 for Invoice #56789.
Pay securely using this link: https://secureqbplugin.com/pay12345
Due by: 10/05/2024.
b. Smartphone Notification
Smartphone notifications can include slightly more details with a direct payment action:
Notification Example:
Title: Payment Request from [Payee Name]
Body: You have a payment request of [$Amount] for [Purpose/Invoice #12345].
Due by: [MM/DD/YYYY].
Pay now via: [Payment URL linked to SecureQBPlugin]
The payment link will connect the payer to a payment portal that integrates with QuickBooks Online through SecureQBPlugin, allowing the invoice data to be automatically updated once the payment is made.
c. Email Message
Email offers more flexibility to include detailed information:
Subject: Payment Request from [Payee Name] – Invoice #[Invoice Number]
Body:
Dear [Payer Name],
You have received a payment request from [Payee Name] for the following details:
- Amount: [$Amount]
- Purpose: [Purpose or Service Description]
- Invoice Reference: #[Invoice Number]
- Due Date: [MM/DD/YYYY]
To complete your payment, please use the secure link below:
[Payment URL linked to SecureQBPlugin]
Upon payment, your QuickBooks invoice will be automatically updated.
Thank you,
[Payee Name]
Contact Info: [Payee Contact Information]
4. ISO 20022 XML Format for FedNow RfP Message
This is the formal message format following ISO 20022 XML standards, integrating with the FedNow system for real-time payment processing. Once the payment is triggered via SecureQBPlugin and confirmed, this XML message is sent to the FedNow system to complete the transaction.
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.013.001.07">
<ReqForPay>
<GrpHdr>
<MsgId>RFPM-98765</MsgId>
<CreDtTm>2024-10-01T10:00:00</CreDtTm>
<InitgPty>
<Nm>John Doe</Nm>
<Id>
<OrgId>
<Othr>
<Id>1234567890</Id>
</Othr>
</OrgId>
</Id>
</InitgPty>
</GrpHdr>
<PmtReqInf>
<ReqdExctnDt>2024-10-05</ReqdExctnDt>
<PmtInfId>INV-56789</PmtInfId>
<PmtMtd>TRF</PmtMtd>
<Amt>
<InstdAmt Ccy="USD">250.00</InstdAmt>
</Amt>
<Dbtr>
<Nm>Jane Smith</Nm>
<Acct>
<Id>
<Othr>
<Id>987654321</Id>
</Othr>
</Id>
</Acct>
</Dbtr>
<Cdtr>
<Nm>John Doe</Nm>
<PstlAdr>
<StrtNm>Main Street</StrtNm>
<BldgNb>123</BldgNb>
<TwnNm>Anytown</TwnNm>
<Ctry>US</Ctry>
</PstlAdr>
<Acct>
<Id>
<Othr>
<Id>123456789</Id>
</Othr>
</Id>
</Acct>
</Cdtr>
<RmtInf>
<Strd>
<RfrdDocInf>
<Tp>
<CdOrPrtry>
<Cd>INV</Cd>
</CdOrPrtry>
</Tp>
<Nb>56789</Nb>
</RfrdDocInf>
<RfrdDocAmt>
<DuePyblAmt Ccy="USD">250.00</DuePyblAmt>
</RfrdDocAmt>
</Strd>
</RmtInf>
</PmtReqInf>
</ReqForPay>
</Document>
Explanation of Key Elements:
- <GrpHdr>: Group header contains the message ID and creation date-time.
- <InitgPty>: The initiating party or payee (John Doe) requesting payment.
- <PmtReqInf>: Payment request information including payment method (TRF for transfer), amount, and payer (Jane Smith) details.
- <Cdtr> and <Dbtr>: Creditor (payee) and debtor (payer) details, including name and account information.
- <RmtInf>: Remittance information, such as the invoice reference (INV-56789) and the amount due ($250).
5. Integration with QuickBooks Online via SecureQBPlugin
To ensure that the RfP integrates into QuickBooks Online, follow these steps:
- Create a Payment Request: When the payment request is sent via text, smartphone, or email, use a SecureQBPlugin link that connects to the payment portal, which interacts with QuickBooks Online.
- Automated Invoice Creation/Update: SecureQBPlugin automates the process of creating or updating an invoice within QuickBooks once the payer clicks the payment link and completes the payment.
- Payment Recording: After the payment is processed via FedNow, QuickBooks Online automatically updates the invoice status as "Paid" via SecureQBPlugin’s integration.
- Data Sync: All payment and invoice information is synced between QuickBooks Online, SecureQBPlugin, and FedNow for real-time tracking.
Conclusion
This end-to-end process for a FedNow Request for Payment (RfP) integrates real-time payments with QuickBooks Online using SecureQBPlugin.com. The payer is notified via multiple channels, and the ISO 20022 XML format ensures compliance with FedNow standards for final payment processing. By integrating with QBO, all transactions are automatically recorded and tracked.
Call us, the .csv and or .xml Request for Payment (RfP) file you need while on your 1st phone call! We guarantee our reports work to your Bank and Credit Union. We were years ahead of competitors recognizing the benefits of RequestForPayment.com. We are not a Bank. Our function as a role as an "Accounting System" in Open Banking with Real-Time Payments to work with Billers to create the Request for Payment to upload the Biller's Bank online platform. U.S. Companies need help to learn the RfP message delivering their bank. Today Payments' ISO 20022 Payment Initiation (PAIN .013) show how to implement Create Real-Time Payments Request for Payment File up front delivering message from the Creditor (Payee) to it's bank. Most banks (FIs) will deliver the message Import and Batch files for their company depositors for both FedNow and Real-Time Payments (RtP). Once uploaded correctly, the Creditor's (Payee's) bank continuing through a "Payment Hub", will be the RtP Hub will be The Clearing House, with messaging to the Debtor's (Payer's) bank.
Our in-house QuickBooks payments experts are standing ready to help you make an informed decision to move your company's payment processing forward.
Pricing with our Request For Payment Professionals
1) Free ISO 20022 Request for Payment File Formats, for FedNow and Real-Time Payments (The Clearing House) .pdf for you manually create "Mandatory" (Mandatory data for completed file) fields, start at page 4, with "yellow" highlighting. $0.0 + No Support
2) We create .csv or .xml formatting using your Bank or Credit Union. Create Multiple Templates. Payer / Customer Routing Transit and Deposit Account Number may be required or Nickname, Alias to import with your bank. You can upload or "key data" into our software for File Creation of "Mandatory" general file.
Fees = $57 monthly, including Support Fees and Batch Fee, Monthly Fee, User Fee, Additional Payment Method on "Hosted Payment Page" (Request for file with an HTML link per transaction to "Hosted Payment Page" with ancillary payment methods of FedNow, RTP, ACH, Cards and many more!) + $.03 per Transaction + 1% percentage on gross dollar file,
3) We add a URI for each separate Payer transaction. Using URI, per transaction, will identify and reconcile your Accounts Receivable.
Fees Above 2) plus $29 monthly additional QuickBooks Online "QBO" formatting, and "Hosted Payment Page" and WYSIWYG
4) Above 3) plus Create "Total" (over 600 Mandatory, Conditional & Optional fields of all ISO 20022 Pain .013) Price on quote.
Start using our FedNow Real-Time Payments Bank Reconciliation:
Dynamic integrated with FedNow & Real-Time Payments (RtP) Bank Reconciliation: Accrual / Cash / QBO - Undeposited Funds