Payment Request

Back to Accounts

Overview

Below is a business-focused explanation of the Payment Request document in Dafater, written for operational and finance teams.


Payment Request – Business Overview

What the Payment Request is used for

The Payment Request is used to formally ask for a payment from a customer or to initiate a payment to a supplier or employee. It acts as a controlled, traceable way to request money before or alongside the actual receipt or disbursement of funds.

In simple terms, it answers the question:
“Who needs to pay, how much, for what, and by when?”

The Payment Request helps ensure that payments are: - Clearly communicated
- Properly authorized
- Linked to the correct business transaction
- Collected or paid on time


Prerequisites and setup requirements

Before using Payment Request, the following should be in place:

These ensure that every Payment Request is accurate and aligned with company policies.


Typical workflow and business process fit

A common business workflow using Payment Request looks like this:

  1. Payment need identified
    A payment is required—either to collect money from a customer or to pay a supplier or employee.

  2. Payment Request created
    The finance or operations team creates a Payment Request, specifying:

    • Who should pay or be paid
    • Amount and currency
    • Reason for payment
    • Due date and payment method
  3. Review and approval
    The Payment Request is reviewed to ensure correctness and compliance with company rules.

  4. Payment communication
    The request is shared with the payer (internally or externally), clearly stating payment expectations.

  5. Payment completion
    Once the payment is received or made, it is recorded and linked back to the Payment Request.

  6. Tracking and follow-up
    Outstanding Payment Requests can be monitored to avoid delays or missed payments.

This workflow improves cash flow visibility and reduces payment disputes.


Key business scenarios where Payment Request is essential

The Payment Request plays a critical role in many everyday business situations, including:

In all these cases, the Payment Request ensures transparency and accountability.


Important considerations for users

When working with Payment Request, users should keep the following in mind:

Used correctly, the Payment Request becomes a powerful tool for controlling payments, improving financial discipline, and strengthening trust with customers and suppliers.


In summary, the Payment Request in Dafater is a vital document for managing how and when money moves in and out of the business, providing clarity, control, and consistency across all payment-related activities.

Basic Information

Fields

Field Name Label Type Required Options Description
paymentrequesttype Payment Request Type Select Outward, Inward Defines whether payment is outgoing or incoming in Dafater.
transaction_date Transaction Date Date - Date when the payment request transaction is recorded.
naming_series Series Select ACC-PRQ-.YYYY.- Auto-generated numbering pattern for payment requests.
company Company Link Company Company responsible for this payment request.
modeofpayment Mode of Payment Link Mode of Payment Preferred payment method for completing the transaction.
party_type Party Type Link DocType Type of entity involved in the payment transaction.
party Party Dynamic Link party_type Specific customer, supplier, or entity involved.
party_name Party Name Data - Display name of the selected party.
reference_doctype Reference Doctype Link DocType Source document type linked to this payment request.
reference_name Reference Name Dynamic Link reference_doctype Specific reference document linked to this request.
grand_total Amount Currency currency Total amount requested for payment.
currency Transaction Currency Link Currency Currency used for this payment transaction.
isasubscription Is a Subscription Check - Indicates whether this payment is subscription-based.
outstanding_amount Outstanding Amount Currency partyaccountcurrency Remaining unpaid amount for the referenced transaction.
partyaccountcurrency Party Account Currency Link Currency Account currency used by the party.
subscription_plans Subscription Plans Table Subscription Plan Detail List of subscription plans included in this request.
bank_account Bank Account Link Bank Account Company bank account for receiving or sending payment.
bank Bank Link Bank Bank associated with the selected bank account.
bankaccountno Bank Account No Read Only - Bank account number for reference purposes.
account Account Read Only - Ledger account linked to the bank account.
iban IBAN Read Only - International Bank Account Number for payments.
branch_code Branch Code Read Only - Bank branch identifier code.
swift_number SWIFT Number Read Only - International SWIFT code for bank transfers.
cost_center Cost Center Link Cost Center Cost center to track financial impact.
project Project Link Project Project associated with this payment request.
print_format Print Format Select - Preferred print layout for payment request.
email_to To Data - Recipient email address for payment communication.
subject Subject Data - Email subject for payment request notification.
paymentgatewayaccount Payment Gateway Account Link Payment Gateway Account Configured gateway account used to process payment.
status Status Select , Draft, Requested, Initiated, Partially Paid, ... Current processing status of the payment request.
makesalesinvoice Make Sales Invoice Check - Automatically create sales invoice after successful payment.
message Message Text - Custom message sent with the payment request.
message_examples Message Examples HTML
Message Example
, , <p>Dear ...
Sample templates to help compose payment messages.
mute_email Mute Email Check - Disable automatic email notifications for this request.
payment_url payment_url Data URL Generated link for completing the payment online.
payment_gateway Payment Gateway Read Only - Payment gateway used to process the transaction.
payment_account Payment Account Read Only - Account where payment will be recorded.
payment_channel Payment Channel Select , Email, Phone Communication channel used to send payment request.
payment_order Payment Order Link Payment Order Linked payment order generated from this request.
amended_from Amended From Link Payment Request Original payment request being amended.
phone_number Phone Number Data - Recipient phone number for payment communication.

Child Tables

Subscription Plans (Subscription Plan Detail)

Field Name Label Type Required Options Description
plan Plan Link Subscription Plan Selected subscription plan applied to this Dafater subscription.
qty Quantity Int - Number of units for the selected subscription plan.

Permissions

Role Read Write Create Delete Submit Cancel
Accounts Manager
Accounts User
DocType Relationship Module
Bank Links to Accounts
Bank Account Links to Accounts
Company Links to Setup
Cost Center Links to Accounts
Currency Links to Geo
Mode of Payment Links to Accounts
Payment Gateway Account Links to Accounts
Payment Order Links to Accounts
Payment Request Links to Accounts
Project Links to Projects