Payment Schedules

Within the enterprise financial architecture, Payment Schedules serve as automated, rules-based templates that dynamically partition a total transaction amount into multiple scheduled installments over time. Once configured, these schedules can be assigned as default payment terms to customer or vendor master records, or applied manually to individual invoices to override standard terms.

By employing payment schedules, you eliminate manual calculation errors and ensure robust cash flow forecasting across both Accounts Receivable and Accounts Payable.

Accessing the Configuration

Navigate to either of the following paths depending on your immediate operational context:

• Accounts receivable > Payments > Payment schedule
• Accounts payable > Payments > Payment schedule

Allocation Methods

The system’s orchestration engine supports three distinct allocation methods to determine the composition of the installments.

1. Fixed Allocation

The Fixed method divides the total invoice amount into equal, predefined monetary installments. The system automatically calculates the required number of payments. If the total is not perfectly divisible by the fixed amount, the remaining fractional value is appended to the final payment.

• Primary Configuration: Requires an explicit Amount to be defined in the General section.
• Best Utilised For: Equipment leases or subscription services with rigid, predictable periodic billing.

2. Fixed Quantity Allocation

The Fixed Quantity method splits the total invoice amount into a specific, predefined number of installments. The system distributes the total equally across these installments, gracefully handling any minor rounding discrepancies by adjusting the final payment.

• Primary Configuration: Requires the Number of Payments.
• Best Utilised For: Project milestone billing, salary advances, or spreading vendor payments evenly across fiscal quarters.

3. Custom Allocation

The Custom method provides absolute, granular control over both the timing and the amount of each installment. You manually construct individual lines within the Payment lines grid, defining either explicit percentage allocations (which must total precisely 100%) or fixed monetary values.

• Primary Configuration: Requires lines to be added specifying whether the entry is a Percent or Amount, the corresponding value, and the Periods after due date.
• Best Utilised For: Complex construction contracts, software development retainers with progress-based billing, or phased marketing budgets.

Operational Parameters

When configuring a payment schedule, several parameters govern the behaviour of the allocation engine:

• Payment Per: Dictates the chronological interval between installments (e.g., Days, Months, Years).
• Currency: Payment schedules are strictly currency-specific. You must establish separate schedules for different operating currencies (e.g., one for USD, another for AED).
• Minimum/Maximum Constraints: You may optionally enforce boundaries on the calculated installment amounts using the Minimum and Maximum payment amount fields. For instance, declaring a minimum ensures no scheduled payment falls below a threshold (e.g., covering transaction processing fees), whilst a maximum safeguards against exceeding authorised credit limits. If a calculated installment breaches these constraints, the system will raise a validation exception during invoice posting.

Architectural Integration

Payment schedules are seamlessly integrated into the core financial subledgers:

• Accounts Receivable: Upon posting a sales invoice, the system evaluates the inherited payment schedule, generates the corresponding payment allocations.
• Accounts Payable: Similarly, upon posting a purchase invoice, the vendor's payment schedule orchestrates the creation of procurement liability installments, directly feeding into the enterprise's cash disbursement forecasting.