Aging Request For Pay
How to Aging Request For Pay
Request for Payment, a new standard for digital invoicing facilitating real-time payments RTP ® and FedNow ® payments that are instant, final (irrevocable - "good funds") and secure.
Creating an Aging Request for
Pay (RfP) spreadsheet involves tracking and displaying the
status of payment requests over time. Typically, aging
reports break down outstanding payment requests into
different time periods, such as 30 days, 60 days, 90 days,
and beyond. Here's a simple guide on how to set up an Aging
RfP spreadsheet:
Spreadsheet Columns:
- Vendor/Requester Name:
- Identify the entity or
individual making the payment request.
- Invoice/Request Number:
- Unique identifier for
each payment request.
- Invoice/Request Date:
- Date when the payment
request was initiated.
- Due Date:
- The date by which the
payment is expected.
- Amount Requested:
- The total amount
requested for payment.
- Payment Date:
- Date when the payment
is made.
- Days Outstanding:
- Automatically
calculated field (Payment Date - Due Date) to
determine how many days the payment is overdue.
Spreadsheet Formulas:
- Days Outstanding
Formula:
- Create a formula in the
"Days Outstanding" column to calculate the number
of days the payment is overdue. Use a formula like:
=IF(ISBLANK([Payment Date]),
TODAY() - [Due Date], [Payment Date] - [Due Date]).
Aging Buckets:
- Current (0-30 days):
- Use conditional
formatting to highlight payments that are within
the current period.
- 30-60 Days:
- Apply conditional
formatting to highlight payments that are 30 to 60
days overdue.
- 60-90 Days:
- Apply conditional
formatting to highlight payments that are 60 to 90
days overdue.
- 90+ Days:
- Apply conditional
formatting to highlight payments that are more than
90 days overdue.
Summary Section:
- Total Amount
Outstanding:
- Sum the amounts for all
outstanding payment requests.
- Average Days
Outstanding:
- Calculate the average
number of days outstanding for all payment
requests.
Visualization:
- Graphs/Charts:
- Create charts to
visually represent the aging of payment requests
over time.
Regular Updates:
- Update Information:
- Regularly update the
spreadsheet with new payment requests, payment
dates, and any other relevant information.
Example Structure:
Vendor |
Invoice Number |
Invoice Date |
Due
Date |
Amount
Requested |
Payment Date |
Days
Outstanding |
ABC Inc |
INV001 |
2023-01-15 |
2023-02-15 |
$1,000.00 |
2023-02-20 |
=IF(ISBLANK(F2), TODAY() -
D2, F2 - D2) |
This structure allows you to
track and manage the aging of payment requests effectively.
Customize it based on your specific needs and the level of
detail you require for your financial tracking.
ACH and both FedNow Instant and Real-Time Payments Request for Payment
ISO 20022 XML Message Versions.
The versions that
NACHA and
The Clearing House Real-Time Payments system for the Response to the Request are pain.013 and pain.014
respectively. Predictability, that the U.S. Federal Reserve, via the
FedNow ® Instant Payments, will also use Request for Payment. The ACH, RTP® and FedNow ® versions are "Credit
Push Payments" instead of "Debit Pull.".
Activation Dynamic RfP Aging and Bank Reconciliation worksheets - only $49 annually
1. Worksheet Automatically Aging for Requests for Payments and Explanations
- Worksheet to determine "Reasons and Rejects Coding" readying for re-sent Payers.
- Use our solution yourself. Stop paying accountant's over $50 an hour. So EASY to USE.
- No "Color Cells to Match Transactions" (You're currently doing this. You won't coloring with our solution).
- One-Sheet for Aging Request for Payments
(Merge, Match and Clear over 100,000 transactions in less than 5 minutes!)
- Batch deposits displaying Bank Statements are not used anymore. Real-time Payments are displayed "by transaction".
- Make sure your Bank displaying "Daily FedNow and Real-time Payments" reporting for "Funds Sent and Received". (These banks have Great Reporting.)
Each day, thousands of businesses around the country are turning their transactions into profit with real-time payment solutions like ours.